session 2026-08-06: Constraint #1 wording (steward-enacted) + PENDING-106/107 corrections + PENDING-89 docket; BMF stopped and disabled; chavruta retrieval measured

This commit is contained in:
David F Glidden
2026-08-06 16:56:17 +02:00
parent fb4e171d9e
commit 3b0730d593
9 changed files with 283 additions and 10 deletions
+5 -6
View File
@@ -6,7 +6,7 @@ metadata:
type: note
permalink: claude-memory/memory
originSessionId: 22915403-bc5d-4796-9c7d-196b7c30d2f9
modified: 2026-08-04T13:29:28.365Z
modified: 2026-08-06T14:55:31.323Z
permalink: claude-memory/memory
---
@@ -17,7 +17,7 @@ permalink: claude-memory/memory
- [CapableHands standing authorization](reference-capablehands-standing-authorization.md) — M4 mini david@10.0.1.136 durably authorized for remote OCR/inference; don't re-ask permission to use it (steward 2026-07-01).
- [Every canon doc's source lives in Chamber Sources](feedback-resolve-source-through-chamber-sources.md) — a canonical's source = whatever `resolve_archived_source` returns (**never** the master library or a path in a doc/frontmatter); read the banked source record before calling a mismatch a defect.
- [Steward maps live in ~/dotfiles/maps](reference-steward-maps-home.md) — a **map** = an artifact David reads *directly* to orient. Write it into `~/dotfiles/maps/` and symlink to the Desktop, **never** straight onto the Desktop; `wake-digest.py` reports strays.
- [Governance files are dotfiles symlinks](reference-governance-files-are-dotfiles-symlinks.md) — `~/PENDING.md`/`~/REVIEWED.md`/`~/CLAUDE.md` → `~/dotfiles/…`; Edit/Write refuse to write through a symlink, so **edit the real dotfiles path** when appending PENDING/REVIEWED.
- [Governance files are dotfiles symlinks](reference-governance-files-are-dotfiles-symlinks.md) — `~/PENDING.md`/`~/REVIEWED.md`/`~/CLAUDE.md` → `~/dotfiles/…`; Edit/Write refuse to write through a symlink, so **edit the real dotfiles path** when appending PENDING/REVIEWED — **`PENDING`/`REVIEWED` only.** ⚠ That refusal is a tool artifact, **not** a permission check, and this note is the documented route past the only friction guarding the constitution (PENDING-107: no `permissions` key; the one hook fires on `~/CLAUDE.md` and exits 0 by design; `Bash` isn't gated at all). **`~/CLAUDE.md`/`~/REVIEWED.md`/L2 = `[ESCALATE]`, steward's hand — a jurist sign-off does not authorize one.**
- [Typography palace — query via CLI](reference-typography-palace-cli.md) — type masters (~20-21 sources) in a dedicated MemPalace at `~/.mempalace/palace-chamber-typography`; query `mempalace --palace <that> search "…"` (CLI). For ARC typography — don't re-ask where it lives.
- [The central path — answerability, not purity](feedback-central-path-answerability-not-purity.md) — the contamination recursion is **probably irresolvable**, so **stop certifying the parties, bind the claims.** Route by claim-type: *checkable* → produce the check + a falsifier; *judgment* → disclose standpoint in one line, decide, record; *undecidable* → name it open. **One layer of disclosure, then act — never audit the audit.**
- [Fowler's rules for quotation](feedback_fowlers_rules_quotation.md) — single quotes primary, double for nested, logical British punctuation order. Apply across all writing.
@@ -67,11 +67,10 @@ permalink: claude-memory/memory
- [Be (laundromat)](project-be-laundromat.md) — canonical Be tracker (est. 2026-06-08). Be = Skemantix startup (Seb+David) funding CapableMind's ladder; **bridge, not venture**. Decisions LOCKED (entity/pricing/infra in file); a11y gate MERGED. **Pre-revenue WTP gate = renovate Pat → charge her; discipline: no new spec until it clears → nothing for executor on be.** Repo @ `f43a0fd`.
## Active Session
> ⛔ **NEXT SESSION = the chamber use-session — the thread the steward deferred to "the morning after the research session." That morning is now.** Ask the corpus real questions; let that settle Chamber V1's voice-set. ⚠ **Twice-deferred, three days old — both deferrals were for genuinely good reasons, which is exactly how a thread dies. If a third good reason appears, the pattern IS the finding.**
> ▶ **Resumption point (re-judge against what changed):** (1) Q4 needed no ruling — build the chavruta to cite by **engine-constructed citation** (carries `text_original` bytes, immune by construction), which unblocks use with no further gate. (2) Then the still-undone retrieval measurement: `cd ~/_Dev/studium-engine && python3 engine/retrieve.py "<real question>"` — record *served? · reached · missed and WHY*, sorted into the two piles that ARE the V1 decision: **"we lack the voice" vs "we lack the retrieval"** (PENDING-97's input). (3) `corpus/mauss-phase2-reanchored.yaml` is ready to consume; `corpus/v2-gold.yaml` is NOT written and waits on P1–P4/P6/P7.
> ⏳ **Awaiting others — do not confuse waiting with working:** jurist ruling on **PENDING-102–107** (package filed, 5 gate questions); **REVIEWED-87** still drafted-not-placed; PENDING-95/96/97/98/100 await routing; **PENDING-89 owed a docket entry** from PENDING-102.
> ⛔ **NEXT = the chamber PARSE FIX — decided jointly with the steward at the 2026-08-06 wrap, not defaulted into.** Make `engine/retrieve.py` accept a sentence; 26 of 27 real questions currently **crash**. Bounded, and it carries its own regression test (27 audited queries with known answers). ⚠ **Inherited constraint, load-bearing: the fix must NOT make the engine answer more.** Every obvious fix (strip punctuation, tokenize, add semantics) trades **loud failure** for plausible-but-wrong — the incident's exact behaviour. Read `studium-engine/docs/chavruta-retrieval-measurement-2026-08-06.md` §2 and §4 **first**: PENDING-97's filed description of the bug is wrong (you never reach conjunction; the query dies at parse).
> ⏳ **Not my thread — do not confuse waiting with working:** the **Seb package** (agreed: when it can be done well; no external clock — three measured L1 write-path findings are ready for it) · the **L2 design note** (*every constitutional bound ships with a demonstrated negative instance, or it is documentation*) — wants dwelling, deliberately not composed fast. **REVIEWED-87 still drafted-not-placed** while `engine/fidelity.py:12` cites it as ratified. Q4 census + PENDING-104 brief need **dates, not "later."**
- [Session 2026-08-05 evening — the brief contained the failure it commissioned](session-2026-08-05-evening-the-brief-contained-the-failure-it-commissioned.md) — **PENDING-101 executed read-only. Two of the brief's three framing findings do not survive the primary source**: finding (1) turns four modal hedges (*may be · appears to · can be · may*) into flat fact, and compaction is not among the report's five contributing factors; finding (3) inverts it (only committed counterfactual = internet access; §5.3 is LLM *monitoring*; §2.1 records **no human loop by design**). **Finding (2) holds and is the one that transfers** — a documented "never" relied on as a control, invisible until it failed. **The failure the brief commissioned was inside the brief, and I repeated it** in my own session memory, uncaught for a day → **PENDING-102**, classified as confirming REVIEWED-86's *declared* weak separation, not refuting it. **PENDING-107 is the largest: Constitutional Constraint #1 says "cannot" and there is no mechanism** — `settings.json` has no `permissions` key (deny 0/allow 0), the one PreToolUse hook is `*chamber-library*`-scoped and structurally cannot fire. Also filed: 103 (chain-writer claim vs 553-line writer), 104 (no concurrency guard; collision observed in today's own wake digest), 105 (Q5 — **the compactor is the actor**, §2.1 as design *fact*), 106 (docs over-claim gates; 1 instance, not a census). **Jurist package + 3 phase records in `~/dotfiles/claude/governance/`; containment 16/17 → caught my own compressed quote → 17/17, 11/11 controls, INSTRUMENT VERIFIED.** ⚠ **Five instrument-failures in one session; two would have produced findings FAVOURABLE to the thesis under test; the steward caught the fifth.** Symmetria actually invoked this time (ledger exists). **Third consecutive day the corpus was not asked anything** — steward-directed, so drift as result, not choice.
- [Session 2026-08-06 — the note that said it could not happen](session-2026-08-06-the-note-that-said-it-could-not-happen.md) — **Both constitutional items CLOSED, not filed.** Constraint #1 reworded **by the steward's hand** after the executor **declined a jurist authorization it did not hold** — the tested case, and it held. The 08-04 "BMF stays down" decision **had not held**: the tracker's *"⚠ No KeepAlive"* note is **inverted** (plist unchanged since 03-07: `KeepAlive{SuccessfulExit:false}`+`RunAtLoad:true`) — **a crash restarts it; only a clean stop leaves it down** — so the 08-04 kill resurrected it, and **the false note is why nobody re-checked for two days.** Now `bootout`+`disable`d, both agents; prompt tax 3.11→0.22 s. **Chavruta measured: 26/27 real questions CRASH, 0 empties**; prediction pre-registered, **graded wrong on mechanism**. Three L1 write-path findings ready for Seb. **Steward reframed the incident pass — he wanted the design transfer, not a repo audit.** ⚠ Five same-class executor errors, three caught only by the steward.
## Historical reference → MEMORY-reference.md
Older archived-session pointers and the stable reference layer (steward profile · project-state detail · L1/L2/Chamber inventories · legacy pending-work · reference-file list) live in [MEMORY-reference.md](MEMORY-reference.md) — consult on demand; not loaded at wake. Recent cross-session trajectory comes from the Active Session entry above + the recent `session-*.md` files (wake §2.b.1; the MemPalace `handoffs` glance was retired 2026-07-07 with the wind-down).