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

session 2026-07-19 evening: engine gate failure-legibility + one-door plan banked; PENDING-64 closure annotated

Browse Source
This commit is contained in:
David F Glidden
2026-07-19 17:16:46 +02:00
parent 8f6577cc0c
commit bff8c714b9
7 changed files with 94 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files
claude/memory/skill-harvest-register.md
+8
View File
@@ -550,3 +550,11 @@ No new skill proposal. Two register notes: **(1)** the S1 proposal **implementat
| **Symmetria §3 flag: record-asserts-applied-before-the-act** | Symmetria §3 flag | A session record (Addendum, brief, tracker line) composed AHEAD of its acts and asserting APPLIED/DONE is contamination shape even when the acts follow in the same session — the say-do order inverts, and an interruption mid-session would leave a false record committed nowhere-true. Caught 2026-07-19 (self-caught, ledger): the placement-gate Addendum asserted both flags APPLIED before the flag work ran; made true pre-commit, but the order was backwards. Antidote: record AFTER the act, or mark the record prospective ("applied below / to follow"). Kin to the existing §3 flag "comments promising behavior the code doesn't deliver", one level up (session artifacts, not code). | Symmetria §3 | **PROPOSED** |
*(One proposal, earned in use. NOT proposed: a "refuse-the-claim-not-the-value" design card — the jurist's praise names a real principle, but it is chamber-side design doctrine already carried in the ruling + edit-set records; a skill-layer card would duplicate a governed record. Revisit only if the shape recurs outside the chamber.)*
### Harvest 2026-07-19 (evening — engine gate failure-legibility + one-door planning)
| Element | Kind | One-line | Where it lands | Status |
|---|---|---|---|---|
| **re-anchor = re-verify: reconstruct the old bound state by sha-match** | verification-ladder entry | When re-anchoring any sha-bound artifact after an upstream edit: reconstruct the OLD bound state from git by matching the declared sha (`git rev-list` the file; hash each historical blob), prove the old→live delta is EXACTLY the expected hunks, and map every changed line against the declared spans/anchors BEFORE re-stamping any sha. Stored-text anchors verify ellipsis-aware (split on `...`/`…`, fragments in order) — a declared condensation divergence then surfaces as the index's own exception, not a false failure. Proven 2026-07-19 on all five after-the-reply sources + the 48-anchor reading-index the completeness grep caught. Will recur constantly under the one-door reconversion posture (every Route-B graduation is a re-anchor). | `reference-verification-ladder.md` | **PROPOSED** |
**Reinforcement (no new proposal):** the 2026-06-18 `/wake-up` telos-patch proposal ("surface the *why* when the thread touches the engine's purpose") gains a second evidence instance — the 2026-07-19 full-map answer under-carried the shortlist/Making telos lane and the steward had to correct it twice (drift-pattern `map-drawn-from-production-lanes-not-telos`). Still awaiting steward judgment with the rest of the standing review.