canon: Delegating Responsibility Over a Project (E0010 synthesis)

[git-repo-auth]

What

Adds one Tier-2 canon document: canon/delegating-responsibility-over-a-project.md, a synthesis answering the captain's question — "What does it look like to delegate responsibility over a project?"

It weaves this week's established patterns into one frame, attributed to Epoch 10 (Flight Crew):

• Stewardship charter — what it grants (authority exercised, no twenty-questions) vs. withholds (captain's authorial voice, irreversible production action, direction/pivots); the allowlist + tripwire machinery.
• The gated loop as the trust mechanism — explore → plan → execute → validate → promote; clearing the gates is the clearance; validation's context break; the captain's 2026-07-09 directive made literal.
• Clearance scales with maturity — odd/maturity.md; ARS PR Fix KICKOFF.md with corrected process from attempt-001 learnings #10 non-blocking reconciliation; reversibility is the test; block only on irreversibility.
• Responsibility, not tasks — the recorder as black box, the debrief as legislator; recording-as-landing; merge attribution.
• The debrief — three failure modes this week (over-halting reversible work, silent substitution, orchestration the captain couldn't run cleanly) and the policies they became. No blame.

Grounding

Every pattern cites an existing artifact: canon/bootstrap/flight-deck-model.md, canon/bootstrap/boarding-pass.md, canon/bootstrap/model-operating-contract.md, odd/maturity.md, canon/principles/irreversibility-is-the-real-cost.md, canon/the-directors-chair-vision.md, docs/appendices/epoch-10.md. No invented sources.

Governance notes

• Synthesis of existing E0009/E0010 canon; it does not shift operator/agent posture on its own, so no epoch bump (same disposition as the director's-chair-vision release note). Version/changelog left to the captain's discretion.
• Legibility standard applied: descriptive title, one-paragraph blockquote, ## Summary, scan-test headers, schema-compliant frontmatter (derives_from a quoted comma-separated string).
• Landed under pre-production authorship — gates cleared as clearance. Assigned to @klappy for visibility; review not requested.

🦦 Crew, not clone.

---

Note

Low Risk
Adds one markdown canon synthesis with no runtime, auth, or data-path changes; governance posture is explicitly described as synthesis-only with contract precedence unchanged.

Overview
Adds Tier-2 canon canon/delegating-responsibility-over-a-project.md, a single synthesis that answers how to delegate responsibility over a project (not task lists) under E0010 Flight Crew.

The doc ties existing governance into one frame: stewardship charters (grant vs withhold, allowlist/tripwire), oddkit gates as the trust mechanism (clearing gates = clearance), maturity-scaled rigor and reversibility (including ARS non-blocking reconciliation), and recorder + debrief (failures → canon). It also records three recent failure modes and the policies they produced, with explicit boundaries (repo charters stay binding; operating contract wins on conflict).

No code, config, or epoch bump—documentation only, citing listed bootstrap/odd/principle sources.

^{Reviewed by Cursor Bugbot for commit b101b8e. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

Canon Quality — P0010 Retrieval-Readiness ⚠️

Soft report for klappy://canon/constraints/retrieval-disclosure-contract. 689 files scanned. Never blocks — informational until the corpus is ready to enforce.

• Blocking-class findings: 15 (structural fields the contract would filter on)
• Warnings: 0 (kind resolves to unknown)
• Informational: 13 (exempt templates/archive/drafts)

Kind distribution: {'essays': 51, 'canon': 235, 'apocrypha': 38, 'docs': 300, 'journals': 59, 'unknown': 6}
Kind source: {'path': 557, 'frontmatter': 126, 'none': 6} (frontmatter-primary, path-secondary)
Default-include visibility: 586 visible, 103 hidden (journals/apocrypha/unknown)

By rule: {'audience-invalid': 2, 'exposure-missing': 5, 'tier-missing': 5, 'tier-invalid': 7, 'fm-missing': 3, 'kind-unresolvable': 6}

These are not schema violations (see the Frontmatter Schema job for those on writings/). They are corpus-readiness signals for the retrieval contract: invalid/missing audience, exposure, tier, and docs whose kind cannot be resolved. Fix in a corpus-cleanup PR before the contract flips to enforcing. See the retrieval-readiness-findings artifact for the full list.

_{Validator: scripts/audit-retrieval-readiness.py · Constraint: klappy://canon/constraints/retrieval-disclosure-contract · Run: #327}

[github-actions]

Canon Quality — Frontmatter Schema ✅

All 49 file(s) in writings/ conform to klappy://canon/meta/frontmatter-schema.

_{Validator: scripts/validate-frontmatter.py · Canon: klappy://canon/constraints/frontmatter-validation-before-merge · Run: #327}

[github-actions]

Canon Quality — Homepage Surfacing ✅

49 essay(s) scanned. Soft report — never blocks; the hard field gate is the Frontmatter Schema job.

All published essays resolve to the homepage feed.

_{Report: scripts/surfacing-report.py · Canon: klappy://canon/constraints/frontmatter-validation-before-merge}

[github-actions]

Canon Quality — oddkit_audit ✅

No dead klappy:// references or legacy link patterns found in writings/. 51 files scanned.

_{Spec: klappy://docs/oddkit/specs/oddkit-audit · Workflow: .github/workflows/canon-quality.yml · Run: #327}