REVIEWED-128 cond. 3 binds 'not read for content before 2026-09-08'. I read a rejected line at 19:49 while diagnosing the wrap seam. Diagnostic intent is irrelevant to the condition, which is about the reading. ⚠ Conditions 1 and 2 were made STRUCTURAL — log_rejection() cannot record an accepted line, a DEFERRED-DECISION makes retention an act. Only condition 3 was left to care, and care failed inside a day, in the session whose central finding is that care is not a mechanism. ⚠ And it surfaced exactly the signal the fortnight was meant to arbitrate: two seam rejections, both at the ceiling (10 and 11 against a cap of 9), which is the jurist's own clustering test. NOT ACTED ON. A cap raised on evidence gathered in breach of the condition protecting that evidence is worse than a cap left wrong. Recorded so the steward and jurist decide its worth rather than discovering later that the executor knew. PENDING-160 gains its sixth instance, and it is the sharpest: the wrap seam's failure was PREDICTED and the prediction was wrong about every part of the mechanism. A heartbeat proved the hook always fired. The detector sought a user-typed command; the wrap arrived as prose plus a Skill call. And the earlier CORRECT fix is what blinded it — a shape no control can see, because the boundary moved when the code changed. Session record, memory index, ledger and daily note amended: the wrap's literal question was answered in-session and is recorded as answered rather than left standing. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01J6hZXNYSxEfZseBGTni4sf
22 KiB
name, metadata, permalink
| name | metadata | permalink | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
claude-memory/memory |
Claude Code Memory
Standing preferences
Entries keep their rule inline when they fire at a moment I would not recognize as needing a lookup; they shrink to a pointer when the trigger is loud enough that I'd open the file anyway. A ⚠ constraint always travels with the workaround it limits.
Rules that fire silently — keep these in front of me
- Fowler's rules for quotation — single quotes primary, double for nested, logical British punctuation order. All writing.
- Canadian spelling in ARC prose — centre/colour ("almost EU"). Draft all steward-voiced prose this way; corpus "center" = autocorrect drift (cleanup open).
- Close thoroughly — no frequent deferrals — frequent deferrals ARE how the cloud accumulated. Close ALL of a block that's closable-now; for the rest, name the specific dependency.
- Shorter, concentrated sessions — ONE tightly-scoped high-leverage bite taken all the way, then wrap; hold the rest as ranked horizons.
- Constitution-as-block, then pull-based corpus — finish the constitution as one block FIRST, then corpus-into-spec pulled by what each engine phase needs. Bounded question → bounded answer; keep open-thread count LOW.
- Removing a claim ≠ removing the reliance — cutting an unsupported sentence can hide the gap; the dependency survives, now invisible. Test: does the conclusion still need it?
- Derive the rule from the consumer, not the survivor — choosing between two disagreeing implementations is selection, not derivation. Derive from what a CONSUMER must do.
- Rank on fields you actually write — a consumer ranking by an evaluative field nothing populates degrades to trivial order while claiming to rank. Verify scoring fields end-to-end; prefer signals already captured.
- The central path — answerability, not purity — the contamination recursion is probably irresolvable, so bind the claims, don't certify the parties. Route by claim-type: checkable → produce the check + a falsifier; judgment → disclose standpoint in one line, decide, record; undecidable → name it open. One layer, then act — never audit the audit.
- Notes are part of the work — footnotes/endnotes are integral: KEEP+CONVERT (
<sup><a>→[^N]), never drop on graduation. - One-shot instruments are proportionate — a measurement answering a question asked once is NOT a directive violation; its counterfactual is an assertion, not a durable tool. The violation is re-writing what's already banked (rule of three → ladder). Too few promoted, not too many built.
- A checkable question over a self-authored corpus — counting events in a record I wrote is self-report with extra steps. Before leaving any question: who authored the corpus it reads, and would a different author have written it differently? Narrow until it turns on what entries literally say.
- Grounding finds my errors, not my support — three packages running, every omission cut AGAINST my own case. Ground in TWO passes: (1) what did I get wrong? (2) what already says this? Search the register for the CONCLUSION, not just the citations. ⚠ Quote from the FILE, never from the relayed message — placement adds and cuts.
- Resurface banked notes before re-deriving · Checkable claim surfaces bugs · Census by mechanism, not proxy · Completion is a tripwire · Trust prior pass frame — the five epistemic disciplines. Kernels: read the banked note before re-deriving · a checkable claim over a soft classification is itself a defect-detector · census by RUNNING the real pipeline · the feeling of "done" is the cue to verify the tail · re-run a prior verification at the scope of your extension. ⚠ Also carried as Symmetria §3 flags — two surfaces, deliberately: §3 loads only when Symmetria is invoked, so these stay here for sessions where it isn't.
Loud trigger — pointer suffices
- Chamber work: ground in constitution + charter + runbook FIRST — any chamber work or talk about it begins there (incl.
reanchor:). Repo CLAUDE.mds are pointers, not state; corpus claims come from a self-tested tool, never a hand grep. - Governance files are dotfiles symlinks — Edit/Write refuse to write through a symlink, so edit the real
~/dotfiles/…path when appending —PENDING/REVIEWEDonly. ⚠ 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).~/CLAUDE.md/~/REVIEWED.md/L2 =[ESCALATE], steward's hand — a jurist sign-off does not authorize one. - Verification ladder — the named instruments; reach for the gate the claim's shape demands instead of re-deriving one. ⚠ FROZEN — REVIEWED-123 (2026-08-17): no additions, rewordings, removals or reorderings, from ANY source, whatever its authorization, until the trial is graded (N-now 51/84 as of 2026-08-25 — up 2 from 49 on 08-24; the counter is a 30-day ROLLING WINDOW per PENDING-147, so it rises and falls as transcripts age in and out. Re-measure, never relay:
len(glob('~/.claude/projects/-Users-davidglidden/*.jsonl')), the trial's own method atgovernance-drift-check.py:331). Entries earned meanwhile queue in PENDING-141's owed-entries list (4 rows). Reading it is unaffected — that is the point of the freeze. - Skill-harvest register — canonical home for proposed skills (governed analog of PENDING.md for tooling);
/wrap-up§1.6 proposes, steward authorizes. Rebuilt 2026-08-07 from the archive: 154 live proposals, grouped by kind, each with an exactarchive:L###pointer. ⚠ The 2026-08-01 compaction was lossless but illegible (55 scraped header rows, 95% of cells cut mid-word) — the count it advertised, 177, was never the number. ⚠ THE STROKE-2 BATCH IS AUTHORIZED BUT SHOULD NOT BE EXECUTED YET — PENDING-141. 41 rows stampedS2are authorized (2026-07-19, execution not a ruling) and 22 areS2?(unsettled). BUT appending them triples the ladder from 20 entries WHILE a pre-registered trial is measuring whether the ladder is reached (baseline 14%, graded at 84 transcripts). Ladder size is an uncontrolled variable in that design, so executing the authorized batch would confound the only check behind REVIEWED-95's causal claim. ⚖ RULED — REVIEWED-123 (2026-08-17): AUTHORIZED (a) HOLD, on six conditions, and the freeze is GENERAL rather than S2-specific. Grading does NOT authorize the append — the batch returns for a ruling. Report N-now at every wake until lifted; 30-day review is a liveDEFERRED-DECISION. ⚠ Filing new proposals now requires a declared firing moment (/wrap-up§1.6); one that cannot name it is documentation and must say so. - Copy-paste-clean governance drafts — draft PENDING/REVIEWED blocks as plain fenced markdown; display formatting leaks into the placed record.
- Verify-before-compose hook — chamber constitutional writes are BLOCKED without
<!-- GROUNDED-IN: … -->+ verbatim Grounding. Don't fight the block. - Tool review after each use — review every tool we built after each run, success OR failure. PASS-BUT-FALSELY is the priority signal. Log:
chamber-library/_curation/tool-evolution-log.md. - Every canon doc's source lives in Chamber Sources — a canonical's source = whatever
resolve_archived_sourcereturns, never the master library or a path in frontmatter. Read the banked record before calling a mismatch a defect. - Engine sources graduate to the permanent chamber — work added for the engine ALSO becomes permanent collection unless stated otherwise; take it all the way (clean→verify→graduate→catalogue→sidecar). Never leave staged.
- Bulk indexing runs in tranches, gated on READBACK — never one multi-day mine; order by criticality; prove each tranche by reading back, not by write-success (933k drawers once stored fine and were unreadable). Steward rule 2026-05-04, learned on MemPalace, applies now to engine corpus work.
- Studium Engine charter — the engine's constitutional doc. Read before building. · Sixtus-V collaboration — build freely, surface only vision-forks; constraint-candidates = 3rd governed instrument. Studium-engine only.
- CapableHands standing authorization — M4 mini
david@10.0.1.136durably authorized for remote OCR/inference; don't re-ask (steward 2026-07-01). - Steward's notebooks + transcription provenance — three notebooks (Journal I B6-slim · A6 field book · A6 "real life"); provenance cites the NOTEBOOK, not the photo; dates are a red rubber stamp; file under the date RECORDED, arrival is metadata. ⚠ Ask each notebook's own archiving form.
- Typography palace — query via CLI — ~20 type masters at
~/.mempalace/palace-chamber-typography;mempalace --palace <that> search "…". For ARC typography; don't re-ask where it lives. - Steward maps live in ~/dotfiles/maps — a map = an artifact David reads directly to orient. Write to
~/dotfiles/maps/, symlink to Desktop, never straight onto the Desktop. - Plane coordination workflow — CENTRAL to steward↔Seb:
app.plane.so/capablemind, thin effort-tasks[BM #N]over canonical GH issues. ⚠ BBF = BetterBridge product, NOT the board. - MemPalace is an unaffiliated stopgap — third-party; don't conflate with BMF/CapableMind. MemPalace PRs await MemPalace's maintainers, not Seb.
- The maturation of the chamber — a dialogue — the 2026-06-28 exchange on the chamber's telos (fidelity-without-trust; reading-is-unsolvable-is-the-feature). Companion to project-studium-engine-telos-chamber-of-voices.
Canonical Workstream Trackers
Read the tracker for any active workstream at /wake-up before composing the briefing. Append substantive moves at /wrap-up — to the chronological log, not only "current state". Per feedback-canonical-workstream-tracker-discipline.md.
- Chamber as versioned releases — THE GOVERNING FRAME for all library work. The 2000-year Chamber as versioned releases with soft borders, each serving a PURPOSE; scope every library bite through this. Open decision: which purpose anchors V1. Read the file, not this line — it holds the reframe that resolved the purpose/scope paralysis.
- Studium Engine — canonical engine tracker. N0–N2 + R0 +
voice_stampbuilt; corpus 14 sources, trilingual, fleet 9 suites / 285. fr cell all but closed — 8 grounded (1 A + 7 B),ratio_A_to_BVOID until PENDING-134 lands. ⚠ PENDING-131 (c) never bound the engine (chunker.pyhaschar_rangesince Cluster A). NEXT: rule PENDING-134 — last blocker is a steward MCP restart. - Studium engine telos — the chamber of voices — the ultimate goal, above the build plan: the childhood chamber of hero-voices, rebuilt so the counsel is accountably theirs. Why verbatim fidelity is load-bearing.
- The Chamber touchstone — the why — seven questions to test work against when lost in the trees. Read at Step 0 of any chamber work. Holds no state; does not decay.
- The Chamber vision is NOT in one place — it lives in seven sources across two repos + memory. A single home would become an eighth unless it supersedes or points.
- L1 reliability — canonical L1 tracker. BLOCKED ON SEB (PENDING-94); BMF is down and staying down. The replay has never resumed, only restarted (
minCursoris a minimum over 11 modules, two never participate ⇒ every start rebuilds from seq 0). Completion is gated by uninterrupted run length, not rate. Recall never worked either (retrieval_count = 0). Read the tracker before ANY L1 work — walked past once on 2026-08-03. - Instrument censuses — have our gates ever fired? — census 01 (has each gate a real negative instance? → decay, not construction, is the failure mode) + census 02 (has it fired at all? → the record divides by whether a human invokes it). Both pre-registered. Read before trusting any gate's silence.
- ARC open-work register — the single code-verified source of truth for what is OPEN on ARC. Read THIS for remaining ARC work, not the chronological tracker. · ARC — chronological record; Stage G DONE/SEALED (GPG
ac0a7ee) — reactive mode governs. - Source library — link + dedupe — master ebook library
~/Documents/___The Library [ePub_AWZ3]/(2190 ebooks). GOAL: link chamber↔sources + dedupe; a real link needs EPUB/PDF internal metadata + edition-identity, not filenames. - Sidecar typology — protocol-dependent reading-indexes —
.meta.jsonstructural sidecar = PROTOCOL-NEUTRAL (the graduated bar); reading-indexes = PROTOCOL-DEPENDENT and probably PLURAL — don't design the schema yet. - Character-as-image hazard — EPUBs rendering diacritics as inline images are SILENTLY MUTILATED by image-drop. Mechanism built + wired; per-source glyph-maps still owed. VIEW the glyph; map to SOURCE form.
- Making sequence source set — COMPLETE against the ReadingList (reconciliation-verified). Sourced ≠ ingested. Read before any Making/studium source work.
- Studium = CM's unfettered sandbox — experiment freely on library/engine without risking CM's runtime; breakthroughs transfer back. Steward-framed 2026-07-08.
- Be (laundromat) — Skemantix startup (Seb+David) funding CapableMind's ladder; bridge, not venture. Decisions LOCKED. Pre-revenue WTP gate = renovate Pat → charge her; no new spec until it clears ⇒ nothing for executor on be.
- The Fool — Tarbuckle — THE ACTIVE WORKSTREAM. Bones derived once 2026-08-25 (peak SUCCESSION 96 · dump ABSENCE 8); name + soul sealed, never regenerate (soul). Doctrine =
BUDDY-PATTERN-jurist-draft-v2-2026-08-22.md; §8 has no blanks (20 min · frequency UNKNOWN · empty-window consumes · body correlates with nothing). NOTHING WIRED — nostatusLine, no script, §13.1 spec unwritten. Trial 09 VOID (REVIEWED-124), void now recorded in all three docs. ⚠ Subject matter lives in CapableMind-AI, instruments in dotfiles, and nothing in CapableMind points back. - Obsidian vault — from archive to practice — canonical vault tracker. Read it; it holds the four-purpose brief (steward, 2026-08-24) that is now the design brief. ⚠ The vault is NOT a git repo — it mirrors to
~/_Dev/david-root-and-branch-vault-git. The capture practice STARTED 2026-08-23 (two predecessors died at 3 and 4 entries; the measure is week four, not week one) — ⚠ this line previously read "has not been started", which went stale the day it began, and previously carried "paper bridge working" as state the tracker did not hold. Item 0 is new and steward-owed: photographed pages of physical BOOKS with margin notes — a different object from the three notebooks, untracked until 2026-08-24. - Chamber-typography — tracker not yet established; moves live in per-session memories (2026-05-11 →) +
project-chamber-cruft-restoration.md+project-chamber-typography-mining-plan-2026-05-15.md.
Active Session
🔑 TARBUCKLE IS WIRED — five surfaces, 125 controls (
6f0ccde3df5e4f7a9dbf2acdbc098a0e5c4cfbaded). body · mumble · wake seam · wrap seam ·! tarbuckle. §13.1 spec written LAST, per §12 — and four filed claims did not survive the substrate, which is why. ⚠ THE SESSION'S CENTRAL FINDING — PENDING-160, filed at the jurist's direction. Five instruments, five passing control suites, five failures on first real use. Controls verify that code does what was written; nothing verifies that what was written survives contact with a model, a shell, or a corpus containing its own reader. ⚠ Not a bad day — the class is months old:governance-mcp.py's own docstrings record it three times on 2026-07-28. ⚠ A FALSE PREMISE REACHED A PLACED RULING. REVIEWED-129: "the jurist has no substrate access" — false (governance-mcp.py, 14 enumerated files) — and the same sentence said "PENDING-82, still open", closed since 2026-08-08. Third instance in one day of a conclusion keeping its reasoning after that reasoning is falsified. Draft correction atclaude/governance/REVIEWED-129-AMENDMENT-1-draft-for-placement.md— JOINS, never replaces. ⚖ PENDING-151 RAN BOTH HALVES. Step 1 (executor, mechanical): 9 pairs, 19,479 words exact, and a confound in its own pre-registered measure — Claude longer 9/9. Step 2 (jurist, unblinded): A 4 · C 3 · B 0 — the null did not appear, criterion amended mid-read on the executor's own length header. ⚠ The surplus half of the question is unanswerable from this corpus. ⚠ THE WRAP SEAM FAILED, WAS DIAGNOSED, FIXED, FIRED, AND WAS THEN REJECTED — all after the wrap. The heartbeat proved theStophook was firing all along, so the silent-net prediction was right that it would fail and wrong about why. The detector sought the steward typing/wrap-up; the wrap arrived as prose + a Skill call. ⚠ The earlier, correct fix is what blinded it. PENDING-160's sixth and sharpest instance. ⚠ PENDING-162[ESCALATE]— the executor breached REVIEWED-128 condition 3 within seven hours, reading the rejection log for content while diagnosing. Conditions 1 and 2 were made structural; only 3 was left to care. ⚠ It surfaced the clustering signal (2 seam rejections, 10 and 11 words vs a cap of 9) that the fortnight was meant to arbitrate — not acted on, and must not be. 📌 STEWARD OWES: place the REVIEWED-129 amendment · rule PENDING-160 · restart Claude Desktop orgovernance_pairis absent · the §5 regrade ruling. ⚠ DELIBERATELY NOT FIXED: theSTEWARD OWES: place REVIEWED-127line now sits inMEMORY-reference.mdwith this block's predecessor. It is false, it is marked bySTATE-CLAIM: memory-index-claims-reviewed-127-unplaced, and correcting it is next session's agreed first act — carried forward rather than discharged as a side effect of this rotation.
- Session 2026-08-25 evening — Tarbuckle wired, and the gap controls cannot see — five surfaces built and every one failed on first real use; PENDING-151 step 1 + step 2 both run. NEXT: the §5 regrade gate — the control is already degraded and decays with every exposure.
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 — 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).
Index discipline (self-bounding — keep this file lean)
Wake-loaded live index; hard budget well under the harness load ceiling. Keep to: Standing preferences · Canonical Trackers as one-line pointers (chronological detail lives in the linked tracker files, not here) · Active Session · these pointers. Rotation + budget-breach handling are wired into /wrap-up (demote prior Active Session on promote) and /wake-up (truncated load = flag + trim). Back up before restructuring.
Compaction history relocated to MEMORY-reference.md at the 2026-08-20 wrap — pure history, not wake-critical.