Skip to content

Add retrieval alias tags to P0012 so 'third loop' finds triple-loop-debrief-review - #309

Merged
git-repo-auth[bot] merged 1 commit into
mainfrom
fix/p0012-alias-tags
Jul 20, 2026
Merged

Add retrieval alias tags to P0012 so 'third loop' finds triple-loop-debrief-review#309
git-repo-auth[bot] merged 1 commit into
mainfrom
fix/p0012-alias-tags

Conversation

@git-repo-auth

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

Copy link
Copy Markdown
Contributor

What this changes

Three alias tags on the P0012 canon doc: triple-loop, third-loop, three-loops.

Why (receipts)

A second session searched "third loop" today and missed this doc entirely (staleness window) — and even against the fresh index it ranks 4th behind generic loop docs, because canon says "triple-loop" and humans say "third loop." The miss led that agent to improvise a parallel meaning for a term canon already owns. Retrieval vocabulary is part of landing canon.

The decision

Two-line frontmatter change to an active canon doc — canon is yours alone (M3). Merge or amend the alias list.

Reversibility

Tag-only; revert restores exact prior state.


Note

Low Risk
Tag-only frontmatter on an active canon method doc; no runtime, auth, or behavioral code paths.

Overview
Adds three frontmatter tags on canon/methods/triple-loop-debrief-review.md: triple-loop, third-loop, and three-loops, so searches for human phrasing like “third loop” surface this canon doc instead of generic loop material.

No body or policy text changes—metadata only, fully revertible by dropping the new tags.

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

Retrieval-vocabulary fix: a same-day cross-session miss showed 'third loop'
ranks this doc 4th behind generic loop docs. Aliases land with canon so
paraphrased names still retrieve the ratified concept.
@github-actions

Copy link
Copy Markdown

Canon Quality — P0010 Retrieval-Readiness ⚠️

Soft report for klappy://canon/constraints/retrieval-disclosure-contract. 707 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': 52, 'canon': 244, 'apocrypha': 38, 'docs': 307, 'journals': 60, 'unknown': 6}
Kind source: {'path': 572, 'frontmatter': 129, 'none': 6} (frontmatter-primary, path-secondary)
Default-include visibility: 603 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: #409

@github-actions

Copy link
Copy Markdown

Canon Quality — oddkit_audit

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

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

@github-actions

Copy link
Copy Markdown

Canon Quality — Frontmatter Schema ✅

All 50 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: #409

@github-actions

Copy link
Copy Markdown

Canon Quality — Homepage Surfacing ✅

50 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

@git-repo-auth
git-repo-auth Bot merged commit b387d02 into main Jul 20, 2026
5 checks passed
@git-repo-auth
git-repo-auth Bot deleted the fix/p0012-alias-tags branch July 20, 2026 22:17
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