Skip to content

ledger: progressive disclosure is the build model, review must not avalanche (2026-07-17)#298

Draft
git-repo-auth[bot] wants to merge 3 commits into
mainfrom
odd/ledger-2026-07-17-progressive-disclosure-anti-avalanche
Draft

ledger: progressive disclosure is the build model, review must not avalanche (2026-07-17)#298
git-repo-auth[bot] wants to merge 3 commits into
mainfrom
odd/ledger-2026-07-17-progressive-disclosure-anti-avalanche

Conversation

@git-repo-auth

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

Copy link
Copy Markdown
Contributor

Low-resolution ledger capture — pre-policy, not for merge as-is.

Appends one black-box ledger entry recording four operator-articulated working lessons from today's process:

  1. Progressive disclosure is the build model — an app/policy set is a progressive JPEG; shippable at every resolution; maturity = clarity of policies, earned through friction, not up-front review.
  2. Anti-avalanche — review must not spawn exponential unrelated work; findings are parked, not built mid-review.
  3. Related batches are the balance — review in human-sized related batches (2–3, sometimes 1); stop the tangents, not the pace.
  4. Durable, not memory — rules that matter live in the ledger, not conversation/memory; ledger → policy, never memory.

Scope discipline (per the execution brief):

  • Low-resolution capture only — kept small and blurry on purpose.
  • No challenge gauntlet run (that's for policies, not raw ledger material).
  • No policy expansion, no follow-on work spawned.
  • Cross-references odd/maturity.md (lesson feat(website): implement public website for PRD v1.0 #1); that doc is not edited.
  • Draft, operator's pen — do not merge. Sharpens into policy later via friction.

…alanche (2026-07-17)

Low-resolution black-box capture of four operator-articulated working
lessons (pre-policy, not ratified): progressive-disclosure-as-build-model,
anti-avalanche review, related-batch review, durable-not-memory. Cross-refs
odd/maturity (not edited). No gauntlet, no policy expansion.
@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: #379

@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. 700 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': 304, 'journals': 61, 'unknown': 6}
Kind source: {'path': 564, 'frontmatter': 130, 'none': 6} (frontmatter-primary, path-secondary)
Default-include visibility: 595 visible, 105 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: #379

@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: #379

@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

klappy added 2 commits July 17, 2026 12:49
…owned working state

Single low-res observation appended (pre-policy, not ratified). No gauntlet,
no policy, no follow-on work.
…oidable avalanche, refinement-folds-in line, mentorship framing

Additive fold into the existing 2026-07-17 anti-avalanche entry (obs. 2a beside
obs. 2). Existing observations unchanged. Low-resolution, operator/neutral voice.
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