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

[HARDENING] PENDING-125 + the PENDING-121 ruling amendment

Browse Source 
Mauss split out on the jurist condition 5a: a live false claim in the governed
record, 53 days old, filed inside a PROPOSAL dies if the PROPOSAL is deferred.
VERIFIED-BOUND against an index bound to a sha the text has not carried since
2026-06-16 — while the anchors themselves hold, known only because a person
read them and recorded it nowhere a checker can reach.

121 gains the ruling in force, my omission of REVIEWED-53 recorded as mine,
and the condition-2 recommendation with its argument against stated.

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 17:57:51 +02:00
co-authored by Claude Opus 5
parent eeb9676bf4
commit 6af47f9060
1 changed files with 36 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
PENDING.md
+36
View File
@@ -1961,3 +1961,39 @@ Three cases, all discriminated: a rule ran → existing output already says so,
**Awaiting:** Jurist design-gate, then steward authorization.
---
## PENDING-125 — A live false attestation in the governed record: Mauss's `reading_index_status` has read VERIFIED-BOUND for 53 days
**Date:** 2026-08-08
**Tag:** [HARDENING]
**Related:** Split out of PENDING-121 on the jurist's condition 5a — *"a live false claim in the governed record, 53 days old, is filed inside a `[PROPOSAL]` and dies if this is deferred."* Same reasoning REVIEWED-101 §5 used for PENDING-118 and PENDING-119 §A used for PENDING-122; **applied twice this week and not applied here.** · engine `corpus/manifest.yaml` · PENDING-121 (the mechanism that would prevent recurrence).
**Summary.** `corpus/manifest.yaml` declares `reading_index_status: VERIFIED-BOUND` for `mauss-essai-sur-le-don`. The binding it names is **broken**: the reading index declares `source_sha256: ecac11b9…`, the manifest and the live file both carry `2889709555f2…`. Stale since the 2026-06-16 chamber cleanliness pass — **53 days as of 2026-08-08.**
**Measured 2026-08-08**, by walking each index's parsed document rather than grepping (a first-pass regex taking the *first* `source_sha256` in the multi-work `david-after-the-reply.yaml` manufactured four false mismatches — the artifact's shape, not its content, defeated the check):
| | index sha vs manifest | `reading_index_status` |
|---|---|---|
| harrison-dominion | agrees | `VERIFIED-BOUND` |
| alexander-pattern-language | agrees | `RE-ANCHORED-BOUND` |
| **mauss-essai-sur-le-don** | **DISAGREES** | **`VERIFIED-BOUND`** |
| after-the-reply-i…v | agrees (all five, per-work) | `RE-ANCHORED-BOUND` |
**Why it is not an emergency, and why that is the point.** The anchors themselves **hold** — R0's contract records it directly: *"a whole-file sha is too coarse (Mauss's differs while every anchor holds)"*, established by a person reading them. So three signals disagree and the only true one **was produced by hand and is recorded nowhere a checker can reach.** The field that looks like it records anchor integrity is wrong; the field that is right is prose in a spec-note; and `reading_index_status` has **0 code consumers** (positive-controlled: three known-consumed keys in the same file return 1–6 consuming scripts each).
**Rationale.** Constraint #4 is *honest degradation*: a system must report its own limits. A governed record asserting `VERIFIED-BOUND` about a binding that is broken is the inverse — it reports a capability it does not have, in the register a reader trusts most. That it has stood 53 days with nobody able to notice is the measurement, not the anecdote.
**Options.**
- **(a) Correct the field now** to an honest value for this source, and leave the mechanism question to PENDING-121. Cheap, and stops the record lying today.
- **(b) Re-anchor the index** to the current text (update `source_sha256`, re-verify anchors), then the field becomes true. ⚠ Costlier, and **re-anchoring without re-verifying is precisely what produced the class** — the ladder's *re-anchor = re-verify, by sha-match* entry.
- **(c) Wait for PENDING-121** and fix it as part of the amendment. ⚠ Leaves a known-false claim standing for the duration of a jurist gate, which is the reason this was split out.
**Recommendation: (a) now, (b) scheduled.** They are different acts: (a) stops the record asserting something false, and needs no ruling; (b) is curatorial work on the index and should be done with the re-verification the ladder requires, not folded into a field edit. ⚠ **(a) is an engine-side manifest edit — D-1, steward-direct** — so it needs the steward's word and not the jurist's.
**⚠ What this does not establish.** Correcting the field does not make anchor drift *detectable*; every hash on this path is whole-file, which is PENDING-121's subject. It also does not tell us whether **`VERIFIED-BOUND` vs `RE-ANCHORED-BOUND`** carry distinct meanings anywhere, or whether the vocabulary is decorative — unchecked, and worth knowing before choosing (a)'s replacement value.
**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).
---