David/dotfiles
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[FIX] PENDING-125(a) built — Mauss corrected, vocabulary found undefined

Browse Source 
Records the landing and the answer to the sub-question I had flagged as
unchecked: the reading_index_status vocabulary has no definition anywhere in
either repo. SHA-STALE is a fourth undefined token, added because none of the
existing three could state the truth, and recorded as a known cost.

The commit was also the first real corpus exercise of the trigger — both rules
fired, fleet green, not a probe.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01A35wiD55yRHj5U1ECZAX4t
This commit is contained in:
David F Glidden
2026-08-08 18:21:05 +02:00
co-authored by Claude Opus 5
parent 2472ed8e88
commit bc54758082
1 changed files with 13 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
PENDING.md
+13 -1
View File
@@ -2069,7 +2069,19 @@ Three cases, all discriminated: a rule ran → existing output already says so,
**Files affected:** `~/_Dev/studium-engine/corpus/manifest.yaml` (one field, option (a)); `~/_Dev/chamber-library/reading-indices/mauss-essai-sur-le-don.yaml` (option (b)).
**Awaiting:** Steward authorization (D-1 lane).
**Awaiting:** ~~Steward authorization (D-1 lane).~~ → **(a) BUILT 2026-08-08; (b) OPEN.**
---
### AMENDMENT 1 — 2026-08-08, option (a) built
**Steward authorized and (a) is landed** — studium-engine `8231bce`. `reading_index_status: VERIFIED-BOUND` → **`SHA-STALE`**, with the comment carrying the full truth: which sha the index declares, which the manifest and live file carry, when it diverged, and that **the anchors hold, hand-checked**, per R0 §3. Bounded to one field, two lines; shas untouched; manifest re-parses at 14 sources.
⚠ **The open sub-question was checked before choosing the value, and the answer is: the vocabulary is UNDEFINED.** Censused across both repos, all file types — `NONE-YET` ×6, `RE-ANCHORED-BOUND` ×6, `VERIFIED-BOUND` ×1 (was 2), and **no definition anywhere**. Every external mention is prose *about this defect*, never a specification. **`SHA-STALE` is therefore a fourth undefined token**, added because none of the three could state the truth — recorded as a known cost, not hidden. Whether the field survives at all is engine-lane (D-1) and rides with PENDING-121 Q2, which ruled it **not a binding surface and not evidence**.
✅ **The commit was also the mechanism's first real corpus exercise:** it touched `corpus/`, so both declared rules fired — binding check passed, then the fleet ran **7 suites green**. Not a probe.
**(b) remains open** — re-anchoring the index to the current text, which must carry the ladder's *re-anchor = re-verify* discipline. **Re-anchoring without re-verifying is what produced this class**, so it is not a field edit and was deliberately not bundled here.
---