Repository navigation
chore(vocabulary): retire rung, default ladder, overlay and the other clashing senses with a checker #12750
Description
Parent
Source: PLAN Phase 10, topic planning-chain-consolidation. Epic: #12646.
Depends on
- refactor(adhd): resolve the view medium through the shared resolver #12668
- refactor(visualization): resolve the view medium through the shared resolver #12669
- refactor(review): resolve the view medium through the shared resolver #12670
- refactor(architecture): resolve the view medium through the shared resolver #12672
- refactor(codebase-health): resolve the view medium through the shared resolver #12677
- refactor(overengineering): resolve the view medium through the shared resolver #12679
- refactor(education): resolve the view medium through the shared resolver #12682
- refactor(prototype): resolve the view medium through the shared resolver #12684
- refactor(work-items): resolve morning-brief's view medium through the shared resolver #12701
- refactor(work-items): resolve the view medium through the shared resolver #12711
- refactor(ai-briefing): resolve the view medium through the shared resolver #12722
- refactor(debugging): resolve the view medium through the shared resolver #12732
- refactor(discovery): resolve the view medium through the shared resolver #12741
Outcome
A vocabulary checker reports AC3's six retired senses outside dated records, with an allowlist of senses that stay; every reported match is fixed, and the workflow stage reads Interview.
Demo: Run the checker over the repository: it exits 0.
The Brief (Problem, Goal, Constraints) is in the epic body.
Decisions
- Q5-Q12: Retired: rung (form vs medium), tier for precedence, default ladder (now fallback chain), overlay (now personal override), surface for a config file, contract for the Brief; the workflow stage reads Interview.
- D8: The vocabulary checker carries an allowlist of senses that stay (for example the autonomy ladder's rung).
Criteria, carried by the sub-issues
- AC3: the checker exits 0 over the repository, excluding docs/adr, docs/upstream, CHANGELOG files and docs/standards; each allowlisted sense is named with its reason (chore(vocabulary): run the vocabulary checker over the whole repository on every pull request (AC3) #13193, the last slice).
- AC4 (carried from feat(rendered-views): one medium resolver with the publish trust walk and fallback chain #12649):
git grep -nE "rendered-views(\.local)?\.md" -- lib pluginsoutside lib/view-settings.mjs, its test and its synced copies prints only CHANGELOG lines and the AC14 notice tests and fixtures named in chore(rendered-views): stop listing retired rendered-views files as a layer to read (AC4) #13180.
Done when
- chore(vocabulary): add the retired-sense vocabulary checker with its allowlist #13178
- chore(rendered-views): stop listing retired rendered-views files as a layer to read (AC4) #13180
- chore(rendered-views): retire rung, default ladder, tier for precedence and surface for a config file #13184
- chore(planning): call the interview's record the Brief, not the contract #13185
- chore(config-cascade): call the personal layer the personal override in the contract and shared lib #13182
- chore(work-items): call the cascade's personal layer the personal override #13186
- chore(source-control): call the cascade's personal layer the personal override #13189
- chore(docs-naming, testing, planning): call the cascade's personal layer the personal override #13190
- chore(attribution, review, multi-agent and five more): call the cascade's personal layer the personal override #13191
- chore(plugins): call the cascade's personal layer the personal override in the remaining plugins #13192
- chore(vocabulary): run the vocabulary checker over the whole repository on every pull request (AC3) #13193
Out of scope
- Renaming the autonomy ladder's rung or any other allowlisted sense
Activity
23 remaining items
kyle-sexton commentedon Nov 4, 2026
Decision recorded.
(agent; not an owner decision)
Question: the work-resolve-issue stop found the remaining matches far beyond one scoped run and the allowlist undecided. Is this an intent change or a size problem?
Decision: a size problem. The outcome and the checker's purpose stand. #12750 is split into sub-issues, each shipping as its own pull request, and stays open as their parent.
Basis (R313):
docs/contracts/rendered-views/README.md"Choosing the rung" and "Default ladder and its reconciliation". "Overlay" retires only for the config cascade's personal<concern>.local.<ext>layer, whichlib/view-settings.mjsalready reports as "personal override".Sub-issues:
pr-require-checks.yml, AC3 over the whole repository (blocked by all of the above except chore(rendered-views): stop listing retired rendered-views files as a layer to read (AC4) #13180)The shared-lib overlay slice comes before the per-plugin ones because setup-apply's printed text, which plugin evals assert, and the synced lib copies have to change together (ADR 0019 drift check). The parent's done-when now lists these sub-issues, so work-unblock closes it when they finish. The "check ListAgents" step is dropped: the lane has no such tool, so the step could never be ticked.
needs-humancomes off: the person-only parts of the stop are settled above.melodic-automation-lanes commentedon Nov 4, 2026
Every sub-issue of this split is closed as completed by a listed human or a merge (#13178, #13180, #13182, #13184, #13185, #13186, #13189, #13190, #13191, #13192, #13193), so the lanes App closes it as completed.