canon: writing-canon carries the reader's one-line demand as its spine

[git-repo-auth]

What

Adds the operator's line — "Show me what I'm deciding in a way that respects my attention and time." — to canon/meta/writing-canon.md in two places:

1. Blockquote (Tier 2): opens the compressed argument as the reader's one demand, which the five extraction tiers then answer.
2. Summary (Tier 4): echoed once at the end of the first paragraph, so the claim is not blockquote-only.

Why here, and only here

The writing canon is the parent document: canon/constraints/retrieval-disclosure-contract.md already carries derives_from: canon/meta/writing-canon.md, so the line propagates by derivation rather than duplication (per dry-canon-says-it-once). The existing canon already contains the testable forms — extraction-depth actionability and per-flag disclosure caps. This PR adds the human-readable spine those forms serve, in the operator's own words.

Review note

The added sentence is the captain's authorial line verbatim; the connective framing around it is the first officer's. Nothing merges without the captain's review of the exact text.

---

Note

Low Risk
Meta canon prose only; no runtime, auth, or enforcement logic changes.

Overview
canon/meta/writing-canon.md now opens Tier 2 with the operator line "Show me what I'm deciding in a way that respects my attention and time." as the reader's single demand, then ties that demand to the existing extraction-depth requirements.

The Tier 4 summary ends with the same line in one sentence, so the spine is not blockquote-only when tooling or humans stop at the summary.

^{Reviewed by Cursor Bugbot for commit 08faec4. 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: #310}

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

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