Skip to content

docs(epoch): declare E0011 — Seat to Loop: The Gate Becomes the Verdict (DRAFT — do not merge)#293

Draft
git-repo-auth[bot] wants to merge 2 commits into
mainfrom
canon/epoch-11-seat-to-loop
Draft

docs(epoch): declare E0011 — Seat to Loop: The Gate Becomes the Verdict (DRAFT — do not merge)#293
git-repo-auth[bot] wants to merge 2 commits into
mainfrom
canon/epoch-11-seat-to-loop

Conversation

@git-repo-auth

@git-repo-auth git-repo-auth Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

Epoch 11 — Seat to Loop: The Gate Becomes the Verdict

DRAFT — captain's declaration in the captain's authorial voice. DO NOT MERGE until you review the exact text.

Thesis: seat -> loop — the gate becomes the verdict. E0011 relocates the unit of trust from the boarded seat (E0010) to the gated two-loop production frame. A valid outcome is one that descended from ratified policy through the loop — exploration -> policy -> PRD -> build -> validate — fresh-validated at every gate, for every role, not just the seated model.

  • Binding contract: policy-precedes-build (design -> policy -> PRD -> build; ratified + derivable + cited; fleet-wide).
  • Mandatory evidence: gate-passage receipts + fresh validation.
  • Forcing fault: the ARS monolith freeze (2026-07-16) — a correctly boarded seat built a thing no policy authorized.

Files (the governance-change-discipline trio + registry)

  • docs/appendices/epoch-11.md — the E0011 appendix. Gauntlet-challenged (oddkit_challenge, canon-tier-2); findings folded (prior-art acknowledgment for "the loop"; single-incident honesty; named alternative). No hard tensions; block_until_addressed: false.
  • docs/appendices/epochs.md — E0011 registry entry, plus backfilled E0009 and E0010 (their appendices existed but the registry skipped them; flagged as a judgment call — revert if you want E0011-only).
  • canon/CHANGELOG.md — canon 0.42.0.
  • docs/oddkit/release-notes/2026-07-17-epoch-11-seat-to-loop.md — release note.

Documented relabel scope (follow-up, NOT executed here)

The loop-frame canon is referenced, not restamped — per the ruling, the write-up is the declaration and the relabel follows it. Do not merge; this is your pen.

…ct (DRAFT — do not merge)

Author the Epoch 11 declaration trio. The write-up IS the declaration; the frontmatter relabel of the loop-frame canon (PRs #288-#291) is a documented follow-up, not executed here.

- docs/appendices/epoch-11.md — E0011 appendix (gauntlet-challenged; findings folded).
- docs/appendices/epochs.md — E0011 registry entry; backfilled E0009/E0010.
- canon/CHANGELOG.md — canon 0.42.0.
- docs/oddkit/release-notes/2026-07-17-epoch-11-seat-to-loop.md — release note.

Binding contract: policy-precedes-build. Mandatory evidence: gate-passage receipts + fresh validation, for every role. Authored in the captain's voice; DRAFT — do not merge until the captain reviews the exact text.
@github-actions

github-actions Bot commented Jul 17, 2026

Copy link
Copy Markdown

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: #372

@github-actions

github-actions Bot commented Jul 17, 2026

Copy link
Copy Markdown

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: #372

@github-actions

Copy link
Copy Markdown

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

github-actions Bot commented Jul 17, 2026

Copy link
Copy Markdown

Canon Quality — P0010 Retrieval-Readiness ⚠️

Soft report for klappy://canon/constraints/retrieval-disclosure-contract. 701 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': 240, 'apocrypha': 38, 'docs': 306, 'journals': 60, 'unknown': 6}
Kind source: {'path': 564, 'frontmatter': 131, 'none': 6} (frontmatter-primary, path-secondary)
Default-include visibility: 597 visible, 104 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: #372

Epoch/crew-model doc set. General-prose 'the captain restates' -> 'the
operator restates'; reader-address '**Operators / captains:**' -> '**Operators:**';
draft-posture note rewritten neutral/passive. CHANGELOG change limited to this
PR's new entry (pre-existing history untouched); epochs.md needed no change. No
rulings, thresholds, enforcement, or meaning changed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant