001-boundaries-and-authority
The product boundary, the component owners, and the separation of authority
Lifecycle approvedImplementation n-aVerification unknownQualification unknown
What this product is, what it is not, and who owns each capability it depends on. Fixes the claim vocabulary (specified / implemented / tested / released), the two interaction modes and which one is built first, the rule that separates an authority change from an implementation change, and the reuse disposition for every shared component this repository would otherwise reimplement. Owns the product half of the constitution and the two founding records under docs/. It owns no code.
Read the full pinned specification ↗Relationships
depends on
depended on by
- 002-environment-lifecycle
- 003-work-and-run-semantics
- 004-execution-adapter
- 005-acceptance-and-evidence
- 006-command-surface
- 007-family-envelope
- 008-harness-delivery
- 009-governance-producer
- 010-profile-unresolved-claims
- 011-init-bootstrap-spec
- 012-remote-desired-state
- 013-supervised-wire-witness
- 015-managed-session-evidence
- 016-bounded-active-specs
- 017-ai-review-diff-cap
- 023-contained-commit-walk
- 024-review-budget-and-ratification
- 027-observation-and-proposals
- 028-agent-attribution-is-refused
Claimed units
- establishes
{ "anchor": "vi-a-declaration-of-completion-is-not-an-acceptance", "file": "standards/spec/constitution.md", "kind": "section" } - establishes
{ "anchor": "vii-a-candidate-cannot-enlarge-its-own-authority", "file": "standards/spec/constitution.md", "kind": "section" } - establishes
{ "anchor": "viii-name-the-enforcement-or-do-not-claim-the-protection", "file": "standards/spec/constitution.md", "kind": "section" } - establishes
{ "anchor": "ix-outcomes-are-recorded-outside-the-child-and-recovery-reconciles-before-it-repeats", "file": "standards/spec/constitution.md", "kind": "section" } - establishes
{ "anchor": "x-intent-execution-verification-and-acceptance-are-separate-records", "file": "standards/spec/constitution.md", "kind": "section" } - establishes
{ "anchor": "xi-a-capability-is-declared-and-qualified-never-assumed", "file": "standards/spec/constitution.md", "kind": "section" } - establishes
{ "anchor": "xii-public-claims-are-graded", "file": "standards/spec/constitution.md", "kind": "section" } - establishes
{ "anchor": "xiii-the-local-product-owes-nothing-to-a-hosted-one", "file": "standards/spec/constitution.md", "kind": "section" } - establishes
{ "kind": "file", "path": "docs/decisions/00-founding-decisions.md" } - establishes
{ "kind": "file", "path": "scripts/check-authored-content.sh" }
Source headings
- 001: The product boundary, the component owners, and the separation of authority
- 1. Purpose
- 2. Territory
- 3. Behavior
- 3.1 What this product owns
- 3.2 What this product does not own, and who does
- 3.3 The claim vocabulary
- 3.4 The two interaction modes
- 3.5 An authority change is not an implementation change
- 3.6 Authored-content rules that hold repository-wide
- 3.7 Observable negative cases
- 3.8 The reuse dispositions, the archive, the slice, and the later interfaces
- Component owners, and what this product's relationship actually is
- The dispositions, stated as section 3.2 requires
- 3.9 What the archive is used for, and what it is not
- 3.10 The two interaction modes, drawn out
- 3.11 The bounded first vertical slice
- The slice's acceptance, stated as refusals
- What the slice deliberately does not prove
- 3.12 Interfaces this product would publish later
- 3.13 The producer pin is stated once, and each adoption is a ledger entry
- 4. Out of scope
- 5. Resolved decisions
- Verification
Frozen anchors
No frozen anchors declared.