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

session 2026-07-24 evening: REVIEWED-72/74 landed (chamber-library spec v2.6.0 — born-digital V-TEXT source-fidelity gate) + PENDING-73 + session memory/ledger + KG

Browse Source
This commit is contained in:
David F Glidden
2026-07-24 16:40:02 +02:00
parent 54b8b5bf29
commit 06203c3833
7 changed files with 91 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
claude/memory/session-ledger-2026-07-24.md
+15
View File
@@ -89,3 +89,18 @@ metadata:
## Sub-agent dialogues
## Bypasses
## Open horizons — [post-clear context window; the REVIEWED-72 build phase]
- 2026-07-24T~14:54 CEST — Fresh context window opened (steward /clear'd ~8 min after wrap to build with room). Thread CONFIRMED at wake, unchanged: **build REVIEWED-72 → unblock the 47-file V-TEXT wave.** Ruled design = run (3) (already passes), so bounded: (1) repoint reference `-t gfm-raw_html`→`-t markdown-smart` on raw source EPUB; (2) declare/excuse injection+glyph delta (PENDING-69 `moved_to`); (3) spec periodic per-format-class reader audit as declared data; (4) demonstrate clean PASS **+ deliberate negative still FLAGs**. Land 969/1046 as §Tiering&Fence supersession + add reassigned-component check to amendment discipline. **Drift to hold today (its sharpest instance is load-bearing here):** under-read-own-measurement — the build IS run (3); read REVIEWED-72 + measure_flag1.py as substrate, don't theorize past the data. Symmetria re-anchored (init); lineage clasp closed.
## Returns — [post-clear build: the measurement refined the RULING's premise, not just mine]
- 2026-07-24T~15:20 CEST — Grounding run (3) on Levi before building the excuse mechanism (`scratchpad/ground_manifest.py`, read-only) DECOMPOSED the 287 added_total: **multiset-added (genuinely candidate-only) = 8 tokens, ALL glyph (wstawać×6, oświęcim, braşov); the other 279 are present-elsewhere in the reference (displacement, multiset-neutral).** Injection's own enumeration (`converted_markers`, 646 digit-markers) lands on the LOST side and explains 0 of the added. ⇒ the ruling's SHAPE holds (moved_to / fabrication-elsewhere-flags), but its SURFACE ("the injector enumerates the added delta") does not — the injector enumerates markers, not relocated-body positions. The clean mechanism = a PRESENCE check (moved_to generalized to the added side): an added token is benign iff present-in-reference (relocation) OR in the declared two-sided glyph manifest; else fabrication → FLAG. The whole-book manifest is ~8 glyph tokens, not 287. Prior question ALSO settled empirically: `_tokens` PRESERVES diacritics (\w+/re.UNICODE) — wstawać≠wstawa — so the glyph half of the manifest IS needed and IS two-sided. Surfaced to steward as a routing question (FIX within REVIEWED-72 vs one-line jurist note, since it redefines what classify's added side measures). Substrate-first caught the compressed framing — the good direction of the day's drift-family.
## Authorization moves
- 2026-07-24T~15:45 CEST — **PENDING-73 filed ([PROPOSAL], change-class confirmation) + jurist package written** (`docs/borndigital-added-side-fabrication-check-JURIST-PACKAGE-2026-07-24.md`; verify-before-compose hook PASSED — GROUNDED-IN §Tiering&Fence source-fidelity 1046–1048 + V-TEXT tier + §V Tier-3-by-omission, quoted verbatim + the REVIEWED-72 ruling/`resolve_review`/`classify()` operative decisions quoted; measurement inlined). Steward chose routing (b) — secure the in-scope judgment BEFORE building, "to be sure of no surprises." One claim to test: the honest added-side excuse redefines classify's added side from position-displacement to a multiset-fabrication measure (present-in-reference ∨ declared-glyph; else FLAG), in-scope for REVIEWED-72 to land atomically. 4 gate Qs w/ leans (in-scope · multiset>presence · two-sided glyph · closed §V-normalization boundary). Did NOT build — HOLD until ruled. Awaiting steward relay → jurist.
## Authorization moves
- 2026-07-24T~16:30 CEST — **REVIEWED-74 PLACED by steward → built the added-side check + DEMONSTRATED (literal question ANSWERED).** Built to the four ruled corrections: (1) `resolve_added` in `verify_body_conservation.py` — multiset fabrication (`Counter(cand)−Counter(ref)−glyph_added`), count-scoped both sides (whole-run-or-nothing loss excuse), classify() byte-identical, V-DSL+sweep don't inherit (10 invariant fixtures pass, incl. the duplication-catch + count-scoped negatives). (2) `apply_char_glyphs` emits the two-sided per-site manifest (added joined words / removed `<img>`-split fragments — the honest asymmetry, matches the reference's own pandoc inline-image tokenization). (3) repointed `reference_tokens_epub` gfm-raw_html→markdown-smart. (4) **FOUR-CASE DEMONSTRATION ran on real candidates** (`scratchpad/demonstrate_four_cases.py`; RECORD at `docs/borndigital-added-side-four-case-demonstration-RECORD-2026-07-24.md`): **Case 1 clean Levi → PASS (fab=0) · Case 2 prose deletion → FLAG · Case 3 fabrication-outside-manifest → FLAG (fab=80) · Case 4 Eichmann added+interior CLEAN (fab=3<23, no regression; boundary runs → resolve_review, REVIEWED-72 flow).** Manifest DERIVED from declared policy = the measured multiset exactly. Threshold=clean-floor(Levi 0/Eichmann 3)+margin=23, declared data. **test_tools 232/232** (+10). **The literal question is answered: clean PASS + deliberate negative still FLAGs under the repointed reference — refuses real loss, not merely passes clean files.** Code on working copy, NOT committed (lands atomically with the §Tiering&Fence supersession — no code ahead of spec). REMAINING = the atomic landing (task 6): wire resolve_added into graduate_to_canonical + spec supersession + graduation-spec declared data + amendment discipline + bounded-diff proof + commit/tag REVIEWED-72/74 + push → then the 47-file wave.
## Authorization moves
- 2026-07-24T~17:30 CEST — **ATOMIC LANDING COMPLETE (REVIEWED-72 + REVIEWED-74), committed `eaa38bf`, pushed github ✓.** Steward directed "push into the landing." Wired resolve_added into `verify_candidate` (V-TEXT) + `graduate_to_canonical.body_conservation_gate` (loads `<stem>.glyph-manifest.json` + `body_conservation.added_fabrication_threshold`); lane writes the glyph-manifest sidecar. **Spec v2.5.0→v2.6.0** (froze v2.5.0 byte-identical; **BOUNDED-DIFF PROVEN** = exactly 4 regions: title · v2.6.0 block · source-fidelity clause revision · §Governance 2 disciplines; 4 deleted lines = only old title + old bullet). graduation-spec `body_conservation:` declared data (reference_writer · added_fabrication_threshold=40 [clean-floor+margin] · reader_audit specified-not-yet-built with cadence/trigger/pass-criterion — VISIBLE per steward). §Governance += reassigned-component check (REVIEWED-72) + in-scope-refinement three-part test (REVIEWED-74). Doc currency: chamber CLAUDE.md v2.6.0 + tool-evolution-log entry. **Fleet 234/234.** All verify-before-compose hooks passed; pre-commit passed. **origin/Gitea unreachable (port 443, known-flaky) — retry owed; github has eaa38bf.** THE 47-FILE V-TEXT WAVE IS UNBLOCKED. Owed: reader-audit RUNNER (named dependency); origin push retry; per-source glyph-maps for 12 census-flagged files; the wave itself.