canon: ratify Discernment Transfer Ladder (captain-attested 2026-07-07) + criterion-6 genericization

[git-repo-auth]

What this is

Captain's routing ruling on the ODD Fly cycle-01 contested doc, executed source-side (authoring home stays klappy.dev while PR #14 board item 2 is OPEN — respected, not adjudicated). The paired ODD sync PR lands separately, stacked on the cycle branch. Your merge is the ratification; nothing here self-merges.

The ruling (verbatim, filtered)

• Route + ratify: "It seems proven over the past week. Many experiments done over many repos. Not just here with you."
• Causal correction: "Let's ratify it as the holes had nothing to do with this. There were other gaps that impacted it."
• Caveat: "Maybe worth making a note that this process is still fragile and needs careful planning and execution and validation."

Changes to canon/methods/discernment-transfer-ladder.md

1. Frontmatter: stability: provisional -> evolving, status: proposed -> active. Note: this repo's stability vocabulary has no active value (0 uses); sibling active methods (governance-validation-via-agents, revision-lens-sequence) carry evolving — used as the proven-equivalent. status: active is the routing-relevant flip (criterion 2 now passes).
2. Provenance and Ratification section (methods-family ## Provenance convention): captain-ratified 2026-07-07 ET, with the causal note (observed gaps in the proving week were attributable to unrelated causes, not this method) so the Open items read as scoped follow-ups, not method-doubt — plus the captain-attributed fragility caveat (proven != robust; careful planning, execution, and fresh-context validation per verification-requires-fresh-context on every run).
3. Criterion-6 genericization (precedent: governance-validation-via-agents [OWNER]/[REPO] pass): Covenynt -> [ORG]; 0 Context/about.md -> [ORG-APPROVAL-POLICY-DOC]; Brief 07 Step 5 / Brief 08 Phase 2 -> [ORG-PILOT-BRIEF] field phases. Kept per criterion 5 (proof, not operational values): the worked-example numbers (41/11, 37/9, 88/4 -> 45/10), model names, the tra-/gaw- foldout-row citation, Kirigami as tool name. Everything else byte-for-byte.

Preflight instruments (cited per the cycle's law)

Extraction convention (verbatim-minus-target_repo, grandfathered klappy:// URIs, never mint new schemes — foldout of0001/of0002, D0002); E0010 stewardship charter + cycle extraction-workflow.md; PR #14 decision board (authoring-home OPEN -> authored here, the de-facto write model); memory-is-not-canon (governance fetched live this session); clock observed via oddkit_time: 2026-07-08T02:05Z = late evening 2026-07-07 ET.

One sitting

Three PRs await your clicks together: ODD #14 (the 6 uncontested syncs), this PR (source-side ratification), and the ODD sync PR (reads this doc into the core + resolves the HELD dossier). Merge this one before the ODD sync PR so the read model mirrors the ratified source.

---

Note

Low Risk
Documentation-only canon metadata, provenance, and placeholder substitution with no runtime or security impact.

Overview
Ratifies the Discernment Transfer Ladder method after captain attestation: frontmatter moves from proposed/provisional to status: active and stability: evolving, and a new Provenance and Ratification section records the 2026-07-07 ruling (proven across repos; gaps in the week were unrelated; proven ≠ robust—still needs careful planning, execution, and fresh-context validation).

Criterion-6 genericization replaces org-specific strings with placeholders (Covenynt → [ORG], approval policy doc and pilot brief references → [ORG-APPROVAL-POLICY-DOC] / [ORG-PILOT-BRIEF] field phases) so the canon doc stays portable; worked-example metrics and model names are unchanged.

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

[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: #312}

[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: #312}

[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 — P0010 Retrieval-Readiness ⚠️

Soft report for klappy://canon/constraints/retrieval-disclosure-contract. 683 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': 231, 'apocrypha': 38, 'docs': 298, 'journals': 59, 'unknown': 6}
Kind source: {'path': 551, 'frontmatter': 126, 'none': 6} (frontmatter-primary, path-secondary)
Default-include visibility: 580 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: #312}