Skip to content

promotions(P0012): addendum — second evidence window + ToC constraint-audit mechanism#310

Open
git-repo-auth[bot] wants to merge 1 commit into
mainfrom
promotions/p0012-toc-addendum
Open

promotions(P0012): addendum — second evidence window + ToC constraint-audit mechanism#310
git-repo-auth[bot] wants to merge 1 commit into
mainfrom
promotions/p0012-toc-addendum

Conversation

@git-repo-auth

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

Copy link
Copy Markdown
Contributor

Captain steering 2026-07-21, seat-recorded. Cures P0012's self-flagged single-window evidence gap with the independent 2026-07-20/21 sweep window (turn-cadence constraint case: 4.5h/10 pings/9 merges vs 18min/0/9), and adds the Theory of Constraints five-step audit as the proposed triple-loop mechanism (Goal metric, convicted constraint, effort audit, sunset review — micro-charter law scheduled first, re-identify each cycle).

Additive only; promotion_status: proposed unchanged. Promotion review remains the captain's decision — per the pipeline, the ≥3-proposed backlog trigger (P0011/P0012/P0013) is currently lit.

Refs: ODD candidates/2026-07-21-theory-of-constraints-as-the-third-loop.md (85f247b) · ODD docs/prd/2026-07-14-second-brain-feeding-loop.md (accepted cadence: weekly, riding tower sweep).


Note

Low Risk
Documentation-only additive update to a proposed promotion artifact; no runtime, auth, or workflow enforcement changes.

Overview
Adds a 2026-07-21 addendum to the P0012 promotion draft only—no canon or enforcement changes, and promotion_status: proposed stays as-is.

The addendum closes the single-calendar-window evidence gap with a second independent sweep (2026-07-20 evening → 2026-07-21 morning): turn-cadence as the binding constraint (4.5h / ~10 captain touches vs ~18 min / zero), plus a second L4-duty-in-prompt-only occurrence class.

It also proposes a Theory of Constraints shape for the standing triple-loop debrief: Goal metric per captain-minute, convicted binding constraint, effort audit (constraint vs local optimum), sunset review of laws whose constraint moved (micro-charter first), and re-identify each cycle—with pointers to related ODD candidate and second-brain PRD cadence.

Reviewed by Cursor Bugbot for commit d6f8705. Bugbot is set up for automated code reviews on this repo. Configure here.

@github-actions

Copy link
Copy Markdown

Canon Quality — Frontmatter Schema ✅

All 51 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: #420

@github-actions

Copy link
Copy Markdown

Canon Quality — Homepage Surfacing ✅

51 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

Copy link
Copy Markdown

Canon Quality — oddkit_audit

No dead klappy:// references or legacy link patterns found in writings/. 53 files scanned.

Spec: klappy://docs/oddkit/specs/oddkit-audit · Workflow: .github/workflows/canon-quality.yml · Run: #420

@github-actions

Copy link
Copy Markdown

Canon Quality — P0010 Retrieval-Readiness ⚠️

Soft report for klappy://canon/constraints/retrieval-disclosure-contract. 710 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': 53, 'canon': 246, 'apocrypha': 38, 'docs': 307, 'journals': 60, 'unknown': 6}
Kind source: {'path': 575, 'frontmatter': 129, 'none': 6} (frontmatter-primary, path-secondary)
Default-include visibility: 606 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: #420

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