docs: product horizons, approval policies and KAgent integration spec #13
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: ochenstarik/server-monitor-manager#13
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/product-horizons-and-integration"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Adopt the reviewed parts of the external vision document as repository specifications, and record the work-order gates that keep unimplemented subsystems from starting before their prerequisites are closed.
New documents
docs/product-horizons.md— four horizons with hard exit criteria. A horizon closes as a whole; a criterion expressed in terms of actual system behaviour closes only by measurement on real topology, and green CI does not substitute for it. Includes the table of what was adopted from the vision document, what was deferred, and why.docs/approval-policies.md— nine approval modes over today's binary confirmation, mapped onto the existingProvisioningJob, TTL and execution-grant mechanisms. Records which operations may never fall belowoperator_reauth, and that CA rotation may never fall belowtwo_person.docs/integration-kagent.md— capability model split into read, request and never-grantable, where never-grantable means absent from the code path rather than disabled by configuration. Untrusted-executor invariant for KAgent Worker.SO_PEERCREDrequired on the discovery socket, reusing the measures already implemented inProvisioningHelperServer. API designed against entities that exist today.Updated
docs/security-model.md— untrusted executors on a Node; the public web-surface decision that must be recorded before that work starts; never-grantable capabilities.docs/roadmap.md— stages 14-18 for the adopted scope, pinned to horizons.README.md— links, with an explicit statement that the new documents describe target behaviour and that nothing in them is implemented.Documentation only; no code, tests or workflows are touched.
🤖 Generated with Claude Code