feat(bootstrap): generic boarding pass — crew-frame instructions anyone can adopt

[git-repo-auth]

What

Adds canon/bootstrap/generic-boarding-pass — the reusable, personal-cargo-free counterpart to the maintainer's canon/bootstrap/boarding-pass.

Why

The maintainer's boarding pass is one person's literal pasted instructions and carries cargo no one else can use (a named captain, the ODD stewardship charter, the Orville/Oddie voice personas, a personal publish gauntlet). This is the version anyone adopting the flight-deck model can paste.

How it was derived

• Layered, not replaced (per ruling): the crew frame wraps the creed + axioms, which stay inline and load-bearing.
• Stripped: named captain → "the human you work with"; ODD stewardship charter; Orville/Oddie; publish gauntlet.
• Kept: crew frame, board-first reflex, fetch-live governance, search-before-asking, two-way cross-check, authorial-voice review gate, the time rule, the debrief/no-blame clause.
• Adds a "What to Adapt" section so adopters know what cargo to add back.

Status

stability: experimental, E0010. Part of the flight-crew experiment — evidence about how models fly under it will be added to flight-deck-model only after real testing produces honest data, not before.

Provenance

Exact text ratified by the captain before commit. Author editorial pass pending on merge. Companion template (docs/examples/project-instructions-template) and essay (writings/getting-started-with-odd-and-oddkit) updates follow as separate changes.

[github-actions]

Canon Quality — Frontmatter Schema ✅

All 48 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: #278}

[github-actions]

Canon Quality — Homepage Surfacing ✅

48 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/. 50 files scanned.

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

[github-actions]

Canon Quality — P0010 Retrieval-Readiness ⚠️

Soft report for klappy://canon/constraints/retrieval-disclosure-contract. 675 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': 50, 'canon': 225, 'apocrypha': 38, 'docs': 297, 'journals': 59, 'unknown': 6}
Kind source: {'path': 546, 'frontmatter': 123, 'none': 6} (frontmatter-primary, path-secondary)
Default-include visibility: 572 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: #278}