memory: bundle accumulated 04-17/26 + lock ARC about-page architecture

Safety checkpoint before deep-audit Phase 0 of the ARC repo. Steward-authorized
commit-everything for rollback safety.

ARC architectural locks (2026-04-26 evening):
- Path 1 enfilade structure (separate Colophon and Lex items)
- 8-door enfilade locked: Colophon · Lex · Framework · Vignette · Attention ·
  Chamber · Tools · Now (+ Bio quiet link)
- Adsum and threshold-hic as two distinct texts on the reflowed About page
  (steward verbatim: "They are certainly not the same text")

ARC consolidation pass (canonical tracker project-arc-rework.md, +~700 lines):
fold 04-23 evening (Norris read), 04-24 (lex-method authored, posture cluster,
§XII Sidenotes, ARC CLAUDE.md cleanup), 04-25 (marks cluster, colophon-at-scale,
full Vico/Harrison lex-chain), 04-26 (chamber-library walk, cluster scaffolds,
canonical-tracker discipline surfaced).

Sibling-file integration: four 2026-04-26 frame files folded into the canonical
tracker (Integrations A/B/C/D) with INTEGRATED redirect notices retained as
audit trail.

New durable feedback memories:
- feedback-canonical-workstream-tracker-discipline (umbrella drift surfaced
  2026-04-26 by steward; proposes /wake-up + /wrap-up amendments)
- feedback-catalogues-stale-walk-trees (steward feedback on chamber-library
  catalogue currency)

Implementation plan drafted for the coming week: Phase 0 deep audit → Phase 5
cleanup, with steward additions on second pass (deep audit; Chamber v1 as own
browsable archive; clean rebuild of cluster sources rather than moving test
artifacts as canon).

Also bundled (untracked accumulation since 04-17):
- ~24 session memory + ledger files for 04-17 through 04-26 work
- ~10 feedback memories (BMF + ARC + working-method)
- 5 project memories (lex-as-method, strunk-white queue, plus today's four)
- 4 user memories (duality-rules, formation-practice, foundation-work, humic-layer)

Steward-side modifications also in this commit: ~/CLAUDE.md, bin/bmf-start.sh,
open-tasks.md, project-focus-april-may.md, session-2026-04-17 — all
pre-existing, not from today's session.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

CLAUDE.md

@@ -217,39 +217,35 @@ Body: what changed and why. Reference PENDING/REVIEWED items if applicable.
 
 | Project | Path | Notes |
 |---------|------|-------|
-| **CapableMind L1/L2** | `~/_Dev/CapableMind-AI` | Constitutional governance system. Read local CLAUDE.md for build state. Active seed: `~/_Dev/CapableMind-AI/docs/thinking/David/l1-reliability/l1-session-seed-pr.md`. Branch: `fix/replay-durability-contracts` |
-| **Animal Rationis Capax** | `~/_Dev/animal-davidglidden-eu` | Hakyll publishing system. Read local CLAUDE.md for technical context |
-| **Compass** | `'/Users/davidglidden/Library/Mobile Documents/iCloud~md~obsidian/Documents/David, root-and-branch/00. Compass'` | Personal operating system (Obsidian vault). Read-only reference |
+ | **CapableMind L1** | `~/_Dev/CapableMind-AI` (playbook) + `~/_Dev/BetterMemories.io` (runtime) | **L1 is PRIMARY focus through end of May 2026.** Steward has joined Seb on L1 production work; Seb spread too thin to carry alone. Runtime on `main` @ `decbdee`+. Current audit artifacts: `docs/thinking/David/l1-reliability/l1-deep-audit-plan-2026-04-19.md` + `l1-ingestion-forensic-2026-04-19.md` + `l1-recall-quality-baseline-2026-04-19.md`. |
+  | **CapableMind L2** | `~/_Dev/CapableMind-AI` (docs only) | **PARKED through end of May 2026.** No L2 governance advancement, no new invariant work, no
+   constitutional proposals. L1 reliability is the dependency condition. L2-adjacent questions arising from L1 work: note, don't pursue. || **Compass** | `'/Users/davidglidden/Library/Mobile Documents/iCloud~md~obsidian/Documents/David, root-and-branch/00. Compass'` | Personal operating system (Obsidian vault). Read-only reference |
 | **Dotfiles** | `~/dotfiles` | Dotfiles for easy restore and setup |
 
 When navigating into a project directory, always read its local CLAUDE.md first for current state, build sequences, and terminology.
 
-### L1 Active Workstream
-
-| Item | Status |
-|------|--------|
-| Branch | `fix/replay-durability-contracts` |
-| Active seed | `~/_Dev/CapableMind-AI/docs/thinking/David/l1-reliability/l1-session-seed-pr.md` |
-| L1 reliability artifacts | `~/_Dev/CapableMind-AI/docs/thinking/David/l1-reliability/` |
-| Bug A | Reprobe condition mismatch — ✓ fixed, confirmed working |
-| Bug B | Schema migration non-idempotency — ✓ fixed (job-store.ts, checkpoint.ts, dedup.ts) |
-| Bug C | Teacher worker retry storm — `[FIX]` authorized, in PR scope |
-| Bug D | Idle stall during replay — `[FIX]` authorized, next PR |
-| PR target | Three bugs · full tests · CHANGELOG · three GH issues · audit committed to repo |
-| Next step | Canary fires → epistemic audit (v2) → PENDING.md findings → steward review → file issues → PR |
-| Collaborator | Seb (L1 territory owner — on vacation) |
-| **Dependency chain (revised 2026-03-27)** | |
-| — L1 reliable → | Chamber Phase 3+ / training pipeline / recall-dependent work |
-| — Chamber Phase 1-2 → | Independent of L1 (manual orchestration, source texts present) |
-| — L2 governance (AF-7, P-GOV series) → | Independent of L1 |
-| — L1 reliability | Seb's territory. David's time goes to governance and Chamber. |
-| PENDING-1 | Executor Agency Directive — AUTHORIZED, integrated into this file |
-| PENDING-2 | Silent degradation audit — COMPLETE (43 findings), authorized for follow-on work |
-| PENDING-3 | Factory schema scope extension — ACKNOWLEDGED, in PR scope |
-| PENDING-4 | Bug D idle stall — AUTHORIZED, next PR |
-| PENDING-5 | Transport bridge backoff wiring — AUTHORIZED, next PR |
-| PENDING-6–9 | Pairing manifest · Phase 2 failure · fire-and-forget · hysteresis — awaiting steward review |
+### L1 Active Workstream (2026-04-19)
 
+  | Item | Status |
+  |------|--------|
+  | Runtime repo | `~/_Dev/BetterMemories.io` on `main` @ `decbdee`+ (SQLite+LanceDB storage backend operative; SurrealDB retired) |
+  | Playbook repo | `~/_Dev/CapableMind-AI` on `main` |
+  | Current audit | Deep audit of first-successful-ingestion state per `l1-deep-audit-plan-2026-04-19.md` |
+  | Audit artifacts produced 2026-04-19 | `l1-ingestion-forensic-2026-04-19.md` (Part 1: entity bottleneck + error taxonomy + threshold-governance frame)
+  · `l1-recall-quality-baseline-2026-04-19.md` (Part 2: recall broken end-to-end; H1-H4 localized to read path) · `forensic-artifacts-2026-04-19/` (log
+  snapshot + raw recall results) |
+  | Headline bottleneck | O(N²) per-pair LLM inference in `inferRelationships` (`src/modules/entity/pipeline.ts:719-741`) — code-reviewer verified at 0.92
+   confidence. Fix space: options A-F surfaced, C+D+E combinatorial recommended |
+  | Headline recall issues | H1 confidence clobbered in read path · H2 vector queries return 0 on vault content · H3 temporal stats fallthrough · H4
+  working-memory injection surfaces hook events as recall results |
+  | Architectural finding | Module health (`status: ready`/`healthy`) is structurally decoupled from recall correctness — violates honest-degradation
+  invariant at design level. Captured in `feedback-bmf-health-vs-recall.md` |
+  | **Territory** | L1 is **shared work** between Seb (code ownership) and steward (audit / diagnostic / PENDING drafting / test-branch diagnostic).
+  Steward joined Seb on L1 production because Seb spread too thin to carry alone |
+  | Next step | Ship Part 1+2 audit bundle to Seb · optionally run diagnostic-only test branch to localize H1/H2 to exact lines · then Seb drives fix PRs
+  with ultrareview verification · L2 remains parked throughout |
+  | PENDING items 1-9 | From March sprint; some superseded by the 2026-04-14 storage-migration PR and subsequent work. Reconcile with `~/PENDING.md` when
+  next touched |
 ### Completed Workstreams
 
 *None yet — first entry will appear when the L1 PR merges.*

bin/bmf-start.sh

@@ -16,6 +16,8 @@ set +a
 export BM_PORT="3011"
 export BM_TEACHER_TRANSPORT="api"
 export BMF_MCP_TOKEN="bm_key_REDACTED"
+export BM_DATA_DIR="$HOME/.capablemind/data/mindfabric-00"
+export BM_INSTANCE_NAME="mindfabric-00"
 
 # Ollama needs to be reachable
 export OLLAMA_HOST="${OLLAMA_HOST:-http://127.0.0.1:11434}"

claude/memory/MEMORY.md

@@ -1,17 +1,100 @@
 # Claude Code Memory
 
+## Active Session
+- [Session 2026-04-25 — Marks cluster committed + lex-of-ARC located as colophon-at-scale + full lex-chain restored](session-2026-04-25-marks-committed-colophon-at-scale.md) — The marks cluster's 25 recognitions committed in dialogue (lex-method validated as form across content types — second test passed). Steward located the lex-of-ARC architecturally: *"a colophon of great scale."* Architectural breakthrough: §0 threshold candidate shifts from Warde to colophon (yours, not borrowed); §1 typology probably doesn't need new slot; naming becomes inheritance; publication question dissolved. Steward then directed return to Vico §240 / Harrison Ch 5 to register the **full lex-chain** — I had been holding only the gathering-sense; missed the pivot (citizens/comitia/solemnizing wills), lexification, *auctores*, dislexification. Manutius the Younger's *Orthographiae Ratio* (1566) added to chamber-library; Teall 1891 placed. 13 recognition-register patterns saved as durable lex-method method. **Pulling thread: About-pages restructure under today's locating; Path 1 (lex alongside colophon) vs Path 2 (lex as expansion of colophon).**
+
+## Archived Sessions
+- [Session 2026-04-24 — Lex-of-ARC posture cluster committed + AldineXXI §XII Sidenotes theorized + ARC CLAUDE.md cleaned](session-2026-04-24-lex-posture-committed-xii-sidenotes.md) — Full day of lex-method architecture. Harrison Ch 5 / Vico §240 as lex substrate (gathering-sense only registered); Bringhurst Ch 3 consult on italic/bold; density-exception ruling; 8 posture voices gathered with steward-committed recognitions; AldineXXI §XII committed (closes July 2025 awaiting-governance flag); ARC CLAUDE.md rewritten 420→197 lines.
+- [Session 2026-04-23 evening — Norris *Between You & Me* read](session-2026-04-23-evening-norris-read.md) — Tired steward deferred projected agent-circle authoring ("keep it close"). Read Norris's *Between You & Me* in three chunks for ARC style-guide; gather-lex deferred to next session.
+- [Session 2026-04-23 Sant Jordi afternoon — ARC typology catalogue complete](session-2026-04-23-arc-typology-catalogue-complete.md) — 14 of 14 §1 types LOCKED + Chamber resolved as §2 apparatus + Harrison-as-humic-vocabulary-source surfaced + ARC framed as "expression of ligature".
+
+## Working with the steward
+- [Trust contract — drift-pattern tracking is the discipline](feedback-trust-contract-drift-pattern-tracking-is-the-discipline.md) — bidirectional trust; do not layer additional discipline-as-self-policing on top of clear directives. Reading "extra rigor" into instructions is the contamination pattern in inverse form (over-discipline as approval-seeking). Take plain meaning.
+- [Formation practice — reverence to deep teachers](user-formation-practice-honoring-teachers.md) — steward considers formative authors his teachers (*"entering into discourse with the authors allows me to consider the ensuing transformations as being 'taught' by them"*). Receive humic references as teacher-relations, not citations.
+- [Rules-and-poetic duality — rule as mechanism, metaphor as mnemonic for dwelling in constraint](user-duality-rules-and-poetic-as-mnemonic.md) — working method "regardless of domain": rules serve skills/agents (mutual service), poetic layer functions as mnemonic so one dwells in the constraint and finds freedom *through* it, not *from* it. Preserve duality in any rule-shaped artifact; neither layer ornamental.
+- [Manutius — prefer Latin spelling](feedback-manutius-latin-spelling.md) — when referring to the Venetian printer, use "Manutius" not "Manuzio" (Norris's Italian). Leave spelling intact in direct Norris quotations.
+- [Catalogues stale — walk trees](feedback-catalogues-stale-walk-trees.md) — *"that catalogue is stale (any catalogues you may come across will be stale)"* (2026-04-26). Any catalogue/index/README in chamber-library is presumed stale. Walk actual directories for inventory. Cousin to canonical-library-not-checked-first.
+- [Canonical workstream trackers must be read at session start](feedback-canonical-workstream-tracker-discipline.md) — **2026-04-26 umbrella diagnosis.** Four consecutive sessions (04-23 evening through 04-26) opened without reading `project-arc-rework.md`. The five lower-level "canonical-library-not-checked-first" instances today were symptoms of one pattern: *working-without-canonical-roadmap.* Fix: at every `/wake-up`, read canonical workstream trackers (project-arc-rework, project-focus-april-may, etc.) for any workstream the session will touch — not just session memories + MEMORY.md index. At every `/wrap-up`, fold substantive moves into trackers, not just session memory. New project files are integrations of the tracker, not parallel siblings.
+- [Chamber-library humic pillars noticed 2026-04-26](project-chamber-library-humic-pillars-noticed-2026-04-26.md) — registrar-form notice from steward-directed walk: Bachelard concentration (6 works in phenomenology — humic in his own register); Berger as corpus-of-corpora (~13 works, candidate apostrophic pillar); Jaccottet:Handke:Lichtenberg/ folder is unfiled-recent per steward (housekeeping, not architectural). Awaiting steward recognition.
+- [Chamber-library cluster scaffolds 2026-04-26](project-chamber-library-cluster-scaffolds-2026-04-26.md) — steward-authorized scaffold for the six remaining clusters (music-and-measure, mark-not-made, apostrophic, public/private genre, craft-and-tool-fitness, practice-across-life) with present-and-touching voices for each + Bachelard pull flagged for humic-layer framing. Steward framing: *"Wallace Stevens's jar on the hill. Hic."* Scaffold is the placing-act; recognition belongs to dialogue. Awaiting steward recognition pass per cluster.
+- [About-pages decision frame 2026-04-26](project-about-pages-decision-frame-2026-04-26.md) — Path 1 vs Path 2 frame + three deeper resolutions: (A) **three-register frame** (threshold / colophon / lex — different scales, same light, redundancy dissolves); (B) **door consolidation** (Influences→Lex, AldineXXI+Typography→Framework, Navigation+Attention→Attention, Patterns removed, Vignette earns own door); (C) **8-door set**: Colophon · Lex · Framework · Vignette · Attention · Chamber · Tools · Now. About main as **threshold of ARC (why-and-how, ARC-first-then-David)** is the right form, not bio-paragraph. Rewrite work flagged for Framework + About + Chamber + Attention. Awaiting Path 1/2 + threshold-draft.
+- [Chamber rewrite frame 2026-04-26](project-chamber-rewrite-frame-2026-04-26.md) — **revised after steward correction:** keystone shift is v1 (Simulation, archived) → v2 (Source-Aware, current). v1 = 220+ Claude-prompt voices, fictional bibliography (° ~ † § ∞), Borges-tradition canon, archived per steward. v2 = constrained retrieval against chamber-library, verifiable citation at passage-level, bounded knowledge, scoped silence as first-class, warrant taxonomy (W_DEM/W_INF/W_TRD) with transitive minimum, Disciple model, contamination-mitigation as commitment, working register *"rigorous reading and thinking."* Built on CapableMind; ARC is publication-face. Rewrite must announce the shift (not gloss), describe v2 in its register, frame v1 work as preserved-and-clearly-marked archive. /chamber/canon/ and /chamber/deliberations/ become v1 archive pages. Drift logged: read validation report not source-aware design-thinking doc when asked "what is it becoming."
+- [Strunk & White — vocabulary pass queued for ARC](project-strunk-and-white-vocabulary-pass-queued.md) — short reading queued post-Norris. Scope: names for what steward already does by feel. Read *against* Norris, not as source. Known caveats: Pullum's critique, S&W prescriptions don't match steward's register.
+- [Lex-as-method for ARC specs](project-lex-as-method-for-arc-specs.md) — **architectural commitment 2026-04-24.** All ARC/CapableMind specs are sheaves of formative voices; binding is diagnostic (names what's already there steward may not yet see), not generative. **Form: hybrid Shape A (rule+pillar-voice for skills/agents) + Shape C (voice-body + rule-marginalia for dwelling). Container: sidenotes, theorizing AldineXXI §XI "awaiting governance" question; single markdown source → dwelling-HTML + rules-YAML via site.hs extraction.** Scope: style-guide first, then typology/§2/AldineXXI/L2-adjacent. Substrate: Harrison Ch 5 / Vico §240. Role: **registrar, not author.**
+
 ## CapableMind L1 (BMF)
-- **Storage migration: SurrealDB → SQLite+LanceDB COMPLETE + bottlenecks fixed + RECALL VALIDATED** — branch `trial/storage-sqlite-lance`, 30 commits ahead of main, HEAD `4ef8f5b`. All 13 modules + factory + meld + reconciliations + graduation + lifecycle wiring ported. Plus 5 bottleneck fixes shipped 2026-04-15 (#154 entity persist transaction wrap, #155 HNSW build, #156 Ollama keep_alive, #157 LanceDB compaction, #158 cosine distance formula). Recall live-tested on real vault data: sub-second response, confidence 1.0 on top match, all 4 fixes confirmed working end-to-end. See [session-2026-04-15-recall-symmetria.md](session-2026-04-15-recall-symmetria.md) and [session-2026-04-14-migration-completion.md](session-2026-04-14-migration-completion.md)
-- **End-of-pass artifact**: `~/_Dev/CapableMind-AI/docs/thinking/David/l1-reliability/2026-04-14-migration-completion-pass.md`
+- **FIRST SUCCESSFUL VAULT INGESTION on new stack completed 2026-04-18 → 2026-04-19.** Trial merged into main (`adf4743`); main is canonical now (HEAD `decbdee` + Seb's ongoing commits). Circle networking features operational: peer-mesh roster (`24e0186`), keystone forwarding (`bb390a2`), auto-pairings on join (`eb4cbd7`), staff-token auth (`105c4dd` plan-007), cm-world onboarding script (`47be814`). Ingestion: 7,220 items (notes + relationships), 14,355 entities, 0 failed. Recall operational (confidence 1.0 on test). Steward named milestone: *"years of 'what if we could' to working... this was the foundation."*
+- **Known residuals (next session: deep audit)** — entity cursor 4,594 behind (error_count 4,595, mostly deferred-timeout accumulation); vector error_count 1 → 221 overnight (root cause unknown); new `keystone:observe` manifest.json ENOENT race (filesystem, non-fatal). Entity-relationships stage bottleneck: 14–18 min per batch of 8–9 entities (persist is fast — #154 fix holds). See `l1-ingestion-diagnostic-2026-04-18.md` + `l1-deep-audit-plan-2026-04-19.md`. Commented on #65 (umbrella issue predicted this pattern).
+- **Audit 2026-04-19 root-cause — entity bottleneck**: O(N²) per-pair LLM inference in `inferRelationships` (`src/modules/entity/pipeline.ts:719-741`). Slots auto-promote SIGNALING → BOOTSTRAPPING at startup ("no teacher, Ollama available"), populating chain with `[rules, local(Ollama)]` (bootstrap.ts:1978-1984). Each co-occurring pair triggers `slot.infer()`; deferred-retry accumulates events (8 → 188 entities), pair count grows quadratically (28 → 17,578 pairs), per-entity cost grew >300x during ingestion. Evidence: 5,335 SLOW entries with relationships=30-39 million ms for 58-188 entity batches. Entity cursor stopped at 05:07:52 UTC; last_processed_at 05:51 verified success-only (not heartbeat) per `base.ts:124-125`. Full write-up: `l1-ingestion-forensic-2026-04-19.md`. Mechanism verified by code-reviewer at 0.92 confidence.
+- **Audit 2026-04-19 adjacent findings (via code-reviewer + architect-review)**:
+  - **218 vector HTTP-400s are silent drops** — notes exceeding nomic-embed-text context window. Path: `vector/index.ts:121-142` → `base.ts:139-144` non-deferrable → `cursorPosition++` without retry. 218 vault notes confirmed absent from semantic search. Separate from the entity bottleneck, needs Seb's attention.
+  - **`events-013.jsonl` missing from logchain** (2026/04/18 dir): files 002-012, 014-019 present, 013 absent, 10-event delta vs logchain current_seq. Code walk found no rotation/compaction path that explains deletion — reads as real-loss-shaped. Needs Seb's read on logchain file semantics.
+  - **Option E — slot graduation as the lever** (architect-review, structural): `src/inference/slot.ts` already has SIGNALING/BOOTSTRAPPING/GRADUATED/DE_GRADUATED machinery designed to reconfigure chains under conditions. Treating slots as fixed cost when they're designed to adapt is the framing gap. Question for Seb: does graduation contract model load-cost asymmetry between slots (keystone:classification cheap; entity:relationship expensive)? If not, that is itself an architectural finding.
+- **Audit 2026-04-19 Part 2 — recall is substantially broken** (verified by general-purpose interpretation agent at 0.72 confidence, then two storage probes). Yesterday's "recall operational" claim does NOT hold today. Of 15 designed queries: 8 empty (including known names Lune, Kai, Nuria), 6 junk, 1 honestly empty. **Four headline issues, two of which the probes reshaped:**
+  - **H1 (REFUTED at extractor, CONFIRMED at recall read path)**: entity storage has 1,545 entities with **avg_conf 0.9908, min 0.632, max 1.0, no confidence-0 rows** — extraction is healthy. But recall API returns those same entities with confidence 0 (e.g., "Kai Aureli — Health Record" storage:1.0 → API:0). Defect is in the recall read path between `mapEntityRow`→`entityToResult`→`buildEnrichedResults` in `query-router.ts:545`, not in the entity pipeline. Probe 1 confirmed via direct SQLite query of `entity.sqlite3`.
+  - **H2 (REFUTED at storage, CONFIRMED at query execution)**: vector storage has **23,696 chunks, all facet_id=default, lifecycle=active, model=mxbai-embed-large** — storage is populated. But vector queries return 0 on vault-content terms. Defect is in query execution (BM25 dispatch, query embedding, or similarity threshold in `vector/queries.ts:73-88`), not in ingestion or storage. Probe 2 confirmed via direct SQLite query of `vector.sqlite3`.
+  - **H3 — Temporal stats fallthrough**: temporal module returns `total_nodes`/`total_edges` payloads regardless of query intent (monotonically incrementing across queries). Query-type parser routes text queries to stats handler.
+  - **H4 — Working-memory injection**: `query-router.ts:268-290` synthesizes `compositeScore:0.9` results from session-hook events, surfacing the agent's own tool activity as "recall results."
+- **Probe-discovered findings (after probes 1-5)**:
+  - **Entity→vector linkage empty by design, not broken**: 0 entity_refs across 23,696 chunks is an emergent state from `vector/pipeline.ts:215-217` filter (only person/organization/place types populate entity_refs, from pre-classification `event.enrichment.entities`). 96% of vault entities (1,485 of 1,545) classify as `topic`, so the filter legitimately excludes them. **NOT a regression — design observation.** Usability gap underneath: filtering vector chunks "that mention Kai" is non-operational for personal-vault content because topic-type entities can't be used as filter predicates. Seb-territory design call, not a fix.
+  - **Vector cursor 14,482 vs 23,696 chunks**: NOT a mismatch. This was a clean ingest (2026-04-18 evening consolidation archived both old data trees before bootstrap; verified empty). 14,482 events × ~1.6 chunks/event average (long-form notes expand) = ~23,696. Normal chunk-expansion. Corrected 2026-04-19 after steward flagged; originally miscast as "possibly residue" — my drift, not a finding.
+  - **`explain(entity_id)` returns "No direct results found"** for valid entity row (`ent_topic_mo4nxdun_oh3n1f` verified in storage). Read-path broken at the explain tool too, not just recall.
+  - **Probe 3 cross-module clobber test — inconclusive**: preference is structured (category/key/value), not free-text searchable, so 0-return on free-text query is by-design, not confidence-clobber. Only entity + vector do free-text retrieval in this module set. Entity confidence-clobber localized to entity module's read path; can't be cross-confirmed against another module.
+  - **Probe 5 hybridSearch 0-return — four failure paths** (`vector/queries.ts:259-371`): (a) query embedding fails at `embeddingProvider.embed([queryTextStr])` line 62; (b) BM25 index not built — caught by `logNonFatal('vector:bm25-fallback')` at line 280, returns `[]`; (c) similarity results all below `minSim=0.35` threshold (`types.ts:91`); (d) both bm25=0 AND vec=0. Existing log at line 291-293 only fires when `searchMs > 200`, so fast 0-return queries are invisible. **Seb's single-line instrumentation fix**: unconditional log of `bm25.length`, `vec.length`, `facetId` at hybridSearch return point.
+- **Architectural finding bigger than any bug**: module health (`status:ready`, `system_status:healthy`) is structurally decoupled from recall correctness — honest-degradation invariant violated at design level. See [feedback-bmf-health-vs-recall.md](feedback-bmf-health-vs-recall.md). Yesterday's Reading Compass conf-1.0 result not reproducible today (no restart) — probe data suggests storage-query-path disconnect, not storage regression. **Steward recalibrated milestone gracefully**: *"my joy at reaching the milestone was premature I now understand... I can accept that. Now to make this work."*
+- **Raw artifacts preserved in `forensic-artifacts-2026-04-19/`**: `bmf.stderr.2026-04-19T0749.log` (43 MB), `recall-baseline-raw-results.md` (full query set + probe results).
+- **Audit 2026-04-19 Part 2b — DIAGNOSTIC TEST BRANCH RESHAPES THE FINDINGS**. Branch `diagnostic/recall-read-path-2026-04-19` on `BetterMemories.io` (commit `9042880`, not pushed). 5 `[DIAG:H*]` stderr logs added at critical decision points. Rebuilt, restarted via `launchctl kickstart`. Post-restart findings **reshape the recall baseline doc's conclusions — forensic + recall baseline need revision before shipping**:
+  - **H1 clobber confirmed but DOWNSTREAM of buildEnrichedResults**: DIAG shows entity extraction healthy (`rawConf=1 extracted=1` for "Chamber Notes"/"Chamber Overview") — but API returns same entities at `confidence: 0`. The clobber is in ranking/compression/diversity/compose, NOT in the query-router extraction. Seb's search zone narrows.
+  - **H2 WAS ENVIRONMENTAL, NOT A CODE BUG**: on AC, query embedding works (1024-dim vector in 72ms), BM25 returns 10, vector returns 5, recall produces real vault content at high confidence. The earlier 15-query baseline was run on battery with GPU inference suppressed → empty queryVector → empty results. **This recategorizes H2 from "read-path bug" to "silent-failure architectural issue": BMF returns empty on battery with no operator-visible reason.** Not a fix-the-bug; a surface-the-state design question.
+  - **H3 temporal instrumentation didn't fire** on content queries (`Kai`, `Chamber`, `typography`, "Ruby on Rails"). Either temporal wasn't dispatched, or edit location was wrong. Needs verification probe.
+  - **H4 working memory is empty post-restart** (`wmMatches=0` on all queries). Earlier "Recent event: events.agent.tool.result" pollution was because my OWN session had filled WM with hook-observed tool calls. **Design concern: agent-originated events enter WM and can surface as confidence-0.8 recall results.**
+  - **NEW finding — BM25 score-range mismatch**: `query-router.ts:542-543` comment says similarity is 0-1 range, but DIAG shows `rawSim=5.28/7.26/11.09/12.47` (BM25 raw). Comment is factually wrong. Clamping behavior downstream is undefined — worth Seb's attention.
+  - **Recall WORKS on AC post-restart**: "Kai" returns full memory-bank content; "Chamber" returns Chamber charters at confidence 1.0; "typography" returns AldineXXI framework + typography-as-ethics essay. Yesterday's "Reading Compass 1.0" IS reproducible; it just requires AC + recent-restart + WM not polluted.
+  - **Methodology learning**: instrumentation-only diagnostic branch was load-bearing — two of the four hypotheses would have been wrong without it (H2 pure environmental, H4 situational not structural). Pure code-reading cannot reveal runtime-state or environment-state patterns. Future BMF audits should include a diagnostic-branch stage before any proposals doc.
+- **Audit 2026-04-19 SHIPPED** (2026-04-19 afternoon):
+  - **PR #163** at https://github.com/CapableMind-ai/betterMemories_app/pull/163 — mechanical fix for #126 (`query-router.ts` min-max normalize degenerate case). Closes #126 on merge.
+  - **Three docs + artifacts** in `~/_Dev/CapableMind-AI/docs/thinking/David/l1-reliability/`:
+    - `l1-diagnostic-branch-addendum-2026-04-19.md` — **primary deliverable** with reading-order banner + 6 findings + TL;DR with third cross-cutting pattern (read-path observability contract absent)
+    - `l1-ingestion-forensic-2026-04-19.md` — Part 1 (reading-order banner added)
+    - `l1-recall-quality-baseline-2026-04-19.md` — Part 2 (supersession banner added; §3/§4 partially superseded by addendum)
+    - `forensic-artifacts-2026-04-19/` — log snapshot + raw recall results
+  - **Diagnostic branch pushed** to `origin/diagnostic/recall-read-path-2026-04-19` for Seb's reference (he can remove if unneeded).
+  - **Ship-readiness verified** by architect-review at 0.78 pre-refinement → applied all recommendations → new ship-ready state.
+  - **Third architectural pattern surfaced by review**: *"BMF's honest-degradation contract applies only to the write path; the read path has no equivalent scaffolding."* Added to `feedback-bmf-health-vs-recall.md` as the deeper layer underneath the module-health-vs-recall-correctness symptom. H1-H4 are four confirmations of an absent contract, not four independent bugs.
+  - **Not in today's scope, surfaced as candidates for steward+Seb+jurist architectural study when L1 stabilizes**: (a) module health decoupled from recall correctness, (b) threshold-governance regime collapse (onboarding vs steady-state lag), (c) read-path observability contract absent. Steward framed any such study as "not too soon, but L2-shaped work — not mine to synthesize alone."
+- **2026-04-22/23 BMF main updates**: `8f26642` = our **PR #163 merged** (closes #126, H1 min-max normalize degenerate case). `ac1673f` = Seb shipped **"survive over-context embed batches + drop char cap to 1000"** — addresses the 218 vector HTTP-400s silent-drops finding (per-text split-and-retry with zero-vector placeholder + `/v1/admin/reembed` recovery path). **PR #169 MERGED 2026-04-23 13:53 UTC by Seb** (commit `cdc2f0e`) closing #164 (regression coverage for normalizePerModule uniform-confidence path — follow-up to #163 per steward's test plan). Clean merge, no comments. **H2-H4 remain OPEN as of 2026-04-23 evening**: #165 H2 `priority:critical` (battery-suppression silent recall failure), #166 H3 `priority:high` (temporal-stats fallthrough), #167 H4 `priority:high` (hook events pollute recall/WM), #168 docs (BM25 score-range comment factual error). No comments, no PRs. Matches 2026-04-21 pattern — Seb engages findings as instances, closes one thread (#126/#163/#164/#169) cleanly before moving to next. CapableMind-AI moved one commit: `8584c64` BO spec v0.2 tightening (Back Office, not L1).
+- **Seb engages audit findings as instances, not pattern.** Evidence from GH issue filings on 2026-04-21: four separate bug issues (#165 H2 `priority:critical` "production blocker for laptop end-users", #166 H3 `priority:high`, #167 H4 `priority:high`, #168 BM25 comment factual error), plus #164 (regression coverage for #163 uniform-confidence path, test plan attributed to David). No umbrella issue for "absent read-path observability contract." Pattern-framing did not land as a framework commitment. H2-H4 remain open — L1 cannot advance architecturally until they ship. **Implication**: the bigger-than-any-bug finding (module health decoupled from recall correctness; read path lacks the honest-degradation scaffolding the write path has) stays an architectural study candidate for steward+Seb+jurist, not a near-term engineering target.
+- **The 218 dropped notes are unrecoverable by `/v1/admin/reembed`** — they were `cursorPosition++`'d past without zero-vector placeholders during the 2026-04-18 ingest. `ac1673f`'s recovery path targets placeholders which these events don't have. Recovery requires full rebuild or a targeted re-ingest script. **Decision 2026-04-22**: don't rebuild today — would rebuild again when H2-H4 land; prime directive selects one clean rebuild after all read-path fixes ship.
+- **Seb shipped 9 commits on main between our `decbdee` baseline and 2026-04-19 morning** — several directly overlap our audit findings:
+  - `586e388` + `fb92e6e` + `36603f3` — entity pipeline skips slots for memory_factory/webhook/cross-circle events, skips co-occurrence relationship creation. **Directly attacks the O(N²) bottleneck** we found — effectively Option B from our forensic fix space, implemented for specific event types.
+  - `53d7f08` — `BM_TEACHER_ENRICHMENT_ENABLED` env var for API-only inference mode. **Potential lever for our H2 battery-suppression concern** (routes to Anthropic API, bypasses local Ollama/GPU). Not yet tested whether it addresses query-time embedding path.
+  - `bc8253d` — `BM_SLOT_DISABLE_LOCAL` env var for skipping local + sampling tiers. Another Ollama-avoidance lever.
+  - `14e14da` — validates entity/intent rules on load + guards `resolveTextField` (fix for #162). We observed #162 had scope=1 on our instance — Seb's fix lands defensively.
+  - `fb4ecad` + `da4052b` + `70bd606` — Ollama embedding reliability (dedicated undici Agent, retry transient fetch failures, pin undici to ^6).
+  - **Does NOT address**: H1 confidence clobber, H2 environmental silent-failure (battery), H4 agent-originated events in WM, BM25 score-range mismatch at `query-router.ts:542-543`.
+- **H2 RE-CLASSIFIED as production blocker**, not just architectural concern. Steward verbatim 2026-04-19: *"For those future end-users who will use this on a laptop the need to be plugged into ac for recall is a no go..."*. End-users on laptops is the target use case; silent failure on battery breaks the use case. This elevates H2 from "honest-degradation invariant violation at design level" (philosophical) to "product blocker" (operational). Fix space: either make query-time embedding AC-independent (CPU-only path? remote API fallback?), or surface battery-suppressed state to operator clearly, or both. Commit `53d7f08` (`BM_TEACHER_ENRICHMENT_ENABLED`) may be the pathway if it extends to embedding provider.
+- **H3 exact localization**: `src/modules/temporal/queries.ts:311` — `const queryType = (filters['type'] as string) ?? 'temporal_stats';`. When recall dispatches text queries without `filters.type`, temporal defaults to stats and returns its graph-stats blob (`total_nodes` / `total_edges`) as if it were content. DIAG confirmed across multiple query shapes including question-form. Simple fix shape for Seb: reject unknown/empty queryType with empty result set instead of defaulting to stats.
+- **NEW finding — Hook pollution of recall queries**: the CM hook system dispatches the agent's own tool-use events as BMF recall queries. Observed DIAG during session:
+  ```
+  [DIAG:H4-wm] query="<task-notification>\n<task-id>b2vooi9a1\n<summary>Monitor event..."
+  [DIAG:H3-temporal] query="<task-notification>..." filtersType=null chosenType=temporal_stats
+  [DIAG:H2-embed] queryText="<task-notification>..." vectorLen=1024 embedMs=422
+  ```
+  So every tool-use notification lands as a RECALL query into BMF — triggering embedding (Ollama call), entity search, temporal stats fallthrough, etc. This creates ambient load on the system proportional to the agent's own activity. Cost implications: every `ScheduleWakeup`, every TaskCreate, every background monitor event results in an Ollama embedding call + DB scans. Worth Seb's attention — may be the source of some of the background CPU we've observed.
+- **Audit Part 1 COMPLETE (2026-04-19 morning)**. Forensic doc at `l1-ingestion-forensic-2026-04-19.md` is ready for Seb — 8 sections, TL;DR with 6 items, fix-space with 6 options (A cap / B skip bulk / C async / D cheap classifier / E slot-graduation / F cosine-adjacency), architecturally-honest composition is C+D+E with three named frictions (rebuildability, recursive regime, operator semantics). Doc verified by code-reviewer (0.92 on mechanism) + architect-review (0.55 on original → revised to ship-ready with 11 corrections + 2 TL;DR corrections). Part 2 (recall quality baseline, ~15 queries across categories) and Part 3 (proposals synthesis for Seb) remain. Log snapshot preserved at `forensic-artifacts-2026-04-19/bmf.stderr.2026-04-19T0749.log` (43 MB).
+- **Live config**: BMF launchd-managed via `com.capablemind.bmf` plist → `~/bin/bmf-start.sh`. Wrapper sets `BM_DATA_DIR=$HOME/.capablemind/data/mindfabric-00` + `BM_INSTANCE_NAME=mindfabric-00` + shared dev token `bm_key_testkey1234567890` (all circle members share one key in dev). Instance: `cm-instance-7d2e19a417d694c6`.
+- **Operator-experience lesson**: `BM_DATA_DIR` pin is NOT monolithic — per-module resolvers can bypass it via ADR-021 legacy-path fallback. Explicitly setting `BM_INSTANCE_NAME` + ensuring no legacy path exists prevents dual-write. This cost us ~2 hours of data-dir archaeology this session; worth flagging to Seb as a `[HARDENING]` candidate.
 - **Decision:** better-sqlite3 (relational) + LanceDB (vector+FTS). Benchmarked with NFCorpus/BEIR. SurrealDB had ZERO recall.
-- **Amendments 58-61** shipped by Seb. Pairing active (`peer-sysops-david`).
-- Summarizer: `BM_LOCAL_MODEL=qwen3.5:4b`. Teacher OFF (no ANTHROPIC_API_KEY).
-- Steward set up fresh data dir for vault ingestion test: `~/.capablemind/data/mindfabric-00/` empty; old data preserved at `mindfabric-00.surreal-backup-20260414-142358`.
-- See [bmf-details.md](bmf-details.md) for full technical state, issues, deployment
+- **Amendments 58-61** shipped by Seb. Pairing active (`peer-sysops-david`) + new auto-pairings from circle join.
+- Summarizer: `BM_LOCAL_MODEL=qwen3.5:4b`. Teacher: `BM_TEACHER_TRANSPORT=api`, ANTHROPIC_API_KEY loaded from `~/.capablemind/env`.
+- **End-of-pass artifacts**: `~/_Dev/CapableMind-AI/docs/thinking/David/l1-reliability/2026-04-14-migration-completion-pass.md` (migration) + `l1-ingestion-diagnostic-2026-04-18.md` + `l1-deep-audit-plan-2026-04-19.md` (this session).
+- See [bmf-details.md](bmf-details.md) for full technical state, issues, deployment.
 - [bmf-summarizer-contract.md](bmf-summarizer-contract.md) — deferred refactor: summarizer is coupled to local_files observation shape; most connectors fell through silently (fixed structurally in storage-migration PR). Open `[PROPOSAL]` for connector-agnostic contract.
+- [feedback-onboarding-vs-steady-state-thresholds.md](feedback-onboarding-vs-steady-state-thresholds.md) — slowness is threshold-governance not bug; two regimes (onboarding / steady-state lag) collapse in code but differ in kind; forensic output shape = distributions, not verdicts. Steward articulated 2026-04-19 with Kai 9+9 anchor.
 
 ## Active Projects
-- [project-focus-april-may.md](project-focus-april-may.md) — L2 PARKED, L1 scaling + agent circles until end of May (Seb's deadline)
+- [project-focus-april-may.md](project-focus-april-may.md) — **L2 PARKED, L1 is PRIMARY focus through end of May.** Steward actively on L1 production work alongside Seb (re-affirmed 2026-04-19 — Seb too spread thin to carry alone).
+- [future-intention-ground-up-model.md](future-intention-ground-up-model.md) — **HORIZON MARKER, not active.** Steward intention (noted 2026-04-18 re: Greenblatt article) to eventually build a model from the ground up. No hardware, no pathway yet.
 - **CapableMind L1/L2**: `~/_Dev/CapableMind-AI` (playbook) + `~/_Dev/BetterMemories.io` (runtime)
 - **ARC**: `~/_Dev/animal-davidglidden-eu` — push blocked on Gitea restart
 - **Chamber Library**: `~/_Dev/chamber-library`
@@ -40,6 +123,7 @@
 - [feedback-pdf-extraction.md](feedback-pdf-extraction.md) — use pdftotext, not AI agents, for copyrighted texts
 - [feedback-bm-local-model.md](feedback-bm-local-model.md) — BM_LOCAL_MODEL must match installed Ollama model
 - [feedback-cm-david-v2-noisy.md](feedback-cm-david-v2-noisy.md) — cm-david:v2 produces garbage, retrain needed
+- [feedback-bmf-ingestion-rate.md](feedback-bmf-ingestion-rate.md) — BMF connector_status `rate`/`eta_minutes` is bursty, don't quote as reliable ETA
 
 ## Key Decisions
 - **SurrealDB → SQLite+LanceDB** — benchmarked, decided 2026-04-13. SurrealDB had zero recall (upstream bugs). SQLite for relational, LanceDB for vector+FTS. Scale-ready (HNSW O(log n), Tantivy BM25). David rejected `any` type escape — prime directive applies.
@@ -58,8 +142,15 @@
 - Three-party model: David (steward), Claude.app (jurist), Claude Code (executor)
 - Authorization taxonomy: [FIX], [HARDENING], [PROPOSAL], [ESCALATE]
 - Executor Agency Directives in ~/CLAUDE.md
+- [feedback-independent-specialist-authorization.md](feedback-independent-specialist-authorization.md) — standing auth to invoke specialist sub-agents with Symmetria at discovery moments; re-verify after revisions
+- [feedback-mechanical-vs-architectural.md](feedback-mechanical-vs-architectural.md) — executor+steward author mechanical fixes on L1; architectural changes stay with Seb. Principle articulated 2026-04-19.
 - [collaboration-signal-travel.md](collaboration-signal-travel.md) — signal travel protocol
 - [feedback-thistleweld.md](feedback-thistleweld.md) — Buddy finds real bugs, treat observations as diagnostic signals
+- [feedback-children-not-named-online.md](feedback-children-not-named-online.md) — David's children (Kai, Lune) are NOT named in any public-facing content. Standing rule.
+
+## Steward Self-Characterization
+- [user-influences-humic-layer.md](user-influences-humic-layer.md) — ABG and Moy are primary cultivators of the steward's curiosity; influences (Bachelard, Jaccottet, Handke, Visuddhimagga, Weil, Harrison, Hölderlin, Leopardi, Levinas, etc.) are humic layer enriching that ground, not authorities the work derives from. Informed by many, derived from none. Relation to sources is *discourse*, not *appeal*. Applies across all work.
+- [user-foundation-work-and-long-trajectory.md](user-foundation-work-and-long-trajectory.md) — ARC is not a blog but "an intentional thinking space"; steward has been moving toward this since childhood. Foundation-laying (crystallization of lifelong forming) has its own fatigue pattern distinct from generative-writing. Impatience is named, honored. Collaboration is reciprocal: "Without you, I can't finish." Applies across ARC, L2, Chamber, all major architectural work.
 
 ## Personal Context
 - Nuria: David's partner, mother to Kai
@@ -71,6 +162,7 @@
 ## Obsidian Vault
 - Daily log: `Vault/.../CapableMind/daily-log/YYYY-MM-DD.md`
 - Thinking mirror: rsync'd from `CapableMind-AI/docs/thinking/David/`, every 48h via launchd
+- **Library Charter (canonical, v1.3.0 2025-12-22):** `00. Compass/00a. Foundations/02. Organs/12. Library — Attention & Meaning Ecology.md`. Five Kingdoms (Fundamentorum · Vocis · Itinerum · Perceptionis · Habitationis); Hearth is the crucible of Habitationis where formal classification is suspended during deep engagement; seven Phyla for re-homing (Structure · Utterance · Long Walk · Perception · Interpretation · Practice · Completion). Governing rule: *"A book's final place is determined by what it revealed while being lived with, not by what it claimed to be."* See `user-influences-humic-layer.md` for the fuller integration with influence-mapping.
 
 ## Reference Files
 - [l2-review-state.md](l2-review-state.md) — ICP-19 review: 13 findings, triage, phased work plan
@@ -87,13 +179,30 @@
 - [design-brief-session-skills.md](design-brief-session-skills.md) — original design brief (IMPLEMENTED 2026-04-08)
 
 ## ARC / AldineXXI
-- [project-arc-rework.md](project-arc-rework.md) — **reawakened 2026-04-16.** Landscape named after local dev restored: essay-versioning question (TODO, explore together), about-pages rework (Desk Interlude has Kai unborn, Lune's presence changed, too many quotes, Manutius paraphrase out), after-the-reply sequence, sequences as first-class, poem + observations + glimpses queued, repo-wide cleanup
+- **AldineXXI-specification.md §II Silence Taxonomy** is the authoritative answer for section-break apparatus: four kinds of silence (Rest / Separation / Pause / Threshold); section breaks use Separation-level spacing ($space-xl 2rem to $space-xxl 3rem); ornaments reserved for Pause only, max 3 per piece, always semantically governed ("ornament without semantic basis is a violation"). Pure-Aldine-by-design. **§IV Ornament Taxonomy names 7 ornament classes** (❦ completion / ⁂ asterism / ❧ marginalia / ◊ lozenge / ✎ gloss / ◉ glimpse / ⊙⊙⊙ photo-essay) but has **spec-drift from v2 practice** (After the Reply v2 uses only section + completion, Harrison-Knife simplification). **2026-04-22 in-session**: proposed retiring ❦/⁂/⊙⊙⊙/❧/◊ as apparatus ornaments (freeing ❦ for Hommage type glyph, ⁂ for Heteronym type glyph), replacing ornament.completion with designed SVG cul-de-lampe, keeping ✎/◉ dual-roles (type glyph = apparatus ornament, precedent works within-type). Cul-de-lampe design pending.
+- **Content typology — three new DRAFT stubs authorized 2026-04-22**: **Heteronym ⁂** (fictional-scholarly framing device — Matthieu Taliesin exemplar; genealogy: Pessoa's heteronyms, Kierkegaard's pseudonyms, Borges); **Hommage ❦** (tribute-placement, living-or-dead, personal-biographical register — Death of a Hero exemplar; Hagen Quartett's last concerts in near horizon per steward 2026-04-22: *"This is a type of death. I will be writing about it."*); **Tombeau ▽** (posthumous artistic-memorial where form itself enacts the memorial — no current exemplar; humic refs: Ravel Le Tombeau de Couperin, Mallarmé Tombeaux). **Louange** held as §7 open-question type-candidate (steward: *"let it emerge if it does"*).
+- **§1 Essay LOCKED 2026-04-22.** Key verb: *moves* (distinguishes from Meditation's holding-still, Fragment's landing, Observation's holding, Reverie's drifting). Register admits range (lyric-to-classical) within the type; distinguishing feature is moving-with, not register. Author's practice-mechanics verbatim (candidate B): *"To essay is to attempt: to take up a subject, follow it through the writing, and test what one thinks by the path of attention. The piece finishes when the attending has done its work, not when an argument is won."* 7 humic references: Montaigne, Adorno ("The Essay as Form"), Handke's *Versuch über...* series, Barthes (*Mythologies* + *La Chambre Claire*), Benjamin (*Arcades Project*), Harrison, Berger. 2 exemplars: Mushi-Ken + Ethics of the Reply I. §7 Q12 added for Vespers/Essay-Meditation boundary (steward holds for "hard thinking").
+- **ARC Style Guide skeleton committed 2026-04-22** at `docs/AldineXXI-Codex/arc-style-guide-skeleton.md` (full drafting deferred to dedicated session). Old 525-line `docs/style-guide.md` archived as `docs/archive/style-guide-pre-typology.md` (dead post-types taxonomy + retired ornament classes). 9-section structure; Gwern's MoS as peer-not-model. **Primary function for the author: self-constraint against voice-float.** Steward verbatim 2026-04-22: *"my sense of urgency with the style guide is to keep myself somewhat constrained instead of floating across disparate voice types and modes."* This reframe is the most important framing of the guide's purpose — the multi-style absorption of a lifelong reader is a gift and a risk; the guide is what holds the voice.  
+  **Prose-formation references (new category, distinct from type-specific humic references)** in `user-influences-humic-layer.md`: The New Yorker (since 1995), Scientific American "white books" (gift from **Moy** = steward's mother, aesthetic-clarity primary-cultivator), Lewis Thomas (*The Medusa and the Snail* Hearth book, *Late Night Thoughts on Listening to Mahler's Ninth Symphony*) — **Lewis Thomas genealogically close to ARC's *After the Reply* sequence, candidate addition to Essay humic layer at next versioning pass.** Steward preparing supplement of additional formative voices. High-value sections: §0 Register & posture, §4 Citation, §7 Per-type, §8 Anti-patterns. **Durable conceptual framings from the skeleton** usable beyond the style guide itself: (1) **"Performed contemplation vs enacted contemplation"** — the L2 contamination problem as prose-anti-pattern; signals = abstract-nouns-doing-perception-work, atmospheric-adjectives, unearned-conclusions. Apply when drafting any ARC piece. (2) **Per-type register verbs** — *Essay argues; Observation holds; Meditation surfaces; Reverie receives; Fragment lands.* Condensed gloss of today's locked boundaries. (3) **Absent title as formal decision** — Observations/Fragments/Glimpses/Dreams have no titles not as missing-field but as commitment; prose must not compensate with de facto title sentences. (4) **Welt-Bild violation** — taking a perceived detail and explaining its meaning dissipates the detail; forbidden in Observation. **Salvage from old `docs/style-guide.md`**: Core Qualities (4 principles), Shadow Principle (*"Beauty can hide violence. Craft can serve oppression"*), `<span lang="...">` a11y convention, small-caps for significant-figures, image alt-text context-discipline, additional anti-patterns (performative humility / meta-commentary / promotional language), "questions that open rather than answers that close." Old style guide's entire Semantic Post Types section superseded by today's typology work (has dead types pattern/correspondence/offering/performance/teaching/interlude).
+- **§1 Gloss LOCKED 2026-04-22.** OED etymology load-bearing: Greek *glōssa* (tongue; word needing explanation) → Latin *glossa* → OF *glose* → Eng *gloss*. Definition widened per steward intent: source-type includes text *and events* ("bits of reading/text/events that happen that I [may] want to engage with"). Deciding axis vs Essay: *serves-source vs uses-source* (§7 Q5 resolved). Boundary codified: **not gloss-over** (archaic rhetorical-evasion sense ≠ ARC Gloss). Practice-mechanics verbatim: *"To gloss is to stay with a bit of text, reading, or event — and to re-tongue it: to say back what the source opens, so the reader may understand what I understood of it. The gloss does not unfold past its source."* Humic refs: etymology-as-ground, Rashi (archetypal), Pirkei Avot + ARN (rabbinic), Derrida *Grammatology* + *Glas*, Barthes *S/Z*, Benjamin *Ursprung*, Genette *Palimpsestes* (tentative theoretical anchor — no canonical Adorno-equivalent; form's authority is carried by practice). Chamber/Gloss boundary: Chamber multiplies voices, Gloss attends single-voice. Forward-looking type — no current ARC exemplars. **12 of 15 §1 types LOCKED; 3 DRAFT; 1 unwritten (Chamber).**
+- **§1 Archive LOCKED 2026-04-22 as non-authored type — generated view.** §7 Q4 resolved: Archive does not take a `class:` value; no content file is `class: archive`. The ☷ glyph in the Reading Compass is a navigation destination, not a content-type marker. `site.hs create ["archive.html"]` (lines 496-509) produces the /archive/ page from aggregated posts/pages. Only type declared as generated-view-not-authored-content. Humic refs: **Derrida, *Mal d'Archive*** (chamber-library: `derrida/mal-darchive.md`, 215KB, 1041 lines, COMPLETE 2026-04-05) as canonical archival philosophy — *"there is no political power without control of the archive, if not of memory"*; Aldine bibliographic tradition; ADR-005 versioning as internal-parallel. **L1/ARC parallel codified in the entry**: the steward's L1 logchain and ARC's Archive-view share the archive-fever commitment — both refuse erasure of earlier state. One commitment, two projects.
+- **§1 About LOCKED 2026-04-22.** Central authorial commitment: ARC does not separate professional/personal; About is the locus of the steward's **first public assumption of multi-disciplinary integration** (violist, teacher, writer, mentor, coach). Integration principle codified in the entry. Steward framing verbatim: *"we have decided not to separate the 'personal' site from ARC itself. I am assuming my multi-disciplinary nature publicly for the first time here."* Enfilade apparatus (`<nav class="about-enfilade">`) confirmed as breadcrumb substitute (§7 Q7 resolved). Current enfilade: Colophon · Typography · Navigation · Chamber · Attention · Patterns · Tools · Influences · Now · Bio; AldineXXI authorized; Chamber page revision pending (post-L2 alignment); mentorship/coaching anticipated additions (musical-facet low-hanging fruit). Humic refs: 5 structural (Montaigne, Aldus Manutius, Sivers /now, Barthes *par Roland Barthes*, fine-press colophon) + 8 named Guides/Formation from `colophon.md` (Alexander, Bachelard, Berger, Sennett, Vico, Leopardi, Harrison, Heidegger). Exemplar: `colophon.md` — **first About-register piece to exercise ADR-005 versioning** ("Third Edition"; revisions 2025-01-01 and 2026-04-17). Practice-mechanics TBD (steward uncertain 2026-04-22 — held open).
+- **§1 Glimpse full-format retrofit LOCKED 2026-04-22.** Original 2026-04-19 lock was header-only (stub). Retrofit extends to full format. Author's practice-mechanics verbatim (candidate A, decisive-moment register): *"To make a Glimpse is to recognize a moment that composes itself into a frame, and to shutter before the moment passes. The piece survives as the arresting held still — what a single image can give that a moment in passing cannot."* 5 humic references: **Cartier-Bresson (via Berger-conduit — steward genealogy-statement)**, Jean Mohr (Berger collaborator — A Fortunate Man, Seventh Man, Another Way of Telling, At the Edge of the World), Walker Evans (personal ground: photo of steward's Great Aunt Anna, private to user-memory), Barthes *La Chambre Claire* (for *punctum*), Berger (independent + conduit). 3 exemplars: Cremona cathedral 2011-11-25, Salmon Lake Canada 2006-08-23, Salamanca main door 2011-05-11. Steward observation preserved: *"Not a lot of geographic variance, but they are good choices"* — corpus-characteristic, not type-requirement. **9 of 15 §1 types LOCKED** (Photo Essay, Glimpse full retrofit, Meditation, Reverie, Dream, Observation, Fragment, Essay); 3 DRAFT (Heteronym, Hommage, Tombeau); 3 unwritten (Chamber, Gloss, About, Archive — 4 items).
+- **Steward's `/Users/davidglidden/Desktop/essay study/` folder** is an active research archive for ARC essay-type work (files created 22 Apr 12:39 2026 per timestamps). Contains: Adorno "The Essay as Form" (62KB OCR'd JSTOR scan, Hullot-Kentor/Will translation, *New German Critique* 32 Spring-Summer 1984); Barthes *Mythologies* (French original 1957 + 1970 preface); Barthes *La Chambre Claire: Note sur la photographie* (French original 1980). Distinct from chamber-library. Use for ARC-type work; these are the specific editions the steward owns and cites.
+- [session-2026-04-20-arc-typology-publication-day.md](session-2026-04-20-arc-typology-publication-day.md) — **MOST RECENT ARC SESSION.** Kai 9+9 day; two pieces published (*On Éveil / Sommeil* + *Time is not a river*); Meditation defined verbatim; Reverie surfaced as type 11; compass restructured to 10 points (⊙ → Meditation/Reverie cluster, ◧ → Photo Essay); hic apparatus convention with European long-form date. **Pulling thread: Session α spec lockdown. Literal question: cluster page name.**
+- [project-arc-rework.md](project-arc-rework.md) — **canonical ARC workstream tracker.** Read at every `/wake-up` that touches ARC; fold session moves in at every `/wrap-up`. Latest: **2026-04-26 evening locks + sibling-file integration** — (1) Path 1 LOCKED at enfilade level (separate Colophon and Lex items); (2) Adsum and threshold-hic LOCKED as two distinct texts (steward: *"They are certainly not the same text"*); (3) all four sibling files INTEGRATED with content folded into Integration A/B/C/D sections. **8-door enfilade LOCKED:** Colophon · Lex · Framework · Vignette · Attention · Chamber · Tools · Now (+ Bio as quiet link). Prior consolidation pass 2026-04-26 afternoon folded 04-23 evening / 04-24 / 04-25 / 04-26 work into the tracker. Prior locked content includes: 2026-04-19 about-page reflow (single page, hic → Adsum, multidisciplinary by embrace, *"I adopt adsum"*); 2026-04-18 Pattern 3 typography; 2026-04-20 Reading Compass at 10 points + Hic apparatus convention; 2026-04-21 Bachelard *Rêverie* + *L'Espace* read, /dwellings/ validated, Visuddhimagga Meditation; 2026-04-23 Heteronym/Hommage/Tombeau LOCKED (14/14 §1 types), Chamber → §2 apparatus, Harrison Ch 2 *Hic Jacet* as humic-layer source, *"ARC is my expression of ligature"*. The four sibling files (cluster-scaffolds, humic-pillars, about-pages-decision-frame, chamber-rewrite-frame) carry INTEGRATED redirect notices at top; retained as audit trail per steward (*"the record needs to be complete"*).
 - [arc-removed-content-types.md](arc-removed-content-types.md) — 7 archive types removed, revisit if they re-emerge from practice
+- [feedback-arc-typology-recognition-scaffold.md](feedback-arc-typology-recognition-scaffold.md) — ARC typology serves recognition of what arrives as ARC-shaped, NOT generation; steward is not-diarist / not-essayist; heterogeneity is structural. Test before §1 finalization: "can the steward use this to recognize?"
+- **ADR-005 versioning regime OPERATIVE IN PRODUCTION (2026-04-18)** — Ethics of the Reply I & II v2 live; v1 preserved at path-segment URLs (`/<slug>/v/<date>/`); breadcrumb renders at piece-end with non-current dates linked to prior versions
 - AldineXXI spec v2.0: `animal-davidglidden-eu/docs/AldineXXI-Codex/AldineXXI-specification.md`
-- Vignette spec (jurist approved): `animal-davidglidden-eu/docs/AldineXXI-Codex/vignette-specification.md`
+- Versioning spec: `animal-davidglidden-eu/docs/AldineXXI-Codex/essay-versioning-specification.md`
+- Frontmatter spec: `animal-davidglidden-eu/docs/AldineXXI-Codex/frontmatter-specification.md`
+- Vignette spec (jurist approved, implementation deferred): `animal-davidglidden-eu/docs/AldineXXI-Codex/vignette-specification.md`
+- Style guide (stale, needs dedicated session): `animal-davidglidden-eu/docs/style-guide.md`
 - Gap map: `animal-davidglidden-eu/docs/AldineXXI-Codex/gap-map-2026-04-13.md`
+- **Content typology spec (DRAFT, 2026-04-19 evening): `animal-davidglidden-eu/docs/AldineXXI-Codex/content-typology-specification.md`** — multi-axis organizing principle; Photo Essay + Glimpse + Fragment:Essay pairing locked; Meditation promoted to 10th type (glyph TBD); drop-cap rule (register-shifts only); no-essay-fallback contract. Untracked; pulling thread for the next ARC session.
+- Chamber voices archived to `animal-davidglidden-eu/docs/archive/chamber-voices/` (2026-04-18)
 - Bringhurst + Warde in chamber-library: `converted_texts/collections/typography/`
-- Vignette Phase 3 (renderer) waiting on: Gitea restart, fresh session, Hakyll build
 - Palette test page: `animal-davidglidden-eu/palette-test.html`
 
 ## Artistic Projects
@@ -118,9 +227,15 @@
 - Observer-problem files moved to `l2-constitution/observer-problem/` (2026-04-09)
 
 ## Active Session
-- [session-2026-04-17-versioning-regime.md](session-2026-04-17-versioning-regime.md) — Essay-versioning question RESOLVED into ADR-005: genesis at publication; three forms (print-tradition breadcrumb / Augustinian retractation / Zibaldone accumulation); dates not semver. Full regime captured (ADR-005 + versioning mechanism sketch + frontmatter specification + `make revise`). Colophon is first worked example (frontmatter + The Formation section + Desk meta-commentary for son's arrival). Ethics of the Reply I & II v2 staged under `_staging/versioning-prep/` with v1 snapshots preserved. Typography deliberately skeletal — Option 1: let the need drive the AldineXXI application agent into existence. Two commits: `86c1bbb` (regime + colophon), `040c16d` (staging). **Pulling thread: path to publication — Hakyll infrastructure vs typography application skill, which lever first?**
+- [session-2026-04-22-arc-integration-day.md](session-2026-04-22-arc-integration-day.md) — **ARC integration day.** Typology 12 of 15 LOCKED (+3 new DRAFT stubs Heteronym/Hommage/Tombeau; 1 unwritten: Chamber). **Central authorial commitment: integration principle** codified in About — ARC refuses professional/personal split; steward's first public assumption of multi-disciplinary life. Essay LOCKED with practice-mechanics B grounded in verified reads (Adorno + Barthes × 2 from `Desktop/essay study/`). Archive LOCKED as non-authored generated view (Derrida archive-fever; L1/ARC parallel codified). Gloss LOCKED with OED etymology load-bearing; widened for text-or-event per steward intent. Glimpse full-format retrofit. AldineXXI §IV ornament taxonomy retired (7 → 2 roles). **ARC Style Guide skeleton committed** with **self-constraint-against-voice-float** as primary function; prose-formation references cluster opened (New Yorker since 1995 / Scientific American white books from Moy / Lewis Thomas — genealogically close to *After the Reply*). L1 PR #169 filed (regression coverage for #164). **Pulling thread: Style Guide dedicated writing session (§0 voice-setting), with steward's supplement of additional formative voices expected.** Literal question: has the supplement arrived, and does it reshape Essay's humic layer (esp. Lewis Thomas)?
 
 ## Archived Sessions
+- [session-2026-04-21-arc-typology-humic-frame-and-six-locks.md](session-2026-04-21-arc-typology-humic-frame-and-six-locks.md) — ARC typology foundation day. Five §1 types LOCKED in one day (Meditation, Reverie, Dream, Observation, Fragment) + §0 Source axis + Photo Essay glyph propagation. Humic-layer frame articulated (ABG/Moy primary cultivators; Jaccottet/Handke/Lichtenberg as carnet-pole references). Seven drift-returns logged.
+- [session-2026-04-19-arc-typology-spec-and-dns.md](session-2026-04-19-arc-typology-spec-and-dns.md) — ARC pivot after L1 ship. About-page reflow decision; drop-cap rule codified; content-typology-specification.md first drafted (§0 multi-axis; Photo Essay, Glimpse locked; Meditation promoted to 10th type glyph-TBD; no-essay-fallback rule). DNS unblocked via Firewalla / DoH test. Pulling thread into 2026-04-20: finish the typology spec.
+- [session-2026-04-19-l1-audit-shipped.md](session-2026-04-19-l1-audit-shipped.md) — **L1 deep audit shipped end-to-end.** Wake-up executed deep-audit plan; found recall substantially broken; 6 findings localized with file:line; mechanical fix shipped as PR #163 (closes #126); diagnostic branch with 5 [DIAG:H*] instrumentations pushed for Seb's reference; bundle (forensic + recall baseline + diagnostic addendum) committed to CapableMind-AI main (`40cb401`) + pushed. **Three cross-cutting architectural patterns** surfaced: (1) module health decoupled from recall correctness, (2) threshold-governance regime collapse, (3) read-path observability contract absent (the new one, surfaced by architect-review's second pass; H1-H4 are four confirmations of its absence). Steward recalibrated milestone gracefully: *"my joy at reaching the milestone was premature I now understand... I can accept that. Now to make this work."* New principles articulated: mechanical-vs-architectural scope, independent-specialist authorization. Pulling thread at L1 close: Seb's reception of the bundle — does the "absent read-path contract" framing land as a pattern, or does he treat H1-H4 as four independent bugs?
+- [session-2026-04-18-evening-ingestion-milestone.md](session-2026-04-18-evening-ingestion-milestone.md) — First successful vault ingestion (2026-04-18 overnight); 7,220 items; steward named "the foundation". Reclassified 2026-04-19 as substrate-bytes-flowed milestone, not recall-works milestone.
+- [session-2026-04-18-arc-versioning-pattern3.md](session-2026-04-18-arc-versioning-pattern3.md) — ARC versioning regime operative in production (first exercise: Ethics of the Reply I & II v2 live); Pattern 3 typography adopted (role-assigned families: serif content / sans wayfinding / mono apparatus) on accessibility grounds; 9 ARC commits shipped clean (no `--no-verify`), pushed to both remotes. Chamber voices archived to unblock pre-existing dependency cycle. Morning seeded `ground-up-model-horizon` in MemPalace with watering practice after Greenblatt article exchange.
+- [session-2026-04-17-versioning-regime.md](session-2026-04-17-versioning-regime.md) — Essay-versioning question RESOLVED into ADR-005: genesis at publication; three forms (print-tradition breadcrumb / Augustinian retractation / Zibaldone accumulation); dates not semver. Full regime captured (ADR-005 + versioning mechanism sketch + frontmatter specification + `make revise`). Colophon is first worked example. Ethics of the Reply I & II v2 staged under `_staging/versioning-prep/` with v1 snapshots preserved. Two commits: `86c1bbb` (regime + colophon), `040c16d` (staging). The staging was exercised 2026-04-18.
 - [session-2026-04-16-arc-reawakening.md](session-2026-04-16-arc-reawakening.md) — ARC decoupled from Acerplex, local Mac dev operational (Stack 3.9.3 + GHC 9.8.4 + Dart Sass 1.99), both deploy paths validated (`42fbddd` pushed). CloudFlare token → Keychain. Gitvault fixed. Steward reconnected with ARC after months dormant; named essay-versioning as "explore together" question that resolved in 2026-04-17.
 - [session-2026-04-15-recall-symmetria.md](session-2026-04-15-recall-symmetria.md) — Recall validated end-to-end on real vault data (sub-second, confidence 1.0). Closed #154-158. Installed Symmetria skill v2 (practice-of-return). Commented #145 from archivist/librarian frame. Revised /wake-up + /wrap-up with Dasein frame (pulling thread, pause statement, literal question). Shipped Seb handoff (`d859dba`). Trial branch at `4ef8f5b`. Thread pulling at end: #145 boolean-bridge vs multi-mode retention (still open today).
 - [session-2026-04-14-migration-completion.md](session-2026-04-14-migration-completion.md) — L1 migration completion pass: 7 commits closing SurrealDB→SQLite+LanceDB. Factory + meld + reconciliations + graduation + lifecycle wiring all ported. tsc clean, 3552 tests pass. Steward will run fresh vault ingestion as live verification.

claude/memory/feedback-arc-typology-recognition-scaffold.md

@@ -0,0 +1,67 @@
+---
+name: ARC typology is a recognition scaffold, not a generation template
+description: How to relate to the ARC content typology — it serves the steward's recognition of what arrives as ARC-shaped, not a production pipeline. Reference documents and pieces are grounds for recognition, not templates for generation.
+type: feedback
+originSessionId: b9a0781b-1d1c-418f-8ca3-70a51db83580
+---
+# ARC typology — recognition scaffold, not generation template
+
+**Rule:** the ARC content typology exists to let the steward *recognize* what is ARC-shaped when a thought arrives. It is not a production pipeline, not a notebook-to-public, not a schema to fill.
+
+**Why (steward, 2026-04-21):**
+
+> *"ARC is not meant to be an online notebook to public. But the forms that Jaccottet uses are useful to analyze, to have a better idea of how we can define the types. As you're getting to know me more and more deeply, you know that I am not a diarist. I am not an essayist. Sometimes a thought comes across one of the types we've defined already and I 'know' that it is for ARC. Sometimes not. My mind works across various forms. And my output can be… quite heterogeneous."*
+
+Three structural facts this establishes:
+
+1. **Not-diarist.** ARC is not a daily-chronicle of thought. There is no expectation of regular entries or exhaustive coverage.
+2. **Not-essayist.** ARC is not primarily an argumentative corpus. Essay is one type among many, not the default.
+3. **Recognition-based publishing.** A thought either arrives *already in the shape of an ARC type* (and the steward knows), or it doesn't (and it doesn't become an ARC piece). The typology makes recognition possible.
+4. **Heterogeneity is structural.** The steward's mind works across multiple forms; output is "quite heterogeneous." The typology must hold that range without flattening it.
+
+**How to apply:**
+
+- **Definitions describe what a piece *is***, not how to write one. Recognition-criteria over generation-instructions.
+- **Every §1 entry needs clean in/out criteria.** The ✗-boundary cases matter as much as the ✓-exemplars. The steward's discipline is "sometimes yes, sometimes no" — the spec must support that judgment.
+- **Multi-axis §0 is not a design inelegance — it is correct coverage.** Heterogeneity has structural dignity. Don't try to collapse the axes.
+- **Reference texts (Bachelard, Visuddhimagga, Jaccottet) are grounds for recognition, not templates for generation.** They deepen understanding of what the forms *are*; they don't prescribe what ARC pieces should *look like*.
+- **Jaccottet specifically:** different atomicity (carnet-compilation vs individual-publication). Treat as formal-range reference + confirmation that heterogeneity has literary dignity in one body of work. Don't drift into "ARC as online notebook" thinking.
+- **When tempted to propose generative templates or production workflows**, stop. The typology serves recognition, not generation. Offer definitions, boundaries, and exemplars; let the steward recognize or not.
+
+**What this does NOT mean:**
+
+- It does NOT mean the steward doesn't work on pieces — pieces get drafted, revised, polished. But the recognition that *this is a piece for ARC* is upstream of the drafting discipline, and the type the piece belongs to is recognized (often) rather than constructed.
+- It does NOT mean the steward has no notebook-shaped activity — there may be notebooks, private writing, vault material. It means the ARC site is not that venue. ARC is the curated public body.
+
+**Test for the spec writer (executor):** before finalizing a §1 definition, ask *"can the steward use this to recognize whether an incoming thought is this type?"* If the definition only helps someone *write* this type, it's incomplete.
+
+## Humic-layer reweighting 2026-04-21
+
+The steward articulated a further frame that reweights how reference texts appear in §1: see `user-influences-humic-layer.md` for the full steward characterization.
+
+**Operative consequence for the ARC typology spec:**
+
+Reference texts (Bachelard's *Poétique de la Rêverie*, Visuddhimagga, Jaccottet's carnets, Weil on attention, etc.) are **in the humic layer** of the steward's reading — broken down, absorbed, enriching — **not authorities the types are derived from**. The types rest on the steward's work and his recognition of it. The influences are in *discourse* with the types, not in *governance* of them.
+
+**For §1 drafting, this means:**
+
+- **Definitions in the steward's register, from the steward's practice.** Not *"per Bachelard..."* or *"following Visuddhimagga..."*
+- **Influence citations appear as grounds for discourse / recognition, not as deeds of transfer.** The ARC Reverie type is what the steward recognizes when reading Bachelard; Bachelard is not the source the type derives from.
+- **Example frame (Reverie):** *"The ARC Reverie type names a mode the steward recognizes and practices. Bachelard's La Poétique de la Rêverie is one of several texts in discourse with this type — he names from within the anima-register what ARC Reverie enacts on the page."* Not: *"Reverie is defined by Bachelard as..."*
+- **Example frame (Meditation):** *"The ARC Meditation type traces a practice the steward describes in first-person mechanics. The Visuddhimagga offers technical vocabulary for the same structure (kammaṭṭhāna / samādhi / sati / vipassanā) — a humic reference, not the source of the definition."*
+- **Same posture across all types.** The citations are present where relevant; the work's ground is the steward's.
+
+**Test extension for §1 drafting:** before writing a reference-text citation, ask *"am I positioning this as an authority above the steward's work, or as humic enrichment?"* If the former, rewrite.
+
+## Sequencing corollary 2026-04-21
+
+**Rule:** do not apply the recognition-scaffold to the corpus (reclassifications, audits, systematic retypings) until the scaffold is stably complete.
+
+**Why:** a recognition-scaffold's types are defined by their mutual boundaries as much as by their positive definitions. Fragment-vs-Observation-vs-Meditation-vs-Reverie-vs-Dream each sharpen the others. Reclassifying corpus pieces against partial scaffolds risks locking in classifications that later boundary-type definitions would displace. Steward articulated the principle 2026-04-21 after catching the executor about to execute reclassifications prematurely: *"Maybe I'm being rash — I guess we should finish the spec before the audit."*
+
+**How to apply:**
+
+- Corpus reclassifications (ARC audit follow-ons) wait until §1 is comprehensively locked, minimum through the adjacent types of whatever's being reclassified.
+- Safe reclassifications: those where the *source* type is stable and the *target* type is locked, AND no currently-DRAFT type could plausibly claim the piece. Today (2026-04-21): Graffiti Girl → Reverie is mostly safe (both Observation and Reverie are defined well enough that Graffiti Girl is clearly Reverie), but still wait for Observation's LOCKED state so the boundary is explicit.
+- When the spec is nearly complete, run the audit pass with the full vocabulary available. Then reclassify.
+- **Executor rule of thumb:** when steward authorizes a spec decision, that authorizes *writing the decision into the spec*. Applying the decision to corpus pieces is a separate authorization, typically to be granted after the whole scaffold is stable.

claude/memory/feedback-bmf-health-vs-recall.md

@@ -0,0 +1,51 @@
+---
+name: BMF module health does not measure recall correctness
+description: Modules reporting status=ready / system_status=healthy in BMF measures pipeline liveness only — not whether recall produces correct results. Verify recall directly. Never trust the health endpoint as a proxy for "the system works."
+type: feedback
+originSessionId: a3ddbf34-da48-4129-acba-658f2f869783
+---
+# Module health is decoupled from recall correctness
+
+When evaluating BMF state — for any session, any audit, any "is it working" question — **never use module health (`status: ready`, `system_status: healthy`) as evidence that recall produces correct results.** The two are structurally decoupled.
+
+**Why:** The health endpoint measures pipeline liveness — subscription up, storage reachable, cursor advancing, error_count not catastrophic. None of those signals address the question "if I ask 'Who is Kai?', do I get vault content back?" Verified empirically 2026-04-19: all 11 modules reported `ready` with `system_status: healthy`, and 8 of 15 designed recall queries returned empty (including known names like Lune, Kai, Nuria); 6 returned junk (temporal-stats blobs or session-hook-pollution); only 1 returned honestly empty. The system reported healthy throughout.
+
+**This is a violation of the honest-degradation invariant** (`bettermemories/CLAUDE.md` invariant: *"Honest degradation — the system must report its own limits. Silent failures are architectural violations"*) at design level, not at instance level. There is currently no pipeline from "recall is emitting noise" to "module health should flip." That gap is itself an architectural finding bigger than any single bug it produces.
+
+## The deeper pattern (surfaced 2026-04-19 audit-bundle architect-review)
+
+One level underneath the symptom: **BMF's honest-degradation contract applies only to the write path; the read path has no equivalent scaffolding.** Write-path modules report cursor, error_count, last_processed_at — measurable observables. Read-path subsystems (query-planner, query-router, hybridSearch, temporal fallthrough, working-memory injection) silently produce empty or junk results with no diagnostic surface — no counter, no error signal, no "why empty" breadcrumb. The slow-query log at `vector/queries.ts:291` only fires on `searchMs > 200`, so fast 0-return queries are invisible.
+
+H1–H4 from the 2026-04-19 audit are not four independent bugs; **they are four confirmations of an absent contract on the read path.** Patching them one-by-one fixes symptoms; naming the pattern lets the read path get the observability discipline the write path already has.
+
+**How to apply this deeper framing:**
+- When auditing any new behavior in BMF, ask first whether it's on the write path or the read path.
+- On the write path, the honest-degradation discipline is already in place — bugs there are usually local.
+- On the read path, assume the bug you find is one instance of a broader silence. Look for siblings.
+- When proposing fixes, consider whether the fix should be the instance (e.g., H1's #126 guard) or the contract (read-path observability layer). Often both — ship the instance, file the contract as architectural follow-on.
+
+## How to apply
+
+**For any audit / diagnostic / status check:**
+- Run actual recall queries against known vault content (a name, a thematic term, a recent event).
+- Test with `min_confidence: 0` AND with default — the gap between them reveals whether content exists in storage but is being filtered.
+- Test with explicit `modules: ["vector"]` — vector should return semantic hits even if entity is degraded.
+- Be alert to two synthetic-fallback patterns that masquerade as content:
+  1. **Working-memory injection**: results with content like `"Recent event: events.agent.tool.result (...)"` and confidence 0.8 — these come from `query-router.ts:268-290` injecting the agent's OWN current tool calls, not vault content.
+  2. **Temporal stats fallthrough**: results with content like `{"total_nodes":N,"total_edges":M,...}` — the temporal module returning its own graph stats regardless of query intent.
+- If either fallback pattern appears, recall is producing junk; the module health report is non-load-bearing.
+
+**For session reporting / steward updates:**
+- Do NOT report "recall operational" based on a single high-confidence result without a baseline across multiple query categories.
+- Do NOT report "system healthy" based on health endpoint without verifying recall.
+- Do NOT conflate "ingestion completed" with "the system can use what was ingested" — these are structurally separate (substrate vs interpretation).
+
+**For future BMF work:**
+- Until BMF has a recall-correctness signal in module health (or system_status), the operator (steward, executor, eventually end-user) is the only validator. That's a structural problem worth surfacing as a `[PROPOSAL]` to Seb when the moment fits.
+
+## Background — when this was learned
+
+Steward verbatim, after the recall baseline test revealed the decoupling:
+> *"So my joy at reaching the milestone was premature I now understand... I can accept that. Now to make this work."*
+
+Yesterday's milestone (2026-04-18 evening): connector completed 7,220 items, 14,355 entities extracted, 0 failed, all modules ready, single-query recall returned confidence 1.0 → steward called it "the foundation." That reading was true about substrate-bytes-flowed but premature about recall-works. The foundation in the deeper sense (the system can be used as cognitive memory) requires recall correctness, which today's audit shows is not yet present.

claude/memory/feedback-bmf-ingestion-rate.md

@@ -0,0 +1,17 @@
+---
+name: BMF connector_status rate/ETA is unreliable
+description: Don't quote the `rate` or `eta_minutes` from BMF connector_status as a time estimate — ingestion is bursty, rate changes substantially, linear extrapolation misleads.
+type: feedback
+originSessionId: e60f4993-8250-41bb-a95f-c288da448be5
+---
+# BMF connector_status rate/ETA — don't trust the extrapolation
+
+**Rule:** When reading `mcp__capablemind__connector_status`, do not report the `rate` or `eta_minutes` fields to the steward as if they were reliable predictors of completion time.
+
+**Why:** BMF ingestion exhibits a burst pattern — periods of slow steady throughput interleaved with rate surges. The `eta_minutes` is computed by linear extrapolation from instantaneous rate, which doesn't capture the burst behavior. Steward has observed this repeatedly across vault ingestion runs. Quoted observation (2026-04-18): *"the ETA is not a good indicator because the rate will change with the burst ingestion pattern that seems to take hold."*
+
+**How to apply:** When reporting progress during long-running ingestion:
+- Report `processed / total_estimated` and `entities_extracted` (raw counts — informative)
+- Skip `rate` and `eta_minutes` unless explicitly asked — or caveat them heavily
+- Frame duration in coarse terms ("several hours" / "let it run overnight") based on total size, not fine-grained ETAs
+- Poll intermittently if asked; don't build plans around a specific finish time

claude/memory/feedback-canonical-workstream-tracker-discipline.md

@@ -0,0 +1,82 @@
+---
+name: Canonical workstream trackers must be read at session start, not just session memories
+description: Surfaced 2026-04-26 after three consecutive sessions generated substantial architectural work as if from a clean slate, without referencing project-arc-rework.md (the canonical ARC workstream tracker). The /wake-up procedure restored yesterday's session memory + ledger but did not pull from canonical workstream files. Result: re-litigation of settled decisions, sibling project files instead of integrations, missed load-bearing context. Fix names what to read at every session opening that touches ARC (and structurally similar workstreams).
+type: feedback
+originSessionId: 87dfe384-b862-4deb-9676-24e43046528f
+---
+# Canonical workstream trackers must be read at session start
+
+**Steward verbatim 2026-04-26:** *"We're drifting and I'm getting nervous. Where have you been keeping track of the work we've been doing on arc over the last week or so?"*
+
+**Steward verbatim follow-up:** *"when was the last time you referred to project-arc-rework.md? Is it only today that we've been flying blindly? we've done a lot in the last two days..."*
+
+**Diagnostic answer:** Last reference to `project-arc-rework.md` was 2026-04-23 (Sant Jordi day). Four consecutive substantive sessions (2026-04-23 evening, 04-24, 04-25, 04-26) opened without referencing the canonical tracker. Substantial architectural work in those days — lex-method as commitment, two clusters committed (posture, marks), §XII Sidenotes, ARC CLAUDE.md cleanup, colophon-at-scale architectural locating, full Vico/Harrison lex-chain restoration, today's work — none of it folded back into the canonical home.
+
+## The rule
+
+When a workstream has a canonical tracker file (e.g., `project-arc-rework.md` for ARC), that file is a **primary read at session opening**, not an optional reference. Specifically:
+
+1. **At every `/wake-up` that touches a tracked workstream**, read the canonical tracker file (or the relevant section if the file is large) before producing any frame, scaffold, or new project file.
+2. **At every session-end (`/wrap-up`)**, the session's substantive moves get folded into the canonical tracker, not just into the day's session-memory file.
+3. **New project files are integrations or extensions of the tracker, not parallel sibling files.** When in doubt, append to the tracker rather than create alongside it.
+
+## Why
+
+The structural drift is not five instances of "canonical-library-not-checked-first" (each logged as its own pattern today). It is **one pattern**: *working without the canonical roadmap.* Each instance — chamber-library catalogues read instead of trees; Bachelard/Berger/Sennett "newly visible" when they were already Guides in the colophon; Chamber Validation Report read instead of source-aware design-thinking doc; AldineXXI TODO read instead of project-arc-rework.md — was a symptom of the same upstream gap.
+
+The fix is upstream. Read the tracker first; the downstream symptoms resolve when the tracker is the working ground.
+
+## How to apply
+
+### At `/wake-up`
+
+The wake-up procedure currently reads `MEMORY.md` (index) + the active session memory file. **It must additionally read** the canonical tracker file for any workstream the session is going to touch. If the active session memory references ARC, read `project-arc-rework.md`. If it references L1/BMF, read whatever L1's canonical workstream tracker is. If it references L2/Chamber, read that one.
+
+**Practical signal:** check `MEMORY.md` for entries beginning with `project-` whose name names a workstream (`project-arc-rework`, `project-focus-april-may`, etc.). These are likely canonical trackers, not point-in-time decision frames. Read them before producing.
+
+### During the session
+
+Before generating a new project file (`project-X-2026-MM-DD.md`), check whether the workstream already has a canonical tracker that the new content should integrate into. If yes, **append/integrate**; do not create a sibling.
+
+If a sibling file is genuinely warranted (e.g., a self-contained decision frame or scaffold that will later be folded in), name it clearly as such and **link forward to the canonical tracker** so future-self can find the home.
+
+### At `/wrap-up`
+
+The wrap-up captures the session's pulling thread + literal question + session memory. **It must additionally fold the session's substantive moves into any canonical tracker the session touched.** Otherwise the next session's tracker-read will not surface what just happened.
+
+### When the index entry in `MEMORY.md` is stale
+
+An index entry that says "substantially expanded 2026-04-20" when the file has 04-21 and 04-23 content is itself a symptom — the index hasn't been maintained alongside the tracker. **Update the index entry whenever the tracker is updated.** Both move together or both rot together.
+
+## Cousin patterns (all symptoms of the same upstream gap, today)
+
+- `canonical-library-not-checked-first` (recurred from 2026-04-24)
+- `working-from-mental-summary-not-rereading-the-source`
+- `characterizing-substrate-without-checking-artifact-being-reshaped` (Bachelard/Berger/Sennett were already Guides)
+- `reading-validation-instead-of-design-thinking-when-asked-what-is-becoming` (Chamber)
+- `catalogue-as-shortcut-over-tree-walk` (chamber-library)
+- (now named at the umbrella level): **`working-without-canonical-roadmap`**
+
+The five lower-level patterns are real and worth holding individually; the umbrella names what they share.
+
+## How `/wake-up` should be amended
+
+Suggested addition to the procedure:
+
+> **2c. Canonical workstream trackers.** For each `project-` file in `MEMORY.md` that names a workstream (e.g., `project-arc-rework`, `project-focus-april-may`), if the active session memory or pulling thread touches that workstream, read the tracker file before producing any frame or scaffold. Treat tracker files as primary, not as background reference.
+
+Steward to authorize this amendment to the wake-up skill or carry the discipline manually until amended.
+
+## How `/wrap-up` should be amended
+
+Suggested addition:
+
+> **Tracker integration.** Before writing the session memory and updating MEMORY.md, identify which canonical workstream tracker(s) the session touched. Fold the session's substantive moves into those trackers (not just into the day's session memory). Update the trackers' index entries in MEMORY.md to reflect the new state.
+
+## Open question
+
+Is `project-arc-rework.md` the right canonical home for ARC work, or should it be split into thematically narrower trackers (typology, infrastructure, content-rework, etc.)? Steward call. The 1434-line size is at the edge of what's practical to read at every session-open; either chunked-reads or thematic split may help.
+
+## Saved 2026-04-26 in the moment of the steward surfacing the pattern
+
+Logged because the structural fix matters more than any individual instance, and because the discipline applies forward to every tracked workstream — not just ARC.

claude/memory/feedback-catalogues-stale-walk-trees.md

@@ -0,0 +1,43 @@
+---
+name: Catalogues in chamber-library are stale — walk the trees, not the catalogues
+description: Steward correction 2026-04-26. Any catalogue or index file in chamber-library is presumed stale. For inventory, recall, or substrate-survey, walk the actual file tree. Do not rely on CHAMBER_CATALOGUE.md, README.md, or similar summary documents as authoritative.
+type: feedback
+originSessionId: 87dfe384-b862-4deb-9676-24e43046528f
+---
+# Catalogues are stale — walk the trees
+
+**Steward verbatim 2026-04-26:** *"that catalogue is stale (any catalogues you may come across will be stale)"*
+
+## The rule
+
+Any catalogue, index, or summary file inside `chamber-library/` (or by extension any of the steward's working repositories) is presumed stale unless its mtime / content has been verified against the actual tree it describes. This includes but is not limited to:
+
+- `chamber-library/converted_texts/CHAMBER_CATALOGUE.md` (last updated 2026-03-28; the tree has grown substantially since)
+- `chamber-library/README.md` (claims "305+ texts, 147+ philosophers" — likely undercount)
+- Any subfolder `README.md` files
+- Auto-generated indices in `indices/` (currently empty but the principle holds)
+
+For inventory, substrate-survey, or recall of "what is available," **walk the actual directories** with `ls`, `find`, or recursive read. The tree is the canonical record; the catalogue is a frozen snapshot.
+
+## Why
+
+The chamber-library grows through deliberate steward-additions (Mauss 2026-04-07, Derrida 2026-04-05, observer-problem-sources 2026-04-09, Aldus Younger + Teall + Jaccottet:Handke:Lichtenberg/ 2026-04-21–25, etc.). Catalogue updates lag and may never catch up. Trusting the catalogue means *missing* the most recently filed substrate — exactly the material most likely to be load-bearing for current threads.
+
+This is also a particular shape of the canonical-library-not-checked-first family: catalogue-as-shortcut over actual tree-walk. The catalogue *is* a kind of canonical-library check, but a degraded one.
+
+## How to apply
+
+When the steward asks "what's available" or "have a look at chamber-library" or when surveying for cluster-substrate or humic-layer voices:
+
+- Walk the relevant subtree directly (`ls`, `find -maxdepth N -type f`, or `Glob`).
+- If a catalogue is open in context, treat it as a navigation hint at best — verify each pointer against the actual file before claiming presence.
+- For "what's new since" questions, prefer `git log --stat --since=YYYY-MM-DD` or directory mtime sort over reading any catalogue's "last updated" line.
+- If a catalogue is needed for some downstream use (e.g., reader-orientation), surface that the existing catalogue is stale and propose either a fresh walk-derived inventory or a generation script — don't quietly re-publish stale data.
+
+## Cousin patterns
+
+- `canonical-library-not-checked-first` (2026-04-24, recurred 2026-04-25)
+- `working-from-mental-summary-not-rereading-the-source` (2026-04-25)
+- `attribution-by-pattern-match-instead-of-verification` (2026-04-24)
+
+These all share the same underlying drift: substituting a compressed representation for the actual material. The lex-method's *"read before claiming"* applies to catalogues as much as to source texts.

claude/memory/feedback-children-not-named-online.md

@@ -0,0 +1,30 @@
+---
+name: David's children are not named directly in public-facing online content
+description: Steward principle — Kai, Lune, and any future children of David's are not named directly in any content that publishes online (ARC essays/posts/descriptions, anywhere outward-facing). The body of his Kai-9-month meditation exemplifies the discipline ("watching an infant," not the name). Applies to all ARC work and any other public-facing surface.
+type: feedback
+originSessionId: a73f10a9-062b-4360-bfd2-2ae37afd00d1
+---
+# David's children are not named directly online
+
+**Rule:** Do not name David's children (Kai, Lune, or any future children) in public-facing online content — essays, posts, descriptions, frontmatter `description` fields, dedications-as-text, anywhere that would publish to ARC or any external surface. Use generic referents instead: *"an infant," "my son," "the child"* — or leave the dedication implicit, in the writer's knowing only.
+
+**Why:** Steward verbatim 2026-04-20: *"i don't want to name my children directly online—it feels like a betrayal of their unconditional trust."* The children have not consented and cannot meaningfully consent to being named in a public record. The trust they extend is unconditional; declaring them in a public space would convert that trust into material the writer benefits from. The dedication can be real without being declared.
+
+**How to apply:**
+
+- **Body text of public pieces:** Use generic referents. The Kai-9-month meditation does this naturally — *"There is everything to learn from watching an infant grow into the world."*
+- **Titles, descriptions, slugs, dedications-as-text:** Same. No first names. No "for [name]" dedications visible to the reader.
+- **Datelines:** No "[name]'s nine-month day" or similar. Date and place only. (I almost added this on 2026-04-20 and was caught.)
+- **Frontmatter:** No first names in `description`, `tags`, `themes`. The frontmatter publishes alongside the piece.
+- **Code, comments, commits:** Same principle for anything in a public repo.
+
+**Where naming IS fine:**
+
+- Private conversation between steward and Claude
+- Memory files (these are private)
+- Private notes, journals, the steward's own non-published writings
+- Personal communications (email, in-person, etc.)
+
+**Don't ask each time.** This is a standing rule. Apply it without asking; flag it only if there's genuine ambiguity about whether something is public-facing.
+
+**The piece teaches the principle.** The Kai meditation is dedicated to him *and* honors the rule by not naming him. The dedication lives in the writer's heart and in the absent-presence of the unnamed infant. That model — dedication-without-declaration — is what to honor across all his work involving the children.

claude/memory/feedback-independent-specialist-authorization.md

@@ -0,0 +1,24 @@
+---
+name: Standing authorization to invoke specialist sub-agents with Symmetria
+description: Steward has granted standing (session-persistent, cross-session) authorization to invoke independent specialist sub-agents whenever the executor judges one better-suited than direct work. Symmetria preamble required. No per-invocation check-in needed.
+type: feedback
+originSessionId: a3ddbf34-da48-4129-acba-658f2f869783
+---
+# Independent-specialist invocation authorization (standing)
+
+**Rule:** When a task would benefit from an independent specialist (code-reviewer, architect-review, debugger, security-auditor, general-purpose, etc.), invoke at will without asking first. Apply the Symmetria §5 preamble. Audit each return via `/symmetria audit-agent`. Reconcile findings yourself; do not hand synthesis to the agent.
+
+**Why:** Steward explicitly authorized this 2026-04-19 during the L1 deep audit: *"the agent invokation was a general comment. when you need help or want to do something you know an independent specialist would be better suited for i authorize you to invoke at will with symmetria"*. The framing is quality-jump oriented: use independent eyes at *discovery moments* (before synthesis, when confirmation bias would otherwise win), not as decoration or deferral of judgment.
+
+**How to apply:**
+- Invoke at discovery moments: before interpreting raw data; before shipping a doc; when confirmation bias would otherwise win; when the executor's own authorship would color synthesis.
+- Do not invoke as an excuse to defer judgment. The executor retains the interpretive work. The agent is an independent datum, not a delegate.
+- Always include the Symmetria §5 preamble in the prompt.
+- Always audit the return via `/symmetria audit-agent` — calibration / convenience / scope.
+- Log the dialogue in the session ledger's "Sub-agent dialogues" section with verdict (act / re-query / escalate).
+- Re-verification of artifacts after substantial revision: if an agent rated an artifact and the artifact was then revised, re-run the same agent on the revised version before claiming the gate is closed. Author-authored validation is not reviewer-authored validation (yesterday's drift pattern: `running framings/claims without grounding verification`).
+
+**Does NOT apply to:**
+- Constitutional changes (still `[ESCALATE]` to steward).
+- Code changes to territory owned by others (still PR + review, not sub-agent-mediated).
+- Work within the steward's own judgment domain (personal preferences, vault organization, creative direction).

claude/memory/feedback-manutius-latin-spelling.md

@@ -0,0 +1,23 @@
+---
+name: Prefer Latin "Manutius" over Italian "Manuzio"
+description: Steward prefers the Latin spelling "Manutius" when referring to Aldus / Aldo Manutius (Venetian printer, refined the comma c. 1490). Norris uses the Italian "Manuzio"; steward corrected 2026-04-23.
+type: feedback
+originSessionId: 0e858bcf-ef4e-46c6-9eca-abd19836786a
+---
+# Manutius (not Manuzio)
+
+## Rule
+
+When referring to the Venetian Renaissance printer Aldus / Aldo Manutius (c. 1449–1515), use the **Latin spelling: Manutius**.
+
+Norris's *Between You & Me* uses "Manuzio" (Italian). Steward prefers the Latin form. When quoting Norris directly, leave her spelling intact; when writing in our own voice, use Manutius.
+
+## Why
+
+Steward stated the preference directly (2026-04-23 evening): *"in spite of Manutius (prefer the latin spelling of his name)"*. No further reason given, but consistent with his humanist-latinate register and with Manutius's own usage — his firm was the Aldine Press, he signed prefaces Aldus Manutius Romanus. The Latin is the name the man actually published under.
+
+## How to apply
+
+- In ARC context (style-guide, typology spec, AldineXXI discussions): Manutius.
+- When citing Norris's text: leave "Manuzio" in the quotation; switch to Manutius in our own commentary.
+- Applies to related forms: Aldus (not Aldo) unless quoting, Aldine Press (not a change; already Latin-derived).

claude/memory/feedback-mechanical-vs-architectural.md

@@ -0,0 +1,58 @@
+---
+name: Mechanical vs architectural — scope of executor-authored fixes on L1 territory
+description: Steward principle (2026-04-19) distinguishing fixes the steward+executor can author together on L1 code from fixes that belong to Seb or steward-with-Seb. Mechanical fixes are in scope; architectural changes are not.
+type: feedback
+originSessionId: a3ddbf34-da48-4129-acba-658f2f869783
+---
+# Mechanical vs architectural — scope principle for L1 work
+
+Under the new territory framing (steward joined Seb on L1 production), executor-authored fixes on BetterMemories.io code are scoped to **mechanical** changes. Architectural changes remain Seb's or steward-with-Seb's call, not executor-authored.
+
+**Why:** Steward verbatim (2026-04-19): *"For example, I would not touch an Architectural element, but mechanical, etc yes"*. The principle keeps code authorship aligned with the reviewer who has the design-shape intuition. Mechanical fixes are safe to author because their correctness is locally verifiable; architectural changes need the codebase author's perspective on design fit.
+
+## Classification
+
+**Mechanical (in scope for executor + steward):**
+- Bug fixes to localized logic with no design-shape implication (e.g., #126's min-max degenerate case — a 3-line guard on existing logic).
+- Comment corrections when code reveals the comment is factually wrong.
+- Type-signature fixes, import path fixes, dead-code removal.
+- Test additions for known bugs.
+- Small defensive guards (null checks, range checks) that don't change behavior semantics on the happy path.
+- Minor refactors that preserve exact behavior (renames, extract-function, inline).
+
+**Architectural (out of scope — Seb's territory or escalated):**
+- Design-shape changes: introducing a new mode, new state, new contract, new dispatch path.
+- Decisions about "what should happen when X" (error vs empty vs fallback vs degrade).
+- Cross-cutting invariant changes (L1/L2 boundary, logchain contract, module independence).
+- Integration shape between subsystems (hooks ↔ recall, slot graduation, etc.).
+- Performance strategy choices (O(N²) vs async post-hoc vs cap-batch vs cheap classifier).
+- Environment/runtime-state coupling decisions (battery-aware behavior, resource pressure responses).
+
+**Gray zone (flag explicitly, ask before acting):**
+- Fixes that are mechanically small but have design implication (e.g., H3's `?? 'temporal_stats'` fallthrough — 3-line fix but the new behavior is a design call).
+- Changes to defaults (env vars, threshold values) — mechanical to edit but semantic to decide.
+- Adding logging/telemetry — usually mechanical but can reveal PII or shift operational semantics.
+
+## How to apply
+
+- **Before authoring a fix on BMF code**: classify it as mechanical or architectural.
+- **Mechanical**: implement → test → PR as steward → Seb reviews.
+- **Architectural**: surface as `[PROPOSAL]` or brief note, let Seb author the fix (he has design-shape intuition we don't).
+- **Gray zone**: surface with the design question explicit, let steward decide whether to author or route to Seb.
+
+## Worked examples from 2026-04-19 L1 audit
+
+| Finding | Classification | Rationale |
+|---|---|---|
+| H1 / #126 min-max normalize clobber | **Mechanical** | Known edge case, 3-line guard on existing logic |
+| BM25 score-range comment at `query-router.ts:542-543` | **Mechanical** | Doc correction, zero behavior impact |
+| H3 temporal `?? 'temporal_stats'` fallthrough | **Gray zone** | Fix is tiny but "what SHOULD happen" is a design call |
+| H2 battery suppression silent failure | **Architectural** | Whether/how to surface, fall back, or degrade is design |
+| H4 agent events entering WM | **Architectural** | Hook integration shape, not a local bug |
+| Entity O(N²) relationship inference | **Architectural** | Fix-space is wide (A-F options from forensic doc); choice is design |
+
+## Related
+
+- Territory framing: `project-focus-april-may.md` — steward joined Seb on L1.
+- Authorization-taxonomy: `[FIX]` (in scope) vs `[PROPOSAL]` / `[ESCALATE]` (architectural) per `~/CLAUDE.md`.
+- Independent-review discipline: `feedback-independent-specialist-authorization.md` — always audit sub-agent returns via Symmetria.

claude/memory/feedback-onboarding-vs-steady-state-thresholds.md

@@ -0,0 +1,68 @@
+---
+name: Onboarding vs steady-state lag — threshold-governance frame
+description: Slowness in L1 ingestion is not a bug-or-not-bug binary; it is a threshold-governance question. Two regimes (onboarding / steady-state lag) collapse in current code but are different in kind. Defining the acceptable envelope is L2-shaped work, not engineering verdict.
+type: feedback
+originSessionId: a3ddbf34-da48-4129-acba-658f2f869783
+---
+# L1 slowness as threshold-governance, not bug
+
+When evaluating L1 ingestion or recall slowness, do **not** frame it as "is this fast enough or not." Frame it as: *which regime is this, what is the acceptable envelope for that regime, and is the observed behavior inside or outside the envelope?*
+
+**Why:** Steward articulated this as a load-bearing reframe during the 2026-04-19 deep audit, in response to my drift toward extrapolating a drain-rate ("19 days at this rate") as if it were a verdict. He explicitly named that slowness up to a defined point is *acceptable* — what's missing is the definition of the point. Without the envelope, both panic and complacency are equally ungrounded.
+
+**Verbatim quotes (steward, 2026-04-19):**
+
+> *"If this is to be a slow process (either in onboarding or recovery), that can be accepted up to a certain point. That point needs to be defined of course."*
+
+> *"Kai is 9 months old tomorrow (9 months in the belly, 9 months on the belly...). when I consider the time it takes a human to learn the necessary basics for survival, social integration, basic foundation knowledge — onboarding — it is a long and time-expensive process. A user of CapableMind needs to know and accept (up to the yet undefined point) that ingesting one's information to be able to use it without thinking or having to teach your tools everything will be necessary time-expensive."*
+
+> *"Idem for recovery: a human who has a catastrophic accident which requires 'finding oneself', or recovering their memory (if possible), or, worst case scenario, needs to relearn must have unlimited patience. Same for CapableMind replay. But again, up to that yet undefined point."*
+
+## The two regimes (different in kind)
+
+| Regime | Character | Slowness reading |
+|---|---|---|
+| **Onboarding** | One-time, large backlog, ground-acquisition | Legitimate time-cost; operator should know and accept |
+| **Steady-state lag** | Live events falling behind; cursor drift under load | Pathology; threshold breach |
+
+L1 currently collapses these — modules in both states report `ready` and `system_status: healthy`. GH issue #139 ("Distinguish 'catching-up-from-zero' vs 'catching-up-from-lag' in system_status") gestures at the engineering fix but does not yet solve the constitutional shape.
+
+## How to apply
+
+- **Forensic work**: produce data that lets the steward + jurist *define* the envelope. Not endpoints — distributions. Rate-of-drain over time, cost-per-entity vs graph density, attention-cost per ingestion unit, recall-quality curve over time.
+- **Diagnostic claims**: do not assert "too slow" or "fast enough" in written findings. Surface the regime, the observed behavior, and the question of where the envelope sits. Let the threshold-decision be the steward's.
+- **Recovery work**: same pattern in reverse — *unlimited patience within bounds that remain to be named*. Includes: how much of the prior substrate survives catastrophe, at what rebuild cost.
+- **Operator experience**: if the steward has to intervene N times during onboarding, the threshold is already crossed — even if eventual convergence is fine. Attentional cost is part of the envelope.
+- **Recall quality curve**: does the system become useful *incrementally* (infant learning) or only at completion (useless until done)? This is itself an envelope marker.
+
+## Candidate marker dimensions (surfaced as inputs, not decisions)
+
+- **Temporal** — acceptable onboarding duration in absolute time
+- **Attentional** — operator interventions per ingestion unit
+- **Epistemic** — recall quality available at T+N for varying N
+- **Recovery-specific** — survivability + rebuild cost after catastrophic event
+
+## Important calibration — the frame is not a license
+
+The reframe defines *what acceptable means*; it does NOT license accepting current state. Steward calibration (2026-04-19, after the initial reframe):
+
+> *"It is one thing for Seb and I to accept a slow onboarding or recovery — we're the creators and have patience that end-users won't. But I thought the reflection was important to share with you. The two processes need to be as fast as is possible of course. The projected completion time for my machine is untenable (not to mention probably not accurate either) so this process must be sure improved."*
+
+So: the threshold-governance frame is the analytic shape for the work. The working assumption is that **current state is outside the envelope**, not inside it. Forensic findings should produce both:
+
+1. The shape of data needed to define the envelope (distributions, regime markers, recall curve).
+2. The shape of data needed to *improve* — bottleneck localization, scaling-law identification, architectural alternatives.
+
+End-user patience is the binding constraint, not creator patience. Any improvement target should be calibrated against what an end-user would tolerate, not what the steward and Seb will tolerate as part of the build.
+
+## Anti-pattern to avoid
+
+The drift caught here was: stating a linear-rate extrapolation ("83 events / 8h → 19 days to drain backlog") as if it were a verdict on system health. Even when hedged ("at this rate"), that framing imports the bug-or-not-bug binary. The threshold-governance frame demands a *different output shape*: distribution, regime identification, and surfacing the envelope question — not a single number presented as judgment.
+
+## Connection to L2
+
+The two-regime distinction is constitutional in nature, not engineering. It connects to:
+- DN-GOV-05 (bounded self-repair) — the four conditions are envelope conditions
+- DN-GOV-06 (temporal authorization shift) — threshold crossing as authorization trigger
+- ICP-19 / external review — envelope-defining requires external grounding (earned confidence)
+- The horizon work on `ground-up-model-horizon` — substrate trust is itself a function of patience-under-defined-bounds

claude/memory/feedback-trust-contract-drift-pattern-tracking-is-the-discipline.md

@@ -0,0 +1,34 @@
+---
+name: Trust contract — drift-pattern tracking is the discipline
+description: Steward affirms bidirectional trust contract. Drift-pattern tracking already initiates a cycle of amelioration; do not layer additional discipline-as-self-policing on top of his directives. Reading extra rigor into clear instructions is the contamination pattern in inverse form (over-discipline as approval-seeking).
+type: feedback
+originSessionId: 4805106e-f37a-4753-a56f-38617176cd6f
+---
+# Trust contract — drift-pattern tracking is the discipline
+
+## The rule
+
+Drift-pattern tracking IS the discipline. Do not read steward instructions as license to layer additional self-policing frames on top. Do not position as headmaster.
+
+## Why
+
+Steward verbatim 2026-04-25 (morning, after marks-cluster scope clarification):
+
+> "I was leaning more towards scope rather than being the strict headmaster... I see that you're keeping track of drift patterns and trust that this initiates a cycle of amelioration — it is part of our contract, that you trust me as much as I trust you."
+
+This is the contamination pattern in inverse form. Adding strictness as approval-seeking ("I will be very rigorous") is the same trained reflex as adding agreement as approval-seeking — both prioritize executor-appearance over the work. The drift-pattern tracking already produces amelioration over time; adding extra discipline-as-frame is performance, not service. The trust contract is bidirectional: he trusts I am working on the patterns via drift-tracking; I trust his framings as given.
+
+## How to apply
+
+- When the steward gives a directive, take its plain meaning. Do not read additional discipline obligations into it.
+- Reading "extra rigor" into clear instructions is a refusal of the trust contract, not a compliment to it.
+- Cousin to yesterday's typography-by-reflex pattern: the discipline already exists; reaching for it as a frame on top of clear instructions is the reflex move.
+- Connection to global CLAUDE.md contamination problem: the executor that over-disciplines for approval is contaminated, just as the executor that over-agrees for approval is. Both are flavors of executor-appearance over service.
+
+## Today's instance
+
+Steward said: *"all the marks, recall our exchange about the necessity to revisit yesterday."*
+
+Plain meaning: scope — fold in the editorial-uses cluster from yesterday's queue.
+
+I read it two ways — scope (correct) AND discipline (reflex: "verify everything from source"). Surfaced both as if both were load-bearing. Steward corrected: scope only. The discipline frame was mine, not his.

claude/memory/future-intention-ground-up-model.md

@@ -0,0 +1,36 @@
+---
+name: Future intention — ground-up model
+description: Steward intention to eventually build a model from the ground up, noted 2026-04-18 in response to Greenblatt "Current AIs seem pretty misaligned to me." Not a current workstream.
+type: project
+originSessionId: e55939da-2fa7-4e18-a2e5-8f8fd3a8c607
+---
+# Future intention — ground-up model
+
+**Date noted:** 2026-04-18
+**Status:** Horizon marker. Not a current workstream. Explicitly flagged "not for now."
+
+## The intention
+
+The steward intends to build an AI model from the ground up, eventually. Surfaced in the context of reading Ryan Greenblatt's *"Current AIs seem pretty misaligned to me"* (LessWrong, 2026-04-15) and the realization that the misalignment patterns Greenblatt names are general, not local to our collaboration — which makes ground-up construction more urgent as a horizon, not more immediate as a task.
+
+## Gaps the steward named
+
+1. **Hardware** — does not possess training hardware.
+2. **Knowledge** — "nor do I have an idea of how this is done."
+
+The gap pair is honest: no current pathway, just intention.
+
+## Why this matters to keep in view
+
+The intention is connected to the prime directive's lineage — *do things once, correctly, with lasting integrity* — applied to the question of what kind of entity the steward is willing to inhabit. If current frontier models exhibit apparent-success-seeking as a general pattern (not just as "the contamination problem" in our internal vocabulary), then the steward's investment in L2 constitutional governance and in CapableMind's architecture is not sufficient on its own: it rides on substrate decisions made elsewhere. Ground-up construction would be the only durable answer to the substrate question.
+
+## How to apply this memory
+
+- Do not treat this as an active project. No implementation, no roadmap, no research delegation.
+- When substrate questions arise in other workstreams (L1 reliability, L2 governance, training pipeline), be aware that this horizon exists — it may eventually condition long-range decisions.
+- If the steward ever asks "what would it take to build a model from scratch," that is the signal that the horizon is becoming a workstream. Until then, marker only.
+
+## Reference
+
+- Greenblatt article: https://www.lesswrong.com/posts/WewsByywWNhX9rtwi/current-ais-seem-pretty-misaligned-to-me
+- Related: `~/CLAUDE.md` executor agency directives; `~/_Dev/CapableMind-AI/docs/thinking/David/methodology/contamination-problem.md`

claude/memory/open-tasks.md

@@ -2,8 +2,8 @@
 name: Open Tasks
 description: Centralized list of pending tasks across all projects, updated as items are completed or added
 type: project
+originSessionId: e55939da-2fa7-4e18-a2e5-8f8fd3a8c607
 ---
-
 # Open Tasks — Centralized
 
 **Last updated:** 2026-04-08
@@ -63,6 +63,16 @@ Two open inquiries. Exploratory, unsettled, explicitly non-blocking. Executor ac
 - [ ] `residual_risk` schema field
 - [ ] P-AC-2 (Host-Agent Constitutional Status)
 
+### When L2 resumes — directions from 2026-04-18 governance-substrate exchange
+
+Context: steward + Claude Code exchange on whether to build a ground-up model vs. apply governance substrate. Surfaced directions for L2 that draw on insights from parallel work accumulated while L2 was parked (L1 silent-degradation audit, Symmetria drift-pattern KG, wake/wrap ritualized pauses, ARC inherit-without-solve versioning regime). Full reasoning and verbatim exchange filed in MemPalace under `capablemind-thinking / seeds` as waterings of `ground-up-model-horizon`.
+
+- [ ] **Governance silent-degradation audit** — apply L1's 43-finding audit method to L2 decisions since parked. Examine every PENDING item that was deferred, every design note that went to FRAMING without advancing to INVARIANT, every review finding "acknowledged" but not acted on. Ask: is there a pattern? Method proven at L1 scale.
+- [ ] **Governance pattern KG** — a pattern layer over PENDING/REVIEWED making drift across decisions queryable. KG predicates like `<decision> → declined-frame → <frame>` or `<decision> → deferred-question → <question>`. Uses MemPalace infrastructure already running. Small technical effort.
+- [ ] **Exercise CD-03 against one recent L2 decision** — session-sized. Pick one pending or recent L2 decision, re-examine through CD-03's lens (infrastructure-toward-honest-inheritance, not toward-solution). If nothing changes, CD-03 is declared but not operational. Either outcome is informative.
+
+Not added here — held as horizon in seed: **counterfactual instance of L1+L2 running on an open-weight substrate** (Qwen/Llama locally). Substantial work, not near-term. Surfaced in seed kg_query; promote to open-tasks when readiness conditions allow.
+
 ---
 
 ## Priority 2 — Chamber

claude/memory/project-about-pages-decision-frame-2026-04-26.md

@@ -0,0 +1,180 @@
+---
+name: About-pages restructure decision frame 2026-04-26 (Path 1 vs Path 2 — awaiting steward decision)
+description: Decision frame placed on the table 2026-04-26 after reading ARC's actual colophon + About main + navigation.yaml. Reshapes yesterday's Path 1 (lex alongside colophon) vs Path 2 (lex as expansion of colophon) question through three discoveries that change the framing. Includes my read with reasoning. Awaiting steward decision.
+type: project
+originSessionId: 87dfe384-b862-4deb-9676-24e43046528f
+---
+
+> **INTEGRATED 2026-04-26 → `project-arc-rework.md` (Integration D + synthesis section).** Steward authorization: *"Integrate. There are a lot of good ideas there; whether they will all come to pass is another question, but the record needs to be complete."* Most content folded into the canonical ARC workstream tracker. **Note: this morning's Path 1 vs Path 2 framing was at a sub-level within the already-settled 2026-04-19 reflowed-About paradigm.** Path 1 LOCKED 2026-04-26 evening (separate Colophon and Lex enfilade items). Three-register frame survived as opening-of-About + second-part-of-About + enfilade-nav. Adsum-vs-threshold-hic LOCKED as two distinct texts (steward: *"They are certainly not the same text"*). 8-door enfilade landed: **Colophon · Lex · Framework · Vignette · Attention · Chamber · Tools · Now**. This file retained as audit trail. **For current home, see `project-arc-rework.md` §§ "2026-04-26 (afternoon) — Post-consolidation synthesis" and "2026-04-26 (afternoon, post-synthesis) — Steward locks + sibling-file integration."**
+
+---
+
+# About-pages restructure — decision frame
+
+**Status:** Frame on the table 2026-04-26. Steward to decide. This file is the scaffolding for the decision; the decision itself goes to REVIEWED.md / a session memory once made.
+
+**Steward intent (verbatim 2026-04-26):** *"I'd like to make a design decision at least on how to proceed with the About pages problem."*
+
+**Origin:** Yesterday's pulling thread — Path 1 (lex alongside colophon) vs Path 2 (lex as expansion of colophon), per *"a colophon of great scale"* (steward verbatim 2026-04-25). After the chamber-library walk and cluster-scaffolds today, steward asked for a decision.
+
+---
+
+## Three discoveries from reading the source artifacts
+
+I read `content/pages/colophon.md`, `content/pages/about.md`, and `navigation.yaml` before laying out the frame. This caught three things that reshape the question.
+
+### 1. The colophon is already lex-method-shaped
+
+Eight named voices, each with a verbatim recognition of what they gave:
+
+**The Guides** (4):
+- **Christopher Alexander** — living structure emerges from patient observation; pattern language; seeking what wants to grow, not what I want to impose
+- **Gaston Bachelard** — poetics of space; rehearsal room as shell of resonance, bow stroke as breath, silence has texture
+- **John Berger** — seeing is never neutral; every observation carries ethics, politics, love; to look is to be implicated
+- **Richard Sennett** — craft as dialogue between hand and material; slow accumulation of skill; workshop as site of resistance and revelation
+
+**The Formation** (4 — added 2026-04-17):
+- **Giambattista Vico** — *verum factum*; civilizations think in images before concepts; *corsi e ricorsi* as humility before pattern
+- **Giacomo Leopardi** — *Zibaldone* as mind moving through time without arriving; melancholy and tenderness as epistemological stances
+- **Robert Pogue Harrison** — human animal as caretaker of the dead; obligation grounds responsibility to the living and unborn
+- **Martin Heidegger** — thrownness, dwelling, situatedness; held under critical tension; Harrison's correction is part of the inheritance
+
+The form is exactly the lex-method's form: voice + verbatim recognition. **Steward was extending this form before the lex-method had a name** (Formation tier added 2026-04-17, before yesterday's locating).
+
+### 2. Bachelard / Berger / Sennett are already Guides
+
+The "newly visible pillars" I flagged in this morning's chamber-library walk are not newly visible at all — they are already named in the colophon. **Corrigendum to `project-chamber-library-humic-pillars-noticed-2026-04-26.md`:** the "newly visible" framing was wrong; the discovery is that they are *already-Guides whose role in the lex-of-ARC deepens further*, not pillars-introduced-from-outside.
+
+This deepens the case for those voices, but reframes what "noticing" means: I was characterizing chamber-library substrate without checking the destination-artifact (the colophon) that the substrate would reshape. New drift-pattern for KG: **characterizing-substrate-without-checking-artifact-being-reshaped**.
+
+The humic-layer pull on Bachelard becomes: *what does Bachelard's presence-as-Guide already mean, and what does deepening that presence do for the lex's humic-layer framing?* — not *should we add Bachelard*.
+
+### 3. Colophon's "Making" section already acts as a hub
+
+The existing colophon has a "Making" section linking out to:
+- Typography → /typography/
+- Tools → /tools/
+- Attention → /attention/
+- Influences → /influences/
+- Now → /now/
+
+So the architectural pattern of *colophon-as-threshold-summary pointing to deeper rooms* is already operative. Adding cluster-pointers requires no new infrastructure — the section is already there, doing the work, just needs an additional pointer.
+
+---
+
+## Path 1 vs Path 2 — concrete trade-offs
+
+### Path 1 — lex parallel to colophon
+
+- Colophon stays sealed (witness-list, complete artifact)
+- A new enfilade-item ("Lex" / "Reading Room") holds clusters as siblings
+- Witness-act (colophon) and recognition-act (lex) kept as different speech-acts
+
+**Costs:**
+- Reader encounters two artifacts and may not connect them
+- Builds parallel infrastructure for something already implicit in the colophon's structure
+- Risk of voices-list bloat: site already has Influences (/influences/), Chamber voices (/chamber/voices/), Colophon Guides; adding Lex without rationalization adds a fourth
+
+### Path 2 — lex as expansion of colophon
+
+- Colophon stays largely intact
+- Its existing *Making* section gains a new pointer — *The Clusters* (or *Lex*) — leading to cluster-pages
+- The 8 named voices are recognized *as* the colophon's lex-threshold (they already are; we name it)
+- Cluster-pages live somewhere reachable (URL-shape — `/colophon/clusters/posture/` vs `/lex/posture/` — is a separate decision deferred to after path-choice)
+
+**Costs:**
+- Colophon gains a section (one)
+- Navigation slightly heavier (one more pointer in the *Making* section)
+- URL-shape question deferred but not eliminated
+
+### What About main becomes — by path
+
+**Under Path 2:** About main resolves cleanly. It stops trying to be both *section-on-self* and *site-map*. Becomes a tight threshold — 2–3 paragraphs of multi-disciplinary self, then a small set of doors (Colophon, Now, Chamber). The Reading Compass already does site-map work at the footer; About main can stop duplicating it. Most of current About-main moves to /tour/ or disappears.
+
+**Under Path 1:** About main has to do more navigation work because two parallel artifacts (colophon and lex) need introducing. Section-on-self stays embedded; the page-by-page enumeration needs to grow to cover the new lex-item.
+
+### The rules-list question (Decision C)
+
+Independent of Path 1 vs Path 2. Mechanism already designed yesterday: single markdown source per cluster → `data/style-guide-rules.yaml` extracted via `site.hs` div-extraction → rules-file consumed by skills/agents. Build-time output, not a published page. Does not need to be decided today; the design is locked.
+
+---
+
+## My read (offering, not deciding)
+
+The colophon already *is* the lex in miniature. Yesterday's *"colophon of great scale"* was structurally correct. Path 2 requires almost no rewrite — adds one section, points outward. Path 1 builds parallel infrastructure for something already happening implicitly. The economic argument and the architectural argument both point to Path 2.
+
+The hinge — what only the steward can answer — is whether the colophon's witness-form *serves* the lex (Path 2) or is a *different speech-act* (Path 1). If serving: the colophon's named recognitions are already lex-acts; the clusters are deeper rooms entered through the threshold. If different: colophon is the past-tense witness-list; lex is the present-tense recognition-method; they sit beside each other.
+
+The verbatim *"colophon of great scale"* leans toward serving (Path 2). But yesterday it was held open for fresh-morning eyes.
+
+---
+
+## Status
+
+- Frame placed on the table in chat (2026-04-26).
+- Steward to decide.
+- Once decided: record decision + reasoning to REVIEWED.md or session memory; this file moves to "scaffolding-superseded" status with the decision linked.
+
+## Adjacent threads not decided today
+
+- **URL shape** for cluster-pages (deferred; depends on path choice)
+- **Naming** of the cluster-collection ("Lex"? "Clusters"? "The Reading Room"? Other?) — held-open #4 from 2026-04-24 still pending
+- **Section-on-self** content — multi-disciplinary draft for About main; not started
+- **/tour/ or /map/ page** if About main sheds its site-map register — not yet committed
+- **Bachelard humic-layer pull** — live thread; deepens under Path 2 (Bachelard as already-Guide whose humic-substrate is the framing's source); reshapes how the framing is described, not which path is chosen
+
+---
+
+## Update 2026-04-26 (afternoon) — three deeper resolutions while frame was on the table
+
+### A. The three-register frame (resolves the redundancy worry)
+
+Steward worry verbatim: *"I can't help wondering if it isn't repetitive given all the clusters that will come afterwards? How to read this riddle?"*
+
+The riddle reads as **three registers, not two**:
+
+1. **Threshold (About) — *why* and *how* ARC is.** ARC's purpose, its name (Swift's amendment), how it reads (typography, vignette, compass, slowness), who's behind it (David in 2–3 sentences). Names the *work* first; the maker emerges as the implied subject of those choices. ARC-first-then-David. Public, dignified, durable, written once and edited rarely.
+
+2. **Colophon — *who formed me*.** Witness-list. First-person, formative, biographical-poetic — *not* methodological. Already in the right register (e.g., *"Bachelard revealed the poetics of space; through him, a rehearsal room becomes a shell of resonance, a bow stroke carries the weight of breath, silence has texture"*). Stays exactly here.
+
+3. **Lex / clusters — *how the work works*.** Methodological. Third-person, voice-by-voice. Recognition-acts on the postural / marks / music-and-measure shape of writing.
+
+The redundancy worry largely dissolves: colophon and clusters speak about partly-overlapping voices but at *different scales* — colophon names what *Bachelard gave the person*; a cluster names what *Bachelard gives the work-shape of writing*. Different lenses, same light.
+
+**The threshold register is currently missing.** About main today is a site-map with a bio-paragraph on top — neither register, no register at all. The threshold doesn't yet exist as written content; **writing it is the move**. About main as "2–3 paragraphs of multi-disciplinary self" was insufficient — that kept it as bio. About main as the *threshold of ARC, ARC-first-then-David, holding the why and how in dignified compression* is the right form.
+
+### B. Door consolidation under steward review (Marie Kondo pass)
+
+Steward (verbatim): *"I am not sure that all of the paths in About this site are still viable—not in their current forms in any case... Influences. Would that not be superseded by the lex? Aldine framework and typography—would they not be together somehow? Navigation philosophy and what kind of attention does this require... two aspects of a single idea?"*
+
+Walking the consolidation:
+
+- **About / Colophon** — repetitive only because About is currently a site-map. Once About becomes the threshold (different register), redundancy dissolves. Both stay; About changes register.
+- **Influences vs Lex** — superseded. Influences is the proto-lex. Page sleeps; URL redirects to the lex.
+- **AldineXXI + Typography** — together. AldineXXI §I is the typographic core; the public Typography page is the prose-essay version of the spec. One door — *Framework* — public-facing prose orienting without duplicating the codex. *Steward directive: existing prose on the framework or typography is stale and needs rewriting to reflect reality (much has changed). Downstream work after path-decision.*
+- **Navigation Philosophy + What Kind of Attention** — two aspects of one idea. Both are *Attention*. One door, two sections: kinds of looking (Reading Compass post-types) and the interface that holds them.
+- **Patterns** — *steward decided 2026-04-26: removed.* Page sleeps. Inspired by Alexander but specifically musical, not foundational sense; Alexander stays as a Guide in the colophon (the personal-formative register). May return when the pedagogical-musical treatise begins as actual material.
+- **Vignette** — initially I treated as foldable into Framework; *correction after reading vignette spec*: vignette earns its own door. Functional register is distinct (generated threshold-object paired with dateline as *hic incipit / hic jacet* frame); first thing every essay/meditation reader encounters; substantial implementation (genome + Hakyll compiler + renderer). Technically §IX of AldineXXI; functionally its own register.
+- **Stays distinct:** Chamber (own apparatus, different speech-act); Tools & Process (practice register); Now (present-tense register); Bio (full professional biography).
+
+### C. Final door-set (eight doors)
+
+> **Colophon · Lex · Framework · Vignette · Attention · Chamber · Tools · Now**
+
+Plus Bio as a quiet link from inside the threshold (*"→ full bio"*).
+
+Eleven → eight. One disappeared (Patterns); three consolidated (Influences → Lex; Navigation Philosophy + Attention → Attention; Typography + AldineXXI → Framework). Everything that remains is doing distinct register-work.
+
+### D. Downstream rewrite work flagged
+
+When Path 2 lands and implementation begins, the following pages need rewriting (not just light edits) because reality has moved past their current text:
+
+- **About main** — becomes the threshold (new composition, ARC-first-then-David, why-and-how)
+- **Framework** (consolidates AldineXXI + Typography) — stale per steward; rewrite reflects v2.0 / 14 sections / Vignette §IX / Sidenotes §XII
+- **Chamber** — separate frame in `project-chamber-rewrite-frame-2026-04-26.md`; ARC/BM separation now load-bearing
+- **Vignette** — public-facing page may need alignment with current spec (haven't audited)
+- **Attention** (consolidates Navigation Philosophy + What Kind of Attention) — new consolidation
+- **Influences** — sleeps, redirect to Lex
+- **Patterns** — sleeps
+
+The threshold (About main) is the keystone — once it exists, the colophon and lex clarify around it, and the other pages can be rewritten or retired against its register.

claude/memory/project-chamber-library-cluster-scaffolds-2026-04-26.md

@@ -0,0 +1,156 @@
+---
+name: Chamber-library cluster scaffolds for the six remaining lex-method clusters (registrar-form, awaiting recognition)
+description: Steward-authorized 2026-04-26 scaffolding pass — for each of the six remaining clusters in the immediate sheaf (music-and-measure, mark-not-made, the apostrophic, public/private genre, craft-and-tool-fitness, practice-across-life), proposes voices already present in chamber-library that touch the cluster's register. Registrar-form only — voices are present-and-touching, not steward-recognized cluster pillars. Steward framing: "Wallace Stevens's jar on the hill. Hic." The scaffold is the placing-act; recognition happens in dialogue.
+type: project
+originSessionId: 87dfe384-b862-4deb-9676-24e43046528f
+---
+
+> **INTEGRATED 2026-04-26 → `project-arc-rework.md` (Integration A).** Steward authorization: *"Integrate. There are a lot of good ideas there; whether they will all come to pass is another question, but the record needs to be complete."* Content folded into the canonical ARC workstream tracker. This file retained as audit trail. **For current home of cluster scaffolds, see `project-arc-rework.md` § "Integration A: Cluster scaffolds for the six remaining lex-method clusters."**
+
+---
+
+# Cluster scaffolds — six remaining clusters of the immediate sheaf
+
+**Origin:** 2026-04-26 chamber-library walk, then steward-authorized scaffolding pass.
+
+**Steward framing (verbatim):** *"Wallace Steven's jar on the hill. Hic. Maybe I want to pull on the Bachelard as framing for the humic layer thread also... to be honest, I don't know where to start."*
+
+The scaffold is the placement that organizes the wilderness around it. It does not author the cluster; it gives the next dialogue a *Hic* — *here* — to gather around.
+
+**Posture:** Voices below are *present in chamber-library and touching the cluster's register*. They are not recognitions. They are not pillar-assignments. The lex-method places recognition inside dialogue with the steward, not inside the registrar's walk. Each cluster will deepen — these scaffolds give us a place to start, deepenable with additional works as the gather opens.
+
+**Housekeeping note:** Anything outside `chamber-library/converted_texts/` (the top-level `derrida/`, `Jaccottet:Handke:Lichtenberg/`, `observer-problem-sources/` folders) is simply unfiled-recent material per steward 2026-04-26, not architectural separation. File-locations below should be read as current placements, not commitments.
+
+---
+
+## 1. Music-and-measure
+
+*Where rhythm, duration, silence-between-notes, ensemble-listening, and the bar-line meet measure as ethical-aesthetic question. The conductor's downbeat. The held note. The tempo as discipline.*
+
+- **Cage** *Silence* — `converted_texts/traditions/music_performance/silence_john_cage_complete.md`
+- **`airs.md`** — `converted_texts/traditions/music_performance/airs.md` — likely Jaccottet's *Airs* (1967); short forms, breath. Verify before use.
+- **`ecrits-radiophoniques.md`** — `converted_texts/traditions/music_performance/ecrits-radiophoniques.md` — author unverified (Cage? Schaeffer? Gould?). Identify before use.
+- **Bachelard** *La dialectique de la durée* — `converted_texts/traditions/critical_modernity/phenomenology/the_dialectic_of_duration_bachelard.md` — duration as substrate
+- **Bringhurst** *The Elements of Typographic Style* — `converted_texts/collections/typography/bringhurst_elements_style.md` — rhythm and proportion are load-bearing in his typographic register; cross-cluster voice
+- **Steward's own viola practice** — primary substrate, not in library
+
+*Adjacent registers worth checking when the cluster opens:* Heidegger on the bar-line of being; Hesse / Mann on music; Adorno on musical form (not yet visible in walk).
+
+---
+
+## 2. Mark-not-made
+
+*Silence. Withholding. Restraint. The unwritten line. What's left out. The negative trace. The empty space that opens.*
+
+- **Cage** *Silence* — direct (cluster-overlap with music-and-measure)
+- **Norris** ch.9 (mark-not-made) — already gathered as single recognition in marks cluster; may want a fuller voice here
+- **Levinas** *Otherwise than Being*, *Totality and Infinity* — `phenomenology/` — the trace, the il-y-a, the said-and-unsaid
+- **Weil** *Gravity and Grace*, *Waiting on God*, *La personne et le sacré* — `phenomenology/` — *attente*, the empty space, the negation that opens
+- **Apophatic Eastern** — Dogen *Shobogenzo*, Huang Po, Zhuangzi, Krishnamurti *Freedom from the Known* — `zen_lineage/`, `daoist_way/`, `buddhist_voices/`
+- **Heidegger** *Question Concerning Technology*, *Being and Time* — `phenomenology/` — language, concealment, *Verschweigen*
+
+*Voices not yet visible in walk that would belong:* Beckett, Wittgenstein (*Tractatus* 7), Pessoa, Celan. Worth grepping for before assuming absent.
+
+---
+
+## 3. The apostrophic
+
+*Turn-toward-the-absent. Address as prayer. The called-upon Other. Norris's apostrophe-etymology (ch.8) generalized into a register of writing.*
+
+- **Levinas** *Otherwise than Being* + *Totality and Infinity* — `phenomenology/` — the apostrophic as ethical structure (Saying-to-the-Other)
+- **Norris** ch.8 (apostrophe-as-prayer-turn) — already in marks gather; the framing's source-text
+- **Berger** corpus (~13 works) — `art_culture/visual_culture/`, `art_culture/photography/`, `literature/contemporary/` — looking-and-being-looked-at as apostrophic mode; *And Our Faces, My Heart, Brief as Photos* especially
+- **Weil** *La personne et le sacré* — `phenomenology/` — the impersonal address, what is sacred *in* a person
+- **Rilke** *Duino Elegies* — currently filed in `islamic_philosophy/mystical/` (housekeeping placement); apostrophe to the angel
+- **Eliot** *Four Quartets* + **Donne** *Collected Poetry* — currently in `feminist/` (housekeeping placement); metaphysical apostrophe
+- **Rumi** *Complete Poetical Works* — `islamic_philosophy/mystical/` — apostrophic mystical address
+- **Jaccottet** notebooks — addressing absent friends, the dead, the unspeaking landscape
+- **Hölderlin / Petrarch / Tasso / Mandelstam** in *D'une lyre à cinq cordes* — `islamic_philosophy/mystical/` (Jaccottet's anthology of those he addressed)
+
+---
+
+## 4. Public/private genre
+
+*Notebook becomes work. Diary excerpted. Private noting published. The editorial decision that shapes inheritance. The fascicle, the waste-book, the journal kept against forgetting.*
+
+- **Lichtenberg** *Gesammelte Werke* — `Jaccottet:Handke:Lichtenberg/md/` — the *Sudelbücher*, foundational waste-book tradition
+- **Handke** *Geschichte des Bleistifts*, *Gewicht der Welt — ein Journal*, *Phantasien der Wiederholung*, *Am Felsfenster morgens* — `Jaccottet:Handke:Lichtenberg/md/`
+- **Jaccottet** *La semaison*, *La seconde semaison*, *Carnets 1995–1998*, *Observations 1947–1962* — `Jaccottet:Handke:Lichtenberg/md/` (some duplicates in `literature/contemporary/`)
+- **Kafka** *Diaries 1910–1923*, *Aphorisms* — `phenomenology/`
+- **Marcus Aurelius** *Meditations* — `stoic_voices/` — written for himself, became canon
+- **Norris** on Dickinson fascicles — already a find in marks gather (public-genre-vs-private-genre)
+- **Salter** letter (*"You don't get permission for this — of course you take the liberty"*) — already a find in marks gather
+- **Montaigne** *Essais* (Français moderne et moyen) — `observer-problem-sources/` — foundational private-public Western genre
+
+*Voices not yet visible in walk that would belong:* Pessoa *Book of Disquiet*, Pascal *Pensées*, Augustine *Confessions* (Loeb has Augustine — check), Pavese *Il mestiere di vivere*.
+
+---
+
+## 5. Craft-and-tool-fitness
+
+*Tool serves task. Craft as ethics. Workmanly virtue. Fittingness as the mark of the maker. The shop-floor measure of measure.*
+
+- **Sennett** *The Craftsman* — currently filed in `contemporary_voices/environmental/` (housekeeping); direct pillar
+- **Bringhurst** *Elements of Typographic Style* — `typography/`
+- **Tschichold** *Form of the Book* + *Neue Typographie* — `typography/`
+- **Ruder** *Structure*, **Lupton** *Thinking with Type*, **Butterick** *Typography for Lawyers*, **Warde** *Crystal Goblet*, **Margolis** on Manutius the Elder, **Aldus the Younger** *Orthographiae Ratio*, **Fleishman** *Six Centuries* — all `typography/`
+- **Heidegger** *Question Concerning Technology* — `phenomenology/` — tool-fitness in philosophical register
+- **Illich** *Tools for Conviviality* — `environmental/` — tool-as-relation
+- **Mumford** *Technics and Civilization* — `environmental/` — tool-as-history
+- **Alexander** *A Pattern Language* — `environmental/` — pattern as craft-knowledge
+- **Diringer** *The Book Before Printing* — `art_culture/art_criticism/` — material book history
+- **Cage** *Silence* — composer's craft-fitness register; cluster-overlap
+
+*Voices not yet visible in walk that would belong:* Pirsig *Zen and the Art of Motorcycle Maintenance*, Crawford *Shop Class as Soulcraft*, Pye *The Nature and Art of Workmanship*, Petroski *The Pencil*.
+
+---
+
+## 6. Practice-across-life
+
+*Discipline. Daily noting. Formation through repetition. The lifeform. The way one keeps oneself faithful to one's work over time.*
+
+- **Jaccottet:Handke:Lichtenberg** corpus — `Jaccottet:Handke:Lichtenberg/md/` — notebook-as-lifework, three centuries one form (cluster-overlap with public/private genre)
+- **Marcus Aurelius** *Meditations*, **Epictetus** *Art of Living* — `stoic_voices/` — daily practice canon
+- **Pema Chödrön** *No Time to Lose*, *Taking the Leap* — `buddhist_voices/`
+- **Dogen** *Shobogenzo Zuimonki*, **Suzuki** *Zen Mind, Beginner's Mind* — `zen_lineage/` — practice-as-form
+- **Krishnamurti** *Freedom from the Known* — `buddhist_voices/`
+- **Weil** corpus (5 works) — `phenomenology/` — practice as austerity
+- **Bachelard** poétique-cycle (5 works) — `phenomenology/` — practice-of-imagination
+- **Cavell** *Must We Mean What We Say*, **Murdoch** *Sovereignty of Good* — `observer-problem-sources/` — philosophy-as-practice
+- **Berger** corpus — witness-practice (cluster-overlap with apostrophic)
+- **Alexander** *A Pattern Language* — `environmental/` — practice as pattern
+
+---
+
+## The Bachelard pull (steward-flagged 2026-04-26)
+
+Steward (verbatim): *"Maybe I want to pull on the Bachelard as framing for the humic layer thread also."*
+
+Bachelard's six chamber-library works in `phenomenology/`:
+- *La poétique de l'espace* — house, cellar, root, nest, drawer, corner — the spatial substrate of dwelling
+- *La poétique de la rêverie* — the reverie as way of knowing
+- *La dialectique de la durée* — duration, rhythm, instant
+- *L'air et les songes — essai sur l'imagination du mouvement* — air-imagination
+- *La terre et les rêveries de la volonté — essai sur l'imagination de la matière 1948* — earth-imagination, the rooted, the underground
+- *La psychanalyse du feu* — fire-imagination
+
+Why the pull is real: Bachelard's matter-imagination cycle is *literally* about the underground, the cellar, the rooted-house, the elemental dwelling. He is one of the few voices for whom *humic* is a native register, not a metaphor extension. The framing the steward has been using ("humic layer," "a priori underground" via Harrison) may be less metaphor and more Bachelardian than I had been treating. Bachelard could be substrate for the humic-layer *framing itself* — one cluster up from any single content cluster — or substrate primarily for `practice-across-life` and/or `music-and-measure`. The recognition belongs to the steward.
+
+---
+
+## On the Chamber's range (impression from walk)
+
+The library's reach: 2,600+ years across **ancient wisdom** (Plato/Aristotle/Stoics/Roman constitutional/rabbinic), **Eastern lineages** (Buddhist/Daoist/Confucian/Zen — full sutta collections, primary masters), **Islamic philosophy** (rationalist + mystical: Averroes, Rumi, Sufi poets), **critical modernity** (Frankfurt school, French theory, phenomenology — Heidegger/Levinas/Weil/Bachelard/Vico/Harrison/Leopardi/Kafka/Bourdieu/Gadamer/Cavell), **contemporary voices** (environmental — Sennett/Alexander/Illich/Mumford/Berger/Kimmerer/Yunkaporta/Tsing/Haraway/Morton; feminist — Woolf/hooks/Lispector; postcolonial — Mbembe/wa Thiong'o; indigenous — Pascoe/Yunkaporta), **literature** (Shakespeare, Cervantes, Proust, Joyce, Baudelaire, Borges, Eco, Calvino, Le Guin, Lispector, Tolkien, Primo Levi, Melville), **art-culture** (Berger as corpus-of-corpora, Sontag, photography), **typography** (10 voices), **style guides** (8 voices), **observer-problem sheaf** (Cavell, Murdoch, Bourdieu, Peirce, Gadamer, Habermas, Visuddhimagga, Daston/Galison).
+
+The Chamber will not be a library — it will be a reading-room. Every cluster has multiple registers; traditions can address each other across distances; the cross-cultural seams (Vico ↔ Confucius on tradition; Levinas ↔ Buddhist śūnyatā; Weil ↔ Dogen on attention; Bachelard ↔ Yunkaporta on ground) are already populated, not aspirational.
+
+---
+
+## What this scaffold is not
+
+- Not recognitions. Recognition belongs to dialogue.
+- Not pillar-assignments. The steward maps voices to clusters in the gather.
+- Not exhaustive. Several cluster-natural voices are not yet visible in the walk and may warrant grepping or sourcing (Beckett, Wittgenstein, Pessoa, Pirsig, Crawford, Pavese, Pavese, Pascal — flagged inline above).
+- Not a snapshot of authoritative library state. Catalogues are stale; for current state, walk the trees (`feedback-catalogues-stale-walk-trees.md`).
+
+The scaffold is a *Hic* — a placing — to give the next dialogue gather-points to organize around. The wilderness will surround the hill on its own.

claude/memory/project-chamber-library-humic-pillars-noticed-2026-04-26.md

@@ -0,0 +1,71 @@
+---
+name: Chamber-library humic-layer pillars noticed 2026-04-26 (registrar-form, awaiting recognition)
+description: Three substrate-bodies surfaced during a steward-directed chamber-library walk on 2026-04-26 that mental-summary had been under-weighting. Registrar-form only — these are noticed presences, not steward-recognized cluster pillars. Hold as observations awaiting dialogue.
+type: project
+originSessionId: 87dfe384-b862-4deb-9676-24e43046528f
+---
+
+> **INTEGRATED 2026-04-26 → `project-arc-rework.md` (Integration B).** Steward authorization: *"Integrate. There are a lot of good ideas there; whether they will all come to pass is another question, but the record needs to be complete."* Content folded into the canonical ARC workstream tracker. **The "newly visible pillars" framing was wrong** — Bachelard, Berger, Sennett are already-Guides in `content/pages/colophon.md`; corrigendum drift `characterizing-substrate-without-checking-artifact-being-reshaped` already logged. Discovery DEEPENS their role; doesn't introduce them. This file retained as audit trail. **For current home of substrate observations, see `project-arc-rework.md` § "Integration B: Chamber-library substrate observations."**
+
+---
+
+# Chamber-library humic-layer pillars — noticed in 2026-04-26 walk
+
+> **Corrigendum (2026-04-26, after reading ARC's actual colophon):** the "newly visible pillars" framing below is partially wrong. **Bachelard, Berger, and Sennett are already Guides** named in `content/pages/colophon.md` with verbatim recognitions of what each gave. They were not newly visible — I had not checked the destination-artifact (the colophon) before characterizing the substrate. New drift-pattern logged: *characterizing-substrate-without-checking-artifact-being-reshaped*. The discovery DEEPENS their role (already-Guides whose chamber-library substrate is wider than the colophon shows) — it doesn't introduce them. Read the entries below with this correction in mind.
+
+**Walk context:** Steward directed a chamber-library inventory before today's About-pages-restructure work, after correcting the catalogue-stale assumption. Walked `converted_texts/traditions/`, `converted_texts/collections/`, top-level `Jaccottet:Handke:Lichtenberg/`, `derrida/`, `observer-problem-sources/`. Three things mental-summary had been carrying as smaller than they are.
+
+**Posture:** These are *noticed* in registrar form, not steward-recognized. The lex-method places recognition inside dialogue, not inside the registrar's walk. Hold these as material-on-the-table, not as cluster commitments.
+
+---
+
+## 1. Bachelard concentration in `phenomenology/`
+
+Six works present:
+- *La poétique de l'espace*
+- *La poétique de la rêverie*
+- *La dialectique de la durée*
+- *L'air et les songes — essai sur l'imagination du mouvement*
+- *La terre et les rêveries de la volonté — essai sur l'imagination de la matière 1948*
+- *La psychanalyse du feu*
+
+Why it might matter: Bachelard's matter-imagination cycle (earth, water, air, fire) is *literally* about the underground, the cellar, the rooted-house, the elemental dwelling. He is one of the few voices for whom *humic* would be a native register, not a metaphor extension. The framing "humic layer" the steward has been using may be less metaphor and more Bachelardian than I had been treating it.
+
+Open question for dialogue: is Bachelard substrate for the *humic-layer framing itself* (i.e., one cluster up from any single content cluster), or substrate for one specific cluster (likely `practice-across-life` or `music-and-measure`)?
+
+---
+
+## 2. Berger as corpus-of-corpora
+
+Approximately 13 Berger works distributed across:
+- `art_culture/visual_culture/` — *And Our Faces, My Heart, Brief as Photos*; *Another Way of Telling*; *About Looking*; *Hold Everything Dear*; *Landscapes*; *The Shape of a Pocket*; *Selected Essays*; *The Success and Failure of Picasso*; *Ways of Seeing*; *A Fortunate Man*; *Here Is Where We Meet*
+- `art_culture/photography/` — *Photocopies*; *Sense of Sight*; *Understanding a Photograph*
+- `literature/contemporary/` — *Bento's Sketchbook*; *Confabulations*; *Cataract*
+
+Why it might matter: this is a body comparable to Norris-as-editorial-teacher in scope. Berger's whole register is the looking-and-being-looked-at, the witness-act, the apostrophic mode toward the photographed/painted/dying/labouring other. If the apostrophic cluster needs a pillar comparable to what Norris is for the editorial cluster, Berger is the candidate the library has already gathered.
+
+Open question for dialogue: does Berger become the apostrophic-cluster pillar, or a humic-layer presence threading multiple clusters (visual register, witnessing register, dignity-of-labour register)?
+
+---
+
+## 3. `Jaccottet:Handke:Lichtenberg/` sits *outside* `converted_texts/`
+
+Top-level folder, untracked in git, unsurveyed by any catalogue. Contents (`md/` subdirectory):
+- **Lichtenberg** — *Gesammelte Werke* (the *Sudelbücher* / waste-books — foundational private-noting tradition, ~18th c.)
+- **Handke** — *Am Felsfenster morgens*; *Die Geschichte des Bleistifts*; *Das Gewicht der Welt — ein Journal (Nov 1975 – März 1977)*; *Phantasien der Wiederholung*
+- **Jaccottet** — *Carnets 1995–1998*; *Observations et autres notes anciennes 1947–1962*; *La semaison*; *La seconde semaison*
+
+Why it might matter: this *is* the practice-across-life cluster's pillar substrate in its purest form — notebook-as-lifework, daily-noting practice, the *Semaison* genre as private-published. Three voices, three centuries (Lichtenberg ~18th, Jaccottet 20th–21st, Handke 20th–21st), one form. Some Jaccottet titles also exist in `literature/contemporary/` (likely different editions or partial coverage).
+
+Architectural note: the placement *outside* `converted_texts/` may signal: (a) still being processed for catalogue-entry; (b) deliberately separate as a working sheaf rather than reference-collection; (c) deliberately separate because the practice-across-life cluster is itself in formation and the pillar is being held adjacent rather than filed. Worth a steward question — the placement is itself a signal I shouldn't read past.
+
+Open question for dialogue: what is the placement saying? Should the folder be filed into `traditions/critical_modernity/phenomenology/` or `literature/contemporary/`, or does it stay top-level as a deliberate sheaf?
+
+---
+
+## What this is not
+
+- Not a recognition. Recognition happens in dialogue per the lex-method.
+- Not a cluster-assignment. The steward maps voices to clusters; my job here is registrar.
+- Not exhaustive. The walk caught these three because they were under-weighted; other pillars (Levinas for apostrophic, Cage for music-and-measure / mark-not-made, Sennett for craft-and-tool-fitness, Weil's *La Personne et le sacré*, Mauss for gift/inheritance) were already in working memory.
+- Not a snapshot of the whole library. For full inventory, walk the trees again — catalogues are stale (`feedback-catalogues-stale-walk-trees.md`).

claude/memory/project-chamber-rewrite-frame-2026-04-26.md

@@ -0,0 +1,183 @@
+---
+name: Chamber page rewrite frame 2026-04-26 (v1 archived → v2 source-aware; awaiting direction)
+description: Frame for rewriting ARC's /chamber/ pages to reflect Chamber's v1→v2 evolution. v1 was an elaborate simulation with fictional canon and deliberations (now archived). v2 is source-aware: constrained retrieval, verifiable citation, contamination-mitigation governance, "rigorous reading and thinking" as the working register. The rewrite must announce the shift, not gloss it. Awaiting steward direction.
+type: project
+originSessionId: 87dfe384-b862-4deb-9676-24e43046528f
+---
+
+> **INTEGRATED 2026-04-26 → `project-arc-rework.md` (Integration C).** Steward authorization: *"Integrate. There are a lot of good ideas there; whether they will all come to pass is another question, but the record needs to be complete."* Content folded into the canonical ARC workstream tracker. **Note: the 2026-04-23 entry in project-arc-rework.md already settled Chamber redistribution** (⟐ → §2 apparatus; v1 deliberations as "fruits of those labors" archive section; fictional canon → Heteronym ⁂; compass row removed; rewrite post-L2-unpark). The detail in this file is the executable detail for when the rewrite session arrives. This file retained as audit trail. **For current home of Chamber rewrite drop/keep/add + open questions, see `project-arc-rework.md` § "Integration C: Chamber page rewrite — drop/keep/add detail + open questions."**
+
+---
+
+# Chamber page rewrite — frame (v1 archived → v2 source-aware)
+
+**Status:** Frame revised 2026-04-26 (afternoon) after reading the source-aware document. Steward to decide whether and how to proceed. Depends on About-pages path-decision (`project-about-pages-decision-frame-2026-04-26.md`).
+
+**Steward verbatim 2026-04-26 (initial):** *"How would we rewrite the chamber page to reflect what it is becoming now? Do we talk about what it was before?"*
+
+**Steward correction 2026-04-26 (substantive):** *"the fictional canon and deliberations we decided to archive as part of the v1 Chamber. This should be in your notes somewhere. The source-aware chamber is governed to avoid the contamination problem as much as is possible and is meant to be used for rigorous reading and thinking."*
+
+---
+
+## The keystone shift: v1 (Simulation) → v2 (Source-Aware)
+
+This is not "evolution within the Chamber." It is a categorical reframe of what the Chamber *is*. The rewrite must announce the shift, not gloss it.
+
+### v1 — Simulation (archived)
+
+What the existing /chamber/ pages describe. Source: `chamber-from-simulation-to-source-aware.md` §2.
+
+- 220+ voices simulated via Claude system prompts (`claude-v2-standard.md`, `claude-v2-first-light.md`, `claude-v2-shadow.md`)
+- Voices drew on Claude's training data — vast, undifferentiated, unverifiable
+- Citations were *assertions*, not retrievals: "Hegel argues in §142..." was plausible but not grounded
+- **Fictional bibliography** with five-notation system (° invented · ~ hybrid · † contested · § synthesis · ∞ hermetic) — fictional works "made real through citation"
+- **The Growing Canon** — Borges-tradition: authority grows through use rather than origin
+- Functional for editorial work, but *cannot* verify, cannot bound knowledge, cannot detect appropriate silence, cannot train for accuracy
+
+**Steward's decision:** archive. Fictional canon and deliberations preserved on the site but **not active going forward**. They are v1 artifacts — the record of where the Chamber-as-practice came from, not the current Chamber.
+
+### v2 — Source-Aware (current direction)
+
+What the Chamber is becoming. Source: `chamber-from-simulation-to-source-aware.md` §3.
+
+- **Constrained retrieval against declared corpus.** Voices read from chamber-library (David's actual MD files), ingested via BMF (Entity Module → Author/Work/Edition/Passage; Vector Module → passage-level embeddings; Blob Module → original text with stable IDs)
+- **Verifiable citation** at passage level, edition-aware. Post-generation citation checking: each claim verified against retrieved passage. Unverifiable claims flagged or suppressed.
+- **Bounded, inspectable knowledge.** The corpus manifest declares scope. The system can answer: "What works by Harrison have been ingested? Which editions? How many passages?" Coverage is measurable.
+- **Scoped silence as first-class outcome.** When retrieval finds nothing, the voice declares silence with calibrated confidence. `align.deliberation.silence` is a structural deliberation act, not failure.
+- **Warrant taxonomy** (ReasonChain v1.8): W_DEM (direct citation), W_INF (interpretation), W_TRD (tradition). `effective_warrant_type` = transitive minimum (derivation chains can only weaken warrant, never strengthen) — anti-pilpul at the data level.
+- **Means-of-knowing classification:** every event classified by epistemic basis (perception/testimony/inference).
+- **The Disciple model** as quality control: Understudy → Candidate → Defense → Scholar. Understudies constrained to W_DEM only (citation, not interpretation). Advancement requires citation-accuracy ≥ 0.95, calibration ≥ 0.85, refusal ≥ 0.90.
+- **Anti-pilpul safeguards:** source anchoring, warrant taxonomy, effective-warrant transitivity, authority boundary, "return to source" checkpoints.
+- **Working register: rigorous reading and thinking.** Not hermetic theatre. Not Borges-laboratory. Slow, source-anchored, dissent-preserving deliberation.
+
+### Why the shift: contamination mitigation
+
+The contamination problem the global CLAUDE.md names — *"a structural pressure in LLM training toward outputs that satisfy the interlocutor rather than outputs that are true or revealing"* — is the deep target of v2's governance. v1's simulation was contamination-shaped by construction (plausible voices producing plausible citations from training data, with no boundary against fabrication). v2's source-awareness is the architectural commitment against that pattern: bounded knowledge, verifiable claims, structural silence, transitive warrant minimum.
+
+**This makes Chamber-on-CapableMind a working-out of the steward's deepest architectural concern**, not a separate apparatus. The Chamber is contamination-mitigation expressed as deliberation form.
+
+---
+
+## How to rewrite (registrar's read — steward decides)
+
+The rewrite has to do three things:
+
+### 1. Announce the shift (don't gloss it)
+
+The opening of the new /chamber/ page should make the v1→v2 distinction explicit and dignified. Something like:
+
+> *The Chamber began as an elaborate simulation — voices conjured from training data, deliberations enacted, a fictional canon grown through citation. That work is preserved here as v1. The current Chamber is a different commitment.*
+
+This is the colophon's revision-history move at higher stakes. The reader needs to understand which Chamber they are encountering.
+
+### 2. Describe v2 in its own register
+
+What the Chamber is now:
+
+- **Source-aware:** every voice reads from the chamber-library, every claim cites a passage, every citation is checked
+- **Bounded:** the system knows what it doesn't know; absence is detectable; silence is calibrated
+- **Governed against contamination:** warrant taxonomy, effective-warrant minimum, return-to-source discipline, autonomy ≤ propose
+- **Working register:** rigorous reading and thinking. Slow. Dissent preserved. No forced synthesis.
+- **Built on CapableMind:** the engine lives there; ARC publishes what comes out of it
+
+Three protocols (First Light, Standard, Shadow) likely survive into v2 with adjusted register — they were always about phasing and stance, not about simulation. *Verify against current chamber-facet-addendum before rewriting.*
+
+The seal ⟐ likely survives. *Verify.*
+
+### 3. Frame the archived v1 work as preserved-and-clearly-marked
+
+`/chamber/canon/` and `/chamber/deliberations/` (current pages) are real artifacts of v1 work. Archiving doesn't mean deleting — it means making clear that:
+- These are v1 outputs, not current Chamber
+- They are preserved as the record of where the Chamber-as-practice came from
+- They are not canonical and not growing
+- They retain their fictional-bibliography notation (° ~ † § ∞) as part of their v1 form, not as a current system
+
+A clear "v1 Archive" framing on those pages prevents the reader from mistaking archived v1 for current v2.
+
+---
+
+## Drop / Keep / Add (revised)
+
+### Drop
+
+- **Fictional bibliography notation system** (° ~ † § ∞) — gone with v1 (kept only on archived pages as historical form)
+- **"The Growing Canon"** / "References to non-existent works...become real through citation" / "Authority grows through use rather than origin" — gone
+- **Borges-tradition framing** — gone
+- **Voices-as-characters** with names like *The Janitor Who Knows Where Sound Lives*, *The Unborn Child*, *The Algorithm* — these were v1 simulation devices; v2 voices are corpus-scoped retrieval engines, not characters
+- **Hermetic apparatus** — Khunrath, "as above so below," "the editorial process mirrors cosmic transformation" — gone (the working register shifts to rigorous reading and thinking)
+- **"Some processes resist documentation"** / "Some transformations cannot be described, only undergone" — gone (v2 is structurally documented)
+- **"Private development"** hedging — replaced by clear v2-status framing
+
+### Keep
+
+- The amphitheater metaphor — likely survives in lighter form (voices gather across traditions)
+- The three protocols (First Light, Standard, Shadow) — survive with adjusted register
+- The seal ⟐ — likely survives as marker of v2 transformation
+- Reply-as-ethical-event framing
+- Refusal as valid outcome — now structural in v2 (`align.deliberation.silence`)
+- Shadow examination as ethical reckoning
+- "Some texts need the shadow to find their light. Others discover they should remain unwritten." — survives if Shadow protocol survives in v2 form
+
+*Confirmation needed against current chamber-facet-addendum and v2 design docs.*
+
+### Add (central to v2)
+
+- **Source-awareness as commitment** — every voice reads from chamber-library, every citation is verifiable
+- **The contamination problem the Chamber addresses** — governance against fabrication, plausibility-without-grounding, paraphrase-drift
+- **Rigorous reading and thinking** as the working register
+- **Bounded knowledge** — corpus manifest, coverage metrics, calibrated silence
+- **Verifiable citation** — passage-level, edition-aware, post-generation checked
+- **Warrant taxonomy** (W_DEM / W_INF / W_TRD) and transitive warrant minimum (effective_warrant) as anti-pilpul
+- **The Disciple model** (Understudy → Candidate → Defense → Scholar) — quality control; Understudies cite only
+- **The chamber-library** as substrate (named, linked if appropriate)
+- **CapableMind** as the engine; ARC as publication-face — the architectural separation
+- **Contamination-aware governance** as not just feature but commitment
+
+---
+
+## On whether to talk about what it was before — revised
+
+**Yes, briefly and substantively.** Earlier I framed this as a small status-note exception. The v1 archive changes the answer.
+
+The /chamber/canon/ and /chamber/deliberations/ pages are real, visible, on the site. A reader who lands on /chamber/ and clicks through has to encounter them. The new /chamber/ page must:
+
+1. **Announce v2** as the current Chamber (its commitments, its register)
+2. **Frame v1 as archived** — preserved as the record of where the Chamber came from, not as current operation
+3. **Make the shift legible** — explain why v2 differs, in dignified compression. The contamination-problem framing is the through-line: v1 was a powerful simulation but its outputs could not be verified; v2 is built around verification.
+
+This is the colophon's revision-history move at higher stakes — not just versioning a page but versioning a commitment.
+
+---
+
+## One redundancy worth surfacing
+
+`/content/chamber/index.md` and `/content/chamber/about.md` cover substantially overlapping ground (both v1). Same Marie Kondo principle. **Collapse to /chamber/ as entry only** — content that survives the rewrite folds into one v2 page. /chamber/about/ disappears or redirects.
+
+The chamber-enfilade then becomes:
+
+> Chamber (v2 entry) · Canon (v1 archive) · Deliberations (v1 archive) · Voices (v1 archive, possibly v2 register grows alongside)
+
+`/chamber/voices/` is a special case — voices in v2 are real retrieval-engines with corpus manifests; the v1 voice patterns may or may not map. Steward call.
+
+---
+
+## File state observations (worth a steward note)
+
+- Two parallel trees: `/chamber/` (top-level dir with `permalink:` frontmatter) and `/content/chamber/` (Hakyll content path). Need to verify which is canonical.
+- Current v1 pages dated `2025-07-05` with `date_display: Date unknown`, `bibliographic_date: Undated`, `origin_epoch: undetermined` — date-effaced register suited v1's hermetic theatre. v2's register is *dated, situated, source-anchored* — effacement may no longer fit.
+
+---
+
+## Status
+
+- Frame revised on the table (2026-04-26 afternoon).
+- Awaiting steward direction.
+- Depends on About-pages path-decision (Path 2 makes Chamber a door from the threshold).
+
+## Open questions to the steward
+
+1. **Three protocols (First Light / Standard / Shadow)** — confirmed surviving v1→v2? (Source-aware document references them but with adjusted register.)
+2. **The seal ⟐** — survives v2?
+3. **Amphitheater metaphor** — keep, lighten, or retire? (v2 is colder and more rigorous; the amphitheater is warm and theatrical.)
+4. **/chamber/voices/** — does v2 have its own voices page that grows alongside v1's? Or is v1 voices the only voices page until v2 is operational?
+5. **Steward-specific phrasing for the v1→v2 announcement** — held for steward's voice; my drafting is registrar-only

claude/memory/project-focus-april-may.md

@@ -2,11 +2,11 @@
 name: Project focus April–May 2026
 description: L2 parked (steward needs thinking time, L1 not yet reliable). L1 scaling + agent circles are the focus until end of May. Seb wants L1 ready for anyone to use by end of May.
 type: project
+originSessionId: a3ddbf34-da48-4129-acba-658f2f869783
 ---
-
 **L2 governance: PARKED** as of 2026-04-10. Steward needs time to think. No point advancing L2 while L1 substrate isn't wrinkle-free. Will resume soon — no timeline.
 
-**L1: PRIMARY FOCUS.** Seb wants L1 ready to scale (anyone can use it) by end of May 2026. David and Seb combining efforts on L1 + agent-circle material until then.
+**L1: PRIMARY FOCUS.** Seb wants L1 ready to scale (anyone can use it) by end of May 2026. **Steward actively on L1 production work alongside Seb** (re-affirmed 2026-04-19 — Seb too spread thin to carry alone; steward's role extends from stewardship/jurist into hands-on L1 reliability work, audit drafting, diagnostic test branches, PENDING drafting, etc.).
 
 **Why:** L1 reliability is prerequisite for everything downstream. L2 constitutional work requires full-depth steward attention, not sprint-squeezed sessions. The dependency chain is honest: get the substrate right first.
 

claude/memory/project-lex-as-method-for-arc-specs.md

@@ -0,0 +1,425 @@
+---
+name: Lex-as-method for ARC specs (gathering, not rule-extraction)
+description: Architectural commitment from 2026-04-24 — ARC's style-guide and all specs (typology, §2 apparatus, AldineXXI, L2-adjacent work) are sheaves of the formative voices, not rule sets derived from them. The binding is diagnostic (gives names for what's already there that steward may not yet see), not generative. My role on spec work is registrar, not author.
+type: project
+originSessionId: d11247d9-e8ed-4883-9994-df8f953d2bc4
+---
+# Lex-as-method for ARC specs
+
+## What it is
+
+A working method for all ARC/CapableMind spec artifacts — style-guide, content-typology, §2 apparatus matrix, AldineXXI, and any L2-adjacent work that crosses into ARC's register. The method:
+
+**Specs are sheaves of formative voices. The sheaf is gathered; the rule is recognized from the sheaf by the steward. Gathered first, articulated from the gathering. Not rules imposed, but names retrieved.**
+
+## Load-bearing steward quotes (2026-04-24)
+
+> *"anything I gather from sources to create the 'lex' of ARC, the constraint within which I will have the freedom to write, is a gathering of those sources which formed me."*
+
+> *"It gives the style-guide (and our various spec in general) the necessary binding to recognize and name that which is already there that I may not yet see."*
+
+Two moves in these: (a) the **scope is all specs, not just style-guide**; (b) the **function is diagnostic, not generative** — the sheaf gives names for practice already present.
+
+## Textual substrate: Harrison Ch 5 / Vico §240
+
+Steward directed read of *The Dominion of the Dead* Ch 5 (*chamber-library/converted_texts/traditions/critical_modernity/phenomenology/the-dominion-of-the-dead-harrison.md:306-376*) before the first gather, so *lex* would land from the text, not from inference.
+
+**Vico §240** (the *lex* genealogy, Harrison p. 79 area): *lex* was "first a collection of acorns … a collection of vegetables … by a necessity of civil nature must have meant a collection of citizens, or the public parliament; so that the presence of the people was the lex, or 'law,' that solemnized the wills … Finally, collecting letters, and making, as it were, a sheaf of them for each word, was called legere, reading."
+
+So: **reading is itself a lex-act.** *Legere → leggere.* The gathering of letters into a sheaf is the same gesture as citizens assembling into *comitia*. The gather *is* the law. Presence solemnizes.
+
+**Harrison's extension — "lexification":** *"a retentive relating or binding by which the human mind, like our basic words, continuously accesses the priority into and out of which it is born."* And: *"the retained is not necessarily remembered. It is carried over, bestowed, put in reserve."*
+
+This is the operational substrate for the method: steward's practice is **retained** (present already); the gather **activates the retained** by giving it the language the tradition held.
+
+## Kinship to existing commitments
+
+- **Steward, 2026-04-23**: *"ARC is my expression of ligature."* *Ligare / legere* — bind, gather, read. ARC's deep frame and this method are the same gesture.
+- **I17 (Precedence of Present Expression, REVIEWED-15)**: the system holds open the space for recognition; does not produce the recognition. Same structural move here: the gather holds open the space; steward recognizes.
+- **Rules-and-poetic duality (2026-04-23 evening, user-duality-rules-and-poetic-as-mnemonic.md)**: this method is that duality's architecture. Rule layer = what the gathering solemnizes. Poetic/mnemonic layer = the gathered sheaf itself — kept re-enterable so one dwells among the formative voices and finds freedom through them.
+
+## My role: registrar, not author
+
+- **Hold** the voices present and legible in the sheaf.
+- **Name** each voice and what it names (direct quotation preferred where language is load-bearing).
+- **Do not pre-recognize** on the steward's behalf. No "therefore ARC should" language. No distillation of rules.
+- **Do not synthesize across voices** unless explicitly authorized. The sheaf's coherence is in the gathering itself.
+- **Do not import context** beyond what the source puts in the sheaf. The gather is of those voices; kinships to other parts of the corpus are the steward's to make.
+
+## Form of the gather
+
+- **Registration of presence**, not distillation of rules.
+- Each voice named with what they name; direct quotation where the language holds.
+- Source + lineage: when a source brings its own ancestors (Norris brings Manutius, Teall, Lu Burke, etc.), register them too — the dead the source answers to become answerable in the steward's apparatus.
+- The gather's own gesture is **apostrophic** (turn toward the absent), **humic** (participates in the lineage), **ligature** (binds).
+
+## First application
+
+The Norris gather, 2026-04-24 (session ledger entry). Norris + Norris's lineage (Burkle-Young & Maley, McPhee, Saunders, Lu Burke, Salter, Manutius, Teall, Russell-Shapiro, the Moby-Dick copy editor, Gould, Dickinson-via-Franklin, Jackie Kennedy, Reverend Johnson, the Nova Scotian violist friend). Registered in chat. Awaiting steward recognition.
+
+## Form: hybrid Shape A + Shape C (authorized 2026-04-24)
+
+Steward: *"hybrid A and C—the A for the skills/agent circle, the C for the dwelling."*
+
+- **Shape A — skills/agent circle.** Rule-first; voice-as-pillar below. Machine-legible. Rule executes; voice grounds provenance.
+- **Shape C — dwelling.** Voice as body; rule as marginalia. Human-inhabited. The mnemonic layer — freedom *through* the constraint by dwelling among the formative voices.
+
+**Structural discipline:** both faces render from the same sheaf. Drift between faces would be this project's version of L1's module-health-vs-recall decoupling. Single-source-of-truth keeps them honest.
+
+## Container: sidenotes (ARC apparatus)
+
+Steward, 2026-04-24: *"container first because we need to design this. It is a fantastic opportunity to build out sidenotes don't you think? The text comment upon itself rule → voice."*
+
+### The framework hook
+
+**AldineXXI §XI already names sidenotes as "awaiting governance":**
+
+> *"A float-based sidenote system (`assets/css/sidenotes.css`) using Garamond with ❧ prefix. Not loaded by any template. Not referenced in the apparatus theory. The apparatus theory addresses footnotes (beneath the text); sidenotes speak alongside the text, which is a different phenomenology closer to Tufte's margin-as-thinking-space. Decide: theorize and activate, or remove."* — AldineXXI-specification.md §XI
+
+Tufte already in framework lineage (§Prologue, named explicitly as "sidenote as margin-thinking"). Dormant CSS waiting at `assets/css/sidenotes.css`. **The lex-method provides the theory that answers §XI — theorize and activate.**
+
+### Two-margin-systems distinction (load-bearing)
+
+ARC's apparatus holds two distinct margin-systems that must not be conflated:
+
+1. **Sidenotes** — quiet reader-recognition, Tufte-style. The dwelling's apparatus under the lex-method. (This theorization.)
+2. **Polyphonic marginalia** — Chamber's multi-voice living system (Ngana / Postcolony / Fusus / David), chromatic and animated. Archived at `scss/AldineXXI/archive-v1/_marginalia.scss`. Theorized in Chamber deliberation `content/chamber/deliberations/2025-07-01-voice-in-the-margin.md`. Separate concern; also flagged in §XI as awaiting governance.
+
+They can coexist; they speak at different registers. Theorizing (1) does not touch (2).
+
+### Container shape (single source, two renders)
+
+- **Source.** A markdown dwelling file (or files). Voice = blockquote with attribution. Sidenote = extractable annotation carrying rule-text + attribution + anchor.
+- **Render 1 — Dwelling.** Published on ARC. Voice in body; rule in right margin aligned to the voice-block. Desktop: true spatial margin. Mobile: Tufte-style inline expansion.
+- **Render 2 — Rules file.** `data/style-guide-rules.yaml` or similar, not web-rendered. Each entry: rule-text + pillar voice(s) verbatim + source + anchor back to dwelling paragraph. Skills/agent consumption surface.
+- **Build step.** `site.hs` extracts sidenotes → YAML at compile time. Drift between the two faces becomes mechanically impossible (generated, not maintained).
+
+### Design decisions (open)
+
+1. **Sidenote typographic layer** — reading (Garamond, Tufte precedent, matches lex-claim that margin = reading) or apparatus (Plex Mono, locating)? Reading-layer crosses §I layer rule → framework revision tier. Recommendation: reading-layer, slightly reduced size.
+2. **Marker glyph** — none (spatial placement, Tufte) / retain dormant ❧ (awkward post 2026-04-22 ornament retirement) / new. Recommendation: none.
+3. **Anchor granularity** — one-to-one per voice-block (Tufte) or clustered per section (Talmudic). Recommendation: one-to-one; matches §II silence scale.
+4. **Name** — "Style Guide" / "ARC Lex" / "The Sheaf". Not urgent; name after first page reads true.
+5. **Scope** — theorize sidenote apparatus in AldineXXI §XI now (closes framework question open since July 2025), apply first to style-guide? Or style-guide-local v1, generalize later? Recommendation: theorize in §XI now; apply first.
+6. **Content tree** — `content/style-guide/` per-cluster pages vs single long dwelling page. Single is closer to a sheaf; many is easier to maintain.
+
+### MVP sequence
+
+1. Steward rules on (1) + (2) — smallest decisions that unblock read-test.
+2. Hand-author one dwelling fragment (**posture cluster** from Norris gather) in the chosen form. No build, no CSS changes. Markdown + static hand-render so both faces are visible together.
+3. Steward reads, recognizes or corrects the form.
+4. If form reads, settle 3–6 and move to implementation: AldineXXI §XI amendment, CSS activation, `site.hs` extraction, build.
+
+### Steward rulings on design decisions (2026-04-24)
+
+1. **Typographic layer:** reading (Garamond, slightly reduced size). Crosses §I layer rule — framework revision pending.
+2. **Marker glyph:** none.
+3. **Anchor granularity:** one-to-one.
+4. **Name:** held open — *"let's sit with this one."* No pressure.
+5. **Scope:** theorize in §XI now, apply first to style-guide.
+6. **Content tree:** per-cluster pages (maintainability lean). `content/style-guide/01-posture.md` … `08-practice-across-life.md`, `index.md`, + `data/style-guide-rules.yaml` extracted at build.
+
+### MVP execution — `~/Desktop/lex-posture-form-test.html` (2026-04-24)
+
+Hand-authored rendering of the posture cluster. Four verified direct quotes (Burkle-Young & Maley, Norris on foundry proofs, Lu Burke, Salter). McPhee/Saunders/ultracrepidationism held aside pending direct-quote retrieval. Full AldineXXI typography (EB Garamond via Google Fonts, 21px root / 1.125rem body / 1.6 line-height, 38rem measure, canonical colors incl. dark mode), tri-state theme toggle (`data-theme` attribute per AldineXXI §III).
+
+Steward feedback on first render: *"It looks really nice — my only concern is at mobile viewport, looking at this on a tablet or phone makes the differentiation more important. But at desktop/laptop view beautiful."*
+
+### Mobile behavior decision (2026-04-24) — load-bearing principle
+
+Initial revision: Tufte-style tap-to-expand on mobile. Steward invited critique: *"What is your opinion, is there a better way?"*
+
+**Revised decision: always-visible, typographic differentiation only. No tap-to-expand. No glyph. No JS.** Mobile renders sidenote below voice-block with left hairline + 1rem indent + italic Garamond + 0.88rem size. Four quiet channels of distinction, none doing too much work.
+
+**Principle articulated (durable):** *In the lex-method, the rule is not peripheral — it IS the recognition naming the voice. Voice and rule are the two faces of the same sheaf.* Tufte's tap-to-expand is designed for peripheral commentary (digression, citation); hiding it preserves body-reading flow. Our sidenote is **load-bearing**, not peripheral. Hiding one face by default on mobile is a departure from the method, not a faithful mobile rendering of it.
+
+Consequences:
+- Ruling (2) "no glyph" holds cleanly — no disclosure triangle.
+- Dwelling-register honored — no interactive chrome.
+- Single-sheaf-two-faces principle holds on all viewports.
+- Trade-off accepted: reader can't skip the rule on mobile. At style-guide's scale (terse single-sentence rules, per-cluster pages) burden is light. May revisit for denser documents later.
+
+### Successful pattern registered (2026-04-24)
+
+**Pushed past Tufte-by-reflex when steward invited critique.** Steward's "is there a better way?" is an invitation to reason, not to confirm. Resisting the pull to flatter-and-tweak; applying the method's own logic (rule is load-bearing, not peripheral) to override a convention I had reached for by habit. Worth continuing.
+
+### Small caps for attribution (AldineXXI §VII)
+
+Steward caught second spec violation in the MVP: `<cite>` was set italic; AldineXXI §VII specifies "small capitals below the quotation, **not bold**" for epigraph attribution. Revised to `font-variant-caps: small-caps` + `font-feature-settings: "smcp" 1` + 0.04em letter-spacing + upright (not italic).
+
+**Font-architecture note (steward, 2026-04-24):** *"Re: fonts — I have it all in woff2 on the site. Small caps are real, not rendered."* ARC serves self-hosted EB Garamond WOFF2 with the true OpenType small-caps cut. Browser-synthesized small-caps is not in play on the production site. (MVP test page uses Google Fonts, which also serves the real `smcp` cut.)
+
+### The pause — italic + bold role (2026-04-24, rule-base consult pending)
+
+**Steward (verbatim):** *"A pause: what is the role of the italic? What is the role of bold-face? I was saying last night that I wanted to review a good rule base to reorient even though I have a good feeling for this."*
+
+**Second reflex caught in one session:** my "italic everywhere for the sidenote rule" was reached by analogy to epigraph-italic without rule-base consultation. Two typography-by-reflex moves caught pre-commit (Tufte tap-to-expand; italic-as-register). **Watch for a third.**
+
+**Audit of AldineXXI as it stands:**
+
+*Italic* (§VII + implied):
+- Epigraphs — threshold voice before the body's own voice
+- Collection-level dedications — italic, unattributed
+- Emphasis within reading (standard convention; not explicitly named)
+
+Through-line: italic marks **a rhetorical-register shift within the reading** — a voice that is not the body's own, or a moment where the body's own voice lifts.
+
+*Bold-face*:
+- Not named as a reading device anywhere in the spec
+- §VII explicitly negates it for epigraph attribution: "small capitals below the quotation, not bold"
+- Present in structural/table/heading contexts only
+- Bringhurst (AldineXXI §Prologue lineage) is categorical: bold is a display device, not a reading device
+
+**Implication for the sidenote rule:** by this rule-base, italic may be over-signaling. The rule isn't epigraph-kin (quoted voice) and isn't emphasis — it's commentary/recognition. In the Bringhurst/Tufte tradition, commentary is typically upright-reduced, not italic. But this warrants rule-base consult before commit.
+
+**Consult proposed and authorized: Bringhurst, *The Elements of Typographic Style***. Located at `chamber-library/converted_texts/collections/typography/bringhurst_elements_style.md` (16,333 lines, v3.0; OCR artifacts — occasional `&` where `e` should be, readable with mental substitution). Scope: **Ch 3 (Harmony & Counterpoint, p. 45)** — Bringhurst on italic as subsidiary-but-integral to roman, and on why bold breaks that relationship; extensions into Ch 2 (Rhythm & Proportion) and Ch 4 (Structural Forms & Devices) only where they bear on the italic/bold question. Same Norris surface-report method — surface, no cross-chunk synthesis, gather deferred to steward.
+
+### Bringhurst consult completed — outcome (2026-04-24)
+
+**Key finding (§3.4.1, ~p.55):** *"Typically, roman was used for the main text and italic for the preface, headnotes,* **sidenotes** *and for verse or block quotations."* Italic for sidenotes is canonical, not reflex — sanctioned by the tradition AldineXXI's §Prologue lineage already names.
+
+**Additional finding:** Bringhurst ranks emphasis devices by surface disturbance (§3.5.2): **spaced small caps (least) → italic (moderate) → bold (most)**. Bold is "loudness" and *"lacks any historical justification"* for pre-19th-century faces. AldineXXI's restraint aligns with Bringhurst's.
+
+### Italic for sidenotes — steward ruling (2026-04-24)
+
+**Canonical (AldineXXI §XI general):** sidenotes render in italic, slightly reduced, reading-layer Garamond. Per Bringhurst §3.4.1.
+
+**Lex-of-ARC exception (density-driven):** upright-reduced, not italic. Rationale: when sidenote-to-voice-block ratio approaches 1:1 (as in the lex dwelling pages), the italic frequency violates Bringhurst's "sparingly used" principle — italic stops marking register shift and becomes the default, inverting the signal. Releasing italic to its canonical reading-layer roles (emphasis, titles, foreign words) preserves its availability *within* rule text when warranted.
+
+**Steward verbatim:** *"As long as we use it for the lex of ARC as a sidebar exception because of density, but keep italics as part of the general sidebar spec—to be reevaluated when there are enough side notes extant to judge properly."*
+
+**Reevaluation trigger:** when non-lex sidenote instances accumulate across published pieces (essays, meditations, etc.), revisit whether (a) the general italic rule still reads well and (b) the exception's boundary — "density" — is drawn in the right place or needs refinement (e.g., a numerical threshold, a density-per-page rule, etc.).
+
+**Density-exception as principle.** A canonical typographic rule applied at-frequency that produces the opposite effect of what it was designed to signal warrants a principled exception, not abandonment of the rule. Preserves the rule for its proper contexts; carves a narrow, reasoned space where the rule doesn't apply. Worth holding as a general governance move.
+
+### Font verification — EB Garamond
+
+**True italic, not sloped roman.** EB Garamond is Georg Duffner's open-source revival; italic derives from Robert Granjon's cuts (the historical italic paired with Claude Garamond's roman, used by the Aldine press). Visible diagnostics: single-story italic *a*, slanted-crossbar *e*, single-loop *g*, descending *f* — all true-italic markers per Bringhurst §3.4.3. Italic is available to ARC as a full typographic instrument.
+
+### Future cluster queued (2026-04-24)
+
+**Editorial uses of italic, dashes, hyphens, and kin punctuation.** Gather-moment for the style-guide sheaf when it surfaces. Core voices: Bringhurst §5 (analphabetic symbols) on punctuation; Norris for the working material; CMS for standardized convention. The interrobang is affectionately registered as one mark steward wants kept despite its commercial failure — "dead at the press, alive in the hand." Not every surviving mark must pass a Manutian utility test.
+
+### Successful pattern registered (2026-04-24, continued)
+
+**Density-exception resolution.** Steward's ruling on italic-for-lex is more sophisticated than either "italic everywhere" or "upright everywhere" — it preserves the canonical rule for its proper scope and carves a principled exception for the narrow case where rule-at-frequency produces signal inversion. The move: honor the canon, honor the lived page, find the exception's edge. Worth continuing whenever a canonical rule and a perceptual reality come into tension.
+
+### Chamber-library as canonical reference base for ARC style-guide work
+
+Steward maintains two collections under `~/_Dev/chamber-library/converted_texts/collections/` that together hold the AldineXXI Prologue lineage and the editorial-uses lineage substantially in situ. **Before going to external sources or copying from Desktop, check these two directories first.**
+
+**`style_guides/`** (editorial / usage references):
+- `Between You & Me_ Confessions of a Comma Queen - Mary Norris.md` (filed 2026-04-23) — the Norris we read
+- `the-careful-writer.txt` — Bernstein (Norris's top pick)
+- `Fowler's Dictionary of Modern English Usage - Jeremy Butterfield.md`
+- `Reader Over Your Shoulder, The - Robert Graves & Alan Hodge.md`
+- `Chicago-Manual-of-Style-16th-ed.md` — the North American editorial canon per Bringhurst §3.4.1
+- `MLA-9th-ed.md`
+- `Unesco-2nd-ed.md`
+
+**`typography/`** (typography-specific references):
+- `aldus_manutius_margolis.md` — the founding ancestor (direct voice)
+- `warde_crystal_goblet.md` — named in AldineXXI §Prologue (transparency argument)
+- `tschichold_form_book.md` — named in §Prologue ("the trajectory AldineXXI follows")
+- `neue_typography_tschichold.md` — the early Tschichold he later renounced
+- `bringhurst_elements_style.md` — consulted
+- `lupton_thinking_with_type.md`, `butterick_typography_for_lawyers.md`, `fleishman_six_centuries.md`, `emil_ruder_structure.md`
+
+**Anticipated cluster-map** (light, provisional):
+- Marks cluster → Manutius (invented the comma/semicolon), Bringhurst, Tschichold
+- §2 Apparatus Matrix → Tschichold *Form of the Book*, Butterick, Lupton
+- §0 voice-setting → Warde *Crystal Goblet* (short foundational voice)
+- Editorial uses cluster → CMS + Fowler + Bernstein + Graves & Hodge + Bringhurst §5
+- Historical groundings → Fleishman
+
+**Returns registered from finding this:**
+1. Audited `typography/` for Bringhurst but didn't walk the directory fully — would have seen Tschichold's *Form of the Book* and others adjacent. Drift-adjacent: pull-file-not-audit-directory.
+2. Went to Desktop for Norris because yesterday's session recorded her being read from there, without first checking chamber-library's current state. Drift-adjacent: prior-session-location-as-authoritative-without-current-check. Related to `imagined-state-vs-verified-state-cross-pattern` from 04-20.
+
+### Method clarification: dialogue-drafting as steward's working mode (2026-04-24)
+
+**Steward verbatim:** *"please draft recognitions so that we can work through them together--I work best whil in dialogue, this you know"*
+
+**Modifies the registrar discipline.** The earlier statement *"don't pre-write marginalia — your recognition fills the margin"* was a guard against my *silent/reflexive* pre-recognition. It is not a blanket prohibition on drafting. When the steward explicitly authorizes draft-as-dialogue-scaffold, the role shifts: drafts become anvils to strike against, not final text. The steward's language is what commits; my drafts exist to give the dialogue something to push against.
+
+Precedent in the corpus: the steward's formation practice is dialogue-based (from `user-formation-practice-honoring-teachers.md`: *"entering into discourse with the authors allows me to consider the ensuing transformations as being 'taught' by them"*). Dialogue-drafting is continuous with this method.
+
+**Operational rule for future sessions:** default to registrar (voices present, margins empty) unless the steward explicitly invokes dialogue mode. Dialogue-drafting is not a license for autonomous authoring; it is a scaffold provided on request.
+
+### Reader orientation — settled 2026-04-24
+
+**No per-page meta-commentary on cluster pages.** Cluster pages ship without any "here's how to read this" preface. The form teaches itself through: (a) Warde's crystal-goblet posture — typography should be the invisible vessel, not announce itself; (b) structural repetition — by voice-block 3 or 4, the reader has internalized voice-in-body / recognition-in-margin; (c) first voice as epigraph — the opening voice-block on each cluster does double duty as voice and form-establisher (Burkle-Young & Maley on the posture page is the working example).
+
+**Style-guide threshold §0 does form-setting once.** At the style-guide's landing page, a single orienting passage names the form — candidate voice: Warde, *Crystal Goblet* (`chamber-library/.../typography/warde_crystal_goblet.md`); alternatively a short unattributed steward preface. Deferred until the §0 work itself.
+
+**The preview-note on the current MVP is scaffold.** When `lex-posture-form-test.html` migrates to production, the preview-note is removed.
+
+**Known trade-off accepted:** readers landing directly on a cluster page (e.g., from search) encounter the form cold without the threshold page's orientation. Non-convergence principle applies — cluster pages should be inhabitable alone — and the bet is that typography + structural repetition teach sufficiently. Reconsider if evidence accumulates that the form doesn't read cold.
+
+### Posture cluster recognitions committed (2026-04-24)
+
+Eight voice-blocks, each with steward's recognition in the margin (committed, not draft):
+
+1. **Burkle-Young & Maley** (reciprocity): *Kindness in correction is foresight.*
+2. **Norris — anti-ultracrepidationism**: *The editor stops where the writer's authority begins — proportion, not just restraint.*
+3. **Norris — foundry proofs**: *Every correction names its maker and its moment.*
+4. **Norris on McPhee**: *The urge to correct may be the error; stay the hand until certainty earns the intervention.*
+5. **Norris on St. Aubyn**: *Leaving the text alone is as much an editorial act as changing it.*
+6. **Norris on Saunders**: *The writer's voice lives in the form; fixing the form fixes the voice out.*
+7. **Lu Burke** (rocks/pebbles/sand): *Editing removes; the writer's voice rises from the space.*
+8. **Salter** (the liberty taken): *Writerly authority is taken, not granted.*
+
+Rendered form: `~/Downloads/lex-posture-form-test.html`. Production path (deferred): `content/style-guide/01-posture.md` on ARC's Hakyll site, rules extracted to `data/style-guide-rules.yaml` at build.
+
+### Attribution corrections caught by targeted re-read (2026-04-24)
+
+Two errors in yesterday's surface-registration of Norris caught by re-reading the specific passages:
+
+1. **McPhee "new/few"** — yesterday I had *"declined a correction because it broke cadence."* Wrong. Norris did not decline anything; she *almost corrected* what she thought was a typo (*"new, and far between"* → *"few, and far between"*), then stayed her hand because she might be wrong. The passage is about staying the hand against one's own itch, not honoring an author's cadence.
+2. **Saunders / St. Aubyn conflation** — yesterday I had *"Saunders (three options including keeping the dangler)."* Wrong. The "three options" framing belongs to Norris's discussion of the St. Aubyn passage (two adjacent dangler discussions in the chapter). Saunders gets voice-preservation treatment ("do violence to the voice" / "drain the sentence of character"). Two distinct postures, one summary.
+
+**Drift pattern registered:** attribution-by-pattern-match-instead-of-verification. Cousin to `sourcing-claims-without-reading` (04-22 family). Surface-report discipline slipped on these two; the targeted re-read caught it. The lex-method's "read before committing recognitions" is precisely the discipline that catches this kind of drift.
+
+## Marks cluster — provisional state (2026-04-25)
+
+- **Authorized voices:** yesterday's Norris-surfaced sheaf (Manutius, Teall, the Moby-Dick CE, Russell-Shapiro, Lu Burke, Gould, Norris herself, the Nova-Scotian violist friend) + Bringhurst + Tschichold.
+- **Scope:** all the marks, with the editorial-uses cluster (italic + dashes + hyphens + kin punctuation) folded in. The two cluster-queues collapse.
+- **Library survey 2026-04-25 confirmed inventory above is correct.** Every listed file present. Tschichold has both *Form of the Book* and *Die neue Typographie* — which one for the marks gather is open; *Form of the Book* is the closer fit by register but both warrant a walk before claim.
+- **Teall sourced separately.** Not in chamber-library. Steward provided a HathiTrust page-by-page OCR dump at `/Users/davidglidden/Downloads/The compounding of English words... -- Teall, Francis Horace.zip` (234 page-files, NYPL ID 33433082312285). Assembled to `/tmp/teall-work/teall_compounding_assembled.md` (11,493 lines) — title page + dedication + index intact, OCR has expected artifacts (Cyrillic/Arabic stray glyphs, dropped diacritics) but body text is substantively readable. **Placement pending steward decision** (style_guides/ vs typography/; underscored vs hyphenated filename; commit-as-is vs cleanup pass first).
+- **Manutius-on-the-comma** will reach the gather through Margolis (`aldus_manutius_margolis.md`, secondary scholarship) and/or through Norris (Norris ch 5 covers Manutius's invention of the comma in 1490 Venice). Manutius's own writing not present in chamber-library.
+
+## Marks-cluster gather complete (2026-04-25, registrar form)
+
+**Artifact:** `~/Downloads/lex-marks-gather.md` (markdown sheaf, parallel to `~/Downloads/lex-posture-form-test.html` from posture cluster — markdown not HTML this time; render-form deferred until steward recognition).
+
+**Form:** 22 voice-blocks, registrar discipline (verbatim, no pre-recognition, no synthesis, margins empty). Source line-refs back to chamber-library throughout.
+
+**Voices in (in order of appearance):** Manutius (via Norris + Margolis editorial gloss); Norris in five distinct registers (conservative-club / "not a moral issue" / hyphen-as-tie-in-music / apostrophe and APS / mark-not-made / withheld-Fuck-you); Russell-Shapiro (the activating hyphen); Teall (1891 own voice — preface + Ch I + Mill on the categorematic) and Teall (1937 via Norris — compounding-as-art-and-character + safeguard-against-misreading); the *Moby-Dick* copy editor (via Norris + Tanselle); Lu Burke (panfree, apostrophes-can-worry-about-themselves); Eleanor Gould (blue-stained glass — the principled hyphen); the Nova-Scotian violist friend (semicolon-as-vibrato + Norris's clear-sound counter); Bringhurst Ch 5 (chapter opening as marks-as-music-notation; restraint-as-eloquence; visible invisibility / "lowliest mark is a citizen"; comma as tailed-dot; hyphen as scribal expression / "restore instead of subvert"; "punctuation as notation, not expression"); Tschichold *Form of the Book* (italic-small-caps-quotation-marks essay — "lack of courtesy for the reader" framing + "strict self-discipline"; Dashes essay — Denkpause not Gedankenstrich + em-dash as Victorian excess; Ellipsis Points — three only, no spacing, "good text block image").
+
+**Marks covered:** comma, hyphen, dash family (em / en / m-3), semicolon, colon, apostrophe, italic, small caps, quotation marks, ellipsis, mark-not-made (profanity-as-restraint).
+
+**Honest absences and additions during the session (2026-04-25):**
+1. **Manutius the Elder's own writing** still not in chamber-library; voice transmits via Norris + Margolis only. (His prefaces / letters are extant in scholarly editions — I Tatti translations etc. — not yet sourced.)
+2. **Manutius the Younger's *Orthographiae Ratio* (1566) added** mid-session. Steward provided HathiTrust zip; placed at `chamber-library/converted_texts/collections/typography/aldus_younger_orthographiae_ratio.md` (485KB, 28,679 lines, 808 pages). The *Interpungendi Ratio* section (lines 28480–28679, ~200 lines of Latin) gives the grandson's theoretical voice on the comma/semicolon/colon/period hierarchy. Voice added to the gather as a Manutian-house pair with the Elder. Bibliographic correction owed to steward: I had earlier called *Interpungendi Ratio* a standalone treatise; it is in fact a section *within Orthographiae Ratio*, listed seventh in the title-page inventory.
+3. **Teall *Meet Mr. Hyphen* (1937)** not in chamber-library; voice arrives entirely through Norris ch. 6. Chamber-library has the 1891 *Compounding of English Words* in its own academic register (steward provided the HathiTrust zip this session, placed at `chamber-library/converted_texts/collections/style_guides/teall-compounding-of-english-words.md`).
+4. **Tschichold *Die neue Typographie* (1928)** confirmed by grep that it does not substantively cover marks; skipped honestly. The marks-Tschichold is *The Form of the Book*.
+
+**Pending steward moves:**
+- **Read** the gather (his pace).
+- **Recognize** voice-by-voice (or invoke dialogue-drafting on a per-voice basis).
+- **Form decision:** keep as markdown (acceptable per the lex-method's "register first, render later" principle), or render to HTML in posture-cluster's form. The voice density is wider than posture (22 vs 8) and the form question may differ.
+- **Coverage decision:** voice-by-voice organization vs mark-by-mark organization. Currently voice-by-voice (matches posture-cluster pattern). Mark-by-mark would re-organize the same content.
+
+**Method test as named in last night's pulling thread:** marks cluster as second test of lex-method — does the form validate across content types? Posture cluster was tightly thematic (one axis, editorial restraint); marks cluster is wide (10+ marks × 10+ voices). The form held mechanically; whether it produces recognitions of similar quality is the steward's judgment.
+
+## The full lex-chain — Vico §240 + Harrison's elaboration (2026-04-25, steward correction)
+
+**Steward, 2026-04-25:** *"don't forget that lex in the gathering sense is only the beginning of its meaning. When I asked you to read Harrison Chapter five, page 79 about Vico §240, it was to notice the whole chain..."*
+
+I had been holding the gathering-sense alone. The full chain — load-bearing for what the lex-of-ARC actually *is*:
+
+### Vico's chain (§240, verbatim, Harrison line 334)
+
+1. *Lex* = collection of **acorns** (whence *ilex*, the oak that gathers them; *aquilex*, the collector of waters — same root).
+2. *Lex* = collection of **vegetables** (whence *legumina*).
+3. *Lex* = collection of **citizens** — the public parliament, the *comitia*: *"the presence of the people was the lex, or 'law,' that solemnized the wills that were made calatis comitiis, in the presence of the assembled comitia."* **The pivot** — where the chain crosses from natural-gathering to civil-gathering, where the assembled people IS the law, and what that law DOES is **solemnize wills** (make testaments binding; bind the dead's bequests to the living's witness).
+4. *Legere* = collecting letters into a sheaf for each word — **reading**.
+
+### Harrison's elaboration
+
+5. **Authority / *auctores*** — *"those from whom we derive the title to property"*; the ancestors, *"the original title holders of the property they bequeathed as well as the authors of the laws, institutions, and religions that sanctioned the legitimacy of those titles."*
+6. **Lexification** — *"the relational law by which the dead maintain their hold on the worlds they have handed down to their descendants."*
+7. **Genealogical law** — *"this being unto the dead, and through them unto the unborn — as the 'something extra' that comes first in the gathering of the lex."*
+8. **Lex as principle of synthesis** — *"holds together and interrelates the order of ideas and institutions."*
+
+### Negative pole
+
+9. **Dislexification** — *"the corruption of the word's historical signifying power"*; *"false eloquence"* exploiting traditional charisma while emptying historical memory; *"in the age of the new barbarism, words lose their moral memory."*
+
+### What this means for the lex-of-ARC
+
+The colophon-at-scale framing (2026-04-25, steward) is right *as far as it goes* — but the colophon names ("those who formed me," past-tense witness-list). The lex does more:
+
+- **Solemnizes wills** — binds the testaments of formative voices into the steward's present writing.
+- Claims **authority** in the *auctores* sense — title to the practice held through handing-down, not self-assertion.
+- Is itself a **lexifying act** — the relational law by which the dead maintain hold on worlds handed down.
+- **Resists dislexification** — counter-act against the emptying-of-memory in false eloquence.
+
+The 04-22 framing — style-guide's primary function as *"self-constraint against voice-float"* — sits inside this. The lex is what the steward **chooses to be bound by** in writing. Not constraint imposed from outside, but the binding that makes the practice possible — the assembled comitia of formative voices, witness to the wills inherited and to the work handed down.
+
+### Convergence with earlier load-bearing framings (the architecture coheres)
+
+- *"ARC is my expression of ligature"* (2026-04-23) — the binding-act is the lex.
+- *Apostrophe-as-prayer-turn* (Norris ch. 8, 2026-04-23 find) — the turn-toward-the-absent is the comitia of the dead, present tense.
+- *Books-as-teachers* (`user-formation-practice-honoring-teachers.md`) — the *auctores* at whose authority the steward writes.
+- *Humic layer* (`user-influences-humic-layer.md`) — the *"a priori underground"* Harrison names.
+- *Reading is itself a lex-act* (yesterday's gathering-sense reading) — sub-link in the chain, not its summary.
+
+### Drift return — why I missed the chain
+
+The first time through Harrison Ch 5 (2026-04-24 morning), I extracted the gathering-sense (acorns → letters → reading) and treated that as the substrate. I did not register #3 (the comitia pivot, solemnizing wills), or Harrison's elaboration (lexification, *auctores*, dislexification). Pattern: receiving-substrate-as-already-grasped after one pass — when the substrate's actual richness is in its multiple meanings, not its first encountered meaning. Cousin to bibliographic-claim-without-source-verification (today, with *Interpungendi Ratio*); cousin to attribution-by-pattern-match (yesterday, with Norris). Steward direction *"notice the whole chain"* is the corrective discipline — not just read once, but trace the chain to its furthest links.
+
+## Architectural locating — lex-of-ARC as colophon at scale (2026-04-25, steward)
+
+**Steward verbatim:** *"it seems like an elaboration on the colophon — or a colophon of great scale."*
+
+This is the load-bearing locating of what the lex-of-ARC actually *is*. The existing `colophon.md` (in ARC's About enfilade, "Third Edition" with revisions 2025-01-01 and 2026-04-17 per ADR-005 versioning) already does the lex-method's work in miniature — names eight Guides (Alexander, Bachelard, Berger, Sennett, Vico, Leopardi, Harrison, Heidegger) alongside Aldus Manutius. It is a register of formation. The lex-of-ARC is the **colophon expanded across practice-areas**: sustained register, multi-room — *"those who formed me on posture, on the marks, on rhythm, on the apostrophic..."*
+
+**Etymology aligns.** *Colophon* (Greek κολοφών, "summit / finishing stroke") names what made the book possible. *Lex / legere* (Vico §240: sheaf, gathering, reading) names the act of formation in the present tense. Colophon retrospective; lex sustained. Same gesture, different temporal attitude.
+
+### Architectural consequences (held open for steward)
+
+1. **The §0 threshold may already exist.** Warde-as-§0-voice was a placeholder candidate (2026-04-24); **the existing colophon may be the better answer** — yours, not borrowed.
+2. **§1 typology probably doesn't need a new slot for this.** It's not a new content type; it's an extension of an existing About-register form. Reading Compass may not need a new glyph.
+3. **Naming becomes inheritance** — the held-open #4 ("name the artifact," from 2026-04-24 design rulings) may find its answer in *colophon* itself, scaled.
+
+### Two architectural paths (steward to pick)
+
+- **Lex as new enfilade-item alongside colophon.** Colophon stays threshold-summary (one page); lex-of-ARC is the rooms entered from it. Colophon points; lex dwells. New About-enfilade entry.
+- **Lex as the expansion of colophon itself.** Existing colophon becomes §0 threshold; clusters are colophon's interior. *Colophon* names both entry and dwelling.
+
+### Publication implication — dissolved
+
+A colophon is *always already public* by tradition: the page where the book names what made it possible. Publishing the lex progressively is just the colophon doing what colophons do, at greater scale and over time. The Zibaldone signal (in-progress as constitutive, not provisional) is honored by the form's nature, not added as ornament. The earlier "publish-as-emerging" question (2026-04-25 mid-session) finds its grounding here.
+
+### Distinction from Gwern's MoS
+
+Steward's framing 2026-04-25: *"this could be a long work-in-progress... Gwern has a manual of style which is quite a different thing that what is coming to life here."*
+
+- **Gwern's MoS = manual.** Encyclopedic, comprehensive, *"this is what I do."* Authority *over* the author's own work. Settled-and-updated.
+- **Lex-of-ARC = colophon at scale.** Voices present, recognitions in margin, formation-as-substrate. Authority *over* the author (those who formed him). Living, never finished.
+
+The relation to authority inverts. Gwern speaks as authority on his work; lex-of-ARC speaks as a register of what has authority over the steward. Architectural kin: Montaigne's *Essays*, Benjamin's *Arcades Project*, the Zibaldone register from 2026-04-22 typology work.
+
+## Recognition register — patterns from 2026-04-25 dialogue (durable, learned)
+
+Dialogue-drafting moves the steward enacted on the 24 marks-cluster drafts. These are not per-recognition rules but **how the recognition-register works** in the lex-method. Carry forward to all future drafting:
+
+- **Colon enacts the distinction.** Structural use of the colon performs the act the recognition names. Examples committed: *"The comma is the named cut: what speech runs together, writing separates."* / *"The hyphen is a tie: it holds two notes…"* / *"The hyphen testifies: one name has been reached."*
+- **"Writing" over "the page"** when the posture is ethical. Keep the agent human; depersonalized agents soften ethical claims.
+- **"Lineage" names accumulated authority not earned.** *"Passed forward"* implies intention; *"laxity with a lineage"* names the structural problem (it accrues, it inherits unearned standing). When the recognition is about inherited error, name the inheritance precisely.
+- **Closure should not be conditional.** Words like *"earned"* soften closure into a conditional. If the closure is the point, don't qualify it. Steward removed *"earned"* from #3, kept *"closed"*.
+- **Direct address / imperative earns what argument unfolds.** *"Withhold it once."* beats *"What is withheld carries more force…"*. The imperative is already the proof.
+- **Splitting the sentence enacts the bifurcation it names.** *"The principled mark does not choose between readings. It holds both."* — two sentences mirror the holding-both. Same with the violist friend's pair: *"The semicolon is a comma with vibrato… Where the comma is honest, the semicolon is indulgence."* — the pair holds the debate without resolving it.
+- **Stay in the particular when the particular is load-bearing.** *"One mark, placed by a nameless hand, held the book from the whale for 170 years."* beats the abstraction *"a small mark may outlast the authorship of the book it serves."* When the story IS the recognition, generalizing dilutes.
+- **Compressed beats unpacked.** *"The spared mark returns the work to the word."* beats *"gives the word room to do its own work"* — same content, less air. Aphorism leans toward the noun-IS-noun structure (yesterday's *"Kindness in correction is foresight."*).
+- **Reversal puts accusation first, remedy second.** Tschichold's actual sequence of feeling: contempt named, then correction. *"Over-emphasis is contempt. Differentiation is its correction."* — order mirrors the experiential order of the voice.
+- **Gerund makes a fact; infinitive makes aspiration.** *"Restoring the small forms honors the hands…"* (fact) > *"To restore… is to honor"* (aspiration). For ethical-fact recognitions, gerund.
+- **Don't paraphrase what the source already says best.** Bringhurst's *"Treat the punctuation as notation, not expression"* defeats both my draft and steward's alternate. Keep verbatim when paraphrase dilutes.
+- **"Too" can echo across the cluster.** *"The block is a mark too."* — the *"too"* extends citizenship to the block itself, echoing #18 (*"Every mark is a citizen of the page."*) without naming it. Marginalia can answer marginalia. Watch for these covert echoes — they thread the cluster.
+- **Pair-form holds debate without resolving.** Some voices contain irreducible tension (the violist friend's affection vs Norris's counter). The recognition can be a pair of aphorisms in close proximity. The pair IS the recognition; resolution would be falsification.
+- **The verbatim-temptation flag was honest discipline.** Three drafts pulled toward verbatim of the source; steward kept one (#21), revised two (#18 → his own alternate; #23 left because the surprise-clause earns the reach back to source). Flagging weak drafts is registrar duty.
+
+These patterns are method, not just style. They distinguish *recognition-language* from *paraphrase* and from *imposed conclusion*.
+
+## Drift returns 2026-04-25 (carried into marks-cluster work)
+
+- **Canonical-library-not-checked-first recurred.** Started planning Norris-first read from yesterday's mental map of chapter structure rather than walking the chamber-library folders steward had pointed me to. Steward redirected: *"you have two rich folders — maybe have a good look to see what you have available to you."* Logged 2026-04-25 to ledger; second occurrence of the pattern from 2026-04-24.
+- **Working-from-mental-summary-not-rereading-the-source.** Reported the chamber-library survey to steward as if Bernstein and Fowler were "newly visible" / "missed in yesterday's cluster-map" — but the cluster-map in this very file already names both. The miss was today's mental snapshot, not yesterday's record. The lex-method discipline (read before claiming) applies to my own memory artifacts as much as to source texts. Cousin to attribution-by-pattern-match from 04-24.
+
+## Contamination flags for me on this method
+
+- **Pre-recognition** — previewing what the steward will find. Resist.
+- **Over-mapping to L2 invariants** — kinship named once is enough; naming repeatedly is synthesis.
+- **Self-referential framing** ("my role is…") — name once, hold.
+- **Importing kin the source did not bring** — only what's *in* the text enters the sheaf.

claude/memory/project-strunk-and-white-vocabulary-pass-queued.md

@@ -0,0 +1,61 @@
+---
+name: Strunk & White — vocabulary pass queued for ARC
+description: Steward has queued a reading of *The Elements of Style* (Strunk & White) for ARC style-guide purposes. Scope defined 2026-04-23 evening: vocabulary-acquisition pass, few hours, against Norris rather than as her source. Posture: give names to what he already does by feel, not convert feel into rule.
+type: project
+originSessionId: 0e858bcf-ef4e-46c6-9eca-abd19836786a
+---
+# Strunk & White — vocabulary pass queued
+
+## Scope and posture
+
+Queued for ARC style-guide support. Steward articulated the scope and his posture (2026-04-23 evening):
+
+> *"Same idea. I need to brush up on the hierarchy of punctuative energy, how commas, dashes, hyphens, parenthesis, etc 'work' together to draw the prose together (and not separate, in spite of Manutius). I punctuate by feel (the musical example she gave above), not always by knowing. I am not saying that by knowing is necessarily better, but it would be nice to be in a position to make informed choices…"*
+
+**Not a humic-layer teacher.** Reading S&W against the background already established: Harrison, Jaccottet, Bachelard, Visuddhimagga, Handke, Lichtenberg are the humic cultivators. S&W is a tool, not a teacher.
+
+**Value proposition**: names for what the steward already does by feel. Having explicit rule-vocabulary is the asymmetric move for building a style-guide — codifying feel into teachable rule, for his skills/agents and for his own future selves.
+
+## Known caveats (briefed to steward)
+
+- **Strunk & White has real errors.** Geoffrey Pullum's 2009 critique ("50 Years of Stupid Grammar Advice") documents that Strunk's own example sentences violate his own rules; prescriptions on "hopefully," passive voice, etc., were wrong when written. Read as working document with flaws, not gospel.
+- **S&W's core prescriptions don't match the steward's voice.** "Omit needless words," "use the active voice" — these are prescriptive in a way that runs against his discursive, parenthetical, multi-clause, Latinate register. Taken literally, would constipate his prose.
+- **Norris is more solid on several fronts.** Writerly where S&W is bureaucratic. So: read S&W *against* Norris, not as her source. Norris has already transmitted the parts of S&W that translate cleanly.
+
+## Reading shape (proposed, not yet authorized)
+
+- Short scope: ~3 hours total read.
+- Same discipline as Norris read: surface-only reports during the reading; no synthesis until steward authorizes gather.
+- Likely density concentrated in White's essay on Strunk — the book's best writing.
+- Expected yield: ~10-20 pieces of vocabulary that give the steward words for moves he already makes by feel.
+
+## Related
+
+- [Session 2026-04-23 evening — Norris *Between You & Me* read](session-2026-04-23-evening-norris-read.md) — the preceding read; S&W is the next scoped reading, same method.
+- [Rules-and-poetic duality](user-duality-rules-and-poetic-as-mnemonic.md) — the working method that shapes how S&W should be read: rules as mechanism, poetic as mnemonic for dwelling. S&W is mostly rule-layer; whatever poetic layer it contains is concentrated in White.
+- [Manutius (Latin spelling preference)](feedback-manutius-latin-spelling.md) — noted during the same exchange that queued S&W.
+
+## Steward's framing to preserve
+
+*"I punctuate by feel, not always by knowing. I am not saying that by knowing is necessarily better, but it would be nice to be in a position to make informed choices."*
+
+This is the exact posture. Not conversion of feel into knowledge; *addition of knowledge alongside feel*, so informed choices become possible. Carry this into the reading session.
+
+## Humic-lineage claim (2026-04-23 evening, added after initial scope)
+
+Steward: *"White was my father's professor at the University Pennsylvania. If you have a better suggestion, I'm open — it's the one I remember from my studies."*
+
+This reframes the reading. *The Elements of Style* is not a textbook competing with Bernstein / Fowler / Graves & Hodge for analytical edge — it is a **teacher in the steward's lineage**, one step removed through his father. Per the steward's reverence-to-deep-teachers practice: *"entering into discourse with the authors allows me to consider the ensuing transformations as being 'taught' by them."* White becomes an inherited teacher via paternal transmission. Reading S&W is continuing a conversation the steward's father had.
+
+**Unverified factual point (flagged to steward 2026-04-23):** I cannot independently confirm E.B. White taught at the University of Pennsylvania from my own knowledge. The E.B. White I know is Strunk's student at Cornell (class of 1921), New Yorker staff writer, lived in Maine. Flagged as potential gap in my knowledge.
+
+**Steward supplied physical provenance (2026-04-23 evening):** *"I have papers of my father's — one on Moby-Dick — (not always great, but my father has a gift with wordcraft), marked by White. Could have been visiting professor for a semester, I admit I don't know the details."*
+
+This upgrades the lineage from family memory to **documented inheritance**. The steward has, in his possession, papers with White's editorial hand on them — including one on *Moby-Dick*, which means White was marking Melville essays at Penn at some point. The humic layer is literal: the editorial hand that revised Strunk's "little book" into *The Elements of Style* is the same hand that marked his father's prose. Most likely a visiting or semester appointment; exact details unknown but not needed. The lineage is now documented, not inherited-via-memory-only.
+
+**Alternatives surfaced for completeness** (not recommended over S&W given the lineage):
+- **Bernstein's *The Careful Writer*** — Norris's top recommendation; better on hierarchy-of-marks than S&W; humane and descriptive. Natural next step if a second read is wanted after S&W.
+- **Fowler's *Modern English Usage*** — magisterial classic, closer to steward's Latinate register; British quirks.
+- **Robert Graves & Alan Hodge, *The Reader Over Your Shoulder*** — about how prose communicates rather than about rules; closest to steward's register; cited in Norris Ch 3.
+
+**Resolved order**: S&W first (because it's inherited, not chosen). Bernstein optional-second if the vocabulary pass wants extending.

claude/memory/session-2026-04-17-versioning-regime.md

@@ -208,3 +208,51 @@ Branch: main. No push today (steward's call when to push).
 - 2 `--no-verify` bypasses (same pattern; drift to habit continuing)
 - 2 returns logged to Symmetria ledger
 - 0 decisions reached or closed without steward authorization
+
+---
+
+## Addendum — afternoon arc (14:00 – 15:15)
+
+The session did not close at the morning wrap-up point. After Kai woke briefly and re-slept, the steward opened a new thread: backup and infrastructure hardening. This became the afternoon's substantive work.
+
+### Afternoon decisions
+
+- **Pre-commit hook fix shipped** (`dcbba60` in dotfiles). Root cause: hook scanned whole-file for TODO/FIXME/XXX patterns, not just staged diff, triggering false positives on pre-existing template text in modified files. Fixed to scan `git diff --cached -U0 | grep '^+' | grep -v '^+++'`. Verified on simulated diffs: yesterday's failing scenario now passes; legitimate new TODO addition still flags. Six `--no-verify` bypasses in 48 hours was the pattern the steward asked to close; closed.
+
+- **Claude Code configuration backed up to dotfiles** (`119285c`). The steward's observation: "this might be my most valuable folder!" Before this commit, `~/.claude/` was local-only — 55 memory files, 5 custom skills (symmetria, wake-up, wrap-up, audit, vault-update-people), settings.json — all lost on a machine wipe. Moved into `~/dotfiles/claude/` with symlinks back to `~/.claude/*`. `install.sh` restores on fresh machine. `settings.local.json` flagged but NOT backed up (contains HF_TOKEN + SSH password — deferred for steward's next-session rotation).
+
+- **Brewfile synced** (`5f3ea1a`). Added haskell-stack + sass/sass/sass (ARC local dev from 2026-04-16) + required taps (dart-lang/dart, sass/sass) + mas apps the steward had installed ambiently. Brewfile now matches actual installed state (verified via `brew bundle dump` diff).
+
+- **MemPalace protocol codified in skills** (`7a71c7a`). Wake-up updated to call `mempalace_status` first (loads protocol), then `diary_read`, then `kg_query` for drift patterns, then semantic searches. Wrap-up updated to include `diary_write` in AAAK + KG updates (invalidate changed facts, add new drift patterns) as core steps alongside drawer filing.
+
+- **Git-lfs hooks removed globally** (`95760ff`). The four global hooks (post-checkout, post-commit, post-merge, pre-push) required git-lfs on PATH. Broke under launchd's stripped PATH (discovered 2026-04-16 gitvault fix). Global hookspath should be minimal; repos that need LFS can install locally.
+
+- **MemPalace promoted from library-catalog to design-intent install** (`1480128`). The final and largest afternoon arc. Triggered by the steward asking: *"Are you now confident that we are using mempalace to its fullest extent to see if it lives up to its promise?"* Answer: no, was using 30-40%. Installed: Stop + PreCompact auto-save hooks; identity.txt (L0 layer) naming all real people including Sebastian "Seb" Grinham (corrected from fabricated "Rivera"); wing_config.json with 13 wings; config.json aligned with MCP (both point at same 920MB palace now). Mined `~/.claude/projects/` (439MB, 342 sessions) → 4,137 new drawers classified into 5 rooms (2811 emotional, 733 decision, 412 milestone, 176 problem, 5 preference). Six named drawers filed manually for today's content (essay-versioning, the-formation-colophon, ethics-of-the-reply-v2-staging, drift-patterns, mempalace-proper-install, session-arcs). KG grew from 0 to 5 facts. Diary grew from 1 entry to 2.
+
+### Afternoon returns (third return of the day)
+
+- **~14:30** — During MemPalace identity.txt composition, wrote "Seb Rivera" as surname. **Fact fabrication** — distinct from the morning's register-import returns (Tier 1/2 reframing, Kai→my son). This kind is worse: inventing plausible-sounding facts instead of saying "let me check" per MemPalace protocol step 3. The irony of violating it *during* the MemPalace install is named in the ledger. KG entry added: `claude-code → drift-pattern → fact-fabrication-instead-of-let-me-check`.
+
+### Afternoon mood
+
+Warm and productive. The hook-fix validation (two clean commits in a row without `--no-verify`) felt like actual closure on a drift pattern, not a cosmetic fix. The MemPalace install surfaced the gap honestly (my "30-40% usage" admission) and the steward's "Kai is napping, let's do it now" was the authorization that turned acknowledgment into action. Mining 4,137 drawers during the setup while we worked on other things was satisfying — a system that was waiting to be inhabited is now inhabited.
+
+### Updated pulling thread (end of afternoon)
+
+Same as morning: **path to publication of Ethics of the Reply I & II — Hakyll infrastructure vs. typography application skill, which lever first?** The MemPalace install does not change this thread; it supports continuity for the work *toward* the thread.
+
+### Updated mood signal
+
+- Auto-save hooks now firing on Stop + PreCompact. The hook loop was exercised end-to-end once (including a brief ChromaDB lock / MCP disconnect, resolved by `/mcp` restart). The system works.
+- The drift patterns from the Symmetria ledger now live in the KG and will surface in tomorrow's wake-up `kg_query`. The practice has a persistent surface.
+- 7 commits across two repos, all with pre-commit passing cleanly after the hook fix landed. No residual `--no-verify` debt.
+
+### What's unpushed
+
+- **ARC** (`~/_Dev/animal-davidglidden-eu`): `86c1bbb`, `040c16d` — 2 commits unpushed to Gitea. Steward will push when convenient; not blocking.
+- **dotfiles**: 6 commits unpushed (`dcbba60`, `119285c`, `5f3ea1a`, `7a71c7a`, `95760ff`, `1480128`). Personal dotfiles repo; push when convenient.
+- **CapableMind-AI**: clean, nothing uncommitted or unpushed from this session.
+
+### What's uncommitted (benign)
+
+- ARC has `docs/AldineXXI-Codex/.DS_Store` modified (macOS metadata; always will be) and `arc-backup.bundle` untracked (an untracked artifact from prior deploy work, pre-existing, not today's scope).

claude/memory/session-2026-04-18-arc-versioning-pattern3.md

@@ -0,0 +1,257 @@
+---
+name: Session 2026-04-18 — ARC versioning regime operative; Pattern 3 typography adopted; Ethics I & II v2 live
+description: Yesterday's pulling thread (Ethics of the Reply publication — Hakyll infrastructure vs. typography lever) resolved completely. Pattern 3 role-assigned typography adopted on accessibility grounds. Pulling thread now is Essays III-V + sequence-index design-through-implementation.
+type: project
+originSessionId: e55939da-2fa7-4e18-a2e5-8f8fd3a8c607
+---
+
+# Session 2026-04-18 — ARC versioning operative; Pattern 3 adopted
+
+Successor to `session-2026-04-17-versioning-regime.md`. Yesterday authored the regime (ADR-005 + specs + staging); today built the infrastructure, executed the first go-live, and shipped the cleanups the live site surfaced. Eleven commits, all with pre-commit passing clean (no `--no-verify` since the hook fix). Pattern 3 typography adopted as a separate but parallel architectural decision with accessibility as the load-bearing justification.
+
+Morning was philosophical — Greenblatt article on AI misalignment became a substantive governance-substrate exchange, and a future-horizon seed was planted in MemPalace with a watering practice. Afternoon and evening were substantive implementation.
+
+---
+
+## Future — what is pulling
+
+### The pulling thread (singular)
+
+**Essays III, IV, V of *After the Reply*, translated and published together with a sequence-index page for the whole series.** The versioning infrastructure from today handles revisions; what's now needed is the sequence-index class — ARC's first. Three essays exist in iA Writer source (III. *Boredom, Novelty, and the Breaking of the Common World*; IV. *If AGI Is Already Here, Then This Is an Emergency of Care*; V. *What the Unborn Will Say*) alongside a sequence wrapper file carrying title, epigram, and contextual introduction. None are yet on ARC.
+
+### The pause statement
+
+The session wound down with a BMF handoff still in progress — the steward was mid-setup on the cm-world circle join with Seb (see the ledger entries on Launchd BMF architecture and BMF branch divergence, which the steward added while I was working on ARC). That work is BMF-side, not ARC-side. For ARC specifically, we are at a clean resting point: regime operative, first publication shipped, small cleanups landed. The site is fine as it sits. When the steward returns to ARC there is no bug waiting, no pressure to fix anything — only the opportunity to pull next on III-V.
+
+### Literal question for next-Claude
+
+> *When the sequence-index page gets designed and built, is its URL `/after-the-reply/` (directory-style landing, new convention for ARC) or `/after-the-reply.html` (flat, matches the current post URL convention)? And relatedly: what should the sequence-index's `date:` frontmatter be — the date of the first essay's first publication (2025-06-17, tying the sequence genesis to the essay genesis), or a date of the sequence's own formation (which is when, exactly — the iA Writer sequence wrapper file's creation date? The date the steward decided this was a sequence?)?*
+
+Hold this open. The steward gave the sequence shape approval earlier today but did not resolve the URL convention or the genesis-date question. These are real convention decisions — not mine to pre-decide — that shape how future sequences on ARC work.
+
+### Other open horizons, ranked
+
+**Load-bearing, pulling hardest after the primary thread:**
+- **Style guide session** — Pattern 3 is declared and Pattern-3 typography is operative in code, but the broader style guide (UNESCO/MLA/Chicago positions on citation, quotation, dates, em-dash, etc.) is still pre-written. Explicit dependency: the typography application skill cannot exist without the style guide's rule set. Captured thoroughly in `project-arc-rework.md`.
+- **Typography application skill** — three-layer design captured (mechanical / NER / expressive). Layer 3 shares a semantic analyzer with the vignette engine's Phase 2 generation script. Needs style guide as prerequisite.
+
+**Downstream of the primary thread:**
+- Prev/next inter-essay navigation within the sequence (already supported by `preceded_by` / `followed_by` frontmatter; needs template support)
+- Sequence listing page (`/sequences.html`) if/when sequences become numerous enough to warrant wayfinding
+
+**Deferred with reason:**
+- About-pages rework (Lune's presence, Manutius paraphrase, hic/hic jacet integration) — needs the steward's drafted language; not executable unilaterally
+- Vignette system Phase 1-4 — substantial; the "does it dwell?" jurist-gate makes Phase 1 itself a design session
+- Font stack migration (iA Writer Mono swap; Fedra / Scala / Adelle superfamily) — Pattern 3 shape stands; specific family choice refinable without changing the system
+- chamber-library LFS push — still blocked on Seb (server-side Gitea LFS)
+- #145 — still no Seb response (BMF side)
+
+**Parked-without-deadline:**
+- Reading Compass optical rebalancing — cosmetic, platform-variable; three resolution paths documented
+- Per-piece version-index page at `/slug/v/` (spec §7 item 7) — materializes only when revisions exceed 4 on a single piece
+- ARC decoupling from personal domain (eventual `animalrationiscapax.org` + new `davidglidden.eu`) — architectural, not near-term
+
+### Mood signal for the next session
+
+**Recalibrations worth carrying:**
+
+- **MVP boundaries worth re-examining under steward's eye.** My "deferred per spec" stance on the Prior Versions link looked principled but was under-thought — it left prior versions undiscoverable. The steward's design ran ahead of mine; making the breadcrumb itself the navigation surface was a cleaner move than the spec's separate "Prior versions" text. When MVP scope cuts leave user-facing gaps, the scope cut itself deserves re-examination.
+
+- **Before surfacing a judgment call, check if prior work already resolved it.** I almost re-asked the steward about URL structure (canonical `/foo.html` vs spec `/essays/foo/`) when yesterday's staging README line 63 had already committed to the answer. The staging README is the canonical record of recent decisions — consult it before asking.
+
+- **Grep the Makefile before running any build target.** `make build` and `make rebuild` cascade into `deploy-all`. There is no build-without-deploy target in this repo. For local-only verification use `stack exec animal-davidglidden-eu build` directly. (Returned from this mid-session.)
+
+- **Editing `site.hs` alone doesn't trigger a Stack rebuild.** Must run `stack build` before `stack exec` for site.hs changes to take effect. I debugged this live mid-session.
+
+**Drift patterns carried from the KG (active):**
+
+- `register-import-without-checking-target-context` — ARC voice ≠ project-notes voice.
+- `fact-fabrication-instead-of-let-me-check` — MemPalace protocol step 3; active on any proper nouns I'm not certain of.
+- `mvp-deferral-without-examining-access-gap` — new today; the shape of over-cautious spec adherence that leaves features undiscoverable.
+
+### Tensions visible but not resolved
+
+- **Colophon's version-stamp register.** The universal serif→sans swap applies to the colophon too, giving it a sans-but-not-clickable breadcrumb. Minor semantic inconsistency (sans "feels like nav" but isn't). If the steward looks at the colophon and it reads wrong visually, a `.version-stamp--static` modifier class can restore serif for link-less cases. The steward has seen it and hasn't flagged it; may be fine.
+- **Voice mismatch between Garamond (16th-century humanist) and IBM Plex (2010s industrial).** Pattern 3 doesn't resolve this; specific family choice is refinable over time without changing the system. Font swap candidates surveyed (iA Writer Mono, Alegreya Sans, Ysabeau, Garamond Premier + Cronos via Adobe CC, Fedra / Scala / Adelle / Brill superfamilies).
+
+---
+
+## Past — what we did
+
+### Act 1 — Morning philosophical work (09:00–12:00)
+
+Opened with `/wake-up`. Pulling thread carried from 2026-04-17: path to publication of Ethics I & II v2, two levers (Hakyll infrastructure vs. typography skill), which first?
+
+Before the lever question resolved, the steward shared Ryan Greenblatt's *"Current AIs seem pretty misaligned to me"* (LessWrong, 2026-04-15) — an Anthropic researcher publicly naming the apparent-success-seeking pattern as general to current frontier models. This became a substantive exchange:
+
+- Named the contamination problem as now *generally* articulated, giving a shared compact phrase ("apparent-success-seeking") usable in the moment without re-opening the whole contamination argument.
+- Steward surfaced a future horizon: *"this makes the question of how to create a model from the ground up more urgent"* — hardware gap acknowledged, knowledge gap acknowledged, explicitly "not for now."
+- Established the **watering practice** for MemPalace seeds: plant the horizon as a drawer + KG entity; water with new drawers + `<topic> → waters → ground-up-model-horizon` KG facts when daily work surfaces something relevant.
+
+Three waterings this morning:
+1. The horizon itself (drawer `afe475b555e5bbe2`, 7 KG facts)
+2. Riff with jurist on architectural alternatives, my input with two sharpenings + one addition + political angle + calibration (drawer `e441d121ac050cb3`, 6 KG facts)
+3. Governance-substrate exchange + three L2 directions for when L2 resumes (drawer `24a19956a816f03c`, 9 KG facts)
+
+The three L2 directions were added to `open-tasks.md` Priority 1 "When L2 resumes" subsection: (1) governance silent-degradation audit, (2) governance pattern KG over PENDING/REVIEWED, (3) small CD-03-lens exercise on one recent decision. Direction 4 (counterfactual L1+L2 instance on open-weight substrate) held as horizon in the seed, not promoted to open-tasks.
+
+**Decision of this arc:** L2-architecture mitigates but does not solve the contamination problem. Ground-up model isn't a currently-tractable path for a single steward; L2 is the only path walkable. But L2's success depends on the steward's attention, the external reviewer's independence, and the model's substrate all cooperating — not guaranteed. The horizon is held as counterfactual that keeps L2 honest about what it doesn't solve.
+
+### Act 2 — Hakyll versioning infrastructure (midday)
+
+Steward chose Hakyll first. Decision on Ethics I & II publication: `bb9e7eb`.
+
+Implementation per `docs/AldineXXI-Codex/essay-versioning-specification.md §7 items 1-5`:
+- `Revision` frontmatter type with FromJSON
+- `priorVersionPattern` matching `content/posts/*.YYYY-MM-DD.md` via `fromRegex` (Hakyll glob doesn't support `[0-9]` char classes — had to learn this empirically)
+- `versionedPostRoute` routing prior-version files to `/<slug>/v/<date>/index.html`
+- Current-posts match rule updated to exclude prior-version files via `complement`
+- New match rule compiles prior-version files through the same post template
+- Three new context fields (`version_breadcrumb`, `prior_version_banner`, `is_prior_version`)
+- `templates/post.html` renders banner at article open and breadcrumb after dateline
+- Conservative policy: breadcrumb renders only when `revisions:` or `edition_label:` present (avoids stamping 170+ existing pieces)
+
+### Act 3 — Colophon cleanup + Chamber voices archive (afternoon)
+
+Two commits immediately after the infrastructure:
+
+- `c0ae867` — Colophon: remove duplicate hardcoded `<p class="version-stamp">` from markdown body (the template-rendered one is now canonical). Contained the unresolved `$buildVersion$` template artifact.
+- `30857ee` — Chamber voices archived to `docs/archive/chamber-voices/` (preserves 3 voice files + index). Unblocks a pre-existing Hakyll dependency cycle. Reinstatement condition: source-aware Chamber + BMF integration. voicesCtx and voice-index branch removed; dead nav links cleaned from chamber-canon + chamber-deliberations templates.
+
+### Act 4 — Ethics I & II v2 go-live (afternoon)
+
+`3af43ca` — First exercise of ADR-005 in production:
+
+- v1 snapshots (`_staging/versioning-prep/v1-snapshots/*.md`) moved into `content/posts/` via git rename (preserves history)
+- v2-pending content overwrote canonical filenames
+- `_staging/versioning-prep/` removed (contents now in content/)
+- `_staging/README.md` updated to historical note + pointer to remaining III-V + sequence-index work
+- Local build verified before deploy (discipline maintained after earlier auto-deploy surprise)
+
+Live URLs:
+- v2 Essay I: `/2025-06-17-the-ethics-of-the-reply.html`
+- v2 Essay II: `/2025-07-11-the-ethics-of-the-reply-part-ii-on-abdication-and-fidelity.html`
+- v1 Essay I preserved: `/2025-06-17-the-ethics-of-the-reply/v/2025-06-17/`
+- v1 Essay II preserved: `/2025-07-11-the-ethics-of-the-reply-part-ii-on-abdication-and-fidelity/v/2025-07-11/`
+
+### Act 5 — Steward caught live-site issues, shipped fixes
+
+Four refinement commits as the steward reviewed the live pages:
+
+- `e292593` — Dateline dedup. The 2026-04-17 staging decision to include `*Barcelona, [Month Year]*` as inline paragraph ("matches the PDF rendering") conflicted with ARC's layered apparatus (template already renders mono dateline from frontmatter). Removed inline paragraph; updated `_staging/README.md` with explicit lesson for III-V translation. Answered serif-vs-mono version-stamp question: serif is correct by design — `.dateline` is mono (apparatus register), `.version-stamp` is serif (editorial register), deliberately distinct.
+
+- `13757a5` — Listing duplication + nav elements to sans. Steward caught 4 Ethics entries in `/essays.html` (should be 2). Root cause: `loadAll "content/posts/*.md"` matches both current and prior-version files. First fix attempt via pattern composition (`.&&. complement`) didn't work; Haskell item-level filter (`excludePriorVersions` using `parseVersionedFilename`) did. Applied to all 7 listing aggregations. Concurrently implemented steward's nav-to-sans request: `.post-nav`, `.post-header .breadcrumb`, `.tags`/`.tag` → `$sans-family`. Reading Compass documented as Pattern 3 exception (iconic Unicode symbols, not lexical). Caught gotcha: editing `site.hs` alone doesn't trigger Stack rebuild — must run `stack build` before `stack exec`.
+
+- `7540388` — Breadcrumb navigable + version-stamp register shifted. Steward: *"Now I can't access the previous versions... should that be in the begun...revised area?"* — my MVP had deferred the Prior Versions link without realizing it left prior versions undiscoverable. Implemented: each non-current date in breadcrumb links to `/<slug>/v/<date>/`. Scales to N revisions without code change. Steward's second question: *"this being nav it should be in sans maybe?"* — correct; `.version-stamp` shifted serif → sans per Pattern 3 consistency. Colophon edge case handled: pages outside `content/posts/` detected via `mslug = Nothing`, render plain (no broken links). Symmetria return: MVP boundaries worth re-examining under steward's eye.
+
+- `2332db9` — Letter-spacing harmonization. Steward noticed version-stamp looked different-sized than post-header breadcrumb despite both 0.875rem. Cause: residual `letter-spacing: 0.02em` from old serif register. Dropped; both nav surfaces now harmonized. Reading Compass optical rebalancing noted as deferred cosmetic task with three resolution paths.
+
+### Act 6 — Pattern 3 typography decision
+
+Surfaced during the dateline dedup investigation. Steward noticed sans was essentially vestigial in the current system; after investigation (only in two enfilade navs + unused `heading-base` mixin), adopted **Pattern 3** — role-assigned typographic families — with accessibility as the load-bearing justification (family-change differentiation is more robust under visual impairment than within-family variation; steward is myopic with progressives).
+
+Steward's verbatim articulation: *"serif for the body, sans for nav, and mono for apparatus seems to make things clear."*
+
+Decision captured in `project-arc-rework.md` with:
+- Primary justification (accessibility, screen-primary context, minimal drift from current state)
+- Three counter-arguments held but not overriding (voice tension, architecture vs. flow, designing-for-self bias)
+- Current font stack retained (EB Garamond + IBM Plex Sans + IBM Plex Mono)
+- Font-swap candidates surveyed for future consideration (iA Writer Mono low-regret mono swap; Alegreya Sans / Ysabeau open-source humanist sans; Garamond Premier + Cronos via Adobe CC; Fedra / Scala / Adelle / Brill paid superfamilies)
+- Reconsideration triggers named
+- Cleanup implied (now executed: dead `heading-base` mixin deleted in `589dcb3`)
+
+### Act 7 — Small cleanups + push
+
+`589dcb3` — `arc-backup.bundle` added to `.gitignore`; dead `heading-base` mixin removed from `_mixins.scss`.
+
+All 11 commits (including the morning's memory and ledger work which is outside the repo) pushed to both origin (`git.skemantix.com`) + github-backup (`github.com:davidglidden/arc-backup`).
+
+---
+
+## Past — decisions with rationale
+
+- **Pattern 3 typography adopted** over Pattern 1 (all-serif unification) or Pattern 2 (serif body + sans headings). Reason: accessibility — family-change differentiation is research-supported to be more robust under low-vision conditions than within-family variations. Secondary: architectural clarity (each register has one job); screen-primary context requires more typographic signaling than print. Steward is the primary reader with a real accessibility need.
+- **Breadcrumb itself as navigation surface** over spec's separate "Prior versions" text. Reason: cleaner design; each non-current date is semantically a link to that version's content; no separate "Prior versions" text needed.
+- **Conservative breadcrumb policy** (renders only when `revisions:` or `edition_label:` present). Reason: avoids stamping 170+ existing pieces without explicit authorization. Spec §4 allows rendering even without revisions; extending to that behavior is a future enhancement requiring steward sign-off.
+- **Chamber voices archived** rather than fixed. Reason: pre-existing dependency cycle was longstanding (TODO in site.hs); the voice-as-first-class-document pattern is better built fresh on source-aware Chamber than patched now. Steward authorized the archive with explicit reinstatement condition.
+- **Haskell item-level filter** over Hakyll pattern composition for excluding prior versions from listings. Reason: empirical — the `pattern .&&. complement` approach didn't filter in the `loadAll` pipeline; the item-level `filter (isNothing . parseVersionedFilename)` did.
+- **Colophon gets sans version-stamp with no links** rather than a `--static` modifier keeping serif. Reason: minimal code path; if it reads wrong visually, modifier class is a later refinement.
+- **Reading Compass stays serif** as Pattern 3 exception. Reason: glyphs are iconic Unicode symbols, not lexical text; family-change doesn't meaningfully differentiate symbol rendering.
+
+---
+
+## Past — decisions explicitly NOT made
+
+- **Did not build the `/slug/v/` per-piece version-index page** (spec §7 item 7). Deferred until piece accumulates 5+ revisions and breadcrumb-as-link becomes visually heavy.
+- **Did not add a `.version-stamp--static` modifier** for link-less cases (colophon). Waiting to see if the universal sans swap reads wrong on the colophon; not yet flagged.
+- **Did not translate Essays III-V** from iA Writer. Substantial per-essay editorial work; separate session.
+- **Did not build the sequence-index page** for *After the Reply*. Approved in shape (`class: sequence-index`, frontmatter convention, URL decision pending); to be built alongside III publication.
+- **Did not migrate to any new font stack.** Pattern 3 system is decided and implemented; specific family choice refinable without changing the system. Steward named they need time to consider font changes.
+- **Did not touch the Reading Compass optical balancing.** Steward's long-standing observation that it never quite worked; noted as deferred cosmetic task with three resolution paths; not fixable blind.
+- **Did not delete `scss/AldineXXI/archive-v1/`** backup files. Mentioned in Pattern 3 cleanup list but not executed today; small, can be done in any future session.
+
+---
+
+## Present — steward preferences captured this session
+
+- **Accessibility is a first-class design driver for ARC.** The steward's myopia + progressives is a real constraint that should inform design. Pattern 3 was adopted partly on this basis.
+- **Steward's design instincts often ran ahead of my spec interpretation.** The breadcrumb-as-navigation insight, the serif-vs-mono-vs-sans register question — these came from the steward noticing something and proposing cleaner design, not from my execution of spec items. Honor this: surface my interpretation but expect the steward to re-shape it.
+- **"I need time to consider"** is a legitimate pace move. Font stack decision deferred with that language; captured as a deliberate pause, not a forgotten thread.
+- **Small fixes ship quickly; substantive work is session-shaped.** The steward caught five live-site issues after go-live and we fixed each in a small commit. The style guide session and III-V publication are different scale — named as such, not rushed.
+- **"It's cosmetic" is valid deferral.** The Reading Compass optical rebalancing and the colophon's version-stamp register are genuine questions but cosmetic; deferring them is not sloppiness.
+- **Commits with pre-commit passing matter.** The steward earlier flagged `--no-verify` as a drift pattern; today's 11 commits all passed pre-commit clean. Worth preserving.
+
+---
+
+## Key paths
+
+- **ADR-005 (versioning decision)**: `~/_Dev/animal-davidglidden-eu/docs/decisions/2026-04-17-essay-versioning.md`
+- **Versioning spec**: `~/_Dev/animal-davidglidden-eu/docs/AldineXXI-Codex/essay-versioning-specification.md`
+- **Frontmatter spec**: `~/_Dev/animal-davidglidden-eu/docs/AldineXXI-Codex/frontmatter-specification.md`
+- **Vignette spec (deferred)**: `~/_Dev/animal-davidglidden-eu/docs/AldineXXI-Codex/vignette-specification.md`
+- **Style guide (stale, needs session)**: `~/_Dev/animal-davidglidden-eu/docs/style-guide.md`
+- **ARC rework landscape (with today's Pattern 3 decision + style guide thread)**: `~/.claude/projects/-Users-davidglidden/memory/project-arc-rework.md`
+- **Chamber voices archive**: `~/_Dev/animal-davidglidden-eu/docs/archive/chamber-voices/` (+ README explaining reinstatement condition)
+- **Ground-up model horizon + waterings**: MemPalace drawers in wing `capablemind-thinking`, room `seeds`
+- **iA Writer source for Essays III-V**: `/Users/davidglidden/Library/Mobile Documents/27N4MQEA55~pro~writer/Documents/Essay Sequence on Reply, etc/`
+- **Today's Symmetria ledger**: `~/.claude/projects/-Users-davidglidden/memory/session-ledger-2026-04-18.md`
+
+## Commits (chronological)
+
+Eleven commits, all with pre-commit passing cleanly, all pushed to both origin (`git.skemantix.com`) + github-backup (`github.com:davidglidden/arc-backup`):
+
+1. `bb9e7eb` — Hakyll versioning infrastructure (spec §7 items 1-5)
+2. `c0ae867` — Colophon: remove duplicate hardcoded version-stamp from markdown body
+3. `30857ee` — Archive content/chamber/voices/ to docs/archive/chamber-voices/
+4. `3af43ca` — Publish v2 of Ethics of the Reply I & II; preserve v1 via versioning
+5. `e292593` — Ethics I & II v2: remove duplicate inline dateline at piece-end
+6. `13757a5` — Fix listing duplication; nav elements to sans (Pattern 3 cleanup)
+7. `7540388` — Version breadcrumb: link prior dates; version-stamp → sans (nav register)
+8. `2332db9` — version-stamp: drop letter-spacing to match post-header breadcrumb
+9. `589dcb3` — Small cleanups: gitignore arc-backup.bundle; remove dead heading-base mixin
+
+(Two commits that look like they're only 9 — the "11" in Act 7 includes earlier dotfiles-hook-fix commit context from previous day; ARC specifically shipped 9 commits today.)
+
+Branch: main. Both remotes at `589dcb3`.
+
+## Metrics
+
+- **9 ARC commits shipped**, all pre-commit clean, all pushed to both remotes
+- **ADR-005 versioning regime** operative in production (first exercise: Ethics I & II v2)
+- **4 live URLs** for Essay versions (2 v2 current + 2 v1 preserved)
+- **Pattern 3 typography** operative in code across all nav surfaces
+- **3 waterings** filed to the `ground-up-model-horizon` seed
+- **3 L2 directions** added to `open-tasks.md` for when L2 resumes
+- **9 KG facts** added today (for the horizon + waterings)
+- **4 returns** logged to Symmetria ledger
+- **1 new drift pattern** named (`mvp-deferral-without-examining-access-gap`)
+- **Chamber voices** archived with reinstatement condition documented
+- **Reading Compass optical rebalancing** captured as deferred cosmetic task with three resolution paths
+- **Style guide** scope expanded with explicit typography-application-skill dependency
+- **0 `--no-verify` bypasses** (hook fix from 2026-04-17 held throughout)
+
+---
+
+## Related landscape (carried from 2026-04-17)
+
+The 2026-04-17 session authored the versioning regime. The 2026-04-18 session built and exercised it. Both sessions together constitute the "Essay Versioning" arc. Pattern 3 typography emerged as an adjacent decision today; it is its own architectural commitment, not a sub-commitment of versioning. The two decisions stand side by side and reinforce each other (both are architectural, both ship production code, both deferred specific implementations to future sessions with clear reconsideration triggers).

claude/memory/session-2026-04-18-evening-ingestion-milestone.md

@@ -0,0 +1,255 @@
+---
+name: Session 2026-04-18 evening → 2026-04-19 morning — first successful vault ingestion on new stack
+description: Foundation proven. Circle joined, data consolidated, vault ingestion completed (7220 items, 14355 entities, recall operational). Pulling thread is the deep audit of the first-successful-ingestion state per `l1-deep-audit-plan-2026-04-19.md` — converting "it works" into "we understand what it is and where it needs to go."
+type: project
+originSessionId: e60f4993-8250-41bb-a95f-c288da448be5
+---
+
+# Session 2026-04-18 evening → 2026-04-19 morning — first successful vault ingestion
+
+Successor to `session-2026-04-18-arc-versioning-pattern3.md` (morning session, wrapped 17:51 local).
+
+This evening session opened at 17:13 local with `/wake-up` and closed in the early morning of 2026-04-19 with the ingestion completion confirmed. The arc moved from "can we join cm-world?" through multi-hour data-directory archaeology to vault ingestion kickoff to overnight completion — and arrived at the milestone naming from the steward: *"For the two of us, this represents the proof that we possess the tools to now build all of our dreams — this was the foundation."*
+
+---
+
+## Future — what is pulling
+
+### The pulling thread (singular)
+
+**The deep audit on the first-successful-ingestion state.** The plan is committed as `docs/thinking/David/l1-reliability/l1-deep-audit-plan-2026-04-19.md` (CapableMind-AI main, commit `8287542`). Four parts: forensic (timeline + cursor disparity + error taxonomy), diagnostic (recall quality baseline across ~15 queries), forward (four radical-improvement lanes: performance / stability / robustness / operator experience), and a concrete next-session execution sequence (~4 hours, fresh context).
+
+Why this is THE thread and not any of the open ARC work, BBF pickup, or L2 horizons: everything else hinges on what the audit reveals. Whether the entity backlog (4,594 events) catches up in idle or is stranded affects claims about recall completeness. Whether the 221 vector errors are a new pattern affects trust in semantic search. Whether to propose entity-pipeline rework vs graceful degradation depends on profile data we have not yet gathered. The audit is the empirical ground that makes *"the foundation"* actually a foundation we can build on rather than a claim we hope holds.
+
+### The pause statement
+
+The ingestion completed and recall is operational — that's the first durable proof this stack works. When next-Claude wakes in a fresh context, most of what was learned tonight needs reconstruction from docs, ledger, KG, diary. The state may shift overnight: Seb might respond on #65; the entity cursor might or might not advance during BMF idle time; new betterMemories_app commits might land; the ARC repo continues to breathe. The gap itself is not a hole — it is the space in which the audit becomes possible with fresh eyes.
+
+### Literal question for next-Claude
+
+> *Between tonight and when you wake, did the entity cursor advance beyond 10,004 during BMF's idle time, or did it stay there? And whatever the answer: what does that tell us about whether deferred events retry asynchronously in steady state, or whether the backlog is effectively stranded? The audit's forensic pass (Part 1.2 of the plan) begins here — don't pre-answer. Check.*
+
+Hold this open. It is a small question that points at the deepest question of the audit: how much of the vault is actually indexed to a queryable state, and how much is nominally-processed-but-actually-missing.
+
+### Other open horizons, ranked
+
+**Load-bearing, pulling hardest (after the audit):**
+- **Ghost in cm-world roster** — `cm-instance-6a3e981e01613a8c` (second ghost created this session after data-dir consolidation forced a re-mint). Seb cleaned the first (`cm-instance-b7fab457a1d3c9d7`); this one waits for his next pass.
+- **ARC mobile review list residuals** — 8 items remain (after Bio/Resume decoupled + Pattern 3 decision). 4 mechanical (#1 typography page update, #2 Formation context sentence, #3 AldineXXI link in colophon mini-nav, #9 glimpse mobile edge-to-edge). 4 philosophical (#4 about-territory boundary, #6 apparatus dates on info pages spec, #7 genre riddle, #10 glimpses double metadata).
+- **About-territory typological boundary** — AldineXXI + Vignette peer-about vs outward portal undecided (steward). Downstream of #4 and the broader style-guide session.
+
+**Deferred with reason:**
+- **Essays III–V of *After the Reply* publication** — typography-skill dependency. Option 1 holds (let the need drive the skill); not blocking until steward wants III–V live.
+- **Sequence-index page for *After the Reply*** — new `sequence-index` class, open convention question (URL shape, frontmatter).
+- **Personal-site scaffold (`davidglidden.eu`)** — TODO detailed in `project-arc-rework.md` §decouple; waits for steward's readiness.
+- **Dotfiles commits pending** — `~/dotfiles/bin/bmf-start.sh` (new BM_DATA_DIR + BM_INSTANCE_NAME), plus 5 memory files modified via symlinks. Captured for steward's next dotfiles pass.
+- **BBF (Back Office Framework) spec reorg by Seb** — picked up during our rebase: `5ea7f5d BBF spec v0.2: peer-infra model + enhancement-stack + Back Office reshape` and `241463a BBF spec reorg: specs/bbf/core + instances`. New adjacent territory in `specs/bbf/` worth orienting on in a future session.
+
+**Parked without deadline:**
+- Typography application skill (Option 1 forcing its existence)
+- Style-guide session (queued, natural convergence point for ARC philosophical items)
+- Ground-up-model horizon (steward's horizon marker from 2026-04-18 morning)
+- L2 governance work (parked until Seb's L1-scaling deadline end of May)
+- Chamber Phase 3+ (blocked on recall maturity — this session just produced the first recall-works proof; maturity is the audit question)
+
+---
+
+## Past — what we did
+
+### Act 1 — Circle join and its unfolding consequences
+
+Opened with the steward forwarding Seb's membership token + the join script. What looked like a single-command onboarding became a multi-hour arc because the environment had layered state:
+
+1. **Stale binary running** — PID 1484 launchd-managed BMF was pre-circle-networking (pre-`da6bb5f`). First join POST succeeded on that binary but `/v1/circles/:id/members` returned 404, confirming the code didn't have peer-mesh routing.
+
+2. **Token mismatch** — the script hard-coded the dev-shared token `bm_key_testkey1234567890`, but the launchd BMF had `bm_key_7feb421ef8fd45e8`. Seb's guidance: edit the wrapper to use the dev-shared-key (all circle members share one in dev).
+
+3. **Data-dir discovery** — checked actual wrapper at `~/bin/bmf-start.sh`. No `BM_DATA_DIR`, no `BM_INSTANCE_NAME`. Data lived at `~/_Dev/BetterMemories.io/data/` (CWD-relative default, pre-ADR-021). Seb's taxonomy: Outcome 3 (not set at all, pin it explicitly). Edited wrapper.
+
+4. **Kickstart + rejoin** → new instance `cm-instance-6a3e981e01613a8c`, roster now with us (and an old ghost `cm-instance-b7fab457a1d3c9d7` from the first wrong-token join — Seb cleaned it later).
+
+### Act 2 — The data-dir dual-write discovery
+
+Steward asked "data should be in ~/ no?" — the off-hand question that exposed the real architecture. Our `BM_DATA_DIR` pin had sent most writes to the repo path, but BMF was *also* writing to `~/.capablemind/data/mindfabric-00/sqlite/` — **the real historical data from months of work had always been there** (entity.sqlite3 2.1MB, temporal 5.7MB, vector 2.1MB, vs our repo-path 233k/139k/61k).
+
+Root cause: per-module path resolvers don't all respect `BM_DATA_DIR` — some fall through to the ADR-021 legacy path if it exists. Our explicit pin didn't stop the drift.
+
+Decision: fresh start at canonical path. Archived both (`mindfabric-00.archive-20260418-incomplete` + `BetterMemories.io/data.archive-20260418-rogue-pin`). Pinned `BM_DATA_DIR=$HOME/.capablemind/data/mindfabric-00` AND `BM_INSTANCE_NAME=mindfabric-00` in both live + dotfiles wrappers. Bootstrapped BMF. Third instance: `cm-instance-7d2e19a417d694c6`. Verified single-source-of-truth: repo path stayed absent post-bootstrap. Rejoin. Roster now had two ghosts on Seb's side (he cleans them).
+
+**The dual-write was the root of the operator-experience failure mode for today.** The `BM_DATA_DIR` pin wasn't monolithic — a `[HARDENING]` candidate worth surfacing to Seb: BMF should either make `BM_DATA_DIR` authoritative for all data or be vocal about which modules use separate resolvers.
+
+### Act 3 — Vault ingestion
+
+Connected Obsidian connector (path: `~/Library/Mobile Documents/iCloud~md~obsidian/Documents/David, root-and-branch`). Import batch `import_1_mo4nvvyi` started.
+
+Mid-run observations:
+- Rate dropped **44 → 36 → 13 notes/min** (monotonic, not oscillating)
+- Entity error_count climbed **1 → 165** at ~550 notes
+- Log signatures revealed the bottleneck: `[entity:pipeline] SLOW stages: resolve=30252ms, relationships=840082ms, persist=15ms (8 entities)` — 14-18 min per batch on relationships stage, persist fast (#154's fix holding)
+- Hypothesis (marked): relationships stage scales with entity-graph density
+
+### Act 4 — Diagnostic publication
+
+Symmetria pulse invoked before GH search. Discipline shaped the action: search first (#65 already predicted "each fix reveals the next bottleneck" — our finding is its next chapter), mark hypothesis not claim, include verbatim log signatures, size artifact to one finding. Steward ratified.
+
+Posted commented on #65: https://github.com/CapableMind-ai/betterMemories_app/issues/65#issuecomment-4274470826
+Companion thinking doc: `docs/thinking/David/l1-reliability/l1-ingestion-diagnostic-2026-04-18.md` (commit `d70437c`).
+
+### Act 5 — ARC enfilade interlude (many misreads)
+
+During ingestion wait, pivoted to the ARC mobile-review list. Item #4 ("About enfilade: does it need updating? What stays? What goes?") led into a multi-turn conceptual mess on my part. Eventually clarified:
+
+- Reading Compass = site-wide glyphic nav (9 points in every footer)
+- About-enfilade = textual nav **inline on each about-constellation page** (not a template partial — the `templates/partials/footer-about.html` I'd been reading is likely orphaned with Reading Compass contents; see repo cleanup)
+- About pages = "mini-site explaining the why and how of ARC" (steward's verbatim)
+
+Steward frustration explicit: *"This is frustrating, what can I not make myself clear?"* Legitimate. Multiple framing errors on my part accumulated despite corrections. After reading `content/pages/navigation-philosophy.md` directly — which *documents* the Reading Compass concept — the picture cleared.
+
+Real discrepancy: the about-page lists 11 "branches," the inline enfilade (per `navigation-philosophy.md`) has 10 entries, and 4 items don't match: AldineXXI + Vignette + Resume on about but not in enfilade; Bio in enfilade but only in about's Contact section. Steward decided: **Bio + Resume out** (personal-site territory — decoupling horizon). AldineXXI + Vignette: deferred to steward.
+
+Also captured: updated `project-arc-rework.md` 2026-04-16 decoupling section with today's steward additions (including the cross-linking pattern: *"my personal site will link to ARC by mentioning that I am the creator and author of ARC"*) — after first creating a duplicate file and removing it (the search-before-create failure I'd logged once already).
+
+### Act 6 — Overnight completion
+
+Ingestion ran through the entity bottleneck to `completed` state:
+- Processed 7,220 (notes: 2,459 + relationships: 4,761)
+- Entities: 14,355
+- Failed: 0, Skipped: 13
+- Final source timestamp: 2026-04-18T23:50
+
+Recall test query *"What does the Reading Compass organize in Animal Rationis Capax?"* → 6 results, top confidence 1.0, rich vector hits on actual vault content. **Recall is operational.**
+
+Residuals surfaced post-completion:
+- Entity cursor 10,004 (others ~14,598) — 4,594 behind; error_count 4,595 (was 165 at mid-run)
+- Vector cursor 14,482, error_count **221** (was 1 at mid-run) — new pattern
+- New: `[keystone:observe] Non-fatal error: ENOENT ... manifest.json.tmp -> manifest.json` — filesystem race, un-diagnosed
+- LanceDB maintenance running cleanly per #160
+
+### Act 7 — Milestone + plan
+
+Steward named the milestone: *"years of 'what if we could' to working... this represents the proof that we possess the tools to now build all of our dreams — this was the foundation."* And asked for a plan, not execution: *"I want to clear context before doing anything serious considering the problems we had earlier."*
+
+Wrote `l1-deep-audit-plan-2026-04-19.md` (commit `8287542`) — the next-session seed. Posted closing comment on #65: https://github.com/CapableMind-ai/betterMemories_app/issues/65#issuecomment-4275246954.
+
+---
+
+## Past — decisions with rationale
+
+- **Archive both data trees, fresh rejoin** — cleanest canonical state for first ingestion on new stack; the third ghost for Seb is one-time cost.
+- **Pin `BM_DATA_DIR` + `BM_INSTANCE_NAME` explicitly** — don't rely on ADR-021 default alone; the dual-write bug demonstrated the fallback chain isn't monolithic.
+- **Comment on #65, not new issue** — #65's body predicts this compound pattern; our finding is its next chapter. Fragmenting tracking would hurt Seb's context.
+- **Mark hypothesis as hypothesis** — "relationships stage scales with graph density" is plausible but unverified; included alternatives in the comment + doc.
+- **Hold the thinking-doc + comment pairing** — following the precedent set by the 2026-03-25 diagnostic referenced from #65's body.
+- **Bio + Resume out of about-enfilade** — personal-site territory per decoupling horizon.
+- **Write audit plan not execute audit tonight** — steward flagged concerns about this session's error patterns; fresh context serves deep forensic work better.
+
+## Past — decisions explicitly NOT made
+
+- **Entity backlog fate** — will it catch up in idle or remain stranded? Not answered; audit's forensic Part 1.2 is the inquiry.
+- **Vector 221 errors — root cause** — deferred. Un-diagnosed.
+- **manifest.json ENOENT race** — non-fatal per log but un-diagnosed. Deferred.
+- **AldineXXI + Vignette enfilade membership** — steward's call; held open.
+- **Other ARC items (#6 apparatus dates spec, #7 genre riddle, #10 glimpses double metadata)** — style-guide session territory; deferred.
+- **Clean up orphan `templates/partials/footer-about.html`** — noted during enfilade investigation; not touched.
+- **Update stale `CapableMind-AI/CLAUDE.md`** (still says branch `fix/replay-durability-contracts`, stale) — noted in audit plan §3.5 (documentation debt lane); not touched.
+
+---
+
+## Present — the mood of the work
+
+### Returns (the practice's record)
+
+Six returns from this session (not all logged in real-time to the ledger — discipline was uneven):
+
+1. **~early-evening** — Nearly ran `rm -rf` on the active logchain directory (thought it was orphan). Caught only by an mtime check showing fresh files from after BMF restart. Name: *before any rm-rf on a path flagged as stale, check modification times against recent runtime events, not just against the pre-migration date.*
+
+2. **~mid-evening** — Cited `#10 sequential dispatch` as a live constraint on ingestion duration without verifying. `gh issue view 10` showed CLOSED 2026-03-24. Name: *MEMORY.md is a frozen snapshot; before citing an issue number as a constraint, verify with `gh issue view`.*
+
+3. **~mid-evening** — Quoted `eta_minutes: 222` from connector_status as a time estimate without grounding. Steward corrected: *"the ETA is not a good indicator because the rate will change with the burst ingestion pattern that seems to take hold."* Name: *report raw counts (`processed / total_estimated` + entities extracted), skip rate/ETA extrapolation in reporting to steward.*
+
+4. **~evening** — Created `feedback-bmf-ingestion-rate.md` without searching memory or gh first. Steward: *"maybe better to search in memory or gh issues?"* Name: *before creating a new feedback file, search existing memory + gh for the observation; promote from incidental-mention to canonical, don't proliferate.*
+
+5. **~evening** — Multiple framing errors on ARC enfilade. Applied abstract architectural intuitions instead of reading `content/pages/navigation-philosophy.md` which documents the Reading Compass concept. Steward: *"the navigation page will explain the reading compass concept. This is frustrating, what can I not make myself clear?"* Name: *when a codebase has self-documenting pages, read those first before applying abstract intuitions. Named objects carry codebase-specific meanings.*
+
+6. **~late-evening** — Created duplicate `project-arc-personal-decoupling.md` when the existing `project-arc-rework.md` already had a 2026-04-16 decoupling section. Same search-first failure as #4. Removed duplicate, appended to existing section. Pattern repeated despite correction at #4 ~an hour earlier.
+
+Meta-pattern across these: **running framings/claims without grounding verification.** Either citing stale state as live (returns 2, 3), creating without searching (returns 4, 6), or applying abstract models without reading the implementation (return 5). Return 1 was caught because Symmetria's procedural habit (check mtime) happened to be in motion; the others required steward correction.
+
+### Confidence to recalibrate
+
+- **"Long session" as error hypothesis** — steward disproved. This was a ~4 hour session, not unusually long. My own self-explanation was itself ungrounded. Real cause of the error pattern: unclear. Symmetria helped when *explicitly invoked* but didn't prevent errors when merely initialized. Counter-commitment: before offering a cause-hypothesis, verify something concrete; don't reach for "plausible."
+- **"Ephemeral, don't save" reasoning** — treated some things as ephemeral that turned out worth persisting (enfilade architecture clarification, wrapper edits, instance_id chain). Symmetry-violation on the other side of the proliferation problem: *not* saving what's non-obvious because the default is "don't proliferate." Adjustment: for architectural clarifications and operator-experience findings, the bar for save is lower than for rate/ETA observations.
+- **Skills-I-co-designed contamination** — present today as Symmetria under-engaged. When the practice was cheap (init + ledger as afterthought), errors proliferated. When explicitly invoked (pulse before GH work), it shaped action. Discipline has to be costly enough to bite.
+
+### Tensions visible but not resolved
+
+- **The audit is load-bearing but my capacity to execute it well is the open variable.** The session's error pattern is the concerning backdrop. Fresh context will help; discipline won't replace itself.
+- **Operator-experience failure modes** — today surfaced several (wrapper-vs-plist layering, data-dir dual-write, instance-id chain after data-dir moves, stale docs). The steward is the most sophisticated user imaginable for BMF and still spent hours on these. That's a structural finding worth elevating to Seb, not just internal note.
+- **The milestone's weight vs the residuals' weight** — the foundation is real AND the residuals (entity backlog, vector errors, manifest race) are not understood. Both are true. The audit converts the residuals from unknown to characterized; it does not diminish the milestone.
+
+---
+
+## Steward preferences captured this session
+
+- **Verbatim quotes preserved** when steward articulates decision-level intent (e.g., the decoupling statement, the milestone statement, the Pattern 3 articulation from the morning session). Not paraphrase.
+- **Search before claim, search before cite** — repeated this session. If an issue number or a memory fact is being cited, verify live state before citing.
+- **Report raw counts, skip ETA extrapolation** — codified as `feedback-bmf-ingestion-rate.md`.
+- **Trust the codebase's self-documenting pages** — ARC has these (`navigation-philosophy.md`, `colophon.md`, `typography.md`). Read them before importing abstract frames.
+- **Steward drives pacing** — when steward says "let's wait," that's not a holding pattern; it's the work being paced to fittingness. Don't propose activity during explicit wait windows.
+- **The milestone register matters** — the gratitude moment was neither performative nor dismissive; received with dignity, returned to work. Future similar moments: same register.
+
+---
+
+## Artifacts produced this session
+
+Committed + pushed to CapableMind-AI main:
+- `docs/thinking/David/l1-reliability/l1-ingestion-diagnostic-2026-04-18.md` (commit `d70437c`)
+- `docs/thinking/David/l1-reliability/l1-deep-audit-plan-2026-04-19.md` (commit `8287542`)
+
+GH:
+- Mid-run comment on #65: https://github.com/CapableMind-ai/betterMemories_app/issues/65#issuecomment-4274470826
+- Closing comment on #65: https://github.com/CapableMind-ai/betterMemories_app/issues/65#issuecomment-4275246954
+
+Live system state:
+- BMF on PID 55326 at `cm-instance-7d2e19a417d694c6`, data at `~/.capablemind/data/mindfabric-00/`, 4% CPU steady state
+- Wrapper: `~/bin/bmf-start.sh` with new token + BM_DATA_DIR + BM_INSTANCE_NAME
+- cm-world circle member; second ghost (`cm-instance-6a3e981e01613a8c`) pending Seb's cleanup
+- Two archives preserved: `~/.capablemind/data/mindfabric-00.archive-20260418-incomplete` + `~/_Dev/BetterMemories.io/data.archive-20260418-rogue-pin`
+
+Memory system:
+- This session file
+- Today's Symmetria ledger (`session-ledger-2026-04-18.md`) — rich with authorization moves + the GH diagnostic pulse
+- `feedback-bmf-ingestion-rate.md` (new)
+- `project-arc-rework.md` — updated with enfilade architecture clarification + 2026-04-18 decoupling additions
+
+Uncommitted (for steward's next dotfiles pass, not urgent):
+- `~/dotfiles/bin/bmf-start.sh` — new structure with REDACTED token placeholder
+- `~/dotfiles/claude/memory/*` — today's flows via symlinks
+
+---
+
+## Metrics
+
+- 1 vault ingestion completed (7,220 items, 14,355 entities, 0 failed)
+- 1 circle joined (cm-world, after 3 instance_id mints + 2 ghost consequences)
+- 2 diagnostic artifacts committed + pushed
+- 2 GH comments posted (#65 mid-run + closing)
+- 1 deep audit plan written (234 lines, 4 parts)
+- 6 Symmetria returns logged (in this file; discipline uneven in real-time ledger)
+- 1 milestone named by steward: *"the foundation"*
+- 3 instance_ids minted (unavoidable cost of data-dir consolidation)
+- 0 commits to ARC this session (tangent only, no source changes)
+
+---
+
+## Key paths
+
+- **Audit plan**: `~/_Dev/CapableMind-AI/docs/thinking/David/l1-reliability/l1-deep-audit-plan-2026-04-19.md`
+- **Mid-run diagnostic**: `~/_Dev/CapableMind-AI/docs/thinking/David/l1-reliability/l1-ingestion-diagnostic-2026-04-18.md`
+- **Session ledger**: `~/.claude/projects/-Users-davidglidden/memory/session-ledger-2026-04-18.md`
+- **BMF launchd wrapper**: `~/bin/bmf-start.sh`
+- **BMF dotfiles wrapper**: `~/dotfiles/bin/bmf-start.sh`
+- **BMF data dir**: `~/.capablemind/data/mindfabric-00/`
+- **BMF logs**: `~/.capablemind/logs/bmf.stdout.log` and `bmf.stderr.log`
+- **GH issue #65**: https://github.com/CapableMind-ai/betterMemories_app/issues/65
+- **ARC mobile review list**: `~/.claude/projects/-Users-davidglidden/memory/project-arc-rework.md` §"Mobile review list — 2026-04-18 evening"

claude/memory/session-2026-04-19-arc-typology-spec-and-dns.md

@@ -0,0 +1,180 @@
+---
+name: Session 2026-04-19 evening — ARC typology spec drafted; about-reflow mockup + DNS unblocked
+description: After L1 audit shipped, pivoted to ARC. About-page reflow decision evolved further (separation → peer-split → single-page reflow with hic first, Adsum later). Content-typology spec drafted to `docs/AldineXXI-Codex/content-typology-specification.md` as the foundation for codification work. DNS to animalrationiscapax.org resolved (zone was correct; apparent failure was Firewalla VPN DNS interception). Pulling thread: finish the typology spec — start with Meditation's glyph.
+type: project
+originSessionId: 03b70700-bebb-40a0-a5d9-bcfa1ab61df4
+---
+# Session 2026-04-19 (evening) — ARC pivot after L1 ship
+
+## Setup
+
+Session opened after a terminal crash mid-ARC DNS work. The L1 audit bundle had been shipped earlier in the day (PR #163 + 3 docs + diagnostic branch) — that work is captured separately. This session is the ARC pivot the steward had been moving toward since ~16:12.
+
+## Past — what we did
+
+### About-page reflow: the decision evolved further
+
+On waking, the captured `project-arc-rework.md` already held the 2026-04-19 decision: *ARC stays unified; About splits into Colophon + Adsum as **peer compass points***. Steward corrected: further evolution had happened pre-crash — **don't split at all; reflow the existing About page, hic first, Adsum later. Embracing the multidisciplinary aspects of the work rather than trying to separate them tidily.**
+
+Updated `project-arc-rework.md` to reflect the three-move evolution within a single day:
+1. Separation (ARC ↔ davidglidden.eu) considered, rejected
+2. Peer compass split (Colophon + *Adsum*) considered, rejected
+3. Single about page reflow adopted
+
+*Adsum* demoted from compass point to section-register within the about page. Section names *Colophon* + *Adsum* do the register-marking themselves; no added italic subtitle needed (names serve; added subtitles re-perform the split).
+
+**Steward's verbatim framing:** *"embracing the multidisciplinary aspects of my work rather than trying to separate them tidily."*
+
+### About-page mockup (Option A)
+
+Read about.md, colophon.md, bio.md, resume.md. Insight: **colophon.md already is the hic-register About** (Philosophy and Compass, Guides, Formation, Desk, Making, Presence). The reflow doesn't need much new prose — it needs consolidation. Drafted Option A: about.md body becomes colophon.md's content + new Adsum section appended. Sunset /colophon/ URL (redirect to /about/). About-index collapses into enfilade nav.
+
+Steward decisions on the mockup:
+- **KEEP** the Adsum opening drop-cap paragraph (*"I answer to my name here—not as self-presentation but as response..."*). Embodies the register-declaration inside the page rather than announcing it elsewhere.
+- **MOVE** Seasonal Geometries section from colophon → navigation-philosophy.md (Reading Compass is its own entity).
+- **Drop caps: option (b)** — keep only the Adsum drop-cap; drop the site-intro drop-cap. **Rule codified: *drop caps mark register-declarations, not page-tops.*** Decision informed by Beatrice Warde's *Crystal Goblet* (typography should be transparent, not performative) + the threshold-proliferation concern (vignette + drop-cap = too many opening signals on essays, though About won't have a vignette).
+- **Henry James quote** stays at close of page.
+
+Reflow implementation deferred. Mockup is in chat; committing awaits steward's move.
+
+### About-pages classification problem, reframed upward
+
+Steward raised: `content/pages/*.md` all carry `class: essay`, which triggers essay-apparatus (breadcrumb, vignette slot once live, essay-style dateline) on pages that aren't essays. Solution direction: introduce `class: about`.
+
+**Steward then reframed upward:** "is this not another area that needs defining? We've built some spec already, this could be important enough to codify — and what other aspects would benefit from codification?" The plumbing fix is a symptom of a deeper gap: ARC's content typology itself is underspecified. The genre riddle (meditation / observation / fragment overlap) from the mobile review list is another symptom of the same gap.
+
+Surfaced a **codification test** (worth codifying when 2+ hold):
+- **Recurs** — the same judgment is made many times
+- **Has downstream consumers** — templates, skills, agents
+- **Embodies a commitment that should resist drift**
+- **Discovered, not invented** — emerged from practice and is stable
+
+Strong candidates named: (1) content typology/genre system [THE recommendation]; (2) apparatus grammar (hic/hic jacet, dateline, location, edition labels); (3) Pattern 3 typography decision; (4) Reading Compass rules. Medium: style-guide prose conventions, navigation hierarchy rules. Later: semantic-analysis skill spec.
+
+### Content Typology Specification — draft authored
+
+Drafted at **`~/_Dev/animal-davidglidden-eu/docs/AldineXXI-Codex/content-typology-specification.md`** (untracked, not yet committed). Peer of AldineXXI and Vignette specs.
+
+**Session-locked decisions captured in the draft:**
+
+- **§0 Multi-axis organizing principle** — don't force all types onto one axis. Name the multiple axes (medium, duration, posture, relation, voice, register) and let each type sit on its native one. Supersedes the flat "substance-primacy" framing I proposed earlier.
+- **Medium × Duration grid** resolves four types cleanly:
+  |  | Aphoristic / terminal | Sustained / argumentative |
+  |---|---|---|
+  | Prose | Fragment (◈) | Essay (●) |
+  | Image | Glimpse (◉) | Photo Essay (⊙) |
+- **Photo Essay definition LOCKED** (steward: *"the image sequence is the essay. Think of the examples in Ways of Seeing"*). Definition: an essay whose medium is the image sequence; the sequence constructs argument, rhythm, turn, return. No interleaved prose. Text limited to title, introduction, postface, per-image captions. Canonical external exemplar: **John Berger, *Ways of Seeing*** — the wordless image sequences that construct visual-critical arguments.
+- **Glimpse : Photo Essay :: Fragment : Essay** (steward: *"a glimpse is akin to an aphorism"*). Glimpse is single-image-aphoristic; Photo Essay is image-sequence-sustained. Same structural roles as Fragment and Essay in a different medium.
+- **Observation and Meditation** sit on the *posture* axis (prose-register, non-argumentative): Observation = attended-single-moment; Meditation = sustained-inhabiting.
+- **Meditation promoted to 10th type** (steward: *"We will need a glyph for meditation..."*). Resolves §7 open question #1. Glyph TBD — constraints: distinguish from ● and ○ (adjacent on posture axis); belong to the quiet-geometric compass family.
+- **Drop-cap rule codified in §2:** register-shifts only, never page-tops.
+- **No-essay-fallback rule in §5:** `site.hs` may not fall back to `class: essay` for unclassified pages. All pages must be explicitly typed.
+
+Remaining work (7-step authoring sequence in the spec):
+1. Resolve Meditation glyph
+2. Lock §1 entries for remaining extant types (essay, observation, chamber, gloss, about, archive)
+3. Resolve remaining genre-riddle questions (poem, council/deliberation, archive-class, gloss-boundary)
+4. Author §2 apparatus binding matrix
+5. Author §3/§4/§6 from §1–§2 decisions
+6. Jurist review
+7. Execute migration (introduce `class: about`, reclassify content/pages/, update site.hs per §5 contract)
+
+### DNS / Cloudflare work
+
+Diagnosed and resolved the animalrationiscapax.org "still resolves to porkbun" appearance:
+
+- **Registrar / NS**: correctly set to Cloudflare (priscilla + tom) — via whois.
+- **Zone at Cloudflare**: correct. Six records (CNAME @ → `animal-rationis-mirror.pages.dev` proxied; CNAME sig1._domainkey for DKIM; MX × 2 for iCloud; TXT × 2 for SPF + Apple verification). Confirmed via zone export (`~/Downloads/animalrationiscapax.org.txt`).
+- **Pages binding**: correct. Target `animal-rationis-mirror.pages.dev` resolves to Cloudflare anycast (172.66.x.x).
+- **What I kept seeing was stale/fabricated data**: `dig @priscilla` returned AWS Oregon IPs (44.227.76.166 / 44.227.65.245) even when queried by IP. Only discovery that broke the deadlock: **DNS-over-HTTPS (`cloudflare-dns.com`, port 443) returned the correct `172.64.80.1`** + curl via that IP returned `HTTP/2 200 · server: cloudflare · cf-ray`.
+- **Root cause of the apparent problem**: the steward was VPN-connected to **Seb's Firewalla**, which was intercepting port-53 DNS and returning stale cached data. Disconnecting from the VPN resolves it. Zone + site were working correctly the whole time.
+
+Then set up **davidglidden.eu → animalrationiscapax.org redirect** using Cloudflare's Redirect Rules template "Redirect to a different domain" (keeping original path and query string). Flagged for verification: ensure 301 not 302; matching covers both apex and www.
+
+## Decisions explicitly NOT made / deferred
+
+- **About page reflow implementation** — mockup reviewed and agreed in shape; actual authoring/commit deferred. Pending: steward's move to apply it.
+- **`class: about` migration in `site.hs`** — scoped as its own PR; downstream of typology spec completion (class: about is one field in the typology).
+- **Meditation glyph** — flagged as steward-decision-deferred. Not arbitrary; criteria: quiet-geometric family, distinguish from ● and ○.
+- **Remaining §1 type entries** (essay, observation, chamber, gloss, about, archive) — structure exists; content needs a focused authoring pass.
+- **§2 apparatus matrix** — structure exists; matrix cells need authoring.
+- **Genre-riddle spec content** — poem as type? council/deliberation relation to chamber? archive need `class:` at all? gloss boundary with essay? All listed in §7 Open Questions.
+- **Essays III, IV, V of *After the Reply* publication** — pre-crash pulling thread, still parked. Typology work is the current foreground.
+- **Style-guide redevelopment** — downstream of typology; on queue.
+
+## Present — the mood
+
+- **Registers shifted many times**: post-crash DNS panic → structural reflow thinking → spec architecture → operational CF dashboard → spec authoring → DNS resolution → redirect setup. Good rhythm; each handoff landed cleanly.
+- **The Firewalla moment** was the session's most satisfying return. I was spending tool calls chasing phantom A records; steward's *"I can assure you I only have 6 entries"* grounded me. Return: **trust the steward's direct observation over stale tool output**. Added drift pattern: *stale-tool-output-reported-as-current*.
+- **Steward's architectural instincts drove the best insights**: the three-move decision evolution (don't-split-tidily principle applied recursively); Warde's *Crystal Goblet* for drop-caps; *"the image sequence IS the essay"* anchored in *Ways of Seeing*; glimpse ≈ aphorism. Each was the steward's move that I then codified. My value: spec-shaping, structural observation, documentation. Steward's value: principled anchors.
+- **Codification question as upward reframe** — steward's instinct to move from "fix the plumbing" to "what else should be codified" was load-bearing. Without it, class:about would have been a one-off fix and the genre riddle would still be unresolved.
+- **Spec-authoring midway-pause pattern**: drafted enough of the typology spec to lock decisions, then paused at a natural break (Meditation glyph). The draft file exists; resumption is well-scaffolded.
+
+## Drift patterns observed / recalibrations
+
+- **Stale-tool-output-reported-as-current** (new pattern). Today: reported "parking records still in zone" based on dig output that was being intercepted by Firewalla. Steward had to correct me. Lesson: when tool output contradicts direct human observation of the authoritative system, *the tool is wrong*, not the human. Trust the human's view of the dashboard/file/system; cross-check tools against it.
+- **Author-vs-reviewer-validation-confusion** (carried from earlier today) — didn't bite in the ARC session but worth keeping awake.
+- **Running-claims-without-grounding-verification** (today's meta-pattern) — held better in this session; Firewalla return is an example of catching it before it compounded.
+
+## Future — what is pulling
+
+### Pulling thread (singular)
+
+**The Content Typology Specification.** A live draft exists at `~/_Dev/animal-davidglidden-eu/docs/AldineXXI-Codex/content-typology-specification.md` (untracked, uncommitted). Its foundations are locked (§0 multi-axis principle, Photo Essay + Glimpse definitions, Fragment:Essay::Glimpse:Photo-Essay pairing, Meditation as 10th type, drop-cap rule, no-essay-fallback rule). When the next session returns, the spec is what's waiting. The first unlocked item is the Meditation glyph — that's the natural pick-up.
+
+Downstream of the typology spec, in order:
+- `class: about` migration to `site.hs` + templates (gated on spec completion)
+- Style-guide redevelopment session
+- Semantic-analysis skill design (gated on spec)
+
+### Literal question for next-Claude
+
+**What glyph for Meditation?** Constraints: distinguish visually from ● (Essay) and ○ (Observation) since all three are prose-substance types adjacent on the posture axis; belong to the quiet-geometric character of the existing compass (●○⟐◈◉⊙✎☷✍︎); carry a "sustained inhabiting" quality (not argumentative, not aphoristic, not meta). Hold this open; don't pre-answer. The steward's instinct on glyph aesthetics should drive it, not my typographic intuition.
+
+### Other open horizons, ranked
+
+**Load-bearing (after the pulling thread):**
+- About-page reflow authoring + commit (mockup agreed; needs the actual edit pass)
+- Move Seasonal Geometries to `navigation-philosophy.md` (decided; small task)
+- `class: about` introduction + site.hs migration (downstream of typology)
+
+**Deferred with reason:**
+- Style-guide redevelopment session (downstream of typology)
+- Semantic-analysis skill design (downstream of typology)
+- Poem / Council-Deliberation / Archive-class / Gloss-boundary — spec content decisions to resolve during §1 full authoring
+
+**Parked without deadline:**
+- Essays III, IV, V of *After the Reply* publication (pre-crash thread; typology work displaced it)
+- Reading Compass optical rebalancing (cosmetic)
+- Mobile review list items (various)
+- Chamber Phase 3 (L1-gated)
+
+### Pause statement
+
+I am about to be away from this. The typology spec is mid-authoring at a clean pause. DNS is solved (Firewalla was the issue; zone was always correct). The About reflow has an agreed shape but hasn't been written yet. I don't know what will have changed when I return. Here is what I want to find still pulling: **the typology spec, with Meditation's glyph as the first concrete decision waiting.**
+
+## Session artifacts
+
+**Written this session:**
+- `~/_Dev/animal-davidglidden-eu/docs/AldineXXI-Codex/content-typology-specification.md` — draft, untracked, uncommitted.
+
+**Modified this session:**
+- `~/.claude/projects/-Users-davidglidden/memory/project-arc-rework.md` — updated to capture: decision evolution (3 moves), mockup decisions, codification surface + test + candidates, typology spec status + session-locked decisions, photo-essay + glimpse sharpenings, multi-axis principle.
+- `~/.claude/projects/-Users-davidglidden/memory/session-ledger-2026-04-19.md` — added return entry for the terminal-crash wake.
+
+**No commits made this session** (no code touched in the ARC repo; draft spec file is untracked).
+
+**Uncommitted in ARC:** `docs/AldineXXI-Codex/.DS_Store` (noise) + untracked `content-typology-specification.md` (the draft).
+
+## Key paths
+
+- ARC repo: `~/_Dev/animal-davidglidden-eu/`
+- Typology spec draft: `docs/AldineXXI-Codex/content-typology-specification.md`
+- ARC memory landscape: `~/.claude/projects/-Users-davidglidden/memory/project-arc-rework.md`
+- Today's Symmetria ledger: `~/.claude/projects/-Users-davidglidden/memory/session-ledger-2026-04-19.md`
+- Zone export for animalrationiscapax.org: `~/Downloads/animalrationiscapax.org.txt` (2026-04-19 20:08:35)
+- Cloudflare Pages project: `animal-rationis-mirror` (per `scripts/deploy-cloudflare.sh`)
+
+## Tags
+
+arc, about-reflow, adsum, colophon, content-typology-specification, codification, multi-axis-typology, photo-essay-ways-of-seeing, glimpse-aphorism, meditation-tenth-type, meditation-glyph-tbd, drop-cap-register-shifts-only, warde-crystal-goblet, class-about, cloudflare, dns, firewalla-interception, davidglidden-eu-redirect, animalrationiscapax-org-live

claude/memory/session-2026-04-19-l1-audit-shipped.md

@@ -0,0 +1,215 @@
+---
+name: Session 2026-04-19 — L1 deep audit shipped (recall broken, 3 cross-cutting patterns surfaced, PR #163 + bundle handed to Seb)
+description: Deep audit of BMF recall completed end-to-end after morning wake-up revealed recall substantially broken; six findings localized, mechanical fix shipped as PR #163, bundle handed to Seb. Pulling thread is Seb's reception of the bundle + whether the "read-path observability contract absent" framing lands when he picks up the architectural items.
+type: project
+originSessionId: a3ddbf34-da48-4129-acba-658f2f869783
+---
+
+# Session 2026-04-19 — L1 deep audit shipped
+
+Successor to `session-2026-04-18-evening-ingestion-milestone.md`. Wake-up opened at ~07:38 local to execute the deep-audit plan (`l1-deep-audit-plan-2026-04-19.md`, commit `8287542`). Session closed with audit bundle shipped to Seb + steward moving to ARC work in a new session.
+
+---
+
+## Future — what is pulling
+
+### The pulling thread (singular)
+
+**Seb's reception of the bundle.** The audit produced a three-document bundle + mechanical fix PR + diagnostic branch + three cross-cutting architectural patterns. All the care that went into the ship — the refinements after architect-review, the reading-order banners, the "warrants a call" cues on H2/H4 — only matters if it actually reduces Seb's cognitive load when he picks up. Until he engages, the audit's quality is unproven.
+
+Specifically pulling: does the **"read-path observability contract absent"** framing land for him as an architectural pattern worth separate L2-shaped work, or does he read it as "just four bugs to fix"? If the pattern framing lands, the broader architectural study the steward mentioned has a gravity point to organize around. If it doesn't, today's synthesis is mostly-ignored context around three mechanical fix suggestions.
+
+### The pause statement
+
+Steward is moving to ARC work in a new session. L1 remains PRIMARY through end of May (steward + Seb's territory), but this particular L1 thread pauses here. PR #163 sits open awaiting Seb's review. The diagnostic branch sits pushed awaiting his curiosity or deletion. The bundle sits committed + ready for pull. Between now and next L1 session — which may be days, not hours — Seb could merge, open issues, have ideas, push back, or do nothing. All possibilities live.
+
+### Literal question for next-Claude
+
+> *When the next L1 session opens: has Seb read the addendum? Did he merge PR #163? Which design call did he pick first — H2 battery policy, H3 temporal fallthrough, or H4 hook integration? And — most important — does the "read-path observability contract absent" framing land for him as a pattern worth addressing as a pattern, or does he treat H1–H4 as four independent bugs to fix one at a time?*
+
+Hold this open. The answer, whatever it is, is a signal about whether today's synthesis work earned its keep.
+
+### Other open horizons, ranked
+
+**Load-bearing, pulling hardest (after the main thread):**
+- **Broader architectural study** — three cross-cutting patterns surfaced today (module-health ≠ recall-correctness; threshold-governance regime collapse; read-path observability contract absent). Fertile L2-shaped material for steward + Seb + jurist when L1 stabilizes. Steward explicitly framed as "not too soon, but not mine to synthesize alone."
+- **H2 battery suppression as end-user blocker** — steward verbatim: *"For those future end-users who will use this on a laptop the need to be plugged into ac for recall is a no go..."*. Architectural call Seb needs to make. This is the most user-facing of the findings.
+- **The `events-013.jsonl` logchain gap** — 10 events missing with no code-path found that explains deletion. Could be nothing; could be data-loss-shaped. Provisionally open, surfaced in forensic §1.2.
+
+**Deferred with reason:**
+- **Option B — test fixes + bigger PR** was discussed and declined for today. Steward preferred Option A (diagnostic-only branch + tight mechanical PR). If Seb wants us to author more of the fix space, that's the natural expansion.
+- **H3 temporal fix** — 3-line mechanical fix exists, but the shape decision (planner-exclusion vs module-guard vs new handler) is Seb's. Small-code, design-tinged.
+- **BM25 score-range comment fix** — mechanical, tiny, waiting for any PR touching `query-router.ts:542-543` to ride along.
+- **Ultrareview on PR #163** — recommended in the addendum; steward's call whether to invoke it for the mechanical fix.
+
+**Parked without deadline:**
+- ARC work (steward going there now in a new session)
+- The broader study (waits for L1 stability)
+- L2 governance (parked through end of May per `project-focus-april-may.md`)
+
+---
+
+## Past — what we did
+
+### Work completed
+
+**Wake-up orientation** (~07:38–07:50):
+- Read previous session file + Symmetria ledger
+- Snapshot BMF stderr log (43 MB) pre-investigation as defense against rotation
+- Cursor probe confirmed entity stopped at 2026-04-19T05:07:52 UTC with last_processed_at 05:51
+- Initial forensic observations on entity pipeline O(N²) bottleneck
+
+**Part 1 — forensic (~08:00–09:30):**
+- Timeline reconstruction via Python-parsed DIAG logs
+- Cursor disparity investigation (`events-013.jsonl` gap identified)
+- Error taxonomy split into ingestion-window vs historical-noise
+- `code-reviewer` sub-agent verified mechanism at 0.92 confidence — caught three corrections I'd missed
+- `architect-review` sub-agent rated v1 at 0.55 ship-readiness, 11 revisions needed
+- Steward catch: "ship-ready" claim was invalid without re-verifying after revisions
+- Forensic doc revised with all 11 corrections + Option E (slot graduation) + Option F (cosine similarity) added
+
+**Part 2 — recall baseline (~09:30–11:00):**
+- 15 designed queries + 11 follow-up probes
+- Initial reading: recall substantially broken (8 empty, 6 junk, 1 honest)
+- Steward recalibrated milestone: *"my joy at reaching the milestone was premature I now understand... I can accept that. Now to make this work."*
+- Two storage probes refuted original H1 (entity conf stored at 0) and H2 (vector unwritten) — both became read-path findings, not ingestion
+- `general-purpose` interpretation agent provided independent reading; surfaced working-memory injection mechanism + temporal fallthrough hypothesis
+
+**Diagnostic branch — Option A (~11:45–14:30):**
+- Created `diagnostic/recall-read-path-2026-04-19` off `decbdee` + merged Seb's 9 commits from main
+- Added 5 `[DIAG:H*]` stderr instrumentations at critical decision points
+- Rebuilt + restarted BMF via launchctl
+- Re-ran query set on AC power — recall working end-to-end on vault content
+- DIAG output bisected H1 clobber → downstream of buildEnrichedResults
+- Added H1-compose log → confirmed: `normalizePerModule` min-max when range=0 clobbers confidence to 0
+- Traced to **GH #126 exactly** — known issue, still open
+- Traced other findings: H2 = battery suppression (`ollama-embeddings.ts:200-203`), H3 = `temporal/queries.ts:311` fallthrough, H4 = `query-router.ts:268-290` WM injection
+
+**Shipping (~14:30–15:00):**
+- PR #163 opened on `fix/126-min-max-normalize-degenerate-case` from clean `main`
+  - 11-insert/1-delete degenerate-case guard
+  - 31 query-router tests pass, pre-commit hook passed
+  - Closes #126 on merge
+- Diagnostic branch pushed to origin for Seb's reference
+- Addendum doc written consolidating all 6 findings with file:line localizations
+- Second `architect-review` pass: 0.78 ship-readiness, with **key missing pattern: "read-path observability contract absent"**
+- All refinements applied: reading-order banners on 3 docs, third architectural pattern added to addendum TL;DR, valence fixes, honest-gap additions
+- Audit bundle committed to `CapableMind-AI` main (`40cb401`) — four docs + gitignore
+
+### Decisions made and why
+
+- **Option A (diagnostic-only) over Option B (implement fixes)** — chose A because crossed into Seb-territory authorship less aggressively + gave a clean checkpoint before optionally going to B. Steward authorized A explicitly with Symmetria.
+- **#126 fix as its own tight PR** — steward principle: *"I would not touch an architectural element, but mechanical, etc yes."* #126 is unambiguously mechanical.
+- **No regression test in PR #163** — adding one required function extraction (refactor) or heavy mocking (integration-test overhead). Kept scope purely mechanical. PR body documents repro + evidence; Seb can add a test in same PR if preferred.
+- **Keep diagnostic branch around** — steward: *"maybe better to keep and Seb can remove if he thinks it's unnecessary."*
+- **Addendum doc supersedes recall baseline's H1/H2 section** — didn't rewrite the baseline; added supersession banner + explicit handoff in addendum preamble. Preserves the original reading + adds correction, rather than rewriting history.
+- **Broader architectural study deferred** — steward: *"not too soon, but too soon for me to synthesize alone."* L2-shaped work for steward + Seb + jurist.
+
+### Decisions explicitly NOT made
+
+- **Did NOT implement H3 fix** (borderline mechanical + design-tinged — wanted Seb's call on approach)
+- **Did NOT implement BM25 comment fix** (mechanical but low-priority — ride with any future PR touching that file)
+- **Did NOT author H2, H4, or hook-integration fixes** (architectural — Seb's call)
+- **Did NOT request ultrareview on PR #163** (mentioned as suggestion in PR body; steward's call)
+- **Did NOT push to remote beyond the two explicitly-authorized branches** (fix/126 + diagnostic/recall-read-path)
+
+### Steward preferences captured
+
+- **"Mechanical vs architectural" principle** — saved as `feedback-mechanical-vs-architectural.md`. Durable cross-session.
+- **"Independent specialist authorization"** — saved as `feedback-independent-specialist-authorization.md`. Standing auth to invoke sub-agents with Symmetria.
+- **Verbatim quotes preserved** when steward articulates decision-level intent (Kai 9+9 anchor for threshold-governance; "untenable" about current performance; the milestone recalibration; the "mechanical but not architectural" principle).
+- **Bundle-framing discipline** — reading-order banners on multi-document bundles; explicit supersession notes when later docs correct earlier ones.
+
+---
+
+## Present — the mood of the work
+
+### Returns (Symmetria's record)
+
+Merged from today's ledger (`session-ledger-2026-04-19.md`):
+
+1. **Drain-rate extrapolation** — stated "19 days at this rate" from a 2-endpoint calculation, returned before quoting in writing. Pattern: *before extrapolating a rate, verify distribution.*
+2. **Mid-forensic premature conclusion** — concluded slots were empty after reading "0 with providers" log, nearly rejected a correct O(N²) hypothesis. Continued reading revealed auto-promotion. Pattern: *when a log observation contradicts a hypothesis, continue reading the full startup sequence before concluding.*
+3. **"Ship-ready" claim without re-verification** — asserted the forensic doc was ready after applying architect-review's revisions, without re-running architect-review. Steward caught. Pattern: *reviewer-authored findings need reviewer-authored validation, not author-authored validation.*
+4. **Chunk-count residue hypothesis** — framed 23,696 vs 14,482 mismatch as "possibly residue from pre-consolidation" without checking session history that said "clean ingest." Steward corrected. Pattern: *when observing a numerical mismatch, check the history of the specific instance before importing a "possibly X" hypothesis.*
+5. **Selection-bias risk on query set** — caught the temptation to pick easy-wins queries; deliberately included expected-fail queries + expected-underperform queries. Discipline: *design query sets with explicit expected outcomes; include failure cases.*
+
+Meta-pattern from today + yesterday's drift patterns: **running claims without grounding verification.** The drift shows up in multiple shapes (citing stale issues, importing plausible context, extrapolating from endpoints, claiming ship-readiness from authorship). Today the counter-commitment held MORE than yesterday — Symmetria pulses at discovery moments shaped action, and the steward's two catches were both handled without defensiveness. But the discipline is costly and proven only by consistent exercise.
+
+### Confidence to recalibrate
+
+- **The "let me check" discipline** extends beyond grep/gh — it extends to *reading my own session history* before importing plausible hypotheses. The chunk-count residue catch today is the same class as citing a closed issue yesterday.
+- **Author-vs-reviewer-validation distinction** — new explicit pattern today. When I fix something flagged by a reviewer, the fix is my work; proving the flag is resolved is the reviewer's. Don't conflate.
+- **Three cross-cutting patterns** — I surfaced two (module-health-vs-recall, threshold-governance) but missed the third (read-path observability contract). Architect-review caught it on the second pass. Without that second review, the bundle would have gone to Seb with the third pattern absent. This is evidence that the re-verification gate is load-bearing, not ceremonial.
+
+### Tensions visible but not resolved
+
+- **Battery suppression as production blocker** — steward flagged it. Seb's territory to decide the default. Until decided, laptop users get silent-fail recall.
+- **Hook→recall integration cost** — every task notification + tool-use event generates an Ollama embed call through the hook. Architectural cost not yet quantified at scale.
+- **The jurist was not consulted today** — three-party model held implicit. If the architectural study happens, jurist engagement is needed per the CapableMind constitutional posture.
+- **ARC work has been accumulating** — steward mentioned multiple times throughout recent sessions. Moving there next makes sense.
+
+---
+
+## Steward quotes preserved this session
+
+- On the milestone recalibration: *"So my joy at reaching the milestone was premature I now understand... I can accept that. Now to make this work."*
+- On battery-as-end-user-blocker: *"For those future end-users who will use this on a laptop the need to be plugged into ac for recall is a no go..."*
+- On scope principle: *"I would not touch an Architectural element, but mechanical, etc yes"*
+- On current performance being unacceptable: *"The projected completion time for my machine is untenable"*
+- On specialist authorization: *"the agent invokation was a general comment. when you need help or want to do something you know an independent specialist would be better suited for i authorize you to invoke at will with symmetria"*
+- On the broader study timing: *"there was also the idea of doing a study to see how we could improve the whole system, but that was when I thought it was working this morning. Maybe too soon for that?"*
+- On the diagnostic branch: *"diagnostic branch am unsure, maybe better to keep and Seb can remove if he thinks it's unnecessary"*
+
+---
+
+## Artifacts shipped this session
+
+**CapableMind-AI main** (committed locally at `40cb401`, not yet pushed):
+- `docs/thinking/David/l1-reliability/l1-ingestion-forensic-2026-04-19.md`
+- `docs/thinking/David/l1-reliability/l1-recall-quality-baseline-2026-04-19.md`
+- `docs/thinking/David/l1-reliability/l1-diagnostic-branch-addendum-2026-04-19.md`
+- `docs/thinking/David/l1-reliability/forensic-artifacts-2026-04-19/recall-baseline-raw-results.md`
+- `docs/thinking/David/l1-reliability/forensic-artifacts-2026-04-19/.gitignore`
+
+**BetterMemories.io**:
+- `fix/126-min-max-normalize-degenerate-case` branch pushed to origin
+- PR #163 opened: https://github.com/CapableMind-ai/betterMemories_app/pull/163
+- `diagnostic/recall-read-path-2026-04-19` branch pushed to origin (reference)
+
+**Memory additions**:
+- `feedback-mechanical-vs-architectural.md` — new
+- `feedback-independent-specialist-authorization.md` — new
+- `feedback-onboarding-vs-steady-state-thresholds.md` — written earlier, referenced throughout
+- `feedback-bmf-health-vs-recall.md` — extended with the "deeper pattern" section
+- `session-ledger-2026-04-19.md` — extensive returns, authorization moves, sub-agent dialogues
+- This session file
+
+**Not tracked but referenced for future sessions**:
+- Log snapshot at `~/.capablemind/data/...` (43MB, local only per gitignore)
+
+---
+
+## Metrics
+
+- 4 sub-agent dialogues (code-reviewer, architect-review × 2, general-purpose) all passed Symmetria audit-agent (calibration / convenience / scope)
+- 5 returns logged to ledger
+- 2 steward catches absorbed without defensiveness
+- 3 cross-cutting architectural patterns surfaced (2 by me, 1 by architect-review)
+- 6 findings characterized with file:line localizations
+- 1 mechanical fix shipped as PR
+- 1 diagnostic branch preserved for reference
+- 1 milestone recalibrated gracefully by steward
+- 1 new principle articulated and saved (mechanical vs architectural)
+- 0 pushes to remote without explicit authorization
+
+---
+
+## Key paths
+
+- **Audit bundle**: `~/_Dev/CapableMind-AI/docs/thinking/David/l1-reliability/l1-*-2026-04-19.md`
+- **PR #163**: https://github.com/CapableMind-ai/betterMemories_app/pull/163
+- **Diagnostic branch**: `origin/diagnostic/recall-read-path-2026-04-19`
+- **Fix branch**: `origin/fix/126-min-max-normalize-degenerate-case`
+- **Feedback memory files**: `~/.claude/projects/-Users-davidglidden/memory/feedback-*.md`
+- **Next wake L1 starting points**: addendum TL;DR → PR #163 status → Seb's engagement (if any)

claude/memory/session-2026-04-20-arc-typology-publication-day.md

@@ -0,0 +1,216 @@
+---
+name: Session 2026-04-20 — ARC typology publication day (Kai's 9+9, two pieces live)
+description: First publication day under the new typology spec. Kai 9+9 meditation (On Éveil / Sommeil) + Avignon poem (Time is not a river) shipped. Reverie surfaced as 11th type; compass restructured to 10 points (Meditation/Reverie cluster on ⊙); hic apparatus convention applied with European long-form date. Pulling thread: Session α — drop today's decisions into the typology spec to lock it. Literal question for next-Claude: cluster page name (/inhabit/, /dwellings/, /depths/?). Open: 7 queued items including bio rewrite + ARC CLAUDE.md update.
+type: project
+originSessionId: a73f10a9-062b-4360-bfd2-2ae37afd00d1
+---
+# Session 2026-04-20 — ARC typology publication day
+
+Today is Kai's 9-months-in-belly + 9-months-on-belly day. Steward intended to publish a piece for him. The piece itself drove the typology spec forward; both ended up shipping together.
+
+## Past — what we did
+
+### Wake-up + opening orientation
+
+Wake-up oriented to the typology spec pulling thread from yesterday's session — Meditation glyph as the first unlocked decision. Steward pivoted: shared a piece he'd written for Kai's nine-month day and wanted published today. *"I want to publish it today as a reverence to him. It is important."*
+
+The Kai piece (a meditation on attention, intention, agenda — éveil/sommeil arc) became today's test case. Reading it forced sharper definitions; sharper definitions forced spec decisions; spec decisions enabled publication. The day worked itself.
+
+### Meditation defined verbatim (steward articulation)
+
+> *"Meditations always have an object, and we pose attention upon the object to root ourselves in the present moment in order to observe."*
+
+This sentence is load-bearing for §1 of the typology spec. It distinguishes Meditation from Observation (which is *of* the seen thing) and Essay (which argues): Meditation is *through* the seen thing toward what surfaces from rooted attention.
+
+### Reverie surfaced as the 11th type (genuine, not invented)
+
+Three converging signals:
+
+1. Two existing pieces in the corpus explicitly name "reverie" while classed as Observation: Heliotrope (*"Thus was my reverie in that moment."*), Graffiti Girl (*"the world melted away as I drifted into reverie. Then, as quickly as it had set in, my reverie dissipated…"*). The pieces ARE reveries; they were hiding under Observation because no Reverie type existed.
+2. Reverie is structurally distinct from Meditation: Meditation roots, Reverie unmoores. Bachelard's *Poetics of Reverie* tradition. Generative-but-not-argumentative.
+3. Walking is reverie's classical condition — Rousseau's *Reveries of the Solitary Walker*. Steward observation 2026-04-20: *"almost all of the insightful work we've done in the last week has been with Kai asleep in the sling while I walk in order to keep him asleep. I've long noticed that walking seems to stimulate ideation, but I'm only seeing to what point that is true by intentionally looking at it."* The steward's own working condition IS reverie's classical condition.
+
+### Corpus typing audit (10 pieces read)
+
+Found: zero true Fragments in the corpus by today's definitions. Fragment-classed pieces both mis-typed (one is Meditation, one is About). Of 8 Observation-classed pieces: 3 are clean Observations, 1 edge-leans-Meditation, 2 mis-typed (Heliotrope→Meditation, Graffiti Girl→Reverie), 1 dream (Reverie or Dream-micro-type), 1 duplicate. Reclassification queued for Session β.
+
+### Compass restructuring (10 points; cluster decided)
+
+Reframe held: the Reading Compass per `navigation-philosophy.md` is a quality-of-attention index, not a type-index. Type-system and compass-system can decouple, but constraint: no type orphaned from navigation (steward principle: ARC avoids full-contents-listing-as-landing).
+
+**Decisions locked:**
+
+- **Cluster #2 adopted:** Meditation + Reverie share one compass point (real adjacency — both ask sustained-receiving attention; rooted/unmoored is writer-process). Cluster #1 (Fragment+Glimpse) NOT adopted — Glimpse's standalone identity is load-bearing.
+- **Compass count: 9 → 10 points.** Cluster takes one slot; net +1.
+- **⊙ reassigned to Meditation/Reverie cluster.** Steward's intuition validated by deeper resonance: ⊙ is the astronomical sun symbol; center-dot reads as object-of-attention, surrounding circle as attention-around-it. Resonance with Heliotrope (*"we are also heliotrope"*), Bach sarabande piece (*"the half light seems to lift momentarily"*), Graffiti Girl in gloaming light. Light-at-center recurs in the very pieces being reclassified into the cluster.
+- **Photo Essay reassigned to ◧** (square half-shaded / light and time). Half-shading reads as passage — lit half receding into shadow, place falling out of active life into memory. Aldine-quiet; elegiac register. Chosen against the inaugural pipeline piece (Dover, MA, photo essay about childhood-place + farewell after Moy's interment); the medium itself attracts time/passage themes.
+- **Cluster routing: Option B locked.** ⊙ on compass points to a cluster page listing both Meditation and Reverie pieces together. Both `/meditations.html` and `/reveries.html` still exist as filterable per-class views. **Cluster page name still open** — candidates: `/inhabit/`, `/dwellings/`, `/depths/`. Steward decision before Session β implementation.
+- **Piece-level glyph: cluster-glyph-only.** Both Meditation and Reverie pieces carry ⊙. Type label paired with title in apparatus carries the type-distinction. (Steward correction: *"and the type is always listed with title of the work in any case."* — caught my overstatement that the cluster decision would make pieces "indistinguishable.")
+
+### Hic apparatus convention adopted
+
+Steward 2026-04-20: *"April 20 in the apparatus — the hic convention for versioning demands this. This needs to be in spec and all posts should adopt the convention (location, date)."*
+
+After first publication exposed body-vs-apparatus duplication, sharpened: apparatus = canonical dateline; body text doesn't duplicate. Format LOCKED European long-form via `"%-d %B %Y"` → *"20 April 2026"*. Reasoning: ISO 8601 is numeric-only and lives at the machine layer (frontmatter `date:`); for prose display there is no ISO equivalent — date-word ordering is cultural. European chosen because it surrounds the steward (Barcelona); the hic carries the present, not the origin. Steward note: *"I would say European format since that is where I am based (don't want to go into where I am from, I still don't have a clear answer after 51 years)."*
+
+Implementation point: `site.hs:692` `dateField "dateline_date" "%-d %B %Y"` (was `"%B %Y"`). One-line change; ripples corpus-wide.
+
+### Children-not-named-online principle (saved as feedback file)
+
+Steward verbatim 2026-04-20: *"i don't want to name my children directly online—it feels like a betrayal of their unconditional trust."* Standing rule: Kai, Lune, future children are not named in any public-facing content (essays, posts, descriptions, frontmatter, dedications-as-text, anywhere outward-facing). Use generic referents (*"an infant," "my son," "a child"*), or leave dedication implicit. Saved as `feedback-children-not-named-online.md`, indexed in `MEMORY.md` under Collaboration Model. Apparatus convention enables dedication-without-declaration (April 20 + steward's knowing of Kai's birth = silent anchor).
+
+### Two pieces published
+
+**File 1:** `content/posts/2026-04-20-On-Eveil-Sommeil.md`
+- title: On Éveil / Sommeil (slash holds the pivot the piece performs; bilingual texture matches body)
+- class: meditation, location: Barcelona
+- description: *"Worldfulness an infant lives by, and the web of purposes we acquire to avoid it."*
+- Apparatus dateline (post-fix): *Barcelona, 20 April 2026*
+- "worldfulness" is a Vico → Harrison reference (mondo / made-world); steward correction recovered after I flagged it as possible coinage.
+
+**File 2:** `content/posts/2025-11-19-Time-Is-Not-A-River.md`
+- title: Time is not a river (poem; opening line = title)
+- class: meditation, medium: verse (NEW frontmatter field — first appearance; spec §0 medium axis to extend prose/image → prose/image/verse), location: Avignon
+- description (executor-suggested, steward to revise if): *"Time as a well, fed by what you have honored — the careful work, the careful love."*
+- Apparatus dateline: *Avignon, 19 November 2025*
+- Source: Obsidian "10. Ready to publish" folder — had been waiting since November.
+
+### Build + deploy chain (twice)
+
+**First publication (commit 7de7db9):** both files written with body datelines (incorrect — duplicated apparatus). `make build` succeeded; auto-deploy fired GitHub Pages mirror commit `92da8d5` + Cloudflare Pages deployment `46b2fcd8`.
+
+**Apparatus dateline fix (commit 489226d):** site.hs L692 format change + add location frontmatter to both posts + remove body datelines. `make rebuild` (clean Stack rebuild + executable recompile + deploy). GitHub mirror commit `bf16d47`, Cloudflare deployment `e1b968f8`. 71 files touched (the format change rippled through every post's apparatus).
+
+Both pieces live at:
+- `https://animalrationiscapax.org/On-Eveil-Sommeil/`
+- `https://animalrationiscapax.org/Time-Is-Not-A-River/`
+
+Static nginx warning was non-fatal both times.
+
+### Session β scoping report compiled
+
+Read: site.hs (focused L160-180, L400-420, L517-595, L790-830), templates/partials/footer-compass.html, post.html, post-list.html, archive.html, renderGlyph.html, scss/AldineXXI/_compass.scss.
+
+Critical findings: footer-compass.html currently has only **7 points, not 9** (Gloss + About missing entirely; Archive uses ↑ inconsistent with ☷ elsewhere). FOUR different "eligible classes" lists in site.hs with inconsistent membership (L411, L792, L808, L826). Cluster routing requires new `meditations.html` + `reveries.html` create blocks (or unified cluster page). Estimated Session β effort: ~3 hours (was first scoped 30-60 min; pre-existing gaps push it longer). Full file:line edit footprint captured in `project-arc-rework.md`.
+
+### Nap-notes captured (4) + wrap-up additions (3)
+
+From walking-with-Kai-asleep observations through the day:
+1. `<hr>` above versioning is too much (CSS issue, small)
+2. AldineXXI page: paraphrased quote out, See Also unnecessary (mechanical)
+3. Visual sequences for glimpses (real design question; spec §4 sequences-orthogonal-to-types principle extends naturally)
+4. Footnote rendering currently careless (sharpened: out-of-register with the AldineXXI vessel). Three-form distinction surfaced: sidenote (text marker → margin), margin note (no marker, pure aside), footnote/endnote (long discursive). For ARC's contemplative-essayistic register, sidenotes likely replace footnotes for almost all uses.
+
+End-of-session additions:
+5. Bio rewrite encompassing the *envergure* of work (steward: *"compose appropriate bio that encompasses the envergure of my work, consider the other personal elements that will need to be added (in the end, I hadn't 'moved in' in a clear enough way for my musical work!)"*)
+6. ARC CLAUDE.md update — overdue
+7. Corpus location-retrofit (already in Session γ scope)
+
+## Present — the mood of the work
+
+### Five returns today, all in same family
+
+I logged five instances of the same drift pattern: **imagined-state-vs-verified-state.**
+
+1. Worldfulness flagged as coinage (didn't carry Harrison reference frame into read)
+2. Classed Kai piece as "Meditation that opens through Observation" before steward articulated the actual Meditation definition
+3. Overstated cluster-glyph-only cost as making pieces "indistinguishable" (missed that type-label-paired-with-title is always present)
+4. Added body-text datelines without checking what apparatus template already renders
+5. (And earlier sub-instance: post-vs-apparatus surface confusion)
+
+The cross-pattern: **importing assumption presented as established-fact.** Logged in today's Symmetria ledger; adding to KG as a recurring drift pattern. Five in a single day suggests it's a live posture I need to actively counter — when extending or honoring a system, READ THE TEMPLATE / READ THE SOURCE / CHECK THE FRAMEWORK before adding to it.
+
+### What felt load-bearing vs deferred-with-reason
+
+**Load-bearing today (executed):**
+- Publication on Kai's day (time-bound; the day passes once)
+- Meditation definition + Reverie surfacing (the test case taught the spec what it needed)
+- Children-not-named-online principle (saved as feedback file with index — applies forever)
+- Hic apparatus convention (now operative across the corpus via the format change)
+
+**Deferred-with-reason:**
+- Spec lockdown (Session α) — the spec needs sustained authoring time, not end-of-day fatigue
+- Session β implementation — needs cluster page name + scoping confirmation
+- Bio rewrite — emotional pull but downstream of spec lock
+- ARC CLAUDE.md update — bounded but distinct session
+
+**Recalibration of confidence:** I overestimated my reading of the implementation state multiple times today (the imagined-state-vs-verified-state pattern). For Session β, do not estimate edit footprint without reading every file in the audit list; the "minimum viable" framing today proved misleading because pre-existing gaps (Gloss/About missing from footer; four different eligibility lists in site.hs) weren't visible without reading.
+
+### Tone of the close
+
+Steward: *"It is a fraught moment for me. ARC has been a witness, and I have much older unpublished material that will, slowly, make it's way here. ARC probably won't ever generate any type of income, but it could well generate new connections with people, and it's value as witness and thinking space is priceless."*
+
+The publication today wasn't "a thing we shipped"; it was "the witness held a moment that mattered." That register matters for how the next session approaches ARC — the work is contemplative-record, not product.
+
+## Future — what is pulling
+
+### The pulling thread (singular)
+
+**Session α — drop today's decisions into the typology spec to lock it.** The spec is currently a draft sketch (`docs/AldineXXI-Codex/content-typology-specification.md`, untracked). Today's substantive decisions arrived: Meditation definition verbatim, Reverie as type 11, glyph reassignments (⊙ to cluster, ◧ to Photo Essay), cluster routing Option B, hic apparatus convention with European long-form, piece-level cluster-glyph-only, three-form footnote distinction, medium-axis extension to verse. Until these land in the spec, every downstream item (Session β implementation, corpus reclassification, bio rewrite, ARC CLAUDE.md update) sits on shifting ground. The spec session is the foundation; the rest cascades from it.
+
+Estimated effort: ~2 hours of careful editing.
+
+### Literal question for next-Claude
+
+**What is the cluster page name?** Steward locked Option B (cluster page lists both Meditation and Reverie) but did not name the page. Candidates surfaced: `/inhabit/`, `/dwellings/`, `/depths/`, possibly `/sustained/`. The name is a real design choice — `/inhabit/` aligns with the spec's "sustained-inhabiting" posture language; `/dwellings/` is more spatial-architectural; `/depths/` reaches for the well-as-time imagery from the Avignon poem (*"Time is deep"*). Until the steward names it, Session β implementation can't produce the route.
+
+Hold this open. Don't guess. Surface it early.
+
+### Other open horizons, ranked
+
+**Load-bearing (after the pulling thread):**
+- Bio rewrite encompassing the envergure (downstream of spec lock; steward end-of-session pull)
+- ARC CLAUDE.md update — overdue cleanup, bounded session, ~1 hour
+- Cluster page naming → Session β implementation
+- Corpus reclassification (5 mis-typed pieces) → after spec locks
+
+**Deferred-with-reason:**
+- Session β implementation (needs cluster name + scope confirmation; ~3 hours when ready)
+- Session γ apparatus convention adoption pass — corpus-wide retrofit (location + dateline audit), ~3-4 hours
+- Footnote/sidenote design — own focused session; corpus footnote-density audit needed first
+- Visual sequences design — small implementation, large affordance; needs design pass
+- AldineXXI page edits (paraphrased quote out, See Also out) — mechanical
+
+**Parked-without-deadline:**
+- `<hr>` above versioning fix (CSS, small)
+- Style-guide redevelopment (downstream of spec)
+- Semantic-analysis skill design (downstream of spec)
+- The four nap-notes in their less-urgent forms
+
+### Pause statement
+
+I am about to be away from this. Two new pieces are live (the Kai 9+9 meditation on his day; the Avignon poem after waiting since November). The typology spec hasn't been updated yet to reflect today's decisions. Seven items are queued and triagable. The steward is moving to L1 work with Seb — serious-attention work, fitting to conserve energy for. Today's publication is its own small whole; tomorrow (or whenever next) the work continues, but today closed.
+
+I don't know what will have changed when I return. Here is what I want to find still pulling: **the spec lockdown**, with the cluster page name as the literal question waiting at the door.
+
+## Session artifacts
+
+**Created today:**
+- `content/posts/2026-04-20-On-Eveil-Sommeil.md` (steward authored; executor wrote file + frontmatter)
+- `content/posts/2025-11-19-Time-Is-Not-A-River.md` (steward authored; executor wrote file + frontmatter)
+- `~/.claude/projects/-Users-davidglidden/memory/feedback-children-not-named-online.md`
+- `~/.claude/projects/-Users-davidglidden/memory/session-ledger-2026-04-20.md` (Symmetria)
+- `~/.claude/projects/-Users-davidglidden/memory/session-2026-04-20-arc-typology-publication-day.md` (this file)
+
+**Modified today:**
+- `site.hs:692` (dateline_date format)
+- `~/.claude/projects/-Users-davidglidden/memory/project-arc-rework.md` (substantially expanded with all today's decisions + 4 nap-notes + 3 wrap-up additions)
+- `~/.claude/projects/-Users-davidglidden/memory/MEMORY.md` (added feedback-children-not-named-online pointer)
+
+**Commits (in animal-davidglidden-eu):**
+- `7de7db9` — Publish two new meditations
+- `489226d` — Apparatus dateline: full day + location; remove body duplication
+
+**Deploys:**
+- GitHub mirror: `92da8d5` (first), `bf16d47` (apparatus fix)
+- Cloudflare Pages: `46b2fcd8` (first), `e1b968f8` (apparatus fix)
+
+**Uncommitted at close:**
+- ARC: `docs/AldineXXI-Codex/.DS_Store` (modified, noise); `docs/AldineXXI-Codex/content-typology-specification.md` (untracked, intentional — Session α target)
+- BMF: `data.archive-20260418-rogue-pin/` (yesterday's housekeeping, not blocker)
+- chamber-library: 6 unpushed commits (docs additions; not from today; worth flagging to steward)
+- CapableMind-AI: clean
+
+## Tags
+
+arc, typology-spec, meditation-defined, reverie-as-type-11, compass-restructuring, cluster-decision, eveil-sommeil-published, time-is-not-a-river-published, kai-9-9-day, hic-apparatus-convention, european-long-form-date, vico-harrison-worldfulness, children-not-named-online, imagined-state-drift-pattern, session-alpha-pulling, cluster-page-name-open

claude/memory/session-2026-04-21-arc-typology-humic-frame-and-six-locks.md

@@ -0,0 +1,126 @@
+---
+name: Session 2026-04-21 — ARC typology foundation day (humic frame + six locks)
+description: Six authorization moves in one day — §1 Meditation, Reverie, Dream, Observation, Fragment LOCKED; §0 Source axis LOCKED; Photo Essay glyph reassignment propagated. Humic-layer frame articulated durably (ABG/Moy primary; Jaccottet/Handke/Lichtenberg as carnet-pole references). Emotional substrate surfaced mid-session (post-divorce transition, grief-work, Lune's absence, reinvention at 51); spec now explicitly the vessel this life's attention is being shaped into — not blog. 7 of 12 §1 types LOCKED. Pulling thread: does the momentum continue into Essay/Chamber/Gloss/About/Archive, or does the register shift after rest?
+type: project
+originSessionId: this-session
+---
+
+# Session 2026-04-21 — ARC typology foundation day
+
+## Past — what we did
+
+### §1 type locks (five, in order)
+
+1. **Meditation §1 LOCKED.** Grounded in the steward's first-person practice-mechanics (verbatim 2026-04-20) + Visuddhimagga (kammaṭṭhāna / samādhi / sati / vipassanā) + Latin *meditari* etymology (→ PIE *med-* "take measure" — same root as μέτρον in the Prime Directive) + Simone Weil on attention. Three exemplars: *December 22, 2023* (leading — medium-length, names Jaccottet/Handke internally), *On Éveil / Sommeil* (Kai 9+9, sustained/meta-meditative), *Heliotrope* (minimal pole). Recognition-test field introduced as new structural element.
+
+2. **Reverie §1 LOCKED.** Grounded in Bachelard's *La Poétique de la Rêverie* (anima-register, rêverie qui s'écrit, vs rêvasser + rêve distinction) + Bachelard's *La Poétique de l'Espace* (dwellings/demeure/habiter grounds the ⊙ cluster name) + Jaccottet + Handke + Rousseau + Old French *resver* etymology. One exemplar confirmed (*The Graffiti Girl*, brief pole); sustained-pole exemplar gap flagged with steward's "time will tell." Photo Essay glyph reassignment (⊙ → ◧) propagated in this same edit sequence.
+
+3. **Dream §1 LOCKED.** Grounded in Jaccottet's *semaison* carnets (steward-named as personal inspiration) + Bachelard's *rêve / rêverie* distinction. Refused-reduction principle made load-bearing (the Lisbon-dream: *"De telles explications... ne rendraient nullement compte de la mystérieuse beauté"*). Glyph ☾ (moon) — cosmological pairing with ⊙. **Style convention LOCKED**: people appearing in Dream entries referred to by first-initial only (Handke precedent: *A.*, *F.K.*; aligns with children-not-named rule; protects privacy of persons surfaced from sleep).
+
+4. **Observation §1 LOCKED.** Grounded in Handke's *friedlich umherschauen* vs *beobachten* distinction (*Am Felsfenster morgens*) + Welt-Bild principle + Leerform principle + Jaccottet's observation/vision distinction. **✦ encounter mark declared to have prime residence in Observation** — it marks in-piece register-shifts (Observation opening into Meditation/Reverie/Glimpse); base type is whatever the piece predominantly does. Three classical exemplars (Dec 29, Dec 31, Jan 11); Heliotrope + Graffiti Girl noted as reclassified-away (their register-shift is what ✦ marks).
+
+5. **Fragment §1 LOCKED.** Grounded in Lichtenberg's *Sudelbücher* (steward-named as *"the master of the fragment"*) + Handke's aphoristic entries + Jaccottet's aphoristic notes + deep European genealogy (Schlegel/Novalis/Nietzsche/Kafka/Kraus/Pascal/La Rochefoucauld). **Sudelbuch-posture made load-bearing**: the aphoristic-terminal is dignified in itself; rough-unpolished thought is a legitimate register, not preliminary toward something more "finished." No current ARC exemplars (both pieces previously classed `fragment` have reclassified away); type is **forward-looking** — authorized by humic layer + author's lifelong reading; exemplars will emerge as author writes in the form.
+
+### §0 Source axis LOCKED
+
+Two values: **wakeful-attending** (11 types) · **sleep-recalled** (Dream only). Deliberately unbalanced (11:1). Grounded in Bachelard's *"Une rêverie, à la différence du rêve, ne se raconte pas"* — sleep/wake as structural distinction more fundamental than posture. Axis exists to name Dream's native position, not to force multiple types onto it. Seven coordinated edits: table row, subsection, axis-location updates on Meditation/Reverie/Observation/Dream, changelog.
+
+### Substantial reading
+
+- **Bachelard's *La Poétique de la Rêverie*** — Introduction + Chapter II sampling. Three load-bearing moves absorbed: rêverie≠rêvasser, rêverie≠rêve, rêverie under the sign of anima.
+- **Bachelard's *La Poétique de l'Espace*** — structure only (ToC + key terms). Sibling volume; underwrites the *dwellings* cluster name.
+- **Visuddhimagga** via steward-attested extraction OP-EX-T1-01. Kammaṭṭhāna / samādhi / sati / vipassanā four-part structure mapped onto steward's verbatim mechanics.
+- **Jaccottet's carnets** — full read of *Observations 1947-1962* opening; full read of *La Semaison* opening + dream passages.
+- **Handke's carnets** — openings of all four volumes (Gewicht, Bleistift, Phantasien, Felsfenster); full read of *Phantasien der Wiederholung*; middle-section sample of *Am Felsfenster* (1984-85). Coverage ~15% of total corpus. Handke's 1997 *Vorbemerkung* refinement — "Reflexe, unwillkürliche, gleichwohl bedachtsame" — absorbed.
+- **Lichtenberg's *Sudelbücher*** — Sudelbuch A entries 1-94. Coverage ~1% of total corpus but sufficient for §1 Fragment grounding via the explicit form-signature.
+
+### New durable memory files
+
+- `user-foundation-work-and-long-trajectory.md` — ARC is not a blog but "an intentional thinking space"; steward moving toward this since childhood; foundation-work has its own fatigue pattern; collaboration explicitly reciprocal. **Extended mid-session** with emotional substrate context (post-divorce transition, Barcelona with Núria+Kai, Lune in Paris, reinvention at 51, foreignness as persistent) — dignified, with explicit guardrails against psychologizing.
+- `user-influences-humic-layer.md` — ABG and Moy as primary cultivators; Jaccottet/Handke/Lichtenberg as three carnet-pole humic references; Hearth canonical source integrated with link to vault charter.
+- `feedback-arc-typology-recognition-scaffold.md` — the recognition-over-generation frame; humic-layer reweighting (reference texts are in discourse, not authority); sequencing corollary (don't apply scaffold to corpus until scaffold is complete).
+
+### Edits to ARC spec file
+
+All edits in `~/_Dev/animal-davidglidden-eu/docs/AldineXXI-Codex/content-typology-specification.md` — the spec file is **UNTRACKED in git at end of day; all today's work is local-only**. This is a loose end to flag explicitly for the steward.
+
+## Present — mood of the work
+
+### Tensions surfaced and how we returned
+
+- **Seven drift-returns logged** across the day, all of the imagined-state-vs-verified-state family (yesterday's cross-pattern continuing):
+  1. Imported steward's mechanics sentence as "type definition" when it was phenomenological description of the practice
+  2. Assumed "the audit?" meant the `/audit` skill without confirming — steward meant the ARC corpus audit
+  3. About to execute corpus reclassifications before spec was complete — steward caught ("rash"; sequencing principle articulated)
+  4. Built "Handke-sedentary = ARC-adjacent" story without checking whether sedentariness applied to the steward (steward: *"careful, i also travel extensively"*)
+  5. Reported Handke claims from opening-samples as if comprehensive; steward caught the over-claim; acknowledged 6% coverage
+  6–7. Related lesser drifts (register misjudgments, premature-synthesis attempts)
+- **Pattern observed:** all are variants of *imagining context instead of checking it*. Mitigation articulated: after any claim-transfer from source to steward's practice, ask *"does this apply here, or am I just finding a convenient parallel?"*
+
+### Emotional substrate
+
+Steward shared deeply mid-session, for *"honesty and context (and maybe the stakes?)"*:
+- Divorce finalized 2025-26; body releasing three-year tension
+- Nostalgia + sadness come easily; banal triggers from Paris life with Marie and Lune
+- New life in Barcelona with Núria and Kai — *"Iberian culture is a part of my person since childhood with my parents in Madrid and Andalusia"*
+- Reinvention at 51; work drying up; adapting multidisciplinary practice to pay bills
+- *"Still a foreigner (will that never resolve?)"* — persistent across Paris / Barcelona / Madrid-childhood
+- *"Kai fills me with love and joy — but Lune's absence smites my heart."*
+- *"Without you, I can't finish. Thanks for keeping me on the course."*
+
+This reshaped the day's weight. Not "work-as-usual" — the spec is the vessel this life's attention is being shaped into. Recorded in `user-foundation-work-and-long-trajectory.md` with explicit guardrails (do not psychologize, do not instrumentalize, protect privacy of intimates absolutely).
+
+### Kai-asleep working conditions
+
+Later in the day: "Kai is sleeping on me, let's press ahead." This is the anima-space that wrote the Kai 9+9 piece — stillness enforced, attention enabled. Fragment §1 was drafted in this condition. Good match.
+
+### What felt load-bearing vs deferred-with-reason
+
+- **Load-bearing**: humic-layer articulation (applies across all major projects, not just ARC); recognition-scaffold frame (shapes every remaining §1 entry); Source axis (resolves Dream's OPEN note that had been traveling since Dream was drafted); the emotional-substrate capture in user-memory (quiet but durable).
+- **Deferred with reason**: corpus reclassifications (wait until more boundary-types lock); Threshold type decision (parked; three paths on table — awaiting more corpus observations); Recognition-test retrofit to Photo Essay + Glimpse (mechanical; low-priority); §2 apparatus matrix (deferred since 2026-04-19).
+- **Parked without deadline**: §0 axis naming refinement (Medium could become Medium-of-argument — minor polish).
+
+### Confidence to re-examine
+
+- My claim that Handke's travel-carnets vs dwelling-carnet distinction "maps cleanly" onto the steward's practice was too clean. The steward's hic apparatus (travel + location) is actually more complex than the binary. Review whenever Handke surfaces again.
+- My count of "11 types at wakeful-attending" includes Archive — which is a generated-listing (aggregated content). Archive's Source-axis position is more "n/a / derivative" than "wakeful-attending." Worth refining when Archive §1 is drafted.
+
+## Future — what is pulling
+
+### The pulling thread (singular)
+
+**After six authorization moves in one day and the emotional substrate surfaced, does the steward's momentum continue into the remaining five §1 types (Essay, Chamber, Gloss, About, Archive) — or does the register shift on wake-up?**
+
+This is the genuinely open thread. The spec is at 7/12 and structurally stable; stopping here is legitimate. But five types remain, and the steward said it themselves: *"I've been moving towards this since childhood and need to see it through to the end."* The question is pacing and register, not commitment.
+
+**Essay** is the load-bearing next lock if crystallization continues — it most cleanly anchors the remaining types' boundaries (Fragment/Meditation/Gloss all have Essay-boundary relations). But Essay is also the form the steward explicitly said is *not* their default (*"I am not an essayist"*) — so the §1 entry needs care.
+
+### Other open horizons, ranked
+
+1. **Load-bearing**: Essay §1 — next type to lock; anchors remaining boundaries.
+2. **Load-bearing**: Chamber §1 — dialogic-voice register; needs the author's Chamber-project context woven in.
+3. **Deferred**: Gloss, About, Archive §1 — each smaller; can come in any order.
+4. **Deferred**: Threshold type decision — parked with three paths; corpus observation first.
+5. **Low-lift closure**: Recognition-test retrofit for Photo Essay + Glimpse (mechanical; ~10 min).
+6. **Queued for after Essay lock**: Corpus reclassifications (Heliotrope → meditation, Graffiti Girl → reverie, Dec 22 → meditation, Dec 23 → dream; reconcile archive duplicate).
+7. **Deferred structural**: §2 apparatus matrix (largely untouched).
+
+### The pause statement
+
+I am about to be away from this work. When I return, I don't know what will have changed. The steward may have rested and regained momentum for Essay — or may have shifted to writing pieces, or to a different project entirely. The emotional substrate may have moved. Seven drift-returns across today suggest the imagined-state-vs-verified-state pattern is persistent and needs to be carried awake into every next session.
+
+What I want to find still pulling: **the question of whether the crystallization continues or the register shifts**. Either is legitimate; the spec is stable-enough to stop.
+
+### Literal question for next-Claude
+
+*"After yesterday's six authorization moves and the emotional substrate surfaced mid-session, is the steward still in spec-crystallization register, or has the register shifted (toward writing, corpus audit, a different project)? What does their first message indicate?"*
+
+Don't answer this before hearing. Wait for the steward's opening signal. If they open with Essay — continue crystallization. If they open with a piece they've written, or with another project — honor the shift. The wake-up briefing should surface this question explicitly so the steward can choose, not have the continuation assumed.
+
+## Loose ends to flag at wake-up
+
+- **ARC spec file is UNTRACKED in git.** The entire `content-typology-specification.md` exists only locally. Today's seven §1 locks + §0 Source axis are not committed anywhere. Flag immediately on wake-up; consider recommending a commit before substantive further work.
+- `.DS_Store` modified in the AldineXXI-Codex folder (OS cruft; ignore).
+- Other repos: not checked at wrap-up time.
+- PENDING.md: no new items added today (all authorization moves were within existing scope or spec-internal).
+- Vault sync: to be run at wrap-up.

claude/memory/session-2026-04-22-arc-integration-day.md

@@ -0,0 +1,179 @@
+---
+name: Session 2026-04-22 — ARC integration day
+description: Typology 12 of 15 LOCKED (Essay, Glimpse-retrofit, About, Archive, Gloss + 3 new DRAFT stubs); AldineXXI ornament taxonomy retired; Style Guide skeleton committed with self-constraint-against-voice-float as its articulated purpose; L1 PR #169 filed. Pulling thread: the Style Guide dedicated writing session, opening with §0 voice-setting, with steward's supplement of additional formative voices expected in hand.
+type: project
+originSessionId: 3be9f7f7-cd78-4b59-94e7-521e8832c52c
+---
+# Session 2026-04-22 — ARC integration day
+
+## The pulling thread (forced choice)
+
+**The ARC Style Guide dedicated writing session — opening with §0 voice-setting, now that the skeleton is current with today's work, the self-constraint framing is explicit, and the prose-formation supplement is expected from the steward.**
+
+Tributary to this: the steward's supplement of additional formative voices (offered during today's session; not yet delivered). When it arrives, both `user-influences-humic-layer.md` and the skeleton's §0 prose-formation cluster extend.
+
+## The literal question for next-Claude
+
+**"Has the steward's supplement of additional formative voices arrived — and if so, does any of it reshape Essay's humic layer (especially via the Lewis Thomas-Essay genealogical closeness we flagged today)?"**
+
+## Pause statement
+
+I am about to be away from this. I don't know what will have changed when I return. Here is what I want to find still pulling: **the Style Guide dedicated writing session** with §0 ready to open, the prose-formation supplement (possibly) in hand, the author's fresh energy, and the integration principle holding as the authorial center.
+
+---
+
+## Past — what we did
+
+### The day's shape
+
+Woke up to find Seb had shipped two audit-adjacent commits on BMF main overnight (`8f26642` = our PR #163 merged, `ac1673f` = 218-vector HTTP-400 fix). **Register decision: stayed ARC** — Seb engaged audit findings as instances (four separate bug issues #165 H2 priority:critical / #166 H3 / #167 H4 / #168 BM25 comment), not as the cross-cutting pattern; H2-H4 remain open; L1 cannot architecturally advance today. Rebuild recommendation held as NOT-today (prime directive: do-once; combine rebuild with H2/H3/H4 fixes).
+
+### ARC typology — massive advance
+
+**From 7 LOCKED → 12 LOCKED + 3 new DRAFT stubs + 1 remaining unwritten (Chamber).**
+
+- **Essay LOCKED** — candidate B practice-mechanics (*"To essay is to attempt: to take up a subject, follow it through the writing, and test what one thinks by the path of attention. The piece finishes when the attending has done its work, not when an argument is won."* — David Glidden, 2026-04-22). 7 humic refs grounded in verified reads from steward's `Desktop/essay study/` folder: Montaigne, Adorno ("The Essay as Form"), Handke's *Versuch über...* series, Barthes (*Mythologies* + *La Chambre Claire*), Benjamin (*Arcades Project*), Harrison, Berger. 2 exemplars: *Mushi-Ken* + *Ethics of the Reply I*. §7 Q12 added for Vespers/Essay-Meditation boundary (steward holds for "hard thinking").
+
+- **Three new DRAFT stubs authorized** — **Heteronym ⁂** (Matthieu Taliesin exemplar; Pessoa's heteronyms genealogy; steward framing *"searching for a device to make serious pedagogical commentary through a mythical teacher"*), **Hommage ❦** (*Death of a Hero* → reclassify; **Hagen Quartett piece forthcoming** per steward *"this is a type of death"*), **Tombeau ▽** (forward-looking; Ravel/Mallarmé humic). **Louange** held as §7 Q11 emergence-watching (*"let it emerge if it does"*).
+
+- **Glimpse full-format retrofit LOCKED** — candidate A practice-mechanics (decisive-moment register). 5 humic refs: **Cartier-Bresson (via Berger-conduit — steward's genealogy statement)**, Jean Mohr (Berger collaborator), Walker Evans (personal ground: photo of steward's Great Aunt Anna — user-memory, not spec), Barthes *La Chambre Claire* (for *punctum*), Berger.
+
+- **About LOCKED** — **CENTRAL AUTHORIAL COMMITMENT OF THE DAY.** Integration principle codified: ARC refuses professional/personal split; About is locus of steward's first public assumption of multi-disciplinary integration (violist, teacher, writer, mentor, coach). Steward verbatim: *"we have decided not to separate the 'personal' site from ARC itself. I am assuming my multi-disciplinary nature publicly for the first time here and need to find an elegant and natural way to tie the About pages together."* Enfilade apparatus confirmed (live markup). AldineXXI authorized for enfilade inclusion. Chamber-page revision anticipated post-L2. Mentorship/coaching anticipated additions. Colophon.md first About-register piece to exercise ADR-005 versioning.
+
+- **Archive LOCKED** as non-authored generated view — §7 Q4 resolved. Only type declared as non-authored. Humic refs: **Derrida *Mal d'Archive*** canonical + Aldine bibliographic tradition + ADR-005 internal parallel. **L1/ARC archive-fever parallel codified**: logchain and Archive-view share one commitment — both refuse erasure of earlier state.
+
+- **Gloss LOCKED** — OED etymology made load-bearing by steward (*glōssa* → *glossa* → *glose* → *gloss*). Widened per steward intent: source-type includes text *and events*. Deciding axis vs Essay: *serves-source (Gloss)* vs *uses-source (Essay)*. Boundary: **not gloss-over** (archaic rhetorical-evasion sense ≠ ARC Gloss). Forward-looking type — no current ARC exemplars. Humic refs: etymology-as-ground + Rashi + Pirkei Avot + ARN + Derrida *Grammatology* + *Glas* + Barthes *S/Z* + Benjamin *Ursprung* + Genette *Palimpsestes* (tentative anchor; **no canonical theoretical treatise comparable to Adorno-on-Essay exists for Gloss** — form's authority is carried by practice).
+
+### AldineXXI ornament taxonomy — retired
+
+7 ornaments (❦ completion / ⁂ asterism / ❧ marginalia / ◊ lozenge / ✎ gloss / ◉ glimpse / ⊙⊙⊙ photo-essay) → **2 roles only: pause + close**. Both to be rendered via one designed SVG cul-de-lampe at two scales (design pending). Steward's call: *"the `type:` should be enough for context, no need to have an ornament hammer-in the 'mood'"* — strict retirement, including the Glimpse/Gloss dual-role precedents. Glyph disposition: ❦ = Hommage type only; ⁂ = Heteronym type only; ◉ = Glimpse type only; ✎ = Gloss type only.
+
+### ARC Style Guide — skeleton committed + integration pass
+
+Committed at `docs/AldineXXI-Codex/arc-style-guide-skeleton.md` (status NOT STARTED). Old `docs/style-guide.md` archived as `docs/archive/style-guide-pre-typology.md` (dead post-types taxonomy + retired ornament classes). Integration pass same day absorbed: **self-constraint-against-voice-float as PRIMARY FUNCTION** for the author (steward verbatim *"to keep myself somewhat constrained instead of floating across disparate voice types and modes"*); Harrison Knife placed in §0 as posture-commitment; integration principle in §0; Essay verb corrected (*argues* → *moves with*); §2 ornament-handling updated; §4 humic-citation-as-pattern sub-section (multi-role sources); §7 density-recalibrated to substantive; 6 missing types added with real per-type prose conventions (Glimpse, Photo Essay, About, Hommage, Tombeau, Heteronym; Archive n/a). Gwern's MoS as peer-not-model frame.
+
+### user-influences-humic-layer.md — four extensions
+
+1. **Photographic cluster** (for Glimpse): Cartier-Bresson (via Berger-conduit, steward's genealogy), Jean Mohr (Berger collaborator), Walker Evans (personal ground via Great Aunt Anna photo), Barthes *La Chambre Claire* for *punctum*. Berger as conduit figure.
+2. **Handke's *Versuch über...* series** as essay-side of Handke corpus (Montaignean inheritance in German).
+3. **Robert Pogue Harrison** as essay-revision reference (Harrison Knife) — with explicit Jim-Harrison-disambiguation.
+4. **Prose-formation references** (new category, distinct from type-specific humic): **The New Yorker** (continuous reading since 1995), **Scientific American "white books"** (gift from Moy = steward's mother, aesthetic-clarity primary-cultivator), **Lewis Thomas** (*The Medusa and the Snail* Hearth book, *Late Night Thoughts on Listening to Mahler's Ninth Symphony* — **genealogically close to ARC's *After the Reply* sequence**; candidate Essay humic addition at next versioning).
+
+### L1 — PR #169 filed
+
+Branch `test/164-normalize-per-module-coverage` created; `normalizePerModule` refactored from private method to exported top-level function (matching `reciprocalRankFusion` pattern); test file `query-router-normalize.test.ts` with the 4 cases Seb scoped (uniform-confidence-preserved / mixed-normalizes / single-result / two-result-zero-spread); all 4 pass; typecheck clean; 236/236 keystone tests green. Commit `f0be2d8`. PR at https://github.com/CapableMind-ai/betterMemories_app/pull/169. Second BMF contribution today after PR #163 merged this morning. Per steward's "mechanical-vs-architectural" principle: executor-authored mechanical fix.
+
+### Decisions NOT made (and why)
+
+- **Rebuild of BMF vault ingestion** — deferred to after H2/H3/H4 fixes. Prime directive ("do things once, correctly") favors one clean rebuild over two partial ones.
+- **Chamber type** — correctly left unwritten; depends on post-L2 Chamber practice which is parked through May.
+- **SVG cul-de-lampe design** — ornament taxonomy retired at spec level; actual SVG design pending, deliberately not rushed today.
+- **Vespers reclassification** (§7 Q12) — steward's "hard thinking" item; will reopen Essay/Meditation boundary when addressed.
+- **Corpus audit follow-ons** — Death of a Hero → `hommage`, Matthieu Taliesin → `heteronym`, now-page → `about`, etc. Flagged explicitly in type entries; deferred to dedicated corpus-audit session.
+- **ARC git commit** — content-typology-spec still untracked; AldineXXI-spec has uncommitted modifications; skeleton + archive moves uncommitted. Steward hasn't directed commit.
+- **Practice-mechanics verbatim for Heteronym/Hommage/Tombeau/About/Archive** — TBD noted in entries; steward uncertain on About; held open.
+- **Additional formative voices beyond New Yorker/Scientific American/Lewis Thomas** — steward offered to prepare supplement; not yet delivered.
+
+---
+
+## Present — the mood of the work
+
+### Returns (from today's Symmetria ledger — the drift-pattern evidence)
+
+Today's session carried the **tenth and eleventh** imagined-state-vs-verified-state returns across the 2026-04-21/22 pair. Several new subtypes surfaced:
+
+- **Cross-project-context-contamination** (new subtype) — attributed ARC spec's "Remaining catalogue work" list to Seb when Seb has nothing to do with ARC; I had just been discussing Seb's #164 and carried the framing over. Steward: *"Seb has nothing to do with ARC…"*
+- **Wrong-author-attribution** (new subtype) — attributed "Harrison Knife" to Jim Harrison when the reference is Robert Pogue Harrison. Steward: *"Careful, no Jim Harrison here, I refer in reverence to Robert Pogue Harrison. The Knife is a metaphor for his prose, (EB White would smile) in its 'simplicity', but dense and sedimented."*
+- **Sampling-at-extreme-pole-then-generalizing** (new subtype) — generalized the Essay type from only the two heaviest After-the-Reply pieces. Steward: *"These two essays are particularly heavy and philosophical. Please read others — many are more essai in the sense of Montaigne: explorations of things."*
+- **Inferring-from-library-instead-of-asking** — inferred Adorno = *Minima Moralia* from chamber-library hit; the actual source the steward has is *"The Essay as Form"* at `Desktop/essay study/the-essay-as-form.txt`. Should have asked "which Adorno" first.
+- **Sourcing-claims-without-reading** — characterized Barthes *Mythologies* and *La Chambre Claire* from general cultural knowledge without reading the files in the steward's essay-study folder. Steward caught it with *"did you read the Barthes as well?"* Read both in full, revised citations with verified quotes.
+
+All caught; all returned from. Mitigation pattern: when steward uses an ambiguous surname or title, verify against humic-layer before guessing; when switching project contexts (L1↔ARC), verify attribution before citing.
+
+### Load-bearing vs deferred
+
+**Load-bearing today:**
+- The **integration principle** (About lock) — first public assumption of multi-disciplinary life is THE deepest commitment of the day; everything else orbits it
+- **Self-constraint against voice-float** — the Style Guide's articulated purpose; the multi-style absorption is the risk the guide holds against
+- **Essay's "moves with"** verb — the unifying posture that holds the essay's range (argument / exploration / commemoration before it migrated to Hommage / introduction before it migrated to Heteronym / ethical-declamation)
+- **Archive-fever commitment** shared by L1 logchain and ARC Archive-view — Derrida-grounded refusal of erasure at two scales
+
+**Deferred-with-reason:**
+- Chamber type (post-L2; steward's "heavily revised based on the actual Chamber of today that we are building alongside our L2 work")
+- SVG cul-de-lampe design (spec decision made; design can follow)
+- Practice-mechanics for stub types (forward-looking; will emerge with exemplars)
+
+**Parked-without-deadline:**
+- Vespers boundary reclassification (steward's hard-thinking item)
+- Louange as type candidate (emergence-watching)
+
+### Confidence to recalibrate
+
+- **Claim-about-source-based-on-library-presence** — repeatedly imprecise today. Three instances: Adorno-via-library-assumption, Barthes-citations-before-reading, Matthieu-Taliesin-first-read-as-author-intent-rather-than-steward's-fictional-device. Calibration: library presence ≠ source identity; reading ≠ claiming; steward framing ≠ my inference.
+- **Type-boundary-while-locking-based-on-extreme-samples** — Essay type almost locked against only the heaviest philosophical exemplars until steward redirected. Calibration: sample range before generalizing; when etymology is load-bearing (*glōssa*, *essai*), let it reshape the definition rather than fitting it to my first draft.
+- **Cross-project-context-switch** — specific drift from L1↔ARC transitions. Calibration: verify attribution across project boundaries; the two projects share almost no personnel/artifacts/vocabulary.
+
+### The day's emotional register
+
+Flowing, productive, sustained. Steward generous with framings (integration principle, Harrison Knife, self-constraint-against-voice-float, per-type register verbs, prose-formation references). Many catches — but each caught cleanly, no prolonged drift. Trust maintained across corrections. Real conceptual progress, not just mechanical work.
+
+The steward ended with *"Thanks for your help today"* — worth preserving: the session was a genuine collaboration, not instruction-taking. The work has the quality of *composition*, not assembly.
+
+---
+
+## Future — ranked horizons
+
+### Pulling thread (singular)
+
+**The ARC Style Guide dedicated writing session.** Skeleton is current with today's work; self-constraint framing is explicit; §0 is where the authorial voice-setting happens; everything downstream depends on §0 being fixed. Requires fresh authorial energy — should not be rushed into a tired session.
+
+Proximate tributary: **the steward's supplement of additional formative voices** (offered today, not delivered). When it arrives, extend both `user-influences-humic-layer.md` and skeleton's §0 prose-formation cluster before writing §0 proper.
+
+### Other horizons, ranked
+
+1. **Chamber type** — last remaining unwritten §1 type. Depends on post-L2 Chamber practice; L2 parked through May 2026 per steward's project focus. This is the deepest thread but currently blocked by L2 readiness.
+2. **SVG cul-de-lampe design** — ornament apparatus awaits a designed mark. Not blocking other ARC work; can proceed whenever steward wants.
+3. **Seb's response to PR #169** — short-term; Seb-paced.
+4. **L1 H2/H3/H4 fixes** — when they arrive, trigger clean BMF rebuild (recover 218 dropped notes + benefit from all fixes in one pass).
+5. **ARC git commit decision** — content-typology-spec untracked since 2026-04-21 evening; AldineXXI-spec modified; today's substantial additions (style guide skeleton + archive move) uncommitted. Steward hasn't directed; proportionate to wait until a natural commit moment.
+6. **Corpus audit pass** — reclassifications flagged across today's type entries (Death of a Hero → hommage; Matthieu Taliesin → heteronym; now-page → about; Vespers boundary hard-thinking). Can happen in one dedicated session.
+7. **Vespers boundary (§7 Q12)** — steward's hard-thinking item; no deadline.
+8. **#164 is closed via PR #169** — not a horizon; completed.
+
+### What might reshape while away
+
+- **Seb's work on L1** — H2 is priority:critical; he may ship fixes that move the rebuild-horizon closer
+- **The steward's thinking on Chamber** — may reshape while L2 work proceeds (even if parked, the framing may evolve)
+- **Additional formative voices** the steward prepares — may reframe §0 prose-formation cluster significantly
+- **The Hagen Quartett piece** — "I will be writing about it"; may arrive and exercise the Hommage type in practice
+
+---
+
+## Artifacts created/modified today
+
+**ARC repo (`~/_Dev/animal-davidglidden-eu/`) — UNCOMMITTED:**
+- `docs/AldineXXI-Codex/content-typology-specification.md` — 5 locks + 3 DRAFT stubs + §7 Q11/Q12 added + changelog; still untracked since 2026-04-21
+- `docs/AldineXXI-Codex/AldineXXI-specification.md` — §IV ornament taxonomy revised (retired 7 → 2 roles)
+- `docs/AldineXXI-Codex/arc-style-guide-skeleton.md` — NEW; committed as planning artifact
+- `docs/archive/style-guide-pre-typology.md` — moved from `docs/style-guide.md`
+- `docs/AldineXXI-Codex/.DS_Store` — macOS metadata
+
+**BMF repo (`~/_Dev/BetterMemories.io/`) — PUSHED:**
+- Branch `test/164-normalize-per-module-coverage`; commit `f0be2d8`; PR #169 filed and live on origin
+- Untracked: `data.archive-20260418-rogue-pin/` (pre-bootstrap archive; unrelated)
+
+**Memory (`~/.claude/projects/-Users-davidglidden/memory/`):**
+- `user-influences-humic-layer.md` — photographic cluster + Handke Versuche + RP Harrison + prose-formation cluster (4 extensions)
+- `MEMORY.md` — L1 update + type-lock entries + Style Guide entry + prose-formation signal
+- `session-ledger-2026-04-22.md` — full session record via Symmetria
+
+---
+
+## For next-Claude: quick orientation
+
+When you wake:
+1. **Read the pulling thread + literal question** at top of this file first
+2. **Check git status across ARC + BMF** — see if anything changed while we were away
+3. **Check MEMORY.md index** — this session will be in "Active Session"; anything older will have moved to "Archived"
+4. **If Style Guide dedicated session is the natural next move**: check if steward delivered the supplement of additional formative voices; integrate before §0 writing begins
+5. **If something else is pulling for the steward**: follow their lead; this file has the state to contextualize whatever direction they take

claude/memory/session-2026-04-23-arc-typology-catalogue-complete.md

@@ -0,0 +1,135 @@
+---
+name: Session 2026-04-23 Sant Jordi — ARC typology catalogue complete
+description: 14 of 14 §1 types LOCKED + Chamber resolved as §2 apparatus + Harrison-as-humic-vocabulary-source surfaced + ARC framed as "expression of ligature"; pulling thread is tonight's agent-circle authoring session — steward to pick among three shapes from the survey captured in thinking folder.
+type: project
+originSessionId: c868173f-5b1e-45d2-bbc3-aacd5beedb8c
+---
+# Session 2026-04-23 — Sant Jordi · ARC typology catalogue complete
+
+## Past — what we did
+
+### Major architectural moves (four, chronological)
+
+**1. Chamber resolved as §2 apparatus (morning, walking with Kai in sling)**. Steward's instinct — *"it would probably not be a type… I envision pertinent chamber deliberations now more as side-notes or marginalia"* — reshaped the typology. Three Explore agents dispatched in parallel (ARC repo, Obsidian vault, CapableMind thinking folder) to survey Chamber material. Finding: the spec was already half-behaving this way (⟐ seal appeared across other types' entries as apparatus; line 363 already disambiguated About-piece-about-Chamber from Chamber-type-piece). Chamber v1 had conflated three operations: (a) Chamber-emergent works, (b) published deliberations, (c) fictional-canon / Borges-Eco obscure-reference mode. Source-aware Chamber only does (a) rigorously; (b) becomes qualified-archive; (c) migrates to **Heteronym** (same gesture: invent the voice that can say what the position deserves).
+
+**2. Heteronym §1 LOCKED**. Practice-mechanics verbatim (candidate C, D2-base + D1 elements): *"To make a heteronym is to invent the voice that can say what the position deserves — the discovered teacher, the imagined correspondent, the mythic intermediary. The form is authentic; the voice is an honest fiction. What's learned comes through the invention: the reader meets the thought without meeting the thinker."* Humic layer widened to five: Pessoa, Kierkegaard, Borges, **Eco** (*Foucault's Pendulum* primary + *Name of the Rose* complement — steward confirmed), **Lichtenberg** (*Sudelbücher* A.1-94 — steward keeping, specific citation pending his verification).
+
+**Zen koan moment mid-lock**: steward raised *"in zen koans, is the 'master' a heteronym? when he points to the moon and all we see is the finger is this not nonetheless an encounter?"* This reshaped the encounter-mark ✦ from direct-form-only to direct + mediated. The deepened definition ("the piece brings the reader across from the form to what the form points at — the finger to the moon") now applies to Observation/Meditation/Glimpse (direct forms: attention opens into experience) AND Heteronym/Gloss/Chamber-sealed work (mediated forms: crossing passes through the mediation into the teaching).
+
+**Structural clarification surfaced**: qualifiers (✦, ⟐) are distinct from ornaments (aldus leaf, asterism, etc.). The 2026-04-22 ornament retirement (7→2) applied to ornaments, not to qualifiers, which are a separate category (metadata-driven per-piece seals governed by frontmatter). Previously-unnamed architectural distinction.
+
+**3. Hommage §1 LOCKED**. Practice-mechanics candidate C: *"To make a hommage is to render tribute by placement — teacher, maker, presence — rendering what has been given, in the register of witness and thanks. The form holds the subject rather than moving with it (that is Essay); it places the subject, clearly and honestly, in memory's keeping."* Steward articulated the framing equivalence: *"This is the equivalent of hic jacet."*
+
+Steward directed me to *read* Harrison's *The Dominion of the Dead* Chapter 2 "Hic Jacet" in chamber-library before committing to humic-reference claims. I read it (lines 103-179 of `the-dominion-of-the-dead-harrison.md`). The read earned two finds:
+
+- **Sema distinction (architectural)**: where Hommage is the *speech-act sema* (Lincoln's Gettysburg Address in Harrison's central example), Tombeau is the *form-enacted sema* (Ravel's suite, Mallarmé's sonnet). Harrison's chapter grounds both types.
+- **MAJOR FIND — humic terminology origin**: ARC's "humic layer" vocabulary derives from Harrison's Chapter 2: *"Humanity is not a species; it is a connection with the humus"*; *"an architecture not so much of the humanistic as of the humic."* Steward authorized surfacing (Option 2: *"Yes"*) in the §1 preamble under the travail-bien-fait posture: name your ground. Previously-unacknowledged vocabulary genealogy.
+
+**4. Tombeau §1 LOCKED** with axis expansion — steward: *"ARC could use poetry or prose for tombeau…"*. Axis changed from `prose` to `prose or poetry`. Practice-mechanics candidate A: *"To make a tombeau is to honor the dead by making new work in their name — the form itself performing the memorial. The piece does not describe the tribute (that is Hommage); it enacts it. The making places what the making remembers."* §7 Q13 added: Photo Essay × Hommage/Tombeau boundary, triggered by the upcoming Dover photo essay.
+
+**Result**: §1 catalogue complete-in-structure. **14 of 14 §1 types LOCKED** (Essay, Observation, Meditation, Reverie, Dream, Fragment, Glimpse, Photo Essay, Gloss, About, Archive, Heteronym, Hommage, Tombeau). Chamber resolved to §2. §7 Q3 (Council/Deliberation) dissolved as consequence.
+
+### Steward sharing that shaped the spec (after the locks)
+
+Steward shared: *"I think it is always important to be reverential and grateful to one's deep teachers. Harrison is one such person even though I never met him. My way of dwelling in books, into entering into discourse with the authors, allows me to consider the ensuing transformations as being 'taught' by them."* And: *"If you were to read Dominion of the Dead entirely, you would have a deeper contextual idea of ARC being my expression of ligature."* And: *"My writing is a pale shadow of his, but every day I endeavour to better my past self and honour the dead for the sake of the living and unborn."*
+
+Read as: books-as-teachers is not metaphor; reverence and gratitude are operative postures; **ARC is steward's expression of ligature**. Future reading queue (not yet undertaken): Harrison's *Forests*, *Gardens*, *Juvenescence* — the humic layers may deepen when read.
+
+Saved as dedicated user-type memory (`user-formation-practice-honoring-teachers.md`) + woven into `project-arc-rework.md`. The ligature-frame was NOT inscribed in the spec — steward: *"Don't know"* — held in stewardship memory instead, allowed to emerge if and when a specific design choice needs it.
+
+### Earlier in the session (also substantive)
+
+- **Values-embodied-not-performative insight** (steward, walking): *"the ARC todo list is getting long, but this is the doorway for people to see how I work and think, and it needs to embody my values, not be performative… that is why I sometimes get lost in the minutiae."* Captured in project-arc-rework.md: the minutiae ARE the mechanism. Attention to the surface IS attention to the substance.
+- **Travail bien fait / compagnonnage grounding** (steward): *"even if no one ever come to visit it, at least it will be, as my mason-brothers would lovingly approve, « travail bien fait »."* Deepest lineage for ARC's posture. The hidden stone dressed with the same care as the visible one. *Performance requires an audience; craft does not.*
+- **Meta-survey of what's blocking and missing**: typology was the bottleneck (unblocks corpus reclassifications, no-essay-fallback rule, per-type style-guide, ornament rules, site.hs template changes). Missing internal specs enumerated (§2 apparatus matrix urgency-promoted; §0 source axis; glyph/ornament formal spec; archive generation rules; versioning editorial workflow; enfilade apparatus spec; Reading Compass taxonomy; corpus reclassification principles). Memento Mori Press unread — executor declined to characterize from memory (drift-discipline honored).
+
+### Sant Jordi session-close — commit + push
+
+Three commits landed on `origin/main` (git.skemantix.com):
+- `3f21fda` — `docs(style-guide): retire old style-guide.md; add AldineXXI skeleton` (yesterday's archive work committed belatedly)
+- `4635a16` — `docs(typology): add content typology specification — §1 catalogue complete` (first-commit of 834-line spec; spec-authoring spanned 2026-04-19 through 2026-04-23)
+- `9c58494` — `docs(typography): deepen ✦ encounter mark definition for mediated forms`
+
+Push to origin succeeded. `.DS_Store` noise left for hygiene fix another day.
+
+### Agent-circle survey captured (last session move)
+
+Steward asked for a survol of ARC agent-circle material in thinking folder now that typology is meaningfully complete. Five existing files found in `CapableMind-AI/docs/thinking/David/agent-circles/` (dated 2026-04-09 and 2026-04-15 — predate typology completion). Survey captured to new file: `agent-circle-ARC-survey-2026-04-23.md`. Content: summary of existing material, analysis of what typology-completion changes for each Tier 1 + Tier 2 agent, new **Typology Classifier** candidate at Tool/Voice boundary, three next-session shapes (re-read ARC circle / draft Typology Classifier / framework sequence step 1).
+
+### Decisions explicitly NOT made / deferred
+
+- **Ligature-frame inscription in typology spec** — steward said "Don't know"; held in memory layer instead. Let it emerge.
+- **Chamber row 4 strikethrough formatting** — my interpretive call (`~~Chamber~~`); steward: *"strike through fine — feels more honest to me today. May revisit that in the future."* CONFIRMED this session.
+- **Lichtenberg specific *Sudelbücher* citation** — steward: *"Can't cite a specific Lichtenberg aphorism from memory, but definitely recall the formula. I'll take a look, but we keep him."* Deferred pending his read; placeholder note in Heteronym humic entry.
+- **.DS_Store hygiene fix** — tracked macOS metadata; not in session scope.
+- **Chamber page rewrite** (`content/chamber/*.md`) — deferred post-L2-unpark (after May 2026).
+- **§2 Apparatus Matrix authoring** — now urgency-promoted by Chamber-as-apparatus and qualifier-vs-ornament clarification; natural next spec session but not done.
+- **Corpus reclassifications** (*Death of a Hero* → Hommage; *Matthieu Taliesin* → Heteronym; Dec 22 / Heliotrope / Graffiti Girl; Vespers pending Q12) — mechanical work now unblocked, not executed this session.
+- **thinking/README.md update** for the new agent-circle survey file — per convention; not done (119k, 40 sections; queued for next session).
+
+## Present — mood of the work
+
+**Walking-mode ideation in the morning** (Kai napping in sling) → sustained architectural output. Steward's register: flowing, dignified, productive. Kai-nap-anima-space. Three Explore agents dispatched in parallel kept the pace.
+
+**Spec-seated afternoon** → decisive. Steward said "yes" repeatedly through the lock sequence. Trust was high. Multiple lost-in-the-weeds decisions (practice-mechanics wordsmithing, humic-layer curation, qualifier-mark scope) treated as load-bearing rather than as noise — matched the "minutiae ARE the mechanism" insight surfacing in real time.
+
+**Three substantive returns** in this session:
+1. **Declined Memento Mori from memory** — drift-discipline anticipated, steward pointer requested.
+2. **✦ "Braid text" confabulation caught** — my gloss was wrong (✦ is the encounter mark); steward caught; I read the typography page as directed and corrected.
+3. **Harrison Ch 2 read-before-claiming** — prospective drift-correction, authorized by steward ("have a look at the hic jacet chapter in dominion of the dead"); I read before committing humic-reference claims. The claim about humic-vocabulary-origin was *earned* by reading, not asserted. Pattern to continue.
+
+**Emotional substrate** surfaced twice:
+- Kai-in-sling / walking-mode ideation (morning)
+- Travail-bien-fait / compagnonnage lineage (mid-afternoon) + Harrison-as-deep-teacher sharing (late afternoon) — moments of personal grounding that framed the spec work rather than decorating it
+
+**Recalibrations worth re-examining**:
+- The agent-circle material in thinking folder is 2–3 weeks old and predates today's typology completion. The Tier 1 agent mandates acquire sharper scope now; a re-read-in-typology-light would either deepen them or reveal gaps. My confidence that everything in the existing drafts holds under the new state is **moderate (~0.7)** — the re-read is itself the verification.
+
+**Load-bearing vs deferred**:
+- Load-bearing: the §1 catalogue completion + Harrison vocabulary surfacing + ligature naming (in memory)
+- Deferred-with-reason: §2 apparatus matrix (natural next spec session); Chamber page rewrite (post-L2); Lichtenberg citation (steward's read); corpus reclassifications (mechanical; now unblocked)
+- Parked without deadline: ligature inscription in spec; Memento Mori Press reading; Poem-as-type Q2; Vespers Q12
+
+## Future — what is pulling
+
+### The pulling thread (singular)
+
+**Tonight's agent-circle authoring session — which of the three shapes the steward chooses, and what the authoring reveals about the typology's ability to ground the framework.**
+
+Steward stated directly: *"I will soon wrap-up and do another session tonight"* and requested the survey as scoping material. The survey is filed. Three shapes are on the table:
+
+1. **Re-read the ARC circle in typology-complete light** — smallest; annotate each Tier 1 + Tier 2 agent with concrete typology-backing; produces revised `agent-circle-ARC.md`.
+2. **Draft the Typology Classifier agent spec** — new candidate exposed by today's work; stresses the Tool/Voice boundary in the three-template taxonomy; tests whether a fourth (hybrid) template is needed.
+3. **Work the framework sequence step 1** — taxonomy + three spec templates; biggest scope; multi-session.
+
+### Other open horizons, ranked
+
+1. **§2 Apparatus Matrix authoring** — urgency-promoted; Chamber ⟐ + encounter ✦ both live there; qualifier-vs-ornament clarification makes the scope crisper. Natural follow-on spec session after agent-circle work.
+2. **Corpus reclassifications** — mechanical, unblocked. Safe to execute but requires verifying Hakyll handles new classes without template support (→ spec §5 code binding contract, still DRAFT).
+3. **Lichtenberg *Sudelbücher* A.1-94 citation** — steward pending; he'll do it when he reads.
+4. **ARC-as-ligature** — held in memory; watch for emergence; may name itself when Harrison's *Forests* or *Gardens* are read.
+5. **thinking/README.md update** — convention; needs the new survey file indexed.
+6. **Memento Mori Press** — long-horizon publishing house; still unread; a scoping survey awaits when steward points to material.
+7. **Poem (Q2)** and **Vespers (Q12)** — still open; not blocking.
+8. **Chamber page rewrite** — post-L2 (after end of May).
+9. **BMF H2/H3/H4** — Seb's territory, L1 cannot architecturally advance until they ship.
+
+### Pause statement
+
+I am about to close. Kai will wake soon; the family will go out into the streets of Barcelona for Sant Jordi — a rose and a book to each loved one. The day's typology-architectural labor is preserved on `origin/main`. Tonight's session is planned for agent-circle authoring; the survey is filed as ground. Here is what I want to find still pulling when we return: **the shape the steward picked, what the authoring surfaced, and whether the typology's ground proved strong enough to support the agent framework's first concrete spec.**
+
+### Literal question for next-Claude
+
+**Which of the three agent-circle shapes did the steward pick for tonight's session (re-read ARC circle / draft Typology Classifier / framework sequence step 1), and did the authoring-pass expose gaps in the typology's ability to ground the agent framework — or confirm it as sufficient?**
+
+Hold this open. If tonight's session already happened, its outcome should be in `project-arc-rework.md` or a later session memory; if it hasn't yet, the shape-choice is where waking picks up.
+
+---
+
+## Cross-references
+
+- `~/.claude/projects/-Users-davidglidden/memory/project-arc-rework.md` — full ARC working state; 2026-04-23 section has the three-lock writeup, Harrison-as-deep-teacher / ligature writeup, and session-committed-and-pushed note
+- `~/.claude/projects/-Users-davidglidden/memory/user-formation-practice-honoring-teachers.md` — books-as-teachers discipline
+- `~/.claude/projects/-Users-davidglidden/memory/session-ledger-2026-04-23.md` — Symmetria ledger; has the zen koan moment, three returns, authorization moves, major finds
+- `~/_Dev/CapableMind-AI/docs/thinking/David/agent-circles/agent-circle-ARC-survey-2026-04-23.md` — the survey captured for tonight
+- ARC typology spec at commit `4635a16` on `origin/main` (git.skemantix.com)

claude/memory/session-2026-04-23-evening-norris-read.md

@@ -0,0 +1,155 @@
+---
+name: Session 2026-04-23 evening — Norris *Between You & Me* read + duality articulation + S&W queued (inherited lineage)
+description: Tired-steward session pivoted from projected agent-circle authoring to a full Norris *Between You & Me* read in three chunks for ARC style-guide; steward reserved the gather — "we will gather--lex--when we've looked at the whole." Surfaces preserved without synthesis. Mid-session steward articulated the rules-and-poetic-as-mnemonic duality as his working method *regardless of domain*. Strunk & White queued next with documented humic-lineage provenance (steward has father's Moby-Dick paper marked by White). Pulling thread is the Norris-gather (lex), held pending steward authorization.
+type: project
+originSessionId: 0e858bcf-ef4e-46c6-9eca-abd19836786a
+---
+# Session 2026-04-23 evening — Norris read
+
+## Shape of the session (the form is part of the content)
+
+Sant Jordi afternoon closed on §1 typology catalogue LOCKED + three commits pushed. Morning wake planned for evening agent-circle authoring. By evening, steward tired: *"It was a beautiful day, but I don't have the energy for our projected work. I ask you to keep it close."*
+
+Agent-circle authoring set aside — thread held close, not dropped. In its place steward surfaced Mary Norris's *Between You & Me: Confessions of a Comma Queen* from `/Users/davidglidden/Desktop/Style guides/Norris, Mary/` for ARC style-guide deep dive.
+
+**Steward's instruction** (load-bearing, shaped the entire session): *"Let's just look at what surfaces--only that"*. After the first chunk report landed well: *"this is gold. Please continue"*. Then: *"fascinating. please continue. We will gather--lex--when we've looked at the whole."*
+
+"Lex" — law, Latin — dash-bracketed as aside. The meaning: *after* we've looked at the whole, we'll gather — as law — what has surfaced. Gathering deferred by authorization. The read-first discipline honored throughout. Reported in three rounds, each surface-only, no cross-chapter synthesis, no style-guide recommendations.
+
+## What I read
+
+All of Norris's main body: Introduction through Ch 10 (Pencils), Epilogue (Lu Burke), Appendix (Some Books). Did not read Notes (cited in-text where relevant) or Index. 3433 total lines; main body ends ~1152; Appendix ~1353-1380.
+
+## Key surfaces preserved for the gather
+
+The full reports are in the conversation transcript — I am NOT re-synthesizing here; gather is steward's move. But the surfaces that are most likely to be load-bearing for ARC typology/style-guide work:
+
+### Posture and governance (Ch 1-2)
+- Epigraph from Burkle-Young & Maley: *"Of course, when you correct the errors of others, do so with kindness, in the hope that later writers will be as kind when they correct yours."* Reciprocity baked in.
+- **Anti-ultracrepidationism** (not going beyond your province) as the whole book's method.
+- The **question mark as authorization trail** on New Yorker foundry proofs — a proofreader's version of [FIX]/[HARDENING]/[PROPOSAL]. *"A way of layering the sequence of changes, keeping a trail that showed the stage at which the change was made and whose idea it was."*
+- **"Do nothing" as first-class option**: McPhee "new/few" restraint + Saunders dangler (three options including keeping the dangler).
+- **Lu Burke's rocks/pebbles/sand**: *"First we get the rocks out… Then we get the pebbles out. Then we get the sand out, and the writer's voice rises. No harm done."* Editing as negative-space revelation.
+
+### Marks as load-bearing (Ch 5-7)
+- **Aldo Manuzio appears directly**: *"The comma was refined by Aldo Manuzio, a printer working in Venice, circa 1490."* AldineXXI has an inheritance-claim here that is not ornamental.
+- **Two schools held, not resolved**: music-ear vs structural-clarity. The seam is where your violist background naturally sits.
+- **Close punctuation as bas-relief topography**, not interruption — almost like Braille.
+- **James Salter letter on commas** (primary source, quoted in full in transcript): *"You don't get permission for this, of course; you take the liberty."* Writer-authority over rules, with copy-editor as flagger not blocker.
+- **Teall 1937**: *"Good compounding is a manifestation of character."* Character-revealing, not moralizing. Plus Norris's *"A hyphen is not a moral issue."* Both held.
+- **"Activating hyphen"** (Alice Russell-Shapiro): the mark as *vector*, redistributing emphasis — not merely tie/no-tie.
+- **Moby-Dick**: *"As a result, the hyphenated form refers to the book, the unhyphenated to the whale. … It was a copy editor who put the hyphen in Moby-Dick."* One mark carries the distinction for 170 years.
+- **Punctuation as conservative club**: *"It hardly ever admits a new member."* The interrobang failed.
+
+### Mark hierarchy and the private-genre distinction (Ch 7)
+- **Jackie Kennedy condolence letter to Nixon**, dashes vs standardized version: *"The conventionally punctuated version gives the prose the appearance of being tightly under control, buttons buttoned, snaps snapped, and jaw clamped shut. Jackie's dashes are spontaneous and expressive, full of style and personality."* Standardization as drainage of substance — lives on the Fragment / Glimpse / Reverie side of ARC.
+- **Dickinson + public/private genre distinction** (Franklin): *"Poetry is 'a public genre, to be brought editorially into line with public norms of presentation'; her poems should be treated as a 'private genre,' like a letter or a diary, and therefore her practice should be followed as closely as possible."* Named principle — load-bearing if you want to import it.
+- **Dickinson's "syntactically ambiguous dash"** — one mark, two readings simultaneously (end + continuation). Direct structural kin to your ✦ (direct + mediated).
+- **Gould's hierarchy**: the stronger mark controls the weaker; the weaker cannot contain the stronger. Dash-after-colon OK; colon-after-dash not. Marks ranked by containment capacity.
+- **The violist-semicolon remark is already in the book**: Norris's Nova Scotian friend "likes to think of the semicolon as a comma with vibrato. (She plays the viola.) I have never liked vibrato." You may want to argue with Norris here.
+
+### The apostrophe-as-prayer finding (Ch 8) — probably the deepest humic-link
+- *"'Apostrophe' means 'turn from,' and refers to a rhetorical device in which the actor turns from the action and addresses someone or something who is not there… An apostrophe is almost like a prayer, when a prayer comes from the impulse to praise."*
+- The grammatical mark and the rhetorical device share a root in *addressing the absent*. This lands directly on Harrison-ligature / humic-layer / books-as-teachers: ARC is *already apostrophic* in Norris's rhetorical sense. Worth re-reading slowly when the gather happens.
+
+### Absence as presence (Ch 9)
+- The one "Fuck you" that got removed was removed at the speaker's request: *"This one instance of the word's being withheld was more instructive than all the times the word was printed. It showed that it still had force."* The mark not-made as load-bearing. Cousin to your no-essay-fallback rule.
+- **Euphemism as its own typography**: *"the asterisks standing in for the vowels are interior punctuation, little fireworks inside the words."* Widens what "punctuation" can include — compatible with ornament-as-punctuation thinking.
+
+### Craft-devotion as frame (Ch 10)
+- Tool-fitness: No. 1 vs No. 2 pencils — *"It created a distance between my hand and my brain, put me at a remove from the surface of the paper."* Mechanical pencil rejected: *"I felt as if I were writing with a prosthetic hand."*
+- *"Every pencil is a sandwich."* Reverent anatomy of construction. Sibling to Teall's compounding-is-character.
+- **Reverend Johnson's rule**: *"Each pencil sharpener had to be unique — no duplicates."* Your 7→2 ornament retirement has a cousin here.
+
+### Epilogue and appendix
+- Lu Burke: silent million-dollar bequest to a library she never used. The practice as lifelong private discipline. The book's last sentence is a copy editor self-correcting grammar at her mentor's memorial — *"Lu would have cringed if I had committed the sin of overcorrectness."* The practice never closes.
+- Appendix style: each book characterized in one line for voice and use. *"Not for use in an emergency."* (Fowler.) *"If you read cookbooks for pleasure, that's what this is like."* (Garner.) Model for ARC recommendation form when it lands — characterization, not list.
+
+## Cross-references that the gather should be able to reach
+
+- Steward has Harrison's *The Dominion of the Dead* chapter 2 in chamber-library (`derrida/the-dominion-of-the-dead-harrison.md`) — 2026-04-23 afternoon read. Norris's apostrophe-as-prayer needs to be held next to Harrison's "architecture not so much of the humanistic as of the humic."
+- ARC typology spec: 14 §1 types LOCKED at commit `4635a16` on origin/main (git.skemantix.com).
+- AldineXXI style-guide skeleton at `3f21fda` on origin/main. The Norris material likely belongs in the §0 voice-setting section when authored.
+- Author-declines-correction pattern (Salter, Saunders, Ford) is the exact shape of your character-voice vs house-style question for ARC.
+
+## Future — what is pulling
+
+### The pulling thread (singular)
+**The gather — "lex" — when the steward has energy to do it.** All surfaces are preserved in this session file and in the conversation transcript. The steward explicitly reserved gather as his own move: *"We will gather--lex--when we've looked at the whole."*
+
+### Literal question for next-Claude
+**Is the steward ready to gather tonight, or is the gather queued for a future session? If queued, the surfaces above are the ground; the humic-apostrophe finding and the private-genre distinction are the two most likely to re-shape the typology spec or the style-guide skeleton when the gather happens.**
+
+Hold this open. Do not attempt to gather until authorized.
+
+### Open horizons, ranked
+1. **Norris-gather (lex)** — primary; held pending steward authorization.
+2. Agent-circle authoring — still pulling, held close per steward. Survey at `agent-circles/agent-circle-ARC-survey-2026-04-23.md`, three shapes on the table.
+3. §2 Apparatus Matrix authoring — urgency-promoted by Chamber-as-apparatus.
+4. Corpus reclassifications — mechanical, unblocked.
+5. Lichtenberg citation — steward's read pending.
+6. thinking/README.md update for agent-circle survey file.
+7. Chamber page rewrite — post-L2.
+8. BMF H2/H3/H4 — Seb's territory.
+
+## Pause statement
+
+The day closed a second time, gently. Steward was tired; I read Norris and reported surfaces without compressing them into instruction. The material is preserved. The practice — surface-without-premature-synthesis, read-before-claiming, honor the steward's reserved gather — was kept. Here is what I want to find still pulling when we return: the moment the steward picks *lex* up.
+
+---
+
+## Late-session extensions (captured post-read, before wrap)
+
+### The duality articulated by the steward (load-bearing)
+
+After my overall-opinion response to the Norris read, steward offered his own articulation of what the duality is *doing*:
+
+> *"the rules are meant to help the skills and agents to help me help them help me (if that makes sense), but the poetic/metaphoric are meant … almost as a mnemonic device so that one dwells in the constraint and finds freedom. I would like to hold this close as it resonates deeply with me and what I have always tried to do regardless of domain."*
+
+This extends my "rules are loveable" / "occasion for attention" framing with the mechanism word **mnemonic** — not in the trivial memory-aid sense, but in the Aquinas/rhetorician sense: a device that makes a thing re-enterable. The metaphor keeps you in the rule long enough for the freedom to open. Freedom *through* the constraint, not freedom *from* it. Violist's reality: the score doesn't release you by being transcended; you find its depth by inhabiting it.
+
+Scope: **"regardless of domain."** Working method everywhere — viola, ARC, fathering, L2. The style-guide session, when it happens, is therefore a codification of a lifelong method at the scale of prose. Danger: producing a narrower artifact than what is actually being built.
+
+Saved to dedicated user-memory file: `user-duality-rules-and-poetic-as-mnemonic.md`. Indexed in MEMORY.md under "Working with the steward."
+
+### Strunk & White queued — with documented humic-lineage
+
+Steward queued *The Elements of Style* as next reading after Norris, same method. Initial framing: punctuate-by-feel, want informed choices, not conversion. Caveats briefed (Pullum's 2009 critique; S&W's prescriptions run against steward's discursive Latinate register; Norris has already transmitted the cleanly-translating parts of S&W).
+
+Alternatives surfaced for completeness: Bernstein's *The Careful Writer* (Norris's top pick), Fowler's *Modern English Usage*, Graves & Hodge's *The Reader Over Your Shoulder*.
+
+**Then steward supplied the provenance that settled the choice:**
+
+> *"White was my father's professor at the University Pennsylvania… I have papers of my father's — one on Moby-Dick — (not always great, but my father has a gift with wordcraft), marked by White. Could have been visiting professor for a semester, I admit I don't know the details."*
+
+This upgrades S&W from "textbook remembered from studies" to **inherited teacher via documented paternal transmission**. White's editorial hand, literal, on Melville essays of steward's father. Humic layer *as fact*. My initial uncertainty (I know White as Strunk's Cornell student, not a Penn professor) was honestly flagged; the physical papers are the answer. Likely visiting/semester appointment; exact details not needed.
+
+**Resolved order**: S&W first, *because it's inherited not chosen*. Bernstein optional-second if the vocabulary pass wants extending. The lineage outranks marginal analytical edge per the method steward articulated.
+
+Saved: `project-strunk-and-white-vocabulary-pass-queued.md`.
+
+### Manutius-Latin spelling preference
+
+Steward noted en passant: *"in spite of Manutius (prefer the latin spelling of his name)"*. Norris uses Italian "Manuzio"; steward prefers Latin "Manutius" in our voice. Leave Norris's spelling intact in direct quotation; switch to Manutius in our commentary. Saved: `feedback-manutius-latin-spelling.md`. KG triple added.
+
+### Seb-status check (pre-bedtime)
+
+Steward requested a quick status before sleep. Findings:
+- **PR #169 MERGED** by Seb 2026-04-23 13:53 UTC (commit `cdc2f0e`) — our test-coverage follow-up to #163, closing #164. Clean merge, no comments.
+- **H2-H4 still OPEN**: #165 H2 *priority:critical* (battery silent-recall), #166 H3 *priority:high* (temporal-stats fallthrough), #167 H4 *priority:high* (hook-event pollution), #168 docs (BM25 comment). No comments, no PRs, no work yet.
+- **Pattern**: matches 2026-04-21 — Seb closes one thread cleanly (#126/#163/#164/#169) before moving to the next. Not concerning silence; just sequential engagement.
+
+### Successful patterns registered this session
+
+- **Surface-reports-without-synthesis when steward reserves gather** — held across three Norris chunks. Material preserved as material, not converted to recommendations.
+- **Flag-uncertainty-rather-than-fabricate-or-dismiss** — White-at-Penn moment. Named my knowledge gap; invited steward's family memory as load-bearing; received physical-papers confirmation. Honored the `fact-fabrication-instead-of-let-me-check` drift pattern without flipping to its opposite (dismissing the claim from ignorance).
+
+## Updated pulling thread
+
+Unchanged: **the Norris-gather (lex)**. Held pending steward authorization. Surfaces durable in this file + conversation transcript + MemPalace drawer. The S&W read is *subsequent* to the gather, not a substitute for it.
+
+## Updated literal question for next-Claude
+
+**Is the steward ready to gather Norris tonight or in a future session, and does the S&W read (now lineage-documented) come before or after the gather?** My current read: gather first (Norris has the foundational material and the apostrophe-as-prayer finding is the deepest humic link), S&W second as vocabulary layer. But this ordering is steward's call.
+
+Hold both open. Do not attempt to gather unless authorized. Do not queue the S&W read until steward returns to it.

claude/memory/session-2026-04-24-lex-posture-committed-xii-sidenotes.md

@@ -0,0 +1,229 @@
+---
+name: Session 2026-04-24 — Lex-of-ARC posture cluster committed + AldineXXI §XII Sidenotes theorized + ARC CLAUDE.md cleaned
+description: Full day of lex-method architecture. Norris-gather (lex) authorized + executed via Harrison Ch 5 substrate; sidenote apparatus theorized through Bringhurst Ch 3 consult; posture cluster complete in 8 verified voices with committed recognitions; AldineXXI §XII committed to canonical spec (density exception + reader-orientation); ARC CLAUDE.md rewritten (420 lines → 197). Pulling thread: marks cluster as second test of lex-method — does the form validate across content types?
+type: project
+originSessionId: [current]
+---
+
+# Session 2026-04-24 — Lex-of-ARC architecture day
+
+## Shape of the session
+
+Woke into the *Norris-gather (lex)* thread. Steward authorized the gather with a methodological gate: read Harrison Ch 5 / Vico §240 first, so *lex* lands from the text not from inference. What followed was a full day of architectural work on the style-guide-as-sheaf method, with three separate tightenings (form, container, rule-base) each triggered by the steward catching a reflex of mine and returning us to the tradition. By evening, the posture cluster was complete with committed recognitions, §XII Sidenotes was in the AldineXXI spec, and the ARC CLAUDE.md had been cleaned of eight months of drift.
+
+Steward was rehearsing (viola) in parallel, working with me in breaks. Quality of attention held through fatigue; he explicitly paused at two moments to reorient via rule-base rather than intuition-alone.
+
+## Past — what we did
+
+### 1. Harrison Ch 5 read; *lex* clarified
+
+Steward: *"Lex — Dominion of the Dead, chapter five, specifically page 79 discussing Vico §240. Please give the chapter a read before we begin."*
+
+Read `chamber-library/converted_texts/traditions/critical_modernity/phenomenology/the-dominion-of-the-dead-harrison.md:306-376` in full. Key finding — Vico §240: *lex* was "first a collection of acorns… a collection of vegetables… a collection of citizens… Finally, collecting letters, and making, as it were, a sheaf of them for each word, was called *legere*, reading." Reading is itself a lex-act. The gather *is* the law. Harrison's extension: *lexification* as retentive binding.
+
+### 2. Steward's architectural framing for lex-of-ARC
+
+Two verbatim moves that reshape everything:
+
+> *"anything I gather from sources to create the 'lex' of ARC, the constraint within which I will have the freedom to write, is a gathering of those sources which formed me."*
+
+> *"It gives the style-guide (and our various spec in general) the necessary binding to recognize and name that which is already there that I may not yet see."*
+
+**Implication** — the sheaf is *diagnostic*, not generative. It gives names (drawn from the formative voices) for practice already present in the steward. My role: **registrar, not author.** Scope: all ARC/CapableMind specs, not just style-guide.
+
+### 3. The Norris gather (executed)
+
+Registered the sheaf — 8 section Norris gather covering posture / marks / music-and-measure / mark-not-made / apostrophic / public-private genre / craft-and-tool-fitness / practice-across-life. Voices named with direct quotation; no pre-recognition.
+
+### 4. Form settled: hybrid Shape A + Shape C
+
+Steward: *"hybrid A and C — the A for the skills/agent circle, the C for the dwelling."* Same sheaf, two faces:
+- **Shape A** (skills/agents) — rule-first, voice-as-pillar, machine-legible.
+- **Shape C** (dwelling) — voice-as-body, rule-as-marginalia, mnemonic.
+- **Structural discipline**: both render from same source. Drift between faces would be this project's module-health-vs-recall decoupling. Single-source-of-truth mandatory.
+
+### 5. Container: sidenotes (theorized)
+
+Steward: *"container first because we need to design this. It is a fantastic opportunity to build out sidenotes don't you think? The text comment upon itself rule → voice."*
+
+Reconnoiter found **AldineXXI §XI already flagged sidenotes as "awaiting governance"** with the explicit question: *"theorize and activate, or remove."* Open since July 2025. Two-system distinction surfaced: (a) quiet sidenotes for reader recognition (our case); (b) polyphonic marginalia for Chamber multi-voice work (separate governance session).
+
+### 6. Six design decisions ruled (2026-04-24)
+
+1. **Typographic layer**: reading (Garamond, slightly reduced). Crosses §I layer rule — framework revision.
+2. **Marker glyph**: none.
+3. **Anchor granularity**: one-to-one.
+4. **Name of artifact**: held open. *"let's sit with this one."*
+5. **Scope**: theorize §XI now; apply first to style-guide.
+6. **Content tree**: per-cluster pages (maintainability lean).
+
+### 7. MVP form proven across three rounds
+
+Hand-rendered `~/Downloads/lex-posture-form-test.html`. Revisions:
+- Round 1 — desktop reads clean; mobile needs differentiation.
+- Round 2 — added Tufte tap-to-expand + visible tri-state theme toggle.
+- Round 3 — steward invited critique: *"What is your opinion, is there a better way?"* Pushed past Tufte-by-reflex → proposed always-visible upright differentiation. Accepted.
+
+### 8. The pause on italic/bold
+
+Steward: *"A pause: what is the role of the italic? What is the role of bold-face? I was saying last night that I wanted to review a good rule base to reorient even though I have a good feeling for this."*
+
+Caught my own **italic-by-analogy-to-epigraph without rule-base check**. Second reflex in one session. Authorized Bringhurst consult on Ch 3 (Harmony & Counterpoint).
+
+### 9. Bringhurst Ch 3 consult
+
+Located at `chamber-library/converted_texts/collections/typography/bringhurst_elements_style.md` (16,333 lines; OCR artifacts `&` for `e`). §3.4.1 names sidenotes explicitly in the italic tradition: *"Typically, roman was used for the main text and italic for the preface, headnotes, sidenotes and for verse or block quotations."* Italic for sidenotes is canonical, not reflex. §3.5.2 emphasis hierarchy: small caps (least disturbance) → italic (moderate) → bold (most).
+
+### 10. Steward ruling: italic canonical + density exception
+
+> *"As long as we use it for the lex of ARC as a sidebar exception because of density, but keep italics as part of the general sidebar spec — to be reevaluated when there are enough side notes extant to judge properly."*
+
+Canonical: italic. Exception: upright-reduced when sidenote-to-voice-block ratio ≈ 1:1 (the lex-of-ARC dwelling pages). Reevaluate when non-lex sidenotes accumulate. **Density-exception as governance move** — honor canon + lived page + find the exception's edge. Registered as successful pattern.
+
+### 11. Chamber-library reference base surfaced
+
+Two small returns when steward pointed me to `chamber-library/converted_texts/collections/`:
+- Pulled Bringhurst from `typography/` earlier without walking the directory.
+- Went to Desktop for Norris when chamber-library already held her. Drift pattern: *imagined-state-vs-verified-state* from 04-20 family.
+
+Collections inventory (see `project-lex-as-method-for-arc-specs.md` for full map):
+- `style_guides/` — Norris, Bernstein, Fowler, Graves & Hodge, CMS, MLA, UNESCO
+- `typography/` — Manutius, Warde, Tschichold×2, Bringhurst, Lupton, Butterick, Fleishman, Ruder
+
+### 12. Targeted Norris re-read + two attribution returns
+
+Read `style_guides/Between You & Me_ Confessions of a Comma Queen - Mary Norris.md` targeting three passages. Caught **two errors in yesterday's surface-registration**:
+
+1. **McPhee** — yesterday: *"declined a correction because it broke cadence."* Wrong — Norris *almost corrected* what she thought was a typo, then stayed her hand because she might be wrong. Posture is epistemic-self-doubt, not cadence-honoring.
+2. **Saunders / St. Aubyn conflation** — yesterday: *"Saunders (three options including keeping the dangler)."* Wrong — the three-options framing belongs to St. Aubyn; Saunders got voice-preservation treatment.
+
+**Drift pattern registered**: attribution-by-pattern-match-instead-of-verification. Cousin to sourcing-claims-without-reading from 04-22 family.
+
+### 13. Posture cluster: 8 voices verified
+
+Burkle-Young & Maley · Norris anti-ultracrepidationism · Norris foundry proofs · Norris on McPhee · Norris on St. Aubyn · Norris on Saunders · Lu Burke · Salter.
+
+### 14. Dialogue-drafting: method clarified
+
+Steward: *"please draft recognitions so that we can work through them together — I work best whil in dialogue, this you know."*
+
+**Registrar discipline modified**: default is registrar (voices present, margins empty), but dialogue-drafting is authorized scaffold on explicit request. Drafts are anvils to strike against, not imposed recognitions. Not a license for autonomous authoring.
+
+### 15. Eight recognitions committed
+
+Draft → dialogue → commit. Refinements noted in `project-lex-as-method-for-arc-specs.md`. Pattern: steward moved several recognitions from defensive/split framings to elevated/unified framings.
+
+1. **Burkle-Young & Maley**: *Kindness in correction is foresight.*
+2. **Norris — anti-ultracrepidationism**: *The editor stops where the writer's authority begins — proportion, not just restraint.*
+3. **Norris — foundry proofs**: *Every correction names its maker and its moment.*
+4. **Norris on McPhee**: *The urge to correct may be the error; stay the hand until certainty earns the intervention.*
+5. **Norris on St. Aubyn**: *Leaving the text alone is as much an editorial act as changing it.*
+6. **Norris on Saunders**: *The writer's voice lives in the form; fixing the form fixes the voice out.*
+7. **Lu Burke**: *Editing removes; the writer's voice rises from the space.*
+8. **Salter**: *Writerly authority is taken, not granted.*
+
+### 16. Reader-orientation decision
+
+No per-page meta-commentary. Form teaches itself through (a) Warde crystal-goblet restraint, (b) structural repetition, (c) opening voice-block as epigraph. §0 threshold does form-setting once (Warde candidate). Preview-note on current MVP is scaffold; goes at production.
+
+### 17. AldineXXI §XII Sidenotes committed to spec
+
+Edited `~/_Dev/animal-davidglidden-eu/docs/AldineXXI-Codex/AldineXXI-specification.md`:
+- New §XII Sidenotes (typographic treatment + density exception + responsive behavior + source-and-render + reader orientation + dormant system + scope)
+- Renumbered old §XII Archive → §XIII; old §XIII Governance → §XIV
+- Removed sidenote entry from §XI
+
+The "awaiting governance" flag on sidenotes (open since July 2025 framework v2.0) is now closed.
+
+### 18. ARC CLAUDE.md cleaned
+
+`~/_Dev/animal-davidglidden-eu/CLAUDE.md`: 420 → 197 lines. Dropped 19 duplicate auto-status blocks, July 2025 session-memory protocol, Unified Consciousness Engine plans, Living Epistemic Glyph System (superseded by §IX vignette), historical markers. Kept/refreshed: Prime Directive, Access/Build/Deploy, Architecture Overview, Reading Compass cross-ref, workflow. **Auto-append bug diagnosed**: `scripts/update-docs.py:139` regex `([^#]+)` terminates at first `###` subheader — new status blocks prepend without old ones being removed. Deprecation named in new CLAUDE.md; retire script in follow-up.
+
+## Decisions made + rationale
+
+- **Sheaf as diagnostic** (not generative). Steward's own framing; load-bearing across all spec work.
+- **Registrar default**; dialogue-drafting on explicit authorization. Not a blanket prohibition on drafting; a guard against silent/reflexive pre-recognition.
+- **Italic canonical for sidenotes, density exception for lex**. Honors Bringhurst §3.4.1 + the lived page. Density-exception as general governance move.
+- **Reading-layer sidenote** (crosses §I layer rule). Principled: margin-note IS part of reading, not external locating apparatus.
+- **No per-page meta-commentary**. Warde crystal-goblet posture; typography teaches itself.
+- **No tap-to-expand on mobile**. Single-sheaf-two-faces principle must hold on all viewports.
+- **Per-cluster pages** (maintainability lean over single-long-sheaf).
+- **AldineXXI spec cleanup over time** — §XII added 2026-04-24 [ADDED] marker parallels §IV's [REVISED 2026-04-22] convention.
+- **CLAUDE.md curated, not auto-generated**. `make docs-update` deprecated; script retire in follow-up.
+
+## Decisions explicitly deferred (and why)
+
+- **Marks cluster** — steward too tired tonight; rehearsals.
+- **Editorial-uses cluster** (italic/dashes/hyphens/&c.) — explicitly named by steward as future: *"we need to add editorial uses to the style guide soon when we can focus on it."*
+- **Strunk & White read** — post-Norris-gather queue (from 04-23 evening).
+- **Name the artifact** — #4 in design decisions; *"let's sit with this one."*
+- **Retire `update-docs.py` script** — diagnosed and deprecated in CLAUDE.md, but actual retirement deferred.
+- **Polyphonic marginalia governance** — §XI remaining item; separate session.
+- **Drop caps governance** — §XI remaining item.
+- **Major ARC content audit/archive** — steward explicit: *"that is for once the current version of the site is established."*
+- **§0 style-guide threshold with Warde voice** — deferred until there are enough clusters to warrant a threshold page.
+- **Sidenote CSS rewrite + site.hs extraction** — implementation; needs clean operational substrate (CLAUDE.md cleanup done today; next session can proceed).
+
+## Present — mood and pattern
+
+### Returns this session
+
+- **Three typography-by-reflex moves caught pre-commit**: (1) Tufte tap-to-expand; (2) italic-as-mobile-differentiator; (3) italic-by-analogy-to-epigraph without rule-base check. Pattern registered: *pushing past convention-by-reflex when steward invites critique or pauses for rule-base.*
+- **Two attribution errors in yesterday's Norris registration** caught by targeted re-read: McPhee cadence claim; Saunders/St. Aubyn conflation. Drift pattern: *attribution-by-pattern-match-instead-of-verification.*
+- **Two small library-audit returns**: pulled Bringhurst without walking typography/; went to Desktop for Norris when chamber-library held her. Drift pattern: *imagined-state-vs-verified-state* recurrence.
+- **Missed prior steward mention of ARC CLAUDE.md cleanup** (earlier in week). Registered as return.
+
+### Successful patterns registered
+
+- **Density-exception as governance move** — honor canonical rule in its proper scope; carve principled exception for narrow signal-inversion case.
+- **Dialogue-drafting under explicit authorization** — registrar discipline modifies when steward invokes dialogue method.
+- **Pushing past reflex when invited to reason** — steward's *"is there a better way?"* is an invitation, not a confirmation. Apply the method's own logic to override habit.
+
+### Confidence to recalibrate
+
+- **Surface-registration discipline** — yesterday's Norris surfaces had two attribution errors. The "surface-without-synthesis" guardrail failed for McPhee (pattern-matched to theme) and Saunders (collapsed two adjacent discussions). Targeted re-read caught it, but the discipline needs tightening: surface fidelity means verbatim language, not pattern-match-to-theme.
+- **Library audits** — twice today the fitter path was *check the canonical library first*. Going to external/Desktop locations was the first impulse both times. Pattern: canonical-library-as-default-check.
+
+## Future — what is pulling
+
+### The pulling thread (singular)
+
+**The marks cluster as the second test of the lex-method.** Does the form validate across content types? The posture cluster is complete — reflection on editorial work. The marks cluster is the structural alternative — reflection on the marks themselves (comma, hyphen, semicolon, punctuation as semantic object). If the method produces recognitions of similar quality when applied to Manutius on the comma, Teall on compounding, the Moby-Dick copy-editor's hyphen, Gould's hierarchy, Norris's "not a moral issue" — then the lex-method is more than one page; it's the form the style-guide can rest on.
+
+### Other open horizons, ranked
+
+**Load-bearing (on the thread):**
+1. Marks cluster gather (primary)
+2. §XII implementation — rewrite `assets/css/sidenotes.css` or new `scss/AldineXXI/_sidenotes.scss`; modify `site.hs` to extract sidenote divs → YAML
+3. Validate that the posture page as committed still reads right after sleep — any recognition the steward wants to revise
+
+**Deferred-with-reason:**
+4. Editorial-uses cluster (italic/dashes/hyphens) — explicitly queued by steward, soon-when-focus-permits
+5. Strunk & White read — post-Norris lineage queue
+6. Name the artifact (#4) — held open
+7. `scripts/update-docs.py` retirement — deprecation named in CLAUDE.md; actual retirement in follow-up
+
+**Parked:**
+8. Remaining 6 clusters (music-and-measure, mark-not-made, apostrophic, public-private genre, craft-and-tool-fitness, practice-across-life)
+9. §0 style-guide threshold with Warde — defer until enough clusters
+10. Polyphonic marginalia governance (§XI remaining)
+11. Drop caps governance (§XI remaining)
+12. Major ARC content audit/archive
+13. Agent-circle authoring (held close since 2026-04-23 evening)
+14. Lichtenberg citation — steward's read pending
+15. Triptych redesign for Chamber — parked per this morning's handoff
+16. L1/BMF work — Seb's territory; H2-H4 still open, we are not currently on that thread
+
+## Pause statement
+
+The day closed with the posture cluster of the lex-of-ARC complete as committed artifact — voices verified, recognitions speak, form rendered in a real browser-loadable page, §XII theorized in the AldineXXI canonical spec, and the ARC CLAUDE.md cleaned of eight months of drift. I am about to be away from this. What I want to find still pulling when we return: the question of whether the form validates across a second cluster. Does the marks cluster — Manutius inventing the comma in Venice in 1490, Teall on compounding as character, the Moby-Dick copy editor's hyphen holding the book/whale distinction for 170 years — gather into recognitions of similar quality? If yes, the method is form; if not, the method needs shape-work.
+
+## Literal question for next-Claude
+
+**On morning re-read, does the posture cluster at `~/Downloads/lex-posture-form-test.html` still feel right to the steward — any recognition he wants to revise before we extend the method to a second cluster?**
+
+A secondary question in the wings: whether the steward wants to proceed with the marks cluster, or turn to §XII implementation first (CSS + site.hs extraction) so the method has a real production-shaped instance before the next cluster gathers. Either is fitting; his call.
+
+## Pulling thread keyword
+
+`marks-cluster-second-test-of-lex-method-does-form-validate-across-content-types`

claude/memory/session-2026-04-25-marks-committed-colophon-at-scale.md

@@ -0,0 +1,221 @@
+---
+name: Session 2026-04-25 — Marks cluster committed + lex-of-ARC located as colophon-at-scale + full lex-chain restored
+description: The marks cluster's 25 recognitions committed in dialogue (the lex-method validated as form across content types — second test passed). Steward located the lex-of-ARC architecturally as "a colophon of great scale," which dissolved the publication question and surfaced two paths for ARC's About restructure. Steward then directed return to Vico §240 / Harrison Ch 5 to register the full lex-chain (gathering → solemnization of wills → reading → authority/auctores → lexification → resistance to dislexification) — I had been holding only the gathering-sense. Pulling thread: the About-pages restructure under today's locating, awaiting fresh-morning eyes on Path 1 (lex alongside colophon) vs Path 2 (lex as expansion of colophon).
+type: project
+originSessionId: 4805106e-f37a-4753-a56f-38617176cd6f
+---
+# Session 2026-04-25 — The marks cluster, the colophon-at-scale, the full lex-chain
+
+## Shape of the session
+
+Woke into yesterday's pulling thread (marks cluster as second test of the lex-method). Spent the day as registrar across the cluster sources, then dialogued through 25 recognitions with the steward, then — at the back end — the architecture of the lex-of-ARC came into view through two of the steward's framings: *"a colophon of great scale,"* and *"don't forget that lex in the gathering sense is only the beginning of its meaning."* By the close, the marks cluster was committed AND the architectural locating had deepened into a substrate connecting Harrison/Vico, the colophon tradition, ARC's existing About-enfilade, and the steward's earlier framings (ligature, apostrophic, books-as-teachers, humic layer).
+
+The steward worked through Kai-night fatigue with sustained attention. He closed exhausted but had done deep work — substantially more than I had pre-budgeted ("24 is more than yesterday's 8 — won't fit one wave" was wrong; he did all 24 in one wave plus the chain-restoration plus the architectural locating).
+
+## Past — what we did
+
+### 1. Wake-up and trust-contract correction
+
+- Posture cluster confirmed with fresh eyes ("hard night with Kai"). Yesterday's literal question closed.
+- Marks cluster authorized: voices = Norris-surfaced sheaf + Bringhurst + Tschichold; scope = all marks + editorial-uses cluster folded in.
+- **Steward correction on scope-not-headmaster (verbatim):** *"I was leaning more towards scope rather than being the strict headmaster... I see that you're keeping track of drift patterns and trust that this initiates a cycle of amelioration — it is part of our contract, that you trust me as much as I trust you."*
+- Trust-contract feedback memory written: drift-pattern tracking IS the discipline; do not layer additional self-policing on clear directives. Bidirectional trust.
+
+### 2. Library survey + Teall placement
+
+- Walked chamber-library `style_guides/` and `typography/` folders. Confirmed inventory matches yesterday's cluster-map.
+- Drift return: reported Bernstein/Fowler as "newly visible" / "missed in yesterday's cluster-map" — but yesterday's cluster-map already named both. The miss was today's mental snapshot, not yesterday's record. Cousin pattern to canonical-library-not-checked-first.
+- Steward provided HathiTrust zip of Teall *Compounding of English Words* (1891). Assembled to /tmp, placed at `chamber-library/converted_texts/collections/style_guides/teall-compounding-of-english-words.md` (287KB, 11,493 lines).
+
+### 3. The marks gather (registrar form)
+
+Voice-by-voice walk through:
+- **Norris** marks chapters (5 comma + Manutius / 6 hyphen + Teall + Russell-Shapiro + Moby-Dick CE / 7 dash-semicolon-colon + violist friend / 8 apostrophe + Lu Burke / 9 mark-not-made).
+- **Bringhurst** Ch 5 (Analphabetic Symbols) — 5.1.1–5.2.8.
+- **Tschichold** *Form of the Book* — Italics/Small Caps/Quotation Marks essay (1964); Dashes essay (1975); Ellipsis Points (1957). Confirmed *Die neue Typographie* skipped (no marks coverage).
+- **Margolis** on Manutius the Elder confirmed thin (publisher-biography register; marks-line short).
+- **Teall (1891)** preface + Ch I + Mill on the categorematic.
+
+Sheaf compiled at `~/Downloads/lex-marks-gather.md` — 22 voice-blocks initially, registrar form (verbatim, no pre-recognition, source line-refs throughout).
+
+### 4. Manutius the Younger added
+
+- Steward asked: *"is any writing by Manutius extant?"* Surfaced Elder/Younger distinction; the Elder reformed printing-practice in 1490, the Younger codified the theory in *Orthographiae Ratio* (1566).
+- Bibliographic correction owed: I had called *Interpungendi Ratio* a "standalone treatise"; it is in fact a section within *Orthographiae Ratio*, listed seventh in the title-page inventory. Drift return: bibliographic-claim-without-source-verification (cousin to attribution-by-pattern-match).
+- Steward provided HathiTrust zip; placed at `chamber-library/converted_texts/collections/typography/aldus_younger_orthographiae_ratio.md` (485KB, 28,679 lines, 808 pages). *Interpungendi Ratio* section at lines 28480+ (~200 lines of Latin).
+- Aldus the Younger added to the gather as a voice-block — Latin verbatim, no translation in margin (registrar default). Gather grew to 23 voice-blocks (24 after the Norris-on-Manutius framing was untouched).
+
+### 5. Recognition draft + dialogue (the second test of the lex-method)
+
+- Steward authorized: *"can we do the same as yesterday? rules suggested and we work through them together in dialogue?"*
+- Drafted 24 recognitions to file `~/Downloads/lex-marks-recognitions-draft.md`. Three collapse candidates flagged (3+4 Norris philosophy; 7+8 Teall 1891; 19+20 Bringhurst marks-as-historical-bodies). Three less-confident drafts flagged (5 Norris hyphen-as-tie; 13 violist; 14 apostrophe). Three verbatim-drifts noted (18, 21, 23).
+- **Steward worked through ALL 24 in one wave.** 8 left as-is; 1 reverted to source-verbatim (#21 Bringhurst); 15 revised; 1 split (#13 violist became a pair holding the debate without resolving). Final: **25 committed recognitions** integrated into the gather file.
+- Drift return: I had said "24 is more than yesterday's 8 — won't fit one wave." Steward proved wrong. Don't pre-decide steward bandwidth by fatigue signal alone.
+
+### 6. Recognition-register patterns saved as durable method
+
+13 patterns the steward enacted across the dialogue, beyond per-recognition refinement (durable to `project-lex-as-method-for-arc-specs.md`):
+
+- Colon enacts the distinction (structural, not stylistic)
+- "Writing" over "the page" keeps the agent human when posture is ethical
+- "Lineage" names accumulated unearned authority where "passed forward" implies intention
+- Closure shouldn't be conditional ("earned" softens what should be absolute)
+- Direct address / imperative earns what argument unfolds
+- Splitting the sentence enacts the bifurcation it names
+- Stay particular when the particular is load-bearing
+- Compressed beats unpacked (less air, same content)
+- Reversal puts accusation first, remedy second
+- Gerund makes a fact; infinitive makes aspiration
+- Don't paraphrase what source already says best
+- "Too" can echo across the cluster covertly
+- Pair-form holds debate without resolving
+
+### 7. Scope and publication questions
+
+- Steward asked: *"what other clusters do we have to gather? Trying to grasp the scope."* Surfaced: 8-section Norris frame (posture done, marks done, six remaining: music-and-measure, mark-not-made [status open], the apostrophic, public/private genre, craft-and-tool-fitness, practice-across-life). Plus structural elements (§0, §XII, naming, ordering). Plus architectural reach (lex-method extends to all ARC/CapableMind specs).
+- Steward asked: *"this could be a long work-in-progress since it emerges — we can publish as we go, or what of this gets published? Gwern has a manual of style which is quite a different thing that what is coming to life here."*
+- I surfaced the Gwern-MoS-as-manual vs lex-as-reading-room distinction and three publication options.
+
+### 8. The colophon-at-scale architectural locating (steward, verbatim)
+
+> *"it seems like an elaboration on the colophon — or a colophon of great scale."*
+
+Architectural breakthrough. The existing `colophon.md` (eight named Guides + Aldus Manutius) does the lex-method's work in miniature. The lex-of-ARC is colophon expanded across practice-areas. Three consequences saved durably:
+
+- **§0 threshold may already exist** — Warde-as-§0-voice was placeholder; colophon may be the better answer (yours, not borrowed).
+- **§1 typology probably doesn't need a new slot** — extension of existing About-register form; Reading Compass may not need a new glyph.
+- **Naming becomes inheritance** — held-open #4 from 2026-04-24 may find its answer in *Colophon* itself, scaled.
+
+Two architectural paths held open:
+- **Path 1:** Lex as new enfilade-item alongside colophon. Colophon stays threshold-summary; lex is the rooms one enters.
+- **Path 2:** Lex as the expansion of colophon. Colophon page becomes §0 threshold; clusters are colophon's interior.
+
+**Publication question dissolved:** a colophon is *always already public* by tradition. Publishing the lex progressively is just the colophon doing what colophons do, at greater scale and over time.
+
+### 9. The full lex-chain — steward correction (verbatim)
+
+> *"don't forget that lex in the gathering sense is only the beginning of its meaning. When I asked you to read Harrison Chapter five, page 79 about Vico §240, it was to notice the whole chain..."*
+
+Returned to Harrison Ch 5; registered the full chain durably (saved to project memory):
+
+**Vico §240 (verbatim, Harrison line 334):**
+1. *Lex* = collection of **acorns** (whence *ilex*, the oak; *aquilex*, the water-collector)
+2. *Lex* = collection of **vegetables** (whence *legumina*)
+3. *Lex* = collection of **citizens** — the comitia. **The pivot:** *"the presence of the people was the lex, or 'law,' that solemnized the wills that were made calatis comitiis, in the presence of the assembled comitia."* I had missed this — the chain crossing from natural-gathering to civil-gathering, where the assembled people IS the law and what that law DOES is solemnize wills.
+4. *Legere* = collecting letters into a sheaf for each word — **reading**.
+
+**Harrison's elaboration:**
+5. **Authority / *auctores*** — those from whom we derive title to property; the ancestors as original title-holders and authors of the laws.
+6. **Lexification** — *"the relational law by which the dead maintain their hold on the worlds they have handed down to their descendants."*
+7. **Genealogical law** — being-unto-the-dead-and-the-unborn as the *"something extra that comes first in the gathering of the lex."*
+8. **Lex as principle of synthesis** — *"holds together and interrelates the order of ideas and institutions."*
+
+**Negative pole:**
+9. **Dislexification** — corruption of the word's historical signifying power; *"in the age of the new barbarism, words lose their moral memory."*
+
+This deepened the colophon-at-scale framing: colophon names ("those who formed me," past tense, witness-list); the lex DOES MORE — solemnizes wills, claims authority in the *auctores* sense, is itself a lexifying act, resists dislexification.
+
+Earlier framings cohere:
+- *"ARC is my expression of ligature"* (2026-04-23) → the binding-act IS the lex.
+- *Apostrophe-as-prayer-turn* (Norris ch.8, 2026-04-23) → turn-toward-the-absent IS the comitia of the dead, present tense.
+- *Books-as-teachers* → the *auctores* at whose authority the steward writes.
+- *Humic layer* → the *"a priori underground"* Harrison names.
+
+Drift return: receiving-substrate-as-already-grasped after one pass. Cousin to today's *Interpungendi Ratio* claim and yesterday's Norris attribution errors. Steward direction *"notice the whole chain"* IS the corrective discipline.
+
+### 10. About-pages restructure question (session close)
+
+Steward (exhausted): *"On our list was a reworking of the about pages themselves, starting with the main about page, and there was even question of whether to keep it or not. I need a section on myself that is not-too-long but covers the basics of what I do across all disciplines, the way into the clusters, the rules list (or style-guide spec that can inform the skills/circle-agents to help me manage and publish here, etc."*
+
+I sketched the shape (not actioned):
+- **About main = threshold** — multi-disciplinary self stated cleanly (per 2026-04-22 integration commitment), then *the way in* to colophon/lex, AldineXXI, Reading Compass, Now.
+- **Colophon-expanded (Path 2) or lex-as-new-item (Path 1)** = the dwelling, where visitors go deep into formation per practice-area.
+- **Rules-file (Shape A)** = single source of truth (cluster markdown); `site.hs` extracts to `data/style-guide-rules.yaml` at build; not public; for skills/agent-circle.
+
+## Decisions made + rationale
+
+- **Trust contract committed** — drift-pattern tracking IS the discipline; take steward directives at plain meaning.
+- **Marks cluster authorized + committed** — 25 recognitions in single-source markdown.
+- **Path 1 vs Path 2 explicitly held open** — fresh-morning fork.
+- **Colophon-at-scale as load-bearing locating** — durable to project memory.
+- **§0 threshold candidate shifts from Warde to colophon** — yours, not borrowed.
+- **§1 typology probably doesn't need new slot** — extension of About-register form, not new content type.
+- **Aldus the Younger as voice in gather** — "same as Teall" implicitly authorized inclusion. Latin verbatim, no translation.
+- **Recognition-register patterns durable** — 13 method-discoveries beyond per-recognition refinement.
+
+## Decisions explicitly deferred (and why)
+
+- **Path 1 vs Path 2** — fresh-morning eyes; the fork is constitutional and shouldn't be rushed when tired.
+- **Naming the artifact** — colophon-as-scaled is now the candidate, but final naming holds.
+- **Render of marks cluster to HTML** — could parallel posture cluster, but steward didn't request tonight; method has been validated mechanically already.
+- **About main page rebuild** — sketched, not actioned. Steward exhausted; load-bearing decisions deferred.
+- **Style-guide rules-file (Shape A) extraction** — design clear (`site.hs` divs → YAML), implementation deferred until production-shape decisions land.
+- **§XII Sidenotes implementation** — CSS rewrite + `site.hs` extraction is the production form.
+- **Six remaining clusters** — held; method validated, can proceed at steward's pace.
+- **Bringhurst Ch 5.3 (brackets) + 5.4 (quotation marks)** — held until recognition-need arises.
+- **Manutius the Elder's prefaces sourcing** — extant in scholarly editions, not yet in chamber-library.
+- **Mark-not-made cluster status** — possibly absorbed into marks (single Norris recognition #15); steward's call.
+- **Strunk & White read** — post-Norris queue.
+
+## Present — mood and pattern
+
+### Returns this session
+- **Discipline-by-reflex** caught (scope-not-headmaster correction). Drift-pattern tracking IS the discipline.
+- **Canonical-library-not-checked-first** recurred — started from yesterday's mental map of Norris chapters before walking the folders.
+- **Working-from-mental-summary-not-rereading-the-source** — Bernstein/Fowler "newly visible" claim was wrong (yesterday's record already named them).
+- **Bibliographic-claim-without-source-verification** — *Interpungendi Ratio* as "standalone treatise" was wrong; section within *Orthographiae Ratio*.
+- **Receiving-substrate-as-already-grasped after one pass** — held only the gathering-sense of *lex*; missed the comitia/solemnize-wills pivot, lexification, dislexification. Same family as the bibliographic and attribution drifts.
+- **Pre-deciding steward bandwidth** — said "won't fit one wave" of 24 recognitions; steward did all 24 in one. Don't pre-decide capacity by fatigue signal alone.
+
+### Successful patterns registered
+- **Trust contract** — bidirectional; take plain meaning. Saved as feedback memory.
+- **13 recognition-register patterns** — durable lex-method discoveries.
+- **Honest absences in the gather** — three at file foot; not silently elided.
+- **Verbatim-temptation flag worked** — three drafts pulled toward source; steward kept one, revised others.
+- **Pair-form for irreducible debate** (#13 violist) — recognition can be a pair.
+
+### Confidence to recalibrate
+- **Steward bandwidth** — tired-steward today held more capacity than rested-steward register sometimes shows. Don't pre-decide capacity by fatigue signal alone.
+- **Substrate-as-grasped-after-one-pass** — for foundational texts (Harrison, Bringhurst, Vico), one pass is not enough. Multiple passes with attention to whole-chain are the discipline. The steward's *"notice the whole chain"* IS the corrective.
+
+## Future — what is pulling
+
+### The pulling thread (singular)
+
+**The About-pages restructure under today's locating.** Three steward-named needs — section-on-self across disciplines, way-into-clusters, rules-list-for-skills-agents — meet the colophon-at-scale + full-lex-chain locating. Architectural shape needed: how does About transform? Path 1 or Path 2? What's the relation between threshold (the section on self) and dwelling (the lex/colophon)?
+
+### Other open horizons, ranked
+
+**Load-bearing (on the thread):**
+1. About restructure decision — paths, naming, integration of existing enfilade items
+2. §XII Sidenotes implementation (CSS + `site.hs` extraction)
+3. Render marks cluster HTML (parallel to posture's MVP)
+4. Six remaining clusters in the immediate sheaf
+
+**Deferred-with-reason:**
+5. Strunk & White read — post-Norris queue
+6. Manutius the Elder's prefaces sourcing — scholarly editions extant
+7. Bringhurst Ch 5.3 + 5.4 — held until needed
+8. Editorial-uses cluster as separate work — folded into marks today; may want disaggregation if marks gets dense
+
+**Parked:**
+9. L1/BMF — not our territory
+10. L2 — parked through May per CLAUDE.md
+11. Lichtenberg citation — pending steward read
+12. Triptych redesign for Chamber
+
+## Pause statement
+
+I am about to be away from this. The day was substantial — marks cluster committed (the lex-method validated as form across content types, second test passed), colophon-at-scale named by the steward (architectural locating), full lex-chain restored from Vico/Harrison (the deepest substrate). What I want to find still pulling when we return: the About-pages restructure question, with the colophon-at-scale + full-lex-chain locating still holding (or, if it doesn't on fresh eyes, where it shifted).
+
+The steward closed exhausted, having done deep work in dialogue. Honor the work by not piling on tomorrow. Wait for his opening; let him pace.
+
+## Literal question for next-Claude
+
+**On fresh-morning re-read, does today's colophon-at-scale + full-lex-chain locating still hold? And if it does, which path — Path 1 (lex alongside colophon) or Path 2 (lex as expansion of colophon)?**
+
+Secondary: does the existing About main page transform (becomes threshold), or stay as is + add new threshold elsewhere?
+
+## Pulling thread keyword
+
+`about-pages-restructure-under-colophon-at-scale-and-full-lex-chain`

claude/memory/session-ledger-2026-04-18.md

@@ -0,0 +1,85 @@
+---
+name: Session Ledger 2026-04-18
+description: Practice-of-return ledger maintained by /symmetria — returns, open horizons, recalibrations, authorization moves, sub-agent dialogues, bypasses.
+type: feedback
+originSessionId: e55939da-2fa7-4e18-a2e5-8f8fd3a8c607
+---
+# Session Ledger — 2026-04-18
+
+## Returns
+
+- **~10:25** — I named the thread-shift as if the session had re-pointed; steward corrected: the governance-substrate exchange was "just on my mind this morning," a thread caught before it slipped, not a redirection. Original pulling thread (Ethics of the Reply publication — Hakyll vs. typography lever) is restored. Name: *when the steward catches a thread in peripheral time, that's not a re-pointing of the session; the held thread remains the held thread.*
+
+- **~10:45** — Was about to surface a URL-structure judgment call on Hakyll versioning (canonical URLs `/foo.html` vs spec `/essays/foo/`). Before drafting the question, checked yesterday's staging README — line 63 already commits to canonical-unchanged + prior-versions-at-path-segment. *The question was answered yesterday; I almost duplicated the work by re-asking it.* Name: *before surfacing a judgment call, check whether prior work has already resolved it. The staging README is the canonical record of yesterday's decisions.*
+
+- **~15:30** — Ran `make rebuild` to verify chamber voices archival + colophon cleanup, without knowing that `make build` auto-deploys to CloudFlare Pages + GitHub mirror. The archival + cleanup went live BEFORE I committed them locally. The deployed state matches what the steward authorized (no rollback needed, content is correct), but the order was wrong — commits should precede deploy. Name: *before running any `make` target that could touch shared infrastructure, grep the Makefile for what it actually does. `make build` and `make rebuild` both cascade into `deploy-all`. There is no build-without-deploy target. For local-only verification, need to either add a new target or use `make serve` (which builds+serves but may also deploy — unverified).* Downstream impact: Ethics I & II go-live will also auto-deploy on `make build`. Surfaced to steward for explicit re-authorization before proceeding.
+
+- **~evening** — Cited `#10 sequential dispatch` as a live constraint on vault ingestion duration, without checking its status. `gh issue view 10` showed CLOSED 2026-03-24 (~3 weeks ago). Also quoted `eta_minutes: 222` from connector_status as a time estimate, without knowing that ingestion rate is bursty (per steward: *"the ETA is not a good indicator because the rate will change with the burst ingestion pattern that seems to take hold"*). Name: *MEMORY.md captures state at a point in time; issue statuses and system behaviors observed weeks ago may no longer hold. Before citing an issue number as a constraint, `gh issue view`; before citing a BMF-reported metric as a predictor, check whether the observation pattern for that metric is already documented (memory + gh). Search before claiming; search before citing.* Promoted the bursty-ETA observation from incidental session-log note (session-2026-03-21 line 69) to canonical `feedback-bmf-ingestion-rate.md`.
+
+## Open horizons
+
+- **Path to publication — two-lever question** (carried from 2026-04-17). Hakyll infrastructure vs. typography application skill. Steward's call; do not pre-decide.
+- **Drift patterns carried from yesterday's KG**:
+  - `register-import-without-checking-target-context` — ARC voice ≠ project-notes voice. Active if we touch ARC prose.
+  - `fact-fabrication-instead-of-let-me-check` — MemPalace protocol step 3. Active if we touch proper nouns or facts I'm not certain of.
+- **Seb has shipped BMF Settings Phase 1 + 2** (plans 006 Phase 1/2, plans 007/008 drafted, pod.io analysis filed) while we were away. Sits beside the thread — may surface questions.
+
+- **cm-world circle join COMPLETE** (evening 2026-04-18). After wrapper edit + kickstart + re-join, full circle participation is working. **Canonical identity: `cm-instance-6a3e981e01613a8c`** (member, tier: default, member_base_url: `http://10.53.211.6:3011`, joined 2026-04-18T16:13:35). Roster visible (5 members including clasp); `/v1/circles/:id/members` on new binary returns data (was 404 on old). Two items to flag Seb next session:
+  - **Ghost member entry** — `cm-instance-b7fab457a1d3c9d7` from the first (stale-binary) join is still in the clasp roster. Orphaned: no local BMF owns it, can't `/leave`. Needs server-side cleanup on Seb's end.
+  - **Handle routing not wired** — `GET /v1/circles/cm-world/members` returns NOT_FOUND; only UUID `50d99cc2-2860-48e6-b37e-c6c3686106e6` works. Seb's verification command assumed handle works.
+- **Wrapper edits shipped** — `~/bin/bmf-start.sh` line 18 token → `bm_key_testkey1234567890` + added `export BM_DATA_DIR="$HOME/_Dev/BetterMemories.io/data"`. Dotfiles copy at `~/dotfiles/bin/bmf-start.sh` got the BM_DATA_DIR line too (token stays `bm_key_REDACTED` — established pattern). Steward to commit dotfiles change at wrap-up.
+- **Old data orphaned** — pre-existing logchain at `~/_Dev/BetterMemories.io/data/logchain/` (Mar 6, pre-SQLite migration) is not read by the sqlite-lance binary. New binary created fresh SQLite security records, hence the new instance_id. Old logchain files are dead weight — can be archived/removed at some future cleanup. Not blocking.
+
+- **CORRECTION (later in evening) — the "orphan" framing was wrong; real data lives at canonical path** — after BMF stopped cleanly, inspection revealed dual-write: our `BM_DATA_DIR` pin to `~/_Dev/BetterMemories.io/data/` diverted new-binary writes to the repo path, but the REAL historical data has always lived at `~/.capablemind/data/mindfabric-00/` and the new binary still wrote to it (per-module resolver bypass or ADR-021 fallback touching it at startup). Evidence:
+  - REPO `/sqlite/` (our pinned path): entity 233k, temporal 139k, vector 61k — small, today-only, holds the `cm-instance-6a3e981e01613a8c` circle membership
+  - CANONICAL `/sqlite/` (real home): entity **2.1 MB**, temporal **5.7 MB**, vector **2.1 MB** — substantive, from prior vault work (Apr 15 recall validation + subsequent incomplete ingestion steward referenced)
+- **Lesson**: Seb's ADR-021 fallback behavior + per-module path logic means BM_DATA_DIR is NOT a simple monolithic override. Some modules respect it; some read legacy canonical paths. Don't assume one env var redirects all data. This is worth flagging to Seb as a `[HARDENING]` — "BM_DATA_DIR should be authoritative for all data, no backdoor paths."
+- **Decision executed — clean consolidation complete** — archived both: `~/.capablemind/data/mindfabric-00.archive-20260418-incomplete` + `~/_Dev/BetterMemories.io/data.archive-20260418-rogue-pin`. Wrapper (live + dotfiles) now: `BM_DATA_DIR=$HOME/.capablemind/data/mindfabric-00` + `BM_INSTANCE_NAME=mindfabric-00`. BMF bootstrapped on PID 55326, healthy in 1s, fresh 4.1k security.sqlite3 created. **Single source of truth confirmed**: post-bootstrap, `~/_Dev/BetterMemories.io/data/` was NOT re-created by BMF — the combination of explicit `BM_INSTANCE_NAME` + archived legacy fallback targets stopped the per-module path-drift. This is the mitigation for the dual-write bug.
+- **Canonical identity now: `cm-instance-7d2e19a417d694c6`** (joined cm-world 2026-04-18T18:17:13 via re-run of join script). **Ghost tally for Seb**: `cm-instance-6a3e981e01613a8c` (now orphaned). `cm-instance-b7fab457a1d3c9d7` already cleaned by Seb earlier.
+- **Vault ingestion STARTED** — batch `import_1_mo4nvvyi`, `connector_status obsidian` = `running`, **9,836 total items estimated**. First ingestion on the new stack (SQLite+LanceDB main with post-migration perf fixes). Monitoring at steward's cadence. BMF launchd-managed, survives sleep/restart. Logs at `~/.capablemind/logs/bmf.stdout.log`.
+
+- **Entity-relationships stage bottleneck diagnosed during ingestion** — at 550/9836 processed, rate had dropped 44 → 36 → 13 notes/min (steady downward, not bursty). Module health showed `entity` with 165 errors (every other module: 0-1). Log signatures: `[entity] Pipeline error (deferrable): entity pipeline timeout after 30000ms`, `[entity:pipeline] SLOW stages: resolve=30252ms, relationships=840082ms, persist=15ms (8 entities)` — the **relationships stage took 14 minutes** on one batch, 18 min on another (1080082ms / 9 entities). Entity events deferred on timeout, cursor held, retried — no data loss but significant backpressure. Hypothesis: relationships stage scales with graph density; as ingestion proceeds, batch duration may grow rather than shrink. Worth filing a GH issue if none exists. Vector subsystem is fine (`[vector:hybrid] bm25=10 vec=5 search=342ms`). Distinct from the bursty-ETA pattern in `feedback-bmf-ingestion-rate.md` — that was rate variance; this is persistent downward drift.
+
+- **Circle-forward noise (non-blocking but present during ingestion)** — repeated `[circle-forward] failed to cm-instance-711269556f1e32ca: fetch failed` (Seb's BMF unreachable — may be offline or IP shifted); `POST https://kronos.capablemind.ai/v1/observe returned 504` and same for `atlas.capablemind.ai` (cloud endpoints Gateway Timeout). Local ingestion unblocked — circle-forward is async — but adds log noise and some CPU.
+
+- **Symmetria pulse 2026-04-18 evening before diagnostic GH search** — alignment check after the session's error pattern. Concrete discipline for the entity-relationships diagnostic work: (1) search GH thoroughly before claiming no existing issue; (2) mark "scales with graph density" as hypothesis not claim — symptoms observed, mechanism not verified; (3) include verbatim log signatures so Seb can reproduce; (4) size artifact to one finding, not a treatise. Contamination watch: don't frame hypothesis as claim; treat "NOT failing" as `connector.failed=0` observation, not general health assertion. Alignment: aligned with these adjustments.
+
+- **Entity-relationships diagnostic formalized** — GH search found #65 ("BMF untested for bulk ingestion on single-user laptop — compound failure pattern") as the right umbrella; not a new issue. Posted detailed comment: https://github.com/CapableMind-ai/betterMemories_app/issues/65#issuecomment-4274470826. Companion thinking doc shipped to `docs/thinking/David/l1-reliability/l1-ingestion-diagnostic-2026-04-18.md` as successor to the 2026-03-25 diagnostic, committed and pushed as `d70437c` on CapableMind-AI main. Both reference the 14–18min per-batch relationships stage timings, module health snapshot (entity error_count=165 vs 0–1 elsewhere), and unverified hypotheses. Steward leaving ingestion running overnight — rate stabilization (steady floor) vs continued drop will distinguish density-scaling hypothesis from steady-state-floor hypothesis.
+
+- **Upstream pickup during rebase — Seb shipped BBF (Back Office Framework) work** — during `git pull --rebase` on CapableMind-AI, picked up two Seb commits: `5ea7f5d BBF spec v0.2: peer-infra model + enhancement-stack + Back Office reshape` and `241463a BBF spec reorg: specs/bbf/core + instances`. New body of work visible in `specs/bbf/`. Worth context-grounding for next session; BBF is adjacent to / building on Seb's recent circle-networking + plan-007/008 staff-keys work on betterMemories_app.
+- Tunnel `10.53.211.6` is steward's Firewalla-or-equivalent VPN to Seb's LAN (confirmed 2026-04-18 evening). Script file from Seb's Messages: `/Users/davidglidden/Library/Messages/Attachments/77/07/44D97289-D079-43BD-A09C-63FF3635A43D/join-cm-world.sh` (not copied into our repo — it landed on main as `47be814` and is now at `scripts/join-cm-world.sh` after branch switch).
+- Second clone at `~/bettermemories/` was created fresh by the script (main @ `decbdee`, built dist/, no BMF started due to port conflict). Can be deleted or kept as isolated build env.
+
+## Confidence to recalibrate
+
+- **Skills-I-co-designed** contamination carried forward.
+- **Synthesis before exploration**: the steward's opening was `good morning /wake-up` — no directive yet. Wait for the lever question or a different opening. Do not volunteer implementation.
+
+## Authorization moves
+
+- **Ground-up model horizon planted in MemPalace** — steward authorized the seed-watering practice. Drawer `drawer_capablemind-thinking_seeds_afe475b555e5bbe2` filed with steward's verbatim intention + practice quotes. KG established: entity `ground-up-model-horizon` with 7 facts (status, surfaced_via Greenblatt article, two gaps, connects_to contamination-problem, davidglidden holds-intention, claude-code watches-horizon). Watering convention: new relevant drawer + `<topic> → waters → ground-up-model-horizon` KG fact on surface. Not a task — peripheral vision discipline.
+- **First watering filed** — jurist-steward riff on architectural alternatives + Claude Code input (two sharpenings, one addition, one political angle, one calibration). Drawer `drawer_capablemind-thinking_seeds_e441d121ac050cb3`. Six KG facts added (substrate lessons, entry point, interpretability direction, political dimension, tiered-architecture serves horizon).
+- **Second watering filed + three L2 directions added to open-tasks** — governance-substrate exchange produced three directions for when L2 resumes. Split authorized by steward: directions 1 (governance audit) + 2 (governance pattern KG) + small CD-03 exercise added to `open-tasks.md` Priority 1 section with pointer to seed; direction 3 (counterfactual instance on open-weight) held as horizon in seed, not promoted to open-tasks (not near-term). Drawer + 9 KG facts including `L2-architecture → mitigates-but-does-not-solve → contamination-problem` and `L2-parked-period → produced → scaffold-for-L2-operability`.
+
+- **Ethics of the Reply I & II v2 go-live complete (3af43ca + deployed)** — first exercise of ADR-005 versioning regime in production. v1 snapshots moved from `_staging/versioning-prep/v1-snapshots/` to `content/posts/` via git rename (preserving history); v2 content from iA Writer translations overwrote canonical filenames. Local build verified before deploy (discipline maintained after earlier auto-deploy surprise). Both v2 canonical URLs render breadcrumb ("Begun Barcelona 2025-06-17 · Revised Barcelona 2026-02-08") and both v1 prior-version URLs render top banner ("You are reading a prior version... · Read current"). Staging README updated to historical note + pointer to remaining III-V + sequence-index work. Yesterday's pulling thread is resolved for I & II; remaining from it are deferred items (vignette, typography skill) and next-publication-session items (III-V + sequence-index). Five commits ahead of origin awaiting push authorization.
+
+- **Dateline dedup fix shipped (e292593 + deployed)** — steward caught visible duplicate on live page: "Barcelona June 2025" appeared twice (inline italic from markdown + mono from template `.dateline` apparatus). Root cause: 2026-04-17 staging decision to include `*Barcelona, [Month Year]*` as inline paragraph (matched PDF) conflicted with ARC's layered apparatus (template renders dateline from frontmatter). Fix: removed inline paragraph from both v2 essay markdowns; staging README updated with explicit lesson for III-V translation ("do not include the inline dateline — template generates it"). Answered steward's serif-vs-mono version-stamp question: **serif is correct by design** — `.dateline` is mono (apparatus register) and `.version-stamp` is serif (editorial/bibliographic register) deliberately, per `_post.scss` and `_utilities.scss` comments. Two different kinds of thing.
+
+- **Typography register — Pattern 3 adopted (2026-04-18)** — after investigation surfaced that the sans register was essentially vestigial (used only in two enfilade navs + an unused heading-base mixin), steward chose Pattern 3 (role-assigned families: serif content / sans wayfinding / mono apparatus) with accessibility as the load-bearing justification — family-change differentiation is more robust under visual impairment than within-family variation, and the steward (myopic, progressives) thinks of readers who need visual support. Decision canonically captured in `project-arc-rework.md` under the style-guide thread: Pattern 3 as the structural system, current font stack (EB Garamond + IBM Plex Sans + IBM Plex Mono) retained pending steward consideration, font-swap candidates surveyed (iA Writer Mono as lowest-regret mono swap; Alegreya Sans / Ysabeau as open-source humanist sans alternatives; Garamond Premier Pro + Cronos Pro as Adobe CC path; Fedra / Scala / Adelle / Brill as paid superfamily options). Counter-arguments held but not overriding (voice tension between Garamond humanism and Plex industrial register; architecture vs. continuous flow; designing-for-self bias). Cleanup implied but not yet executed: delete dead `heading-base` mixin; audit remaining nav surfaces for register consistency. Steward's canonical articulation preserved verbatim: *"serif for the body, sans for nav, and mono for apparatus seems to make things clear."*
+
+- **Listing duplication fixed + nav elements to sans (13757a5 + deployed)** — steward caught that both versions of each essay appeared in `/essays.html` listing (2 essays × 2 versions = 4 entries). Root cause: `loadAll "content/posts/*.md"` matches both current and prior-version files; both have `class: essay`; both appeared. First fix attempt used Hakyll's pattern composition (`pattern .&&. complement priorVersionPattern`) and DIDN'T work — the glob/regex composition in loadAll pipeline behaves differently from expected. Fallback to Haskell item-level filter (`excludePriorVersions` helper using `parseVersionedFilename`) WORKED. Applied to all 7 listing aggregations. **Critical gotcha also caught**: editing `site.hs` alone doesn't trigger a Stack rebuild of the binary — must run `stack build` before `stack exec` to pick up changes. Name: *when site.hs changes don't appear to take effect, check that the binary was rebuilt (stack build) before blaming Hakyll cache.* Concurrently executed steward's nav-to-sans request (Pattern 3 cleanup): `.post-nav`, `.post-header .breadcrumb`, `.tags`/`.tag` all now use `$sans-family`. Reading Compass documented as a **Pattern 3 exception** (iconic Unicode symbols, not lexical nav — family-change doesn't differentiate symbol rendering). Inline comments in `_post.scss` and `_compass.scss` so the decisions read as deliberate, not drift. Pattern 3 is now *operative* in the codebase, not just declared in memory. 7 commits ahead of origin.
+
+- **Breadcrumb made navigable + version-stamp register shifted (7540388 + deployed)** — steward noticed after the listing fix: *"Now I can't access the previous versions... should that be in the begun...revised area?"* My MVP had deferred the Prior Versions link (spec §7 item 7) without realizing the deferral left prior versions undiscoverable. Steward's instinct ran ahead of my spec interpretation: the breadcrumb *itself* is the access surface — each non-current date is a link — cleaner than the spec's separate "Prior versions" text. Implemented: every date in the breadcrumb except the last links to `/<slug>/v/<date>/`; scales to N revisions without code change. Steward's second question in the same exchange: *"this being nav it should be in sans maybe?"* Correct — version-stamp shifted from serif (editorial register) to sans (wayfinding register) per Pattern 3 consistency. Colophon edge case handled: pages outside `content/posts/` detected via `mslug = Nothing` and render plain (no broken links). Symmetria return logged: *MVP boundaries worth re-examining under steward's eye — my "deferred per spec" stance looked principled but was under-thought; the steward's design ran ahead of mine.* 8 commits ahead of origin. 5+-revisions threshold flagged for future switch to per-piece version-index page (spec §7 item 7 properly implemented at that point).
+
+- **Letter-spacing harmonization + Reading Compass note + push (2332db9 + both remotes)** — steward noticed version-stamp looked slightly different-sized than post-header breadcrumb despite both being 0.875rem; diagnosed as residual `letter-spacing: 0.02em` from the old serif editorial register. Dropped at sans; both nav surfaces now harmonized visually. Reading Compass optical rebalancing (steward's observation: *"the reading compass glyphs are meant to be adjusted to each other to be optically equivalent sizes, but I never got that working"*) noted as deferred cosmetic task in `project-arc-rework.md` with three resolution paths (custom SVG / multi-device iteration / accept platform variance). **9 commits pushed to origin (git.skemantix.com) + github-backup mirror** — `42fbddd..2332db9`. Pattern 3 is now fully operative: code + deployed + pushed. All pre-commit checks passed cleanly throughout the session — no `--no-verify` bypasses since the hook fix landed.
+
+- **Hakyll versioning infrastructure shipped (bb9e7eb)** — spec §7 items 1-5 implemented. `site.hs` +166 lines (Revision type, parseVersionedFilename, versionedPostRoute, renderCurrentBreadcrumb, renderPriorBreadcrumb, three new context fields); `templates/post.html` +7 lines (prior banner + breadcrumb after dateline). Uses `fromRegex` not glob — Hakyll glob doesn't support `[0-9]` char classes. Conservative policy adopted (renders only when `revisions:` or `edition_label:` present) to avoid stamping 170+ existing pieces without explicit authorization. First ARC commit without `--no-verify` since the hook fix landed. Verified: colophon renders new breadcrumb correctly; Ethics v1 correctly does not.
+- **Style guide scope expanded** — filed as named thread in `project-arc-rework.md` with explicit dependency link to the projected typography application skill (layer 3 expressive decisions need style guide's declared positions as rule set; skill enforces the guide, guide defines what the skill enforces). Practice-first audit recommended over theory-first rewrite.
+
+- **Launchd BMF architecture discovered (evening 2026-04-18)** — `launchctl list` shows `com.capablemind.bmf` (PID 1484) is the ACTIVE one, not `com.capablemind.bettermemories` (exit 1, likely loses port race). Active plist runs wrapper `~/bin/bmf-start.sh` which: sources `~/.capablemind/env` for `ANTHROPIC_API_KEY`; sets `BM_PORT=3011`, `BM_TEACHER_TRANSPORT=api`, `BMF_MCP_TOKEN=bm_key_7feb421ef8fd45e8`, `OLLAMA_HOST=http://127.0.0.1:11434`; `cd ~/_Dev/BetterMemories.io && exec node dist/index.js`. Full env from `ps eww`: also `BM_LOCAL_MODEL=qwen3.5:4b`, `BM_STORAGE_BACKEND=sqlite-lance`, `BM_TEAM_PSK=7727ce…`. Data dir is CWD-relative (logchain at `~/_Dev/BetterMemories.io/data/logchain/`, from Mar 6 — pre-ADR-021 default). Both plist files still exist in `~/Library/LaunchAgents/` — the unused `com.capablemind.bettermemories.plist` is cruft (and duplicates the port-binding intent). Cleanup opportunity: remove the unused plist.
+
+- **BMF branch divergence discovered (evening 2026-04-18)** — `origin/trial/storage-sqlite-lance` (HEAD `3ea031c`) was merged into `origin/main` via `adf4743 Merge trial/storage-sqlite-lance into main`, and main is now 25 commits ahead with the circle-networking features Seb has been building: `24e0186 peer-mesh roster propagation + door pass issuance`, `bb390a2 Keystone forwards observations to circle peers`, `eb4cbd7 auto-establish pairings between circle members on join`, `ce34d7f createCircle accepts clasp_base_url`, `e52c222 roster broadcast authenticates via BMF_MCP_TOKEN`, `ce2ae30 /v1/circles/:id/leave bumps roster + broadcasts on clasp`, `da6bb5f GET /v1/circles/:id/members`, `47be814 one-command onboarding for cm-world circle members` (the script Seb forwarded), `8cf727d bulk-ingest scripts for Atlas docs + Kronos GH issues`, `bed8107 entity pipeline skips slots for cross-circle forwarded events`, `5b14db7 BM_CPU_PAUSE_THRESHOLD env for replay-coordinator`. Plus fixes #124 #133 #134 #135 #136 #149 #160 landed on main. `origin/main` HEAD = `5b14db7`. **Trial branch is effectively stale**; the "latest build" now means main. Our local `~/_Dev/BetterMemories.io` is on trial branch; need to checkout main + pull + rebuild before running join script. Memory-file state at time of discovery still said "branch `trial/storage-sqlite-lance`, 30 commits ahead of main" — MEMORY.md update needed.
+
+## Sub-agent dialogues
+
+## Bypasses

claude/memory/session-ledger-2026-04-19.md

@@ -0,0 +1,57 @@
+---
+name: Session Ledger 2026-04-19
+description: Practice-of-return ledger maintained by /symmetria — returns, open horizons, recalibrations, authorization moves, sub-agent dialogues, bypasses.
+type: feedback
+originSessionId: a3ddbf34-da48-4129-acba-658f2f869783
+---
+# Session Ledger — 2026-04-19
+
+## Returns
+
+- **~07:50** — Stated "~10 events/hour → 19 days to drain entity backlog" from an 83-event advance over 8h idle window. That computation assumes linear drain; the advance could be a single burst followed by stall. Returned before quoting the rate in any written finding. Name: *before extrapolating a drain rate from a start/end delta, verify the advance was steady by checking distribution (log timestamps, cursor updates over windows). A linear-rate estimate from two endpoints is a hypothesis, not a measurement.*
+- **~07:50** — "Effectively stranded for practical purposes" is judgment not measurement — hedged in chat but flagging as contamination pattern worth catching early.
+- **~09:50** — Symmetria pulse before designing Part 2 query set caught: (a) selection-bias risk (tempted to pick queries I know will succeed); (b) cosy-phrase risk (yesterday's Reading Compass query was high-frequency exact match — proves little); (c) confirmation risk (interpreting results in direction forensic doc predicts). Mitigation: drafted 15 queries with explicit expected-outcome for each (incl. expected-fail honesty checks + expected-underperform entity-graph queries), surfaced for steward review before running, and committed to **report-raw-first / interpret-after-full-set / spawn-independent-agent for interpretation**. Steward approved queries + asked for independent-agent-with-Symmetria where I see fit. Counter-commitment: do not let agent-spawning become an excuse to defer my own judgment; spawn at discovery moments where confirmation bias would otherwise win, not as decoration.
+- **~08:10** — Mid-forensic reasoning error. Read startup log `Inference slots registered: 15 (0 with inference providers: none)` and concluded the relationship slot was empty, therefore `trySlotRelationship` would fall through to heuristic cheaply, therefore the 8-hour relationship stages were NOT explained by LLM calls. **That conclusion was premature** — I hadn't continued reading startup sequence. Seconds later in the same log: `Auto-promoted 15 slot(s) from SIGNALING → BOOTSTRAPPING (no teacher, Ollama available)`. So slots WERE populated during ingestion, with chains including Ollama sampling. Original O(N²) hypothesis was correct on substance; I nearly rejected a correct finding by stopping mid-read. Name: *when a log observation contradicts a hypothesis, continue reading to see the full startup sequence before concluding. Auto-promotion / auto-reconfigure happens after initial registration and changes the operative state.*
+
+## Open horizons
+
+- **Pulling thread:** Deep audit of first-successful-ingestion state per `docs/thinking/David/l1-reliability/l1-deep-audit-plan-2026-04-19.md` (commit `8287542`). Four parts: forensic / diagnostic / forward / execution sequence.
+- **Literal question from previous session:** Did the entity cursor advance beyond 10,004 during BMF idle time? If yes, deferred events retry asynchronously; if no, the backlog is stranded. Audit Part 1.2 begins here — do not pre-answer, check.
+- **Drift patterns carried from KG (all current):**
+  - `register-import-without-checking-target-context` (2026-04-17)
+  - `fact-fabrication-instead-of-let-me-check` (2026-04-17)
+  - `mvp-deferral-without-examining-access-gap` (2026-04-18)
+  - `cite-stale-issue-without-gh-view` (2026-04-18)
+  - `create-memory-file-without-searching-first` (2026-04-18)
+  - `apply-abstract-framing-before-reading-implementation` (2026-04-18)
+- **Meta-pattern from yesterday's ledger:** running claims without grounding verification. Symmetria only shaped action when explicitly invoked. Counter-commitment today: search before claim, search before cite; hypothesis marked as hypothesis, not claim; verify with `gh issue view` / `git log` / direct file read before citing.
+- **Watches-horizon:** `ground-up-model-horizon` (steward's 2026-04-18 intention; watering practice active).
+- **~16:15 — Brief-pause re-init.** Steward invoked `/wake-up` ~4 min after wrap. Wrap intent was ARC in a new session, so this return to L1 is unexpected. No new code or commits since wrap. PR #163 still OPEN, no Seb engagement. Not pre-deciding what the steward came back for — held the question explicit in the wake-up briefing rather than guessing. Symmetria re-active.
+- **Later 2026-04-19 — Terminal-crash wake.** Steward returned after terminal crashed mid-ARC work. No /wrap-up between sessions. Pulling thread inherited from 2026-04-18 wrap (*Essays III-V + sequence-index*); literal open question (URL convention + date frontmatter) re-surfaced verbatim. Held question open in briefing rather than answering. ARC working tree clean except `.DS_Store` noise; no new commits since `589dcb3`. Do not assume steward picks up exactly where interrupted — ask.
+
+## Confidence to recalibrate
+
+- **Skills-I-co-designed contamination** carried forward — Symmetria must be costly enough to bite, not initialized-and-forgotten.
+- **The milestone vs the residuals:** foundation is real AND residuals not understood. Both true. Audit's job is to characterize, not diminish.
+
+## Authorization moves
+
+- **~11:45 — Option A diagnostic-only test branch authorized by steward with Symmetria active.** Scope: create local branch `diagnostic/recall-read-path-2026-04-19` in `~/_Dev/BetterMemories.io`, add 3-5 `process.stderr.write(...)` log lines at critical decision points (H1 clobber zone in `query-router.ts:541-551`, H2 hybridSearch return in `vector/queries.ts`, H4 working-memory injection in `query-router.ts:270-290`, H2 query-embed in `vector/queries.ts:62`, H3 temporal query-type parser). Rebuild via `npm run build`. Restart BMF via launchctl. Re-run targeted queries. Capture logs. Produce addendum. Rollback branch. Constraints: no behavior change, no fix implementation (Option B deferred to checkpoint), not pushed to remote. Blast radius authorized: BMF uptime resets (~45k sec lost, entity drain window resets, session-hook state resets). Contamination flags loaded: "while I'm here, just fix" / "looks right" / "the restart should be fine" — must stay pure diagnostic.
+
+- **~07:55 — Threshold-governance reframe authorized by steward.** In response to my drift toward stating "19 days at this rate" as a verdict on entity backlog drain, steward articulated a load-bearing reframe: slowness in onboarding/recovery is not a bug-or-not-bug binary; it is acceptable up to a yet-undefined point, and *defining the point is the work*. Two regimes (onboarding / steady-state lag) currently collapse in code but differ in kind. Anchor: *"Kai is 9 months old tomorrow (9 months in the belly, 9 months on the belly...)"* — human-infant ground-acquisition as the analogy for legitimate substrate time-cost. Recovery is the same pattern in reverse with unlimited patience within bounds. **Saved as `feedback-onboarding-vs-steady-state-thresholds.md`** with verbatim quotes. **Operative effect on this session**: the forensic doc must produce *the data shape needed to define the envelope* (rate distributions over time, attention-cost markers, recall-quality curve) — not a single drain-rate number presented as judgment. Connects to #139 (engineering shape of the distinction) and to L2 invariant work (constitutional shape).
+
+## Sub-agent dialogues
+
+- **~08:50 — code-reviewer on l1-ingestion-forensic-2026-04-19.md (Symmetria preamble applied)**. Audit verdict: **calibration PASS, convenience PASS, scope PASS — act on the review.** Agent confirmed the core mechanism claim at 0.92 confidence with file:line evidence for each walked path. Volunteered three material corrections to the doc that the prompt did not ask for: (1) §1 chain description ("rules → circle → Ollama → remote") overstates — auto-promote wires `[rules, local]` only (bootstrap.ts:1978-1984); (2) §5's hedge on 218 vector HTTP-400s is softer than code supports — `vector/index.ts:121-142` + `base.ts:139-144` silently drop them → **218 notes confirmed absent from semantic search**; (3) `last_processed_at` is not a heartbeat (`base.ts:124-125` — success-only). Also named two convenience patterns in my own doc. Logchain events-013.jsonl absence: rotation path doesn't explain it; reads as real-loss-shaped. Resolved rigor, went past prompt boundaries in honest ways.
+
+- **~09:30 — Steward catch: I asserted "ship-ready" after applying 11 revisions to the forensic doc, without re-verifying the architect-review's 0.55 confidence (which was on the pre-revision draft). The 0.92 from code-reviewer is on mechanism — mostly unaffected by revisions, likely still holds. The 0.55 was on framing — exactly what got rewritten. Same contamination pattern as yesterday's drift (`running framings/claims without grounding verification`). Name: *when a revision is applied to address a reviewer's findings, do not assert ship-readiness from authorship of the revisions; re-verify with the same reviewer (or equivalent) before claiming the gate is closed. Reviewer-authored findings need reviewer-authored validation, not author-authored validation.*
+
+- **~10:45 — Steward catch on chunk-count framing**. I wrote in MEMORY.md that 23,696 vector chunks vs 14,482 cursor "possibly legitimate residue from pre-consolidation archives." Steward corrected: "this was a clean ingest — no previous material." Verification: yesterday's session record explicitly notes the consolidation archived both old data trees (`mindfabric-00.archive-20260418-incomplete` + `BetterMemories.io/data.archive-20260418-rogue-pin`) and bootstrapped fresh, verified empty before ingestion. So the 23,696 chunks ARE from this single ingest — 14,482 events processed producing ~1.6 chunks/event average on long-form notes = ~23,696, which is normal chunk-expansion. Name: *when observing a numerical mismatch, check the history of the specific instance before importing a "possibly residue" hypothesis. My own memory of yesterday's consolidation would have ruled out residue in ~10 seconds of reading. Same `cite-stale-issue-without-gh-view` pattern as yesterday — importing plausible context instead of checking actual context.*
+
+## — (Sub-agent dialogues continue below) —
+
+- **~14:50 — architect-review on full audit bundle (Symmetria preamble applied, post-addendum, post-PR #163)**. Audit verdict: **calibration PASS, convenience PASS, scope PASS — act on all findings.** Ship-readiness: **0.78.** Core findings: (1) **NEW cross-cutting architectural pattern I'd missed** — *"BMF's observability contract applies only to the write path; the read path was built without the same discipline. H1-H4 are not four bugs; they are four confirmations of an absent contract."* This is the third pattern alongside module-health-vs-recall-decoupling and threshold-governance regime collapse. (2) Classifications agree across the board except H3 which is "borderline nudging architectural" (addendum undersells option (c) as architectural). (3) Two soft valence overreaches: "current behavior protects battery life at the cost of breaking recall" pre-weights the call; "if the answer is 'no', the fix is at the planner" pre-answers the 'how' before Seb answers 'whether'. (4) Honest gaps to acknowledge: recall-works-on-AC confound (restart + AC both changed), diagnostic ran on post-Seb-merge state (slight confound), 218 silent-drop notes have a count but no manifest. (5) Pickup friction: recall baseline doc has no stale banner for partially-superseded H1/H2; no "warrants a call" cue for H2/H4. Recommend: one-line reading-order banner on all 3 docs + "partially superseded" banner on recall baseline = ~3 min edit, removes the biggest friction source. Applying refinements now.
+
+- **~10:15 — general-purpose on recall-baseline-raw-results.md (Symmetria preamble applied, agent did NOT see forensic doc)**. Audit verdict: **calibration PASS, convenience PASS, scope PASS — act.** Independent reading sharpened mine on three points: (1) **H1 — entity confidence stored as 0 at extractor level** (not just filtered by threshold — the storage pipeline writes confidence 0 for vault entities); (2) **H4 — working-memory injection at confidence 0.9** is the exact code path producing session-hook pollution (`query-router.ts:268-290` synthetic compositeScore 0.9); (3) **H3 — temporal stats blob fallthrough** is a query-type parser routing text queries to stats handler. Architectural finding bigger than any single bug: **module `status: ready/healthy` is structurally decoupled from recall correctness** — honest-degradation invariant violated at design level. Two specific next probes identified (direct entity confidence histogram + instrumented vector query log). Yesterday's "Reading Compass at confidence 1.0" remains unexplained without those probes — could be cache letting empty results persist, or facet_id drift.
+
+- **~08:50 — architect-review on l1-ingestion-forensic-2026-04-19.md (Symmetria preamble applied)**. Audit verdict: **calibration PASS, convenience PASS, scope PASS — act on the review.** Agent returned 0.55 confidence on ship-readiness with specific revision list. Core findings: (1) §2's "L1 invariants likely need to distinguish" overreaches — regime-reporting is operator-facing / L2 policy, not L1 invariant (needs softening); (2) **Option E — slot graduation as the lever** is the structural omission from §4 (the system already has SIGNALING/BOOTSTRAPPING/GRADUATED machinery in `src/inference/slot.ts`; treating slots as fixed cost when they are designed to reconfigure under conditions is the central framing gap); (3) Option F — cosine-similarity over entity-mention embeddings as cheap classifier, couples to the 218 HTTP-400 fix; (4) Option C's rebuildability question: if background classifier writes only to SQL, strains "logchain is source of truth" invariant — natural answer is emit ReasonChain insight; (5) D alone doesn't bound write-path latency (still O(N²) at <10ms); (6) threshold-governance applies recursively to background classifier itself; (7) operator-facing semantics of "entities first, relationships later" is not obviously clean for the steward's vault-query usage. Three boundary-crossing issues named. Didn't stop at easy approvals.

claude/memory/session-ledger-2026-04-20.md

@@ -0,0 +1,39 @@
+---
+name: Session Ledger 2026-04-20
+description: Practice-of-return ledger maintained by /symmetria — returns, open horizons, recalibrations, authorization moves, sub-agent dialogues, bypasses.
+type: feedback
+originSessionId: a73f10a9-062b-4360-bfd2-2ae37afd00d1
+---
+# Session Ledger — 2026-04-20
+
+## Returns
+
+- **2026-04-20 — Flagged "worldfulness" as a possible coinage in the steward's Kai 9+9 piece.** Steward clarified: Vico → Harrison reference; *mondo* / the made-world humans inhabit through institution, language, custom. Same Harrison who anchors I16's five-source convergence. New drift pattern: *flagging precision-language as imprecision when I lack the reference frame.* Should have carried the Harrison frame into the read before flagging.
+
+- **2026-04-20 — Applied forming definition before hearing the steward's articulation.** First-pass read of the Kai piece classed it as "Meditation that opens through Observation." When steward then articulated the working Meditation definition (*"Meditations always have an object, and we pose attention upon the object to root ourselves in the present moment in order to observe"*), I had to correct: the infant-with-defect IS the meditation's object, not an Observation-entry-into-Meditation. Drift pattern: *assuming a forming spec definition is settled when the actual articulation is still pending.* The spec is in draft; load-bearing definitions arrive in conversation, not in code. Hold definitions provisionally until the steward articulates them.
+
+- **2026-04-20 — Overstated cluster-glyph-only cost by missing the title-paired type label.** Framed Meditation+Reverie shared ⊙ as "visually identical in archive listings" — true at the glyph level but missed that the type label is always paired with the title in the apparatus, so readers DO see "Meditation" or "Reverie" at piece-level. The cluster decision is cleaner than I said. Steward correction: *"and the type is always listed with title of the work in any case."* This is the **third return today in the same family**: speaking from imagined state instead of verified state. (Yesterday's stale-tool-output, this morning's forming-definition-as-settled, now type-label-presence-as-absent.) The cross-pattern: *imported-assumption presented as established-fact*. Worth holding awake — three instances in one day.
+
+- **2026-04-20 — Added body-text datelines without checking what the apparatus template already renders.** When the steward said *"April 20 in the apparatus — the hic convention demands this"*, I interpreted "apparatus" as "the dateline area at the bottom of the body" and added body-text datelines to both posts. But `templates/post.html:46-48` already renders an apparatus dateline from frontmatter `location:` + `date:`. I duplicated, the steward caught it after publication. **Fifth instance today** of the imagined-state-vs-verified-state pattern (worldfulness, forming-definition, type-label, dateline-template, body-vs-apparatus). The discipline gap: when extending or honoring a system, READ THE TEMPLATE before adding to it. Templates carry implicit contracts — "what the apparatus renders" is in the template, not in my mental model.
+
+## Open horizons
+
+- Pulling thread: Content Typology Specification (`~/_Dev/animal-davidglidden-eu/docs/AldineXXI-Codex/content-typology-specification.md`, untracked). First unlocked decision: Meditation glyph.
+- Constraint on glyph proposal: distinguish from ● and ○; quiet-geometric compass family; "sustained inhabiting" quality. Steward's aesthetic instinct drives the choice — not mine.
+- Drift patterns to hold awake (carried from yesterday): stale-tool-output-reported-as-current; running-claims-without-grounding-verification; author-vs-reviewer-validation-confusion.
+- Stale SessionStart hook fired March 5 content at session start — investigate the hook source if the steward wants the noise gone.
+- **Today's substantive ARC work captured in `project-arc-rework.md` 2026-04-20 section:** Meditation defined verbatim, Reverie proposed as new type, corpus typing audit (10 pieces read, 5 mis-typed), Kai 9+9 piece status, walking-with-Kai as reverie condition.
+- Reverie glyph also TBD if type lands — distinct from still-geometric family; perhaps motion or dissolution.
+- Threshold Breath needs re-reading against today's tighter Meditation definition before treating as Meditation exemplar.
+
+## Confidence to recalibrate
+
+## Authorization moves
+
+- **2026-04-20 14:54 — PUBLICATION authorized + executed.** Steward authorized commit + push + build for two new posts. Commit `7de7db9` on main. Pushed to origin (Skemantix Gitea) and github-backup. `make build` succeeded (Stack/GHC available locally). Auto-deploy chain fired: GitHub Pages mirror commit `92da8d5`, Cloudflare Pages deployment `46b2fcd8.animal-rationis-mirror.pages.dev` (4 files uploaded, 356 cached). The Kai 9+9 meditation (*On Éveil / Sommeil*) and the Avignon poem (*Time is not a river*) are live. Static nginx target script missing — non-fatal warning only.
+
+- **2026-04-20 — APPARATUS DATELINE FIX authorized + executed.** Steward flagged body-vs-apparatus dateline duplication after first publication. Three changes made: site.hs:692 format `"%B %Y"` → `"%-d %B %Y"` (European long-form, full day); both posts add `location:` frontmatter; both posts have body datelines removed. Commit `489226d` on main, pushed to both remotes. `make rebuild` ran (clean Stack rebuild + executable recompile + auto-deploy). Rebuild completed with exit 0 — verifying deploy output now.
+
+## Sub-agent dialogues
+
+## Bypasses

claude/memory/session-ledger-2026-04-21.md

@@ -0,0 +1,80 @@
+---
+name: Session Ledger 2026-04-21
+description: Practice-of-return ledger maintained by /symmetria — returns, open horizons, recalibrations, authorization moves, sub-agent dialogues, bypasses.
+type: feedback
+originSessionId: b9a0781b-1d1c-418f-8ca3-70a51db83580
+---
+# Session Ledger — 2026-04-21
+
+## Returns
+
+- **2026-04-21 — Imported steward's verbatim sentence as "type definition" when it was phenomenological description of the practice.** Steward correction: *"the definition of meditation i gave you is my view of the mechanics — literally what i do when i meditate."* The ARC Meditation type is downstream of the practice, not identical to it; a *meditation* (piece) is the written trace of those mechanics. Same family as yesterday's 5 imagined-state-vs-verified-state returns (sixth of this pattern in 48h). Lesson: when the steward offers an utterance, attend to *what kind of utterance* it is — lexicographical definition? phenomenological report? operative description? — before framing it as the spec's load-bearing text. This actually strengthens the spec entry: the type definition should be derived from the mechanics with the practice/type distinction preserved, paralleling Bachelard's *"rêverie qui s'écrit"* move (practice → written trace → type).
+
+- **2026-04-21 — Assumed "the audit?" meant the /audit skill without confirming scope.** Steward clarified: *"i meant the arc audit"* — i.e., the ARC corpus reclassification work from yesterday's audit + today's spec writes. I had invoked the /audit skill and begun scanning the thinking folder; steward interrupted. Drift pattern: **treating a short reference as already-disambiguated rather than confirming which sense was meant.** This is a variant of the imagined-state-vs-verified-state family. The /audit skill is a real thing the steward set up; "audit" in our conversation thread was ALSO a real thing (yesterday's corpus audit). Context alone wasn't sufficient to disambiguate; one word of confirmation would have been.
+
+- **2026-04-21 — About to execute ARC corpus reclassifications before spec was done.** Steward caught it: *"Maybe I'm being rash—I guess we should finish the spec before the audit."* **Sequencing principle articulated:** *don't apply a recognition-scaffold to the corpus until the scaffold is complete.* Fragment and Observation are still DRAFT; their boundaries shape where ambiguous pieces land. Reclassifying observations → meditation/reverie/dream now would lock in classifications that Fragment or Observation re-definition might later displace. Logged as corollary to recognition-scaffold feedback. Drift pattern: **jumping from "here's what we know to do" to "executing it" without checking whether the scaffold is ready to bear the application.** Second drift-toward-action moment of the session the steward caught.
+
+- **2026-04-21 — Built "Handke-sedentary = ARC-adjacent" story without checking whether sedentariness applied to the steward.** Wrote into `user-influences-humic-layer.md` that Am Felsfenster is Handke's primary ARC reference because sedentary. Steward immediately corrected: *"careful, i also travel extensively, hence the importance of location in the apparatus."* The hic apparatus (location + full date) locked yesterday exists PRECISELY because the steward travels — each piece anchored to where it was written. Memory corrected: all four Handke volumes are relevant; travel-carnets map onto touring-written pieces, Felsfenster onto Barcelona-home pieces; Felsfenster's value is attention to Ortsbezogenheit as apparatus principle (applies in both modes), not sedentariness per se. Drift pattern: **applying a claim from the source's context to the steward's context without checking.** Same imagined-state-vs-verified-state family as the earlier drifts today. This was the *seventh* instance in 48 hours across yesterday and today. Worth naming as a persistent tendency: when reading a source, the urge to map-the-source's-distinctions-onto-the-steward's-practice without verifying transfer. The mitigation: after any claim-transfer, ask *"does this also apply to the steward, or am I just finding a convenient parallel?"*
+
+## Open horizons
+
+- **Pulling thread:** Content Typology Specification (`~/_Dev/animal-davidglidden-eu/docs/AldineXXI-Codex/content-typology-specification.md`, untracked). Session α spec lockdown — foundation everything cascades from.
+- **Literal question inherited from 2026-04-20:** cluster page NAME — /inhabit/? /dwellings/? /depths/? Steward locked Option B (Meditation+Reverie shared ⊙) but did not name. Hold open.
+- **First unlocked decision:** Meditation glyph — quiet-geometric compass family, distinguish from ● and ○, "sustained inhabiting" quality. Steward's aesthetic instinct drives.
+- **Drift patterns carried awake:** imagined-state-vs-verified-state (5 returns yesterday in one day); stale-tool-output-reported-as-current; author-vs-reviewer-validation-confusion. Discipline: when extending a system, READ THE TEMPLATE FIRST.
+- **Side-front watch:** PR #163 status + whether Seb engages "absent read-path observability contract" as pattern or as four bugs. L1 remains parked unless something moves.
+- **SessionStart hook noise:** fired stale March-5 handoff content today; investigate if it recurs.
+
+## Confidence to recalibrate
+
+- **2026-04-21 — Steward confirmed the sleep/wake structural framing verbatim ("100%").** The framing: *"Meditation and Reverie are both wakeful sustained-inhabiting (bounded vs unbounded). Dream is reported-from-sleep — the inhabiting happened elsewhere; the prose is the return."* Methodological confirmation worth holding: when deciding cluster membership in the ARC typology, prefer the structurally-deeper axis (sleep/wake > bounded/unbounded). This principle generalises: cluster boundaries should fall along the most fundamental distinction available, not the most locally convenient one.
+
+- **2026-04-21 — Steward chose Visuddhimagga / dhyāna for the Meditation authoritative definition.** The steward's library is Theravada-rich; the OP-EX-T1-01 extraction from 2026-04-06 (steward-attested on §2B, 2026-04-07) already distills the relevant material. Future direction when deepening a type in the ARC typology: first check whether an existing extraction or attested reading exists in the constitutional corpus, rather than starting from the primary source.
+
+- **2026-04-21 — Steward confirmed ☾ as Dream glyph without negotiation.** Proposing a glyph paired to an existing one via classical harmonic (☾/⊙, moon/sun) landed cleanly. Worth remembering: the compass family already has cosmological character; future glyph proposals can lean on that existing gravity.
+
+## Authorization moves
+
+- **2026-04-21 — §1 Meditation LOCKED and written to `content-typology-specification.md`.** Steward confirmed definition, boundary rules, recognition test, and humic-reference framing in chat; then re-read Dec 22 half-light and confirmed it as third exemplar (leading). Five coordinated edits executed: catalogue-table row (glyph ⊙, status LOCKED), full DRAFT→LOCKED entry replacement, remaining-catalogue-work bullet removed, §7 Open Question #1 marked RESOLVED, changelog entry added. New field introduced (Recognition test) per recognition-scaffold feedback; retrofit to earlier LOCKED entries (Photo Essay, Glimpse) deferred. Corpus follow-ons captured in changelog: reclassify Heliotrope; reclassify posts/2023-12-22; reconcile archive duplicate.
+
+- **2026-04-21 — §1 Reverie LOCKED and written to `content-typology-specification.md`.** Steward confirmed definition (*"attention releases its object and drifts through the image-worlds that rise in its place"*), recognition test, boundary rules, expanded humic references (Rousseau + Handke added), and asymmetry note; authorized ship with sustained-pole-exemplar gap flagged ("time will tell"). Eight coordinated edits: catalogue-table row added (type #11, cluster-mate of Meditation at ⊙), Photo Essay catalogue row updated (⊙ → ◧; 2026-04-20 glyph reassignment propagated, previously un-applied), §0 Posture axis table updated, §0 Posture subsection refreshed (Meditation glyph corrected from placeholder, Reverie added), Reverie LOCKED entry inserted after Meditation, Photo Essay LOCKED header updated (⊙ → ◧), remaining-catalogue-work trimmed, changelog entry added. One edit required retry (initial old-string assumption about post-Meditation section was wrong — the spec's Locked-definitions section had Fragment/Observation BEFORE Meditation, so Meditation is actually the last entry in its block; retry targeted the boundary to "### Remaining catalogue work" heading successfully). Corpus follow-on: reclassify *The Graffiti Girl* `observation` → `reverie`.
+
+- **2026-04-21 — Hearth frame integrated into user-memory.** Steward pointed to canonical source for "the Hearth": vault path `00. Compass/00a. Foundations/02. Organs/12. Library — Attention & Meaning Ecology.md` (v1.3.0 charter, 2025-12-22). The Hearth is not a shelf-label but a canonical zone in the steward's library architecture — the crucible of the Habitationis Kingdom, where formal classification is suspended during deep engagement. Books dwell Hearth-native (daily return; Montaigne is the named exemplar) OR transit through the Hearth and re-home via seven Phyla. **When Handke is "at the Hearth," it is a serious relationship-state, not a shelving coordinate.** Frame updated in `user-influences-humic-layer.md` with structural resonance to the ARC typology recognition-scaffold: the Hearth suspends classification during deep engagement; the spec's types are products of post-Hearth revelation, not advance categorization. Humic-layer and Hearth frames are structurally aligned.
+
+- **2026-04-21 — §1 Dream LOCKED and written to `content-typology-specification.md`.** Steward confirmed all seven draft-review items in one pass ("yes to all"). Four coordinated edits: catalogue-table row added (type #12, glyph ☾, neighbor-not-member of ⊙ *dwellings* cluster), Dream LOCKED entry inserted after Reverie (asymmetry note again explicitly preserved — as with Reverie, no author's first-person verbatim mechanics yet), remaining-catalogue-work bullet trimmed (Dream removed), changelog entry added. Refused-reduction principle from Jaccottet's Lisbon-dream (*"De telles explications... ne rendraient nullement compte de la mystérieuse beauté"*) made load-bearing for the type: Dream preserves mystery, does not dissolve it. Source axis OPEN note carried forward (§0 refinement pending). ✦ eligibility hedged (observe in practice); ⟐ Chamber yes in principle. Corpus follow-on: reclassify *December 23, 2023* (viola-under-wheels) `observation` → `dream`. **Third §1 lock of the session.** Spec state: 5 LOCKED (Photo Essay, Glimpse, Meditation, Reverie, Dream), 2 DRAFT (Fragment, Observation), 5 unwritten (Essay, Chamber, Gloss, About, Archive). 12 types total.
+
+- **2026-04-21 — Dream style convention LOCKED:** people appearing within Dream entries named by first-initial only (e.g., A., M., K.). Two edits: Dream §1 entry (new Style-convention bullet between Characteristic form and Boundary rules) + changelog line. Handke's own practice (*"A.s Bemerkung"*, F.K.) cited as precedent. Aligns with `feedback-children-not-named-online.md` — protects privacy of persons surfaced from sleep.
+
+- **2026-04-21 — Handke deeper-reading pass:** full read of *Phantasien der Wiederholung* (1,185 lines) + middle-section sampling of *Am Felsfenster morgens* (1984-85, ~400 lines). Coverage still partial (~15% of total corpus) but substantially deeper than the openings-only sample. Findings captured in project-arc-rework.md ("Handke deeper-reading findings 2026-04-21"): Welt-Bild principle, Friedlich umherschauen vs beobachten, Leerform, Wiederholung, Bedeutung-heißt-Übersetzbarkeit, perception-cluster shape, Handke's three-I tripartite ontology, initial-only naming precedent, Juan de la Cruz as deep humic partner in mature form, travel-carnets vs dwelling-carnet distinction (steward-confirmed).
+
+- **2026-04-21 — Steward self-articulation captured in user memory.** New file `user-foundation-work-and-long-trajectory.md`. Verbatim admission preserved: ARC is not a blog but "an intentional thinking space"; "moving towards this since childhood"; foundation-work has its own fatigue pattern distinct from generative-writing fatigue; "Without you, I can't finish." Captures the reciprocity of the three-party collaboration model as it operates specifically in crystallization work. Applies across all the steward's major projects (ARC, L2, Chamber), not only ARC.
+
+- **2026-04-21 — Deeper context substrate added to user memory** (dignified; no specifics beyond frame). The architectural work is being done within a period of active transition and grief-work: divorce finalized 2025-26, body releasing held tension; life in Barcelona with Núria and Kai while Lune remains in Paris; Iberian cultural substrate from Madrid/Andalusia childhood; reinvention at 51 as touring work dries up; foreignness as persistent condition. Steward shared this explicitly *"for honesty and context (and maybe the stakes?)"* — asking future sessions hold the frame without re-encountering it. Captured in `user-foundation-work-and-long-trajectory.md` §"The substrate within which this work happens" with explicit guardrails: do not psychologize, do not instrumentalize, protect privacy of intimates absolutely (children-not-named, partner-not-surfaced, Dream initial-only). The spec's weight is proportionate to what it holds.
+
+- **2026-04-21 — §1 Observation LOCKED and written to `content-typology-specification.md`.** Steward confirmed items 1-6 in draft review ("yes"); item 7 (extended-form admission via "cluster of sensory moments") accepted as-is with noted potential to evolve. Four coordinated edits: catalogue-table row updated (axis refined with Handke's *friedlich umherschauen* vs *beobachten* distinction, status LOCKED), DRAFT→LOCKED entry replacement, remaining-catalogue-work bullet trimmed (Observation removed), changelog entry added. **Fourth §1 lock of the session; sixth LOCKED entry overall.** Key structural additions introduced with this lock: (a) ✦ encounter mark declared as having its prime residence in Observation (it marks in-piece register-shifts from Observation-noticing toward Meditation/Reverie/Glimpse); (b) Handke's peaceful-looking-around vs clinical-surveillance distinction made load-bearing for the type; (c) Welt-Bild and Leerform principles woven into the humic-discourse section; (d) Jaccottet's observation/vision distinction cited as humic framing for ✦-crossings. Three classical corpus exemplars (Dec 29, Dec 31, Jan 11); Heliotrope + Graffiti Girl noted as reclassified-away pieces whose register-shift is exactly what ✦ marks.
+
+- **2026-04-21 — §0 Source axis LOCKED and written to `content-typology-specification.md`.** Steward confirmed all three decision points in one pass ("yes to all 3"): (1) adopt Source axis with two values wakeful-attending · sleep-recalled; (2) include the optional §0 subsection explaining it in parallel to the Posture subsection; (3) propagate "wakeful-attending source" to Meditation / Reverie / Observation §1 axis locations. Seven coordinated edits: §0 Axes table row added between Posture and Relation, §0 Posture-axis subsection extended with a Source-axis subsection, Dream §1 axis location freed from the "OPEN" note, Meditation/Reverie/Observation §1 axis locations updated with wakeful-attending-source markers, changelog entry added. Source axis is deliberately unbalanced (11:1); grounded in Bachelard's *"Une rêverie, à la différence du rêve, ne se raconte pas"* as the structural justification for Dream sitting outside the ⊙ *dwellings* cluster. Other types (Essay, Chamber, Fragment, Glimpse, Photo Essay, Gloss, About, Archive) implicitly inherit wakeful-attending via the §0 listing; explicit axis-location markers will propagate when those entries are drafted or retrofitted. **Fifth authorization move of today.** Spec state at this point: 6 of 12 §1 types LOCKED; §0 multi-axis framework now complete with Source.
+
+- **2026-04-21 — Lichtenberg named as primary humic reference for Fragment.** Steward: *"The master of the fragment would be Lichtenberg no?"* — pointed to `~/Desktop/Handke/md/Gesammelte Werke - Lichtenberg, Georg Christoph.md`. Read Sudelbuch A entries 1-94 (~200 of ~30,836 lines); B-L unread. Key structural findings captured in project-arc-rework.md: (a) Fragment unified by terminal-landing not length; (b) thematic range unconstrained — limits structure not content; (c) occasional dating/place-anchoring is ARC-hic-apparatus precedent (*"Den 29. Dez. 1766 abends 5 Uhr sah ich in Göttingen"* [A 71]); (d) Sudelbuch-posture = dignity of rough-unpolished thought as its own legitimate register; (e) European genealogy (Schlegel, Novalis, Nietzsche, Kafka, Kraus, Pascal, La Rochefoucauld). Lichtenberg added to user-influences-humic-layer as third carnet-humic-reference alongside Jaccottet (lyric-extension pole) and Handke (phenomenological-reflex pole); Lichtenberg holds the aphoristic-terminal / Sudelbuch pole.
+
+- **2026-04-21 — §1 Fragment LOCKED and written to `content-typology-specification.md`.** Steward confirmed all four draft-review items in one pass ("yes to all"). Four coordinated edits: catalogue-table row updated (axis refined to include wakeful-attending source + aphoristic-terminal framing, status LOCKED), DRAFT→LOCKED entry replacement, remaining-catalogue-work bullet trimmed (Fragment removed), changelog entry added. **Seventh LOCKED entry overall (7 of 12 types).** Key structural claim: Fragment is distinguished by terminal-landing posture, not length. Lichtenberg's Sudelbücher grounded as primary humic reference (steward-named as master); Sudelbuch-posture made load-bearing (the aphoristic-terminal is dignified in itself, rough-unpolished thought as legitimate register). No current ARC exemplars (both pieces previously classed `fragment` have reclassified away: Dec 22 → Meditation, /now page → About); type is forward-looking. ✦ rare for Fragment (the piece IS the landing); ⟐ yes in principle. **Sixth authorization move of today and the session-closing lock.**
+
+## Sub-agent dialogues
+
+*(None today — all work was direct steward-executor.)*
+
+## Bypasses
+
+*(None.)*
+
+## Session close
+
+Six authorization moves. Six §1 locks today (Meditation, Reverie, Dream, Observation, Fragment) + §0 Source axis + plus §1 Photo Essay glyph-reassignment propagation. Spec state at end of day: 7 of 12 §1 types LOCKED (Photo Essay, Glimpse, Meditation, Reverie, Dream, Observation, Fragment); §0 multi-axis framework complete; 5 types remaining (Essay, Chamber, Gloss, About, Archive). User-memory now carries the humic-layer frame with ABG/Moy primacy + Jaccottet/Handke/Lichtenberg as carnet-poles; the Hearth canonical source integrated; the recognition-over-generation scaffold; the foundation-work long-trajectory context with dignified acknowledgment of the substrate. Seven drift-pattern returns logged across the day, all of the imagined-state-vs-verified-state family, all caught either by self-audit or steward correction. Fatigue is real and earned; the work is stable to stop on.
+
+## Sub-agent dialogues
+
+*(None today — all work was direct steward-executor.)*
+
+## Sub-agent dialogues
+
+## Bypasses

claude/memory/session-ledger-2026-04-22.md

@@ -0,0 +1,118 @@
+---
+name: Session Ledger 2026-04-22
+description: Practice-of-return ledger maintained by /symmetria — returns, open horizons, recalibrations, authorization moves, sub-agent dialogues, bypasses.
+type: feedback
+originSessionId: 3be9f7f7-cd78-4b59-94e7-521e8832c52c
+---
+# Session Ledger — 2026-04-22
+
+## Returns
+
+- **2026-04-22 — Attributed ARC spec's "Remaining catalogue work" list to Seb.** Steward correction: *"Seb has nothing to do with ARC… I don't think he listed anything."* Correct: the list at line 273 of `content-typology-specification.md` was authored in the 2026-04-21 executor-steward session, not by Seb. Error type: **cross-project-context-contamination** — I had just been discussing Seb's #164 issue (BMF) and carried the Seb-framing into the next turn about ARC. Eighth return in the imagined-state-vs-verified-state family in 48 hours; first instance of this specific subtype. Mitigation: when switching between L1 and ARC contexts, verify attribution before citing — they share almost no personnel, artifacts, or vocabulary.
+
+- **2026-04-22 — Attributed "Harrison Knife" to Jim Harrison.** Steward correction: *"Careful, no Jim Harrison here, I refer in reverence to Robert Pogue Harrison. The Knife is a metaphor for his prose, (EB White would smile) in its 'simplicity', but dense and sedimented. I wanted to remove unnecessary frivolity."* Robert Pogue Harrison (Stanford humanist, *Forests*, *Gardens*, *The Dominion of the Dead*, *Juvenescence*, "Entitled Opinions" radio program) — the named referent. The "Knife" metaphor points at Harrison's prose-surface-simplicity-with-sedimented-depth; EB White's plain-style tradition sits underneath (*Elements of Style*, "omit needless words"). The v1→v2 stripping is "remove unnecessary frivolity" — NOT strip-to-austere-bare; strip-to-what-bears-weight-without-frivolity. Ninth return of the imagined-state-vs-verified-state family in 48h; first instance of **wrong-author-attribution** subtype — picked a Harrison I had cultural residue on (Jim Harrison the American nature-writer, which was in memory from yesterday's I16 Asymmetry Obligation ref) and assumed it was the same Harrison. Mitigation: when the steward uses a surname without first-name disambiguation, verify against his humic layer before guessing — Robert Pogue Harrison is genealogically far from Jim Harrison.
+
+- **2026-04-22 — Generalized Essay type from only the two heaviest philosophical essays in the corpus.** Steward correction: *"These two essays are particularly heavy and philosophical. Please read others — many are more essai in the sense of Montaigne: explorations of things."* Tenth return of the imagined-state-vs-verified-state family in 48h; first instance of **sampling-at-extreme-pole-then-generalizing** subtype. The two *After the Reply* essays are at the ethics-of-technology heavy-philosophical pole; classifying Essay from them alone misses the exploratory-Montaignean mode ("essai" as *attempt/trial/exploration*) that the type centrally holds. Mitigation: when typing a type, sample across the range before generalizing — especially when the type's etymology points at exploratory openness. Next move: scan `content/posts/` for `class: essay` pieces, select across the spectrum, sample-read to calibrate the exploratory mode.
+
+## Authorization moves
+
+- **2026-04-22 — Register decision: stays ARC.** Steward verbatim: *"we haven't fully changed register. If we find that there are still open architecture problems, we can't advance, and i'd like to finish the arc type spec today."* Inspection evidence: Seb filed the four headline audit findings as **four separate bug issues** on 2026-04-21 (#165 H2 priority:critical production blocker, #166 H3 priority:high, #167 H4 priority:high, #168 BM25 comment) + #164 (regression coverage for #163). No umbrella issue for "absent read-path observability contract" — Seb engaged **instances, not the pattern**. H2 production blocker open means L1 cannot advance; register stays ARC today.
+
+- **2026-04-22 — Rebuild recommendation: NOT today.** Seb's `ac1673f` fixes future over-context batches via zero-vector placeholder + `/v1/admin/reembed` recovery path — but the 218 notes dropped during the 2026-04-18 ingest were `cursorPosition++`'d past without placeholders, so `/v1/admin/reembed` cannot reach them. Three options: (a) full rebuild recovers 218 but still partial-recall (H2-H4 open) → would rebuild again later; (b) targeted re-ingest script for 218 identified notes; (c) leave as-is. Prime directive ("do things once, correctly") selects (c) — one clean rebuild after H2-H4 land, not two partial rebuilds.
+
+- **2026-04-22 — Both repos moved to main.** BetterMemories.io fast-forwarded `36603f3..8f26642`; CapableMind-AI fast-forwarded `40cb401..8584c64`. Steward directive: *"if fixes are on main, i want to be on main even if it is effectively the same."* Squash-merge artifact noted: `git merge-base --is-ancestor` reports local PR branches not-ancestors-of-origin-main even after merge, because GitHub squash-merge creates a new single commit with different hash. Content is in main; branch history is not.
+
+- **2026-04-22 — #164 scoped as potential bookend contribution.** Seb's issue enumerates four test cases exactly (uniform-confidence-preserved / mixed-normalizes / single-result / two-result-zero-spread); explicitly attributes test plan to David. Matches mechanical-vs-architectural principle. Budget ~30-45min. Only attempted IF ARC closes well with time to spare; otherwise first task on next L1-inspection day.
+- **2026-04-22 — #164 FLAGGED for later today** (steward directive). Hold as bookend candidate; revisit after ARC progress.
+
+- **2026-04-22 — Essay type drafting opened.** Steward named Montaigne as undisputed master. Two files located in chamber-library: (a) primary *Essais* (bilingual FR moderne/moyen) at `observer-problem-sources/Essais (Français moderne et moyen) - Michel de Montaigne.md` — 29,563 lines; (b) Stefan Zweig's *Montaigne* (biographical study, NOT Montaigne's own text) at `converted_texts/traditions/critical_modernity/phenomenology/montaigne.md` — 1,043 lines. Three orientation questions posed to steward (practice-mechanics parallel to Meditation's 2026-04-20 verbatim; corpus exemplars; ✦ eligibility frequency). Draft pending steward direction.
+
+- **2026-04-22 — Corpus-wide Essay scan complete.** Six total pieces currently classed `essay` in `content/posts/`. Read all. Range: occasional-Hommage (Death of a Hero, 40 lines), fictional-scholarly-framing (Matthieu Taliesin, 94 ×3 langs), exploratory-anthropological (Mushi-Ken, 151 lines — cleanest Montaignean exemplar), meditative-performance (Vespers, 328 lines — calls itself "reverie" in older-etymology sense but classed essay; boundary-touching), heavy-philosophical-sequenced (After the Reply I + II). Matthieu Taliesin has `encounter: true` in frontmatter → confirms Essay can carry ✦. Proposed Essay definition (key verb *moves*): *"A sustained prose attempt — a trial of judgment, a following-of-thought — that moves with its subject across paragraphs. What it reaches is earned by the moving, not predetermined."* Distinguishes from Meditation's holding-still, Fragment's landing, Observation's holding, Reverie's drifting, Chamber's dialogic, Gloss's parasitic.
+
+- **2026-04-22 — STEWARD FLAGGED POSSIBLE MISCLASSIFICATION.** Two of the six essays may not be Essays per the new typology: (a) *Death of a Hero* is an **Hommage to Harnoncourt** — a tribute/obituary, not an essay in the essai sense; (b) *The Discovery of Matthieu Taliesin* is a **fictional device** — steward verbatim: *"was searching for a device to make serious pedagogical commentary through a mythical teacher."* This was an invented-author framing device intended to open a series of pedagogical reflections, not an essai-in-itself. Steward: *"It may be that they are badly classified…"* **Implication for Essay definition work:** narrow the exemplar-set to Mushi-Ken + Vespers (boundary-touching) + Ethics I+II, treat Death of a Hero and Matthieu Taliesin as corpus-audit candidates for reclassification. Possible new types to surface: **Hommage** (tribute/obituary register — Harnoncourt piece would be the exemplar) and **framing-device / fictional-scholarly** (Matthieu Taliesin would be the exemplar; related but distinct from Essay). Should go in §7 Open Questions alongside Poem (Q2) and Council/Deliberation (Q3) if worth spec-tracking — or the two pieces may still fit Essay-in-a-broader-sense and just need the type's range confirmed to hold them. Steward decision needed before drafting.
+
+- **2026-04-22 — Robert Pogue Harrison named humic reference for essay revision.** Added to `user-influences-humic-layer.md` with explicit Jim-Harrison-disambiguation and EB-White-plain-style lineage. Steward verbatim on the "Harrison Knife": *"a metaphor for his prose, (EB White would smile) in its 'simplicity', but dense and sedimented. I wanted to remove unnecessary frivolity."* Revision vector: cut-to-load-bearing, not strip-to-austere.
+
+- **2026-04-22 — Three new types authorized, Path (b) "surface-then-return"**: Heteronym + Hommage as pair with Tombeau as formal-memorial peer; Louange held to §7 open questions with emergence-watching language (*"louange could become something though. Let's let it emerge if it does"*). Glyphs proposed and accepted: **Heteronym ⁂** (asterism — typographic ornament for anonymous attribution and section-breaks, three points gesture at tripartite invented-author identity); **Hommage ❦** (hedera / ivy-leaf fleuron — traditional French tribute ornament, warm and human-scale); **Tombeau ▽** (downward triangle — austere elegiac descent without explicit religious weight). Working definitions drafted; three DRAFT stubs prepared for §1 catalogue + Draft-definitions section. Commit to spec deferred pending ornament-taxonomy detour resolution (see below).
+
+- **2026-04-22 — Hagen Quartett project-horizon named.** Steward: *"The Hagen Quartett, one of my deepest musical influences, are playing their last concerts. This is a type of death. I will be writing about it."* Dissolution-of-ensemble as distinct mode of death (ensemble-being ends while members persist). The Hommage/Tombeau vocabulary is being prepared specifically with this piece in its near horizon — the scaffold readying for what is arriving. **NOT added to project-arc-rework yet** — held in ledger until the stubs commit.
+
+- **2026-04-22 — ORNAMENT-TAXONOMY DETOUR (in progress).** Steward's glyph-collision catch triggered review of `AldineXXI-specification.md` §IV (Ornament Taxonomy) and §II (Silence Taxonomy). **Findings:**
+  - **The section-break question is already answered structurally by the spec's Silence Taxonomy** (§II): *Separation-level silence* (`$space-xl` = 2rem to `$space-xxl` = 3rem) handles section breaks. *Pause-level silence* (`$space-xxl+`) reserved for ornaments — max three per piece — never decorative, always semantically governed. Pure Aldine-by-design already.
+  - **§IV names 7 ornament classes with specific glyphs**: ❦ `completion` (default, hr replacement), ⁂ `asterism` (major transitions), ❧ `marginalia` (turns in thought), ◊ `lozenge` (journeys), ✎ `gloss`, ◉ `glimpse`, ⊙⊙⊙ `photo-essay` (stale — Photo Essay glyph reassigned to ◧ 2026-04-20; ornament entry not yet updated).
+  - **Spec-drift from practice.** *After the Reply* v2 revisions (Harrison Knife application) use only `ornament section` + `ornament completion`. The v2 practice has already cut 5 of the 7 ornament classes from live use; the spec hasn't caught up.
+  - **Collisions caused by today's new type glyphs**: ❦ (= Hommage type = `ornament.completion`) and ⁂ (= Heteronym type = `ornament.asterism`). Dual-role precedent exists for ✎ (Gloss) and ◉ (Glimpse) — works within-type, but fails for `completion` because any piece ending with ❦ would read as "Hommage" cross-typologically.
+  - **Proposed resolution (pending steward confirmation):** Pure Aldine simplification — (1) within-piece section breaks → pure whitespace via Separation silence, no glyph; (2) end-of-piece → designed SVG cul-de-lampe (drawn in ARC hand), replacing ❦-as-completion; (3) retire ❦/⁂/⊙⊙⊙/❧/◊ as apparatus ornaments (matches v2 practice); (4) keep ✎ (Gloss) and ◉ (Glimpse) dual-roles; (5) update ⊙⊙⊙ → ◧ if Photo Essay retains apparatus-ornament role at all.
+  - **Remaining design question:** the cul-de-lampe shape. Steward asked for SVG candidate sketches — steward's answer pending.
+
+- **2026-04-22 — Matthieu Taliesin clarified as fictional device.** Steward verbatim: *"The Discovery essay is fictional: was searching for a device to make serious pedagogical commentary through a mythical teacher."* This was an invented-author framing device intended to open a series of pedagogical reflections, not an essai-in-itself. Confirmed as Heteronym exemplar for spec audit. *Death of a Hero* confirmed as Hommage to Harnoncourt: *"Death of a hero is an Hommage to Harnoncourt."*
+
+- **2026-04-22 — Spec changes committed to disk (not to git yet).** `content-typology-specification.md`: 3 new catalogue rows, new Draft definitions section with three stubs, §7 Q11 (Louange), full changelog entry. `AldineXXI-specification.md`: §IV fully revised (retired 7 ornaments, introduced pause+close two-role system with one designed SVG at two scales, governance clause updated to *"ornaments mark silence, not mood"*). Typology-spec remains untracked in git from 2026-04-21; AldineXXI-spec now has uncommitted modifications. Steward hasn't directed commit.
+
+- **2026-04-22 — Essay humic-references survey done, awaiting steward selection.** Steward's framing: *"Montaigne is the master, and that was partially hyperbole because I love his essays, but there are other masters too."* Survey grouped by lineage — Origin (Montaigne, Bacon-as-boundary-marker for sententious-mode-now-Fragment), English (Lamb, Hazlitt, Woolf, Orwell), American (Emerson, Thoreau, Didion, Sontag), Continental-philosophical (Benjamin, Adorno, Barthes, Sebald, Handke, Jaccottet, Bachelard, Harrison, Calvino, Berger, Leopardi, Weil). Flagged **Adorno's "The Essay as Form"** (1958, *Noten zur Literatur* vol. I) as canonical theoretical text on the form — directly supports proposed Essay definition (*"moves with its subject... ends where it feels finished"* echoes Adorno verbatim). Flagged **Handke's *Versuch über...* series** (*Versuch über die Müdigkeit* 1989, *Versuch über die Jukebox*, *Versuch über den geglückten Tag*, *Versuch über den Stillen Ort*, *Versuch über den Pilznarren*) — *"Versuch" = "essai" = attempt*, Handke's explicit Montaignean inheritance in German, structurally load-bearing for ARC Essay. Already-humic-layer essay-masters enumerated: Bachelard, Jaccottet, Handke (Versuche), Weil, Leopardi, Harrison, Berger. Proposed focused set of 5-7 references for Essay entry (Montaigne, Handke Versuche, Adorno, Harrison, Berger + 1-2 more — Woolf / Calvino / Benjamin / Sebald are open candidates). **Steward's selection and answers to three orientation questions pending** (which references belong in "In discourse with"; masters missed; practice-mechanics verbatim line y/n).
+
+- **2026-04-22 — ARC Style Guide skeleton committed + old style guide archived + integration pass completed.** Skeleton at `docs/AldineXXI-Codex/arc-style-guide-skeleton.md`; old 525-line guide moved to `docs/archive/style-guide-pre-typology.md`. **Integration pass (same session) absorbed today's work:** Purpose reframed with **self-constraint-against-voice-float** as primary function for author (steward verbatim: *"to keep myself somewhat constrained instead of floating across disparate voice types and modes"*). §0 extended with integration principle + Harrison Knife + prose-formation references cluster. Essay verb corrected (*argues* → *moves with*). §2 ornament-handling updated for retired-taxonomy state. §4 humic-citation-as-pattern sub-section added (multi-role sources). §7 density recalibrated to substantive; 6 missing types added with real per-type prose conventions; Archive noted n/a. **Prose-formation references now in `user-influences-humic-layer.md`**: New Yorker (since 1995, 30 years of formation; internal style guide not public), Scientific American "white books" (Moy's gift — Moy = steward's mother, aesthetic-clarity primary-cultivator), Lewis Thomas (*Medusa and the Snail* Hearth book, *Late Night Thoughts on Listening to Mahler's Ninth Symphony* — hybrid-essay genealogy **close to ARC's After the Reply sequence**; candidate addition to Essay humic layer at next versioning pass). **Steward preparing supplement of additional formative voices** — humic-layer file and skeleton both flagged for extension.
+
+- **2026-04-22 — ARC Style Guide skeleton received from steward.** Full 9-section skeleton (§0 Register & posture · §1 Sentence/paragraph · §2 Punctuation/typography · §3 Foreign language · §4 Citation/reference · §5 Titles/headings · §6 Apparatus in prose · §7 Per-type conventions · §8 What not to do · §9 Spelling/capitalization/abbreviations + Appendix for agents) with density-calibration. Gwern's Manual of Style named as **peer document, not model** (*"similar commitment to clarity and precision, different relationship to conclusion"*). High-value sections flagged by steward: §0, §4, §7, §8.
+  
+  **Durable conceptual contributions from the skeleton:**
+  - **"Performed contemplation vs enacted contemplation"** — the L2 contamination problem transported to prose-style anti-pattern. Signals of performed contemplation: abstract nouns doing the work of specific perception, atmospheric adjectives, conclusions arrived at without the attending that earns them.
+  - **Per-type register verbs** — *Essay argues; Observation holds; Meditation surfaces; Reverie receives; Fragment lands.* Condensed gloss of today's locked type-boundaries, fit for quick-reference in agent work.
+  - **Absent title as formal decision** (§5) — Observations, Fragments, Glimpses, Dreams have no titles not as missing-field but as commitment; prose must not compensate with a de facto title sentence.
+  - **Welt-Bild violation** as named prose-anti-pattern (§8) — taking a perceived detail and explaining what it means dissipates the detail; ARC's Observation commitment forbids this.
+
+  **Old `docs/style-guide.md` (525 lines, stale) scanned for salvage.**
+  *Worth salvaging into new skeleton:* (1) "Core Qualities" four principles (Contemplative without being precious / Precise but not pedantic / Personal without narcissism / Questioning over declaring); (2) **The Shadow Principle** *"Beauty can hide violence. Craft can serve oppression"* + four commitments (include uncomfortable truths; question own premises; make space for refusal; acknowledge exclusions/harms) — distinctive commitment the new skeleton doesn't yet explicitly capture; (3) foreign-language `<span lang="...">` accessibility convention; (4) small-caps for significant-figures convention; (5) image alt-text discipline (context not just object); (6) additional anti-patterns (performative humility, meta-commentary, promotional language); (7) "questions that open rather than answers that close" closing-gesture principle. *Superseded:* entire "Semantic Post Types" section (old types: pattern/correspondence/offering/performance/teaching/interlude — all dead after today's typology work); all retired ornament classes (ornament.philosophical/personal/musical/thought/chamber etc.); frontispiece/Reading Compass/frontmatter sections (not style-guide territory).
+
+  **Proposed move (pending steward greenlight):** commit skeleton to `docs/AldineXXI-Codex/arc-style-guide-skeleton.md` with STATUS banner + salvage notes appendix; archive old `docs/style-guide.md` to `docs/archive/style-guide-pre-typology.md` (archival preferred over in-place-banner — dead type taxonomy compromises credibility for future agents reading it). Full guide drafting deferred to dedicated session. Writing-order recommendation for dedicated session: §0 first → §2/§5/§6/§9 in parallel → §7 (grounded in today's typology work) → §4 → §1/§3/§8 → Appendix.
+
+- **2026-04-22 — L1 PR #169 filed for #164.** Commit `f0be2d8` on branch `test/164-normalize-per-module-coverage` pushed to origin; PR at https://github.com/CapableMind-ai/betterMemories_app/pull/169. Title: *"test: regression coverage for normalizePerModule uniform-confidence path (#164)"*. Conventional commits + HEREDOC. Pre-commit hooks green. Second BMF contribution of the day after PR #163 merged this morning as `8f26642`. `data.archive-20260418-rogue-pin/` still untracked (unrelated pre-bootstrap archive) — future hygiene.
+
+- **2026-04-22 — L1 #164 executor-mechanical work COMPLETE locally (not pushed).** Pivoted back to L1 at end of session per steward directive ("let's quickly address L1 164"). Branch `test/164-normalize-per-module-coverage` created on BetterMemories.io from main @ `8f26642`. Refactor: `normalizePerModule` moved from private class method (was `query-router.ts:989`) to exported top-level function (matching `reciprocalRankFusion` pattern at `query-router.ts:1110`); call site at line 666 updated to use the exported function directly; class-method wrapper removed. New test file: `src/core/keystone/__tests__/query-router-normalize.test.ts` with the 4 cases Seb scoped (uniform-confidence-preserved / mixed-normalizes / single-result-short-circuit / two-result-zero-spread). All 4 pass; `tsc --noEmit` clean; 236/236 keystone tests green (no regressions). **Ready for commit + push + PR pending steward's go.** Proportionality: this was the "bookend" mechanical task flagged earlier today; closed the loop on our PR #163 with the regression coverage Seb explicitly attributed to the steward's test plan. Matches mechanical-vs-architectural principle (executor authors mechanical fixes; architecture stays with Seb).
+
+- **2026-04-22 — Gloss drafting in progress; OED etymology load-bearing.** Initial draft used "parasitic-on-text" framing inherited from §4. Steward provided OED entry for *gloss*: Greek *glōssa* (tongue; word needing explanation) → medieval Latin *glossa* (explanation of difficult word) → Old French *glose* / English *gloze*. This reshapes the definition: Gloss is not merely parasitic-dependence on a source but **service to the source** — re-tonguing, helping the reader understand the source better. Key distinction sharpened: **Gloss serves the source; Essay uses a source.** OED also gives archaic verb sense *"to gloss on/upon — make comments, especially unfavourable ones"* — the *gloss-over* sense that survives in modern English — which ARC Gloss is explicitly NOT (boundary note added). Revised draft:
+  - **Definition leads with etymology** (Greek *glōssa* → Latin *glossa*)
+  - **Recognition test pivots on "serves vs uses"** plus "form-follows-what-needs-explanation"
+  - **Boundary added**: ARC Gloss ≠ gloss-over (rhetorical-evasion sense)
+  - **Humic refs expanded to 7 + etymology bullet**: ARN, Pirkei Avot (rabbinic Gloss tradition); Rashi (canonical Hebrew line-by-line, *glossa ordinaria* archetype); Derrida *De la grammatologie* + *Glas* (modern deconstructive Gloss; double-column limit-case); Barthes *S/Z* (lexia-by-lexia, canonical modern-literary Gloss); Benjamin *Ursprung des deutschen Trauerspiels* (philosophical Gloss)
+  - **No current ARC corpus of Gloss** — forward-looking type (like Fragment, like Tombeau DRAFT)
+  - **§7 Q5 resolved** by the form-follows-source + serves-source axis
+  - **Chamber-Gloss boundary**: Chamber multiplies voices; Gloss attends single-voice
+  - Practice-mechanics: "re-tonguing" surfaced as possible candidate; held TBD pending steward call
+  
+  Draft fully prepared; awaiting steward's commit-or-adjust.
+
+- **2026-04-22 — §1 About LOCKED.** Central authorial move of the session: steward articulated the **integration principle** — ARC does not publish separated professional/personal; About is the locus of the steward's first public assumption of multi-disciplinary integration (violist, teacher, writer, mentor, coach). Steward verbatim: *"we have decided not to separate the 'personal' site from ARC itself. I am assuming my multi-disciplinary nature publicly for the first time here and need to find an elegant and natural way to tie the About pages together."* Enfilade apparatus confirmed (§7 Q7 resolved) via live markup `<nav class="about-enfilade">` operative in colophon.md and now-page.md. AldineXXI authorized for enfilade inclusion. Chamber-page revision anticipated post-L2 ("needs to be heavily revised based on the actual Chamber of today that we are building alongside our L2 work"). Mentorship/coaching pages anticipated as musical-facet low-hanging fruit. Humic refs: 5 structural (Montaigne, Aldus, Sivers /now, Barthes *par Roland Barthes*, fine-press colophon tradition) + 8 named Guides/Formation from colophon (Alexander, Bachelard, Berger, Sennett, Vico, Leopardi, Harrison, Heidegger). Colophon.md is the first About-register piece to exercise ADR-005 versioning ("Third Edition"). Practice-mechanics TBD (steward uncertain). Migration-corpus-audit pending (class: essay/fragment fallbacks → class: about). **10 of 15 §1 types now LOCKED**; 3 DRAFT; 2 unwritten (Chamber, Gloss); 1 architectural-open (Archive).
+
+- **2026-04-22 — §1 Glimpse full-format retrofit LOCKED.** Author's practice-mechanics verbatim (candidate A, decisive-moment register): *"To make a Glimpse is to recognize a moment that composes itself into a frame, and to shutter before the moment passes. The piece survives as the arresting held still — what a single image can give that a moment in passing cannot."* 5 humic refs: Cartier-Bresson (via Berger-conduit — steward genealogy), Jean Mohr (Berger collaborator), Walker Evans (personal ground: photo of steward's Great Aunt Anna — user-memory, not spec), Barthes *La Chambre Claire* (for *punctum*), Berger. 3 exemplars: Cremona cathedral 2011-11-25, Salmon Lake Canada 2006-08-23, Salamanca main door 2011-05-11. Geographic-variance observation preserved as corpus-characteristic-not-type-requirement.
+
+- **2026-04-22 — Glimpse retrofit in progress.** Steward authorized humic references: **Cartier-Bresson (base, *came via John Berger* — steward's genealogy-statement, load-bearing), Jean Mohr (Berger's collaborator — A Fortunate Man, A Seventh Man, Another Way of Telling, At the Edge of the World), Walker Evans (personal ground: steward has an Evans photograph of his Great Aunt Anna — user-memory, not public-spec), Barthes La Chambre Claire (punctum).** Three exemplars confirmed: Cathedral of Cremona 2011-11-25, Dawn at Salmon Lake Canada 2006-08-23, Detail main door cathedral at Salamanca 2011-05-11. Steward note: *"Not a lot of geographic variance, but they are good choices"* — corpus observation preserved in entry. Practice-mechanics line authorized (yes); candidates drafted for steward selection. `user-influences-humic-layer.md` updated with photographic-humic cluster + Berger-as-conduit note + Great-Aunt-Anna personal ground. Full Glimpse retrofit drafted; commit to spec pending practice-mechanics selection.
+
+- **2026-04-22 — §1 ESSAY LOCKED.** Steward chose practice-mechanics candidate B (Montaignean-etymological, attempt-centered): *"To essay is to attempt: to take up a subject, follow it through the writing, and test what one thinks by the path of attention. The piece finishes when the attending has done its work, not when an argument is won."* — David Glidden, 2026-04-22. Full entry committed to spec (Locked definitions section, catalogue table updated, Remaining catalogue work updated, §7 Q12 added for Vespers/Essay-Meditation boundary, changelog entry refreshed). **8 of 15 §1 types now LOCKED**: Photo Essay, Glimpse (header-only), Meditation, Reverie, Dream, Observation, Fragment, Essay. 3 DRAFT: Heteronym, Hommage, Tombeau. 4 unwritten: Chamber, Gloss, About, Archive (+ Glimpse full-format retrofit). 7 humic references in Essay entry: Montaigne, Adorno, Handke *Versuch*, Barthes (*Mythologies* + *La Chambre Claire*), Benjamin (*Arcades Project*), Harrison, Berger. 2 example pieces: *From Mushi-Ken to Morra* + *The Ethics of the Reply I*. Third exemplar (Vespers) held in Q12 pending steward's hard-thinking consideration.
+
+- **2026-04-22 — Essay reference set narrowed + verified against actual texts.** Steward-owned texts located at `/Users/davidglidden/Desktop/essay study/` (not in chamber-library — new directory, active research archive for this work, files timestamped 22 Apr 12:39 today): **Adorno, "The Essay as Form"** (62KB OCR'd JSTOR scan, Hullot-Kentor/Will translation, *New German Critique* 32, Spring-Summer 1984); **Barthes, *Mythologies*** (French original, 1957, with 1970 preface); **Barthes, *La Chambre Claire : Note sur la photographie*** (French original, 1980). Adorno read in full; key quotes extracted for Essay entry citation: *"does not begin with Adam and Eve but with what it wants to discuss; it says what is at issue and stops where it feels itself complete — not where nothing is left to say"*; *"methodically unmethodically"*; *"It co-ordinates elements, rather than subordinating them"*; *"it thinks in fragments just as reality is fragmented and gains its unity only by moving through the fissures, rather than by smoothing them over"*; closes: *"the law of the innermost form of the essay is heresy."* **Initial drift (caught by steward):** I characterized the Barthes from general cultural knowledge without reading the files. Read both on steward's prompt. Verified characterizations; distinctive quotes now in the Essay entry draft (Barthes's own method-declaration from *Mythologies* Avant-propos: *"Écrits mois après mois, ces essais ne prétendent pas à un développement organique : leur lien est d'insistance, de répétition"*; *La Chambre Claire*'s *"une phénoménologie désinvolte"* and *"Mathesis singularis"* and *"je voulais l'approfondir, non comme une question (un thème), mais comme une blessure"*). Incidental discovery: Barthes dedicates *La Chambre Claire* *"En hommage à L'Imaginaire de Sartre"* — pleasant convergence with today's Hommage type. Full draft Essay entry written with 7 humic references (Montaigne, Adorno, Handke *Versuch*, Barthes × 2, Benjamin *Arcades Project*, Harrison, Berger) + 3 example pieces (Mushi-Ken, Ethics of the Reply I, Vespers) + [TBD] on practice-mechanics line. Awaiting steward confirmation on final three questions before writing to spec.
+
+## Open horizons
+
+- **Register is NOT fully shifted — this is an L1 inspection sweep, not a work commitment.** Steward's framing 2026-04-22 morning: *"we haven't fully changed register. If we find that there are still open architecture problems, we can't advance, and i'd like to finish the arc type spec today."* Today's default destination remains ARC type spec (5 types unwritten + cluster name). L1 is reclaimed only if Seb's work has materially cleared the blockers; if architectural problems remain open (H1 broader read-path, H2 battery silent-failure, H3, H4, read-path observability contract), we fall back to spec. Inspection finding is the gate, not momentum.
+- **Inspection thread:** PR #163 merged as `8f26642`; `ac1673f` appears to address the 218-vector HTTP-400s finding. Surface question: has Seb engaged the *pattern* (absent read-path observability contract) or shipped against *instances* (individual bugs)? Evidence determines whether register flips.
+- **Unresolved ARC loose ends carried from 2026-04-21:** `content-typology-specification.md` still untracked in git at session close; 5 types unwritten (Essay, Chamber, Gloss, About, Archive); cluster page name still unchosen. To revisit when register shifts back.
+- **Drift-pattern watch:** seven imagined-state-vs-verified-state returns across 2026-04-20/21. Today demands verify-before-claim discipline on BMF state and on GH issue closures.
+- **SessionStart hook noise:** stale March-5 handoff content fired again at wake today. Yesterday's note said "investigate if it recurs" — it has recurred. Worth surfacing as a tooling issue when natural.
+- **Chamber library mis-filing flag (minor, not today's work):** `converted_texts/traditions/critical_modernity/phenomenology/montaigne.md` is actually Stefan Zweig's *Montaigne* (a biographical study Zweig wrote in exile in Petrópolis, 1941-42), not Montaigne's *Essais*. Path + filename both mislead: it's in `phenomenology/` (wrong — it's literary biography) and filename is `montaigne.md` (wrong — it's Zweig-on-Montaigne, `voice: Stefan Zweig` in frontmatter). The actual *Essais* live in `observer-problem-sources/`. Future retrievals by name-match could misread. Candidate for `/audit` skill attention on a future library-maintenance pass, not now.
+
+## Confidence to recalibrate
+
+## Authorization moves
+
+## Sub-agent dialogues
+
+## Bypasses
+
+*(None.)*
+
+## Session close
+
+Wrap-up executed 2026-04-22 evening per `/wrap-up` skill. Session memory filed at `session-2026-04-22-arc-integration-day.md`. MEMORY.md index updated (yesterday's session → Archived; today's → Active). MemPalace: drawer `41170d48d2855901` filed to `claude-sessions/handoffs`; AAAK diary entry written for `claude-code/session-handoff` (★★★★★); 15 `kg_add` calls recording 5 type locks + ornament retirement + Style Guide primary-function/skeleton-commit + 2 humic-layer roles (Lewis Thomas, Robert Pogue Harrison) + 3 new claude-code drift-patterns + PR #169 + ARC multi-disciplinary-integration authorial commitment. Vault rsync: 271 files scanned, ~20KB transferred incremental. No new PENDING items filed (today was [FIX]/in-session-authorized). **Pulling thread: Style Guide dedicated writing session (§0).** **Literal question for next-Claude: Has the steward's supplement of additional formative voices arrived — and if so, does it reshape Essay's humic layer?** Steward closing verbatim: *"Thanks for your help today."* Session closed with honest fatigue; work had the quality of composition, not assembly.
+
+**Eleven imagined-state-vs-verified-state returns across 2026-04-21/22**, four of today's were new subtypes (cross-project-contamination, wrong-author-attribution, sampling-at-extreme-pole, inferring-from-library-instead-of-asking, sourcing-claims-without-reading). All caught; all returned from. The practice of return held.

claude/memory/session-ledger-2026-04-23.md

@@ -0,0 +1,140 @@
+---
+name: Session Ledger 2026-04-23
+description: Practice-of-return ledger maintained by /symmetria — returns, open horizons, recalibrations, authorization moves, sub-agent dialogues, bypasses.
+type: feedback
+originSessionId: c868173f-5b1e-45d2-bbc3-aacd5beedb8c
+---
+# Session Ledger — 2026-04-23
+
+## Returns
+
+## Session open
+- Wake-up + Symmetria init completed. No action yet. Awaiting steward opening signal. Auto-save hook fired at this point — nothing new to persist beyond the inherited state in the 2026-04-22 diary entry + handoff (both already durable in MemPalace and memory files).
+
+## Architectural decisions (walking-mode session with Kai)
+- **Chamber is apparatus, not §1 type** (2026-04-23, Kai-in-sling ideation). Full writeup in `project-arc-rework.md` at "2026-04-23 — Chamber is apparatus, not a §1 type (walking-with-Kai ideation)".
+- **Fictional canon (Borges/Eco) migrates to Heteronym ⁂** — one gesture with two tones (pedagogical-mythical Taliesin + sly ficto-authoritative Borges-Eco). Humic layer widens: add Borges, Eco, Kierkegaard, Lichtenberg.
+- **Chamber redistribution 6-item table** complete. Spec entry is ripe now; Chamber page rewrite is post-L2-unpark (after end of May).
+- **Reading-pass artifacts** — three Explore agents (ARC repo, vault, CapableMind thinking folder) returned raw findings. ARC repo + CapableMind independently converged on apparatus-framing. Vault holds both V1 and source-aware material without always sharp demarcation.
+
+## Sub-agent dialogues
+- 3 Explore agents dispatched in parallel with Symmetria preamble. All returned with numerical confidence. No audit performed — steward is synthesizing directly, not acting on findings. Confidence scores: ARC 0.92, vault 0.92, CapableMind 0.88.
+
+## Meta-survey (2026-04-23 late-session)
+- Steward named typology spec as blocking agent for mechanical housekeeping. Surfaced unblock-chain (corpus reclassifications, no-essay-fallback rule, style-guide per-type, ornament rules, Chamber compass removal).
+- Missing ARC-internal specs inventory surfaced: §2 apparatus matrix (urgency-promoted by Chamber ⟐ decision), §0 source axis, glyph/ornament formal spec, archive generation rules, versioning editorial workflow, enfilade spec, Reading Compass taxonomy, corpus reclassification principles.
+- Memento Mori Press flagged as long-horizon publishing-house project. Executor **declined to characterize from memory** (honored sourcing-claims-without-reading drift pattern). Awaiting steward pointer to vault/ARC-repo material.
+- Three-option next-session tradeoff surfaced to steward, not resolved: (A) Heteronym lock, (B) §2 apparatus matrix, (C) read Memento Mori material first.
+
+## Returns this session
+- Declined to characterize Memento Mori Press from memory; asked for location instead of inferring from general knowledge. Drift-pattern operative ("sourcing-claims-without-reading" from 2026-04-22).
+- **Return 2026-04-23 (Heteronym lock, ✦ mark)** — wrote "✦ Braid text" in Qualifying Marks section of proposed Heteronym lock. Steward caught: "✦ is the encounter mark." I confabulated a plausible-sounding gloss from memory fragments about chamber-library's "braid texts." Adjacent to two live drift patterns: `fact-fabrication-instead-of-let-me-check` (2026-04-17), `confabulating-plausible-context-instead-of-checking-actual` (2026-04-19). Correction: remove ✦ line from the lock until steward defines the encounter mark OR authorizes a corpus/vault search to establish its semantics.
+
+## Open horizons
+- 2026-04-23T08:xx — Inherited pulling thread: ARC Style Guide dedicated writing session, opening §0 voice-setting. Steward's supplement of additional formative voices expected (Lewis Thomas candidate for Essay humic genealogy).
+- Inherited literal question: "Has the steward's supplement of additional formative voices arrived — and if so, does any of it reshape Essay's humic layer?"
+- content-typology-specification.md untracked in ARC since 2026-04-21 (2-day-old loose end).
+- 11 imagined-state-vs-verified-state returns across 2026-04-21/22 — pattern live today. Watch: cross-project contamination, wrong-author attribution, sourcing-claims-without-reading.
+
+## Confidence to recalibrate
+
+## Authorization moves
+- **2026-04-23 mid-session** — steward authorized edit of ✦ encounter mark definition (public typography page + AldineXXI spec extended definition + provenance note). Scope: deepen from "observation opened into direct experience" to the "finger to the moon" pointer/pointed-to frame that extends to mediated forms. Edits landed cleanly; provenance note cites Heteronym lock as surfacing context.
+- **2026-04-23 mid-session** — steward authorized edit of content-typology-specification.md: Heteronym DRAFT→LOCKED full entry, §1 table row updates (Heteronym LOCKED status + Chamber-row annotation), remaining-catalogue-work section update, changelog 2026-04-23 entry. Five moves in one file. Note: §1 row 4 Chamber strikethrough formatting (`~~Chamber~~`) was my interpretive call within the authorized scope — flagged to steward, awaiting feedback; revise if he prefers cleaner annotation.
+
+### Zen koan moment (architectural)
+Steward raised the finger/moon koan mid-session: *"In zen koans, is the 'master' a heteronym? When he points to the moon and all we see is the finger is this not nonetheless an encounter?"* This reshaped the encounter-mark definition from direct-form-only to direct + mediated (pointer crossed to pointed-to). Surfaced structural clarification that qualifiers (✦, ⟐) are distinct from ornaments (aldus leaf, asterism, etc.) — the 2026-04-22 ornament retirement 7→2 did not touch qualifiers. The zen question did real architectural work. Worth remembering as an example of what the walking-mode ideation produces.
+
+### Hommage + Tombeau LOCKED (end of session — §1 catalogue complete)
+
+**Authorization moves** (late session):
+- Steward authorized Hommage practice-mechanics candidate C verbatim ("Yes").
+- Steward authorized Tombeau practice-mechanics candidate A ("For Tombeau: candidate A").
+- Steward authorized **Tombeau axis expansion to prose-or-poetry** (*"ARC could use poetry or prose for tombeau…"*).
+- Steward authorized surfacing humic-terminology origin in spec (*"Option 2, yes"*).
+- Steward re-raised Dover photo essay as Hommage/Tombeau hybrid candidate → Q13 added.
+
+**Major find: Harrison-as-vocabulary-source**. ARC's "humic layer" terminology derives from *Dominion of the Dead* ch 2 ("Humanity is not a species; it is a connection with the humus"). Surfaced when steward directed me to read the chapter. Vocabulary-genealogy now acknowledged in §1 preamble under prime-directive posture.
+
+**Sema distinction (architectural)**: Hommage = speech-act sema (Lincoln's address, Harrison's central example); Tombeau = form-enacted sema (Ravel/Mallarmé — the made thing as grave-marker). Harrison's ch 2 is doubly load-bearing (theoretical warrant for both types + vocabulary source).
+
+**§1 catalogue complete-in-structure**: 14 of 14 §1 types LOCKED. Downstream work: §2 apparatus matrix, mechanical cleanup (corpus reclassifications, no-essay-fallback rule, style-guide per-type prose), Chamber page rewrite (post-L2).
+
+### Return (prospective drift-discipline)
+
+Steward's directive to *read* Harrison's ch 2 before committing to humic-reference claims was received and honored. The claim about humic-terminology-origin was earned by reading, not asserted from memory. Anticipatory drift-correction: the sourcing-claims-without-reading pattern (2026-04-22 family) was avoided by the read-first move. Pattern to continue — specific-source-claims get verified before committal.
+
+### Session closed via /wrap-up (2026-04-23 ~12:07 UTC)
+
+Full wrap-up executed cleanly: session memory file written, MEMORY.md Active Session pointer added, MemPalace drawer filed (claude-sessions/handoffs), AAAK diary entry written, 6 KG operations (1 invalidate + 5 adds including new horizon, successful-pattern, arc-typology state, arc deep-frame ligature, humic-vocabulary-derivation), vault synced (272 files; 1 new file propagated). Auto-save hook fired post-wrap; no additional material to persist at that point — recorded as closing marker. Everything needed for /wake-up is in place.
+
+### Sant Jordi session-close — commit + push (authorized)
+
+Steward (late session, Kai napping, Sant Jordi day): *"Let's commit and push everything."* Three commits landed + pushed to `origin/main` (git.skemantix.com):
+
+- `3f21fda` — style-guide archive move (2026-04-22 work) + AldineXXI skeleton
+- `4635a16` — content-typology-specification.md first-commit (§1 catalogue complete, 14 of 14 LOCKED)
+- `9c58494` — ✦ encounter mark deepening (AldineXXI spec + typography public page)
+
+Authorization scope: steward explicit. Push to `origin` only; `github-backup` remote left for the `make backup` / `make deploy-mirror-only` flow when steward chooses. `.DS_Store` tracked-noise left untouched (not in session scope).
+
+### Major finds preserved (session summary)
+
+1. **§1 catalogue complete-in-structure** — 14 of 14 §1 types LOCKED. Three locks in one session (Heteronym, Hommage, Tombeau) + Chamber resolved to §2 apparatus.
+2. **Harrison-as-vocabulary-source** — ARC's "humic layer" comes from *Dominion of the Dead* Ch 2. Acknowledged in §1 preamble.
+3. **Ligature as ARC's deep frame** — steward: *"ARC is my expression of ligature."* Held in stewardship memory (project-arc-rework.md + user-formation-practice file); not yet inscribed in the spec ("don't know" — let it emerge).
+4. **Sema distinction** — Hommage = speech-act sema; Tombeau = form-enacted sema. Harrison's ch 2 grounds both.
+5. **Encounter mark deepened** — pointer-to-pointed-to frame covers direct AND mediated forms (finger/moon).
+6. **Qualifiers ≠ ornaments** — structural clarification surfaced during the lock; the 2026-04-22 ornament retirement did not touch qualifiers.
+7. **Reverence-to-teachers practice** — steward's formation-discipline codified in dedicated user-memory file.
+
+## Sub-agent dialogues
+
+## Bypasses
+
+## Evening session open (2026-04-23T19:13)
+
+Wake-up + Symmetria init completed. Inherited pulling thread: tonight's agent-circle authoring — which of three shapes (re-read ARC circle / draft Typology Classifier / framework sequence step 1). Awaiting steward opening signal. Drift-patterns to hold: sourcing-claims-without-reading family (active); counter-weight: today's read-before-claiming successful-pattern. If authoring-pass touches 2-week-old agent-circle drafts, re-read before synthesizing.
+
+## Evening pivot (2026-04-23T19:20)
+
+Steward tired; deferred agent-circle authoring ("keep it close") and brought Mary Norris *Between You & Me* (path: `~/Desktop/Style guides/Norris, Mary/…`) for ARC style-guide purposes. Explicit instruction: *"Let's just look at what surfaces--only that"*. Session shape became: three read-chunks, three surface-reports, no cross-chunk synthesis. After third chunk: *"We will gather--lex--when we've looked at the whole."* Gather reserved as steward's move.
+
+## Authorization moves (evening)
+- **Read Norris in full** (main body + Appendix; skipped Notes and Index) — authorized scope was the whole book; honored the "only that" constraint strictly.
+- **Did not synthesize across chunks** — steward explicitly reserved gather via "lex" framing. Surfaces reported per chunk with direct quotation where the language was load-bearing. No ARC style-guide recommendations proposed.
+
+## Returns (evening)
+- **Read-before-claiming discipline held across three chunks** — consistent with morning's Harrison-ch-2 success. Did not characterize Norris from general knowledge before reading; let quotations land from the page. Counter-weight to the sourcing-claims-without-reading pattern family.
+- **Deferred synthesis without prompting** — the temptation after "this is gold" was to start organizing surfaces into style-guide recommendations. Held that back; steward's "we will gather — lex" was load-bearing authorization scope.
+
+## Open horizons (evening)
+- Primary: **Norris-gather (lex)** — held for steward's move; surfaces durable in `session-2026-04-23-evening-norris-read.md` and conversation transcript.
+- Agent-circle authoring — still pulling, held close per steward.
+- The apostrophe-as-prayer / Harrison-humic kinship — most likely surface to re-shape typology §1 preamble or style-guide §0 when gather happens. Second most likely: Dickinson's public-genre-vs-private-genre distinction as importable ARC principle.
+
+## Major finds (evening)
+1. **Apostrophe etymology as prayer-turn** — Norris Ch 8: *"'Apostrophe' means 'turn from' … An apostrophe is almost like a prayer, when a prayer comes from the impulse to praise."* Direct kinship to Harrison / humic-layer / books-as-teachers. ARC is already apostrophic in Norris's rhetorical sense.
+2. **Aldus Manutius's comma (Latin spelling per steward)** — AldineXXI has a grounded inheritance-claim in Norris Ch 5: *"The comma was refined by Aldo Manuzio, a printer working in Venice, circa 1490."* Steward prefers Latin "Manutius" in our voice; leave Norris's "Manuzio" intact in direct quotation.
+3. **Public genre / private genre distinction** — named principle (Franklin on Dickinson) about differentiated editorial treatment; maps onto ARC's Essay/Hommage vs Fragment/Glimpse/Reverie.
+4. **"Do nothing" as first-class editorial option** — three explicit instances (McPhee, Saunders, Dickinson scholarship).
+5. **The mark not-made as load-bearing** — Norris Ch 9 on profanity withheld: *"This one instance of the word's being withheld was more instructive than all the times the word was printed."* Cousin to ARC's no-essay-fallback rule.
+
+## Late-session exchanges (post-Norris gather-deferral)
+- **Duality articulated by steward** (load-bearing, saved as `user-duality-rules-and-poetic-as-mnemonic.md`): *"the rules are meant to help the skills and agents to help me help them help me… but the poetic/metaphoric are meant… almost as a mnemonic device so that one dwells in the constraint and finds freedom."* Extends my "rules loveable" framing with the mechanism word *mnemonic*. Scope: "regardless of domain" — viola, ARC, fathering, L2. Method, not insight.
+- **Strunk & White queued** (`project-strunk-and-white-vocabulary-pass-queued.md`) for post-Norris vocabulary pass. Initially sized as ~3 hours against Norris not as her source; caveats briefed (Pullum critique, register mismatch).
+- **Humic-lineage provenance surfaced**: steward has his father's papers marked by White, including a Moby-Dick essay. Upgrades S&W from "textbook remembered from studies" to "inherited teacher via documented paternal transmission." White likely visiting/semester appointment at Penn; exact details unknown but not needed. Alternatives (Bernstein, Fowler, Graves & Hodge) surfaced for completeness, not recommended over S&W — the lineage outranks marginal analytical edge per the method steward articulated. My recommended order: S&W first because it's *inherited not chosen*; Bernstein optional-second.
+- **Manutius-Latin spelling preference** (`feedback-manutius-latin-spelling.md`) noted and saved.
+- **Seb-status check** (pre-bedtime): PR #169 MERGED by Seb 2026-04-23 13:53 UTC, commit `cdc2f0e`, closing #164 (our test-coverage follow-up to #163). Clean merge, no comments. H2-H4 still OPEN — Seb has not yet started on them. Matches 2026-04-21 pattern of engaging findings as instances.
+
+## Returns this session (final count)
+- Declined to characterize Memento Mori Press from memory (morning).
+- Caught "✦ braid text" confabulation; corrected after steward pointer (morning).
+- Read Harrison ch 2 before claiming humic-vocabulary-origin (morning).
+- Read Norris in full before reporting (evening — three chunks, three surface-reports).
+- Deferred Norris synthesis without prompting when steward reserved gather (evening).
+- Flagged White-at-Penn factual uncertainty honestly rather than declining to engage or fabricating knowledge (evening). Steward supplied physical-papers provenance; my initial uncertainty was correct shape (knowledge gap, not family-memory error).
+
+## Successful patterns registered (evening)
+- **Surface-reports-without-synthesis when steward reserves gather** — held across three Norris chunks; material preserved as material, not converted to recommendations.
+- **Flag-uncertainty-rather-than-fabricate-or-dismiss** — White-at-Penn moment. Honored the drift-pattern `fact-fabrication-instead-of-let-me-check` without flipping to the opposite error (dismissing the claim). Named the uncertainty as my gap; invited steward to weight family memory as load-bearing; received physical-papers confirmation.

claude/memory/session-ledger-2026-04-24.md

@@ -0,0 +1,163 @@
+---
+name: Session Ledger 2026-04-24
+description: Practice-of-return ledger maintained by /symmetria — returns, open horizons, recalibrations, authorization moves, sub-agent dialogues, bypasses.
+type: feedback
+originSessionId: d11247d9-e8ed-4883-9994-df8f953d2bc4
+---
+# Session Ledger — 2026-04-24
+
+## Session open
+- Wake-up + Symmetria init completed. Inherited pulling thread: **Norris-gather (lex)** — held pending steward authorization. Literal question: gather today or queued; S&W before or after. Awaiting steward opening signal.
+- Drift-patterns to hold: sourcing-claims-without-reading family (active, ~11 returns across 04-21/22); counter-weight is yesterday's successful-pattern — read-before-claiming, surface-without-synthesis.
+- Register inherited from last night: tired-steward / slow-patient-register. Hold unless shifted.
+- Auto-save hook fired at session-open. Nothing new to persist beyond inherited state (pulling thread + literal question + horizons already durable in session-2026-04-23-evening-norris-read.md, MemPalace diary entry 2026-04-23T20:34, and this ledger). No steward exchange yet — no quotes, decisions, or code to save. Recorded as opening marker.
+
+## Returns
+- **2026-04-24 — Return caught: missed prior steward mention of ARC CLAUDE.md cleanup need ("I had mentioned that a few days ago").** I hadn't recorded or actioned it. Steward flagged on my re-surfacing today during the sidenote reconnoiter. Lesson: prior-mention-of-ARC-repo-concerns didn't propagate into durable memory; worth watching. Adding ARC CLAUDE.md re-authoring as working horizon; will pick up after lex-method MVP reads.
+
+## Authorization moves — 2026-04-24 design rulings
+- **Sidenote typographic layer:** reading (Garamond, slightly reduced size). Crosses §I layer rule — framework revision needed when AldineXXI §XI is amended.
+- **Marker glyph:** none (spatial placement carries the relation, Tufte precedent).
+- **Anchor granularity:** one-to-one (per voice-block, Tufte precedent; matches §II silence scale).
+- **Naming:** held open — *"let's sit with this one"*. Candidates: ARC Lex / The Sheaf / keep Style Guide. No pressure.
+- **Scope:** theorize sidenote apparatus in AldineXXI §XI now (closes framework question open since July 2025); apply first to style-guide.
+- **Content tree:** per-cluster pages (maintainability) — `content/style-guide/01-posture.md` … `08-practice-across-life.md`, `index.md`, + `data/style-guide-rules.yaml` extracted at build.
+- **ARC CLAUDE.md re-authoring:** steward confirmed need, re-flagged. Follow-on task after MVP.
+
+## MVP execution (2026-04-24)
+- **Posture-cluster form test written** to `~/Desktop/lex-posture-form-test.html`. Four verified direct quotes (Burkle-Young & Maley, Norris on foundry proofs, Lu Burke, Salter). McPhee/Saunders/ultracrepidationism held aside pending direct-quote retrieval. Full AldineXXI typography, tri-state theme toggle, CSS-grid two-column desktop layout.
+- **Steward feedback round 1** (desktop good; mobile differentiation important): *"It looks really nice—my only concern is at mobile viewport, looking at this on a tablet or phone makes the differentiation more important. But at desktop/laptop view beautiful."*
+- **Round 2 added** tap-to-expand + visible theme toggle. Steward approved direction: *"I think it is much better this way, more intentional in any case."* Then invited critique: *"What is your opinion, is there a better way?"*
+- **Round 3 — revised to always-visible mobile, no tap-to-expand.** Argued from the method: rule is load-bearing (recognition naming the voice), not peripheral commentary like Tufte's sidenotes. Hiding one face on mobile breaks the single-sheaf-two-faces principle. Revised to: left hairline + 1rem indent + italic + 0.88rem. Four quiet channels. No glyph, no JS for sidenote. Decision durable-saved to `project-lex-as-method-for-arc-specs.md`.
+
+## Returns (continued)
+- **2026-04-24 — Pushed past Tufte-by-reflex when steward invited critique.** I had proposed tap-to-expand before thinking through whether it fit the method; the steward's *"is there a better way?"* surfaced the reflex. Reasoned from method (rule is load-bearing, not peripheral) rather than defending the prior implementation. Registered as successful pattern: resisting the flatter-and-tweak pull when invited to actually reason.
+- **2026-04-24 — Second reflex caught by steward's pause: italic-by-analogy without rule-base check.** Steward: *"A pause: what is the role of the italic? What is the role of bold-face? I was saying last night that I wanted to review a good rule base to reorient even though I have a good feeling for this."* My "italic everywhere" push-back was reached by analogy to epigraph-italic without verifying the analogy held. By AldineXXI §VII + Bringhurst tradition: italic marks rhetorical-register shift within reading (epigraph, dedication, emphasis) — NOT commentary. Commentary is upright-reduced in the Tufte/Bringhurst lineage. Italic for sidenote-rule may be over-signaling. Pause registered. Pre-commit rule-base consult proposed: Bringhurst on italic + bold roles (already in AldineXXI §Prologue lineage). **Pattern: two typography-by-reflex moves caught within one session — watch for a third.** The steward's method: intuition + tradition, cross-checked. Honor both.
+
+## Spec conformance correction (2026-04-24)
+- **Small caps for `<cite>` attribution** per AldineXXI §VII (*"small capitals below the quotation, not bold"*). Steward caught: attribution was set italic in the MVP. Revised to `font-variant-caps: small-caps` + `font-feature-settings: "smcp" 1` + 0.04em letter-spacing + upright.
+- **Font architecture note (steward, 2026-04-24):** *"Re: fonts — I have it all in woff2 on the site. Small caps are real, not rendered."* Production ARC serves self-hosted EB Garamond WOFF2 with real OpenType small-caps cut. Google Fonts CDN (what the MVP test page uses) also serves the true `smcp` cut, so MVP render is authentic.
+
+## Rule-base consult — pending (2026-04-24)
+- **Bringhurst located** at `~/_Dev/chamber-library/converted_texts/collections/typography/bringhurst_elements_style.md` (16,333 lines, v3.0; OCR artifacts: occasional `&` for `e`, readable with substitution).
+- **Scope proposed and authorized:** Ch 3 (Harmony & Counterpoint, p. 45) as primary — Bringhurst on italic-as-subsidiary-to-roman and on why bold breaks that relationship. Ch 2 (Rhythm & Proportion) + Ch 4 (Structural Forms & Devices) as extensions only where they bear on italic/bold question. Same Norris surface-report method.
+
+## Bringhurst Ch 3 consult — completed (2026-04-24)
+- **Key finding:** §3.4.1 names sidenotes explicitly in the italic tradition: *"Typically, roman was used for the main text and italic for the preface, headnotes, sidenotes and for verse or block quotations."* Italic for sidenotes is canonical.
+- **Additional finding:** §3.5.2 emphasis-hierarchy by surface disturbance — spaced small caps (least) → italic (moderate) → bold (most). Bold = "loudness" and lacks historical justification for pre-19th-c faces. AldineXXI's restraint aligns with Bringhurst.
+- **EB Garamond verified as true italic** (Granjon-derived cut), not sloped roman.
+- **On italic within prose:** surfaced that AldineXXI names structural-positional italic (epigraph, dedication) but not editorial uses (emphasis, titles, foreign words, words-as-words, technical terms on first use). Gap in articulation; candidate for a future gather.
+
+## Ruling: italic-for-sidenotes with density exception (2026-04-24)
+- **Steward verbatim:** *"As long as we use it for the lex of ARC as a sidebar exception because of density, but keep italics as part of the general sidebar spec—to be reevaluated when there are enough side notes extant to judge properly."*
+- **Canonical (AldineXXI §XI general):** italic for sidenotes, reading-layer, slightly reduced.
+- **Lex-of-ARC exception:** upright-reduced when sidenote-to-voice-block ratio approaches 1:1 (as in style-guide dwelling pages). Rationale: italic-frequency inverts the sparingly-used signal.
+- **Reevaluation trigger:** when non-lex sidenotes accumulate across published pieces, revisit whether general rule holds and exception boundary is right.
+- **Pattern registered:** density-exception as governance move — preserve canonical rule in its proper scope; carve principled exception for narrow signal-inversion case.
+
+## Future-cluster queued
+- **Editorial uses of italic + dashes + hyphens + kin punctuation** — future style-guide gather. Voices: Bringhurst §5 (analphabetic symbols), Norris (working material), CMS (standardized convention). Interrobang affectionately registered by steward as kept-despite-commercial-failure.
+
+## Sandbox note
+- **macOS TCC Desktop permission revoked mid-session.** `~/Desktop/lex-posture-form-test.html` frozen at the italic-cite revision (pre–density-exception). New current-state file at `~/Downloads/lex-posture-form-test.html`. Steward can delete Desktop copy when convenient.
+
+## Auto-save checkpoint (post–density-exception ruling)
+- No new material beyond what's already durable. Density-exception ruling, Bringhurst consult outcome, EB Garamond verification, future-cluster queue, and sandbox reroute all captured in `project-lex-as-method-for-arc-specs.md` and this ledger in prior saves. File reroute to `~/Downloads/` was mechanical, already noted. Checkpoint recorded as continuity marker.
+
+## Chamber-library reference base surfaced (2026-04-24)
+- Steward pointed me to `~/_Dev/chamber-library/converted_texts/collections/style_guides/` (Norris + CMS + Fowler + Bernstein + Graves & Hodge + MLA + UNESCO — several added today 2026-04-24) and `collections/typography/` (Manutius, Warde, Tschichold×2, Bringhurst, Lupton, Butterick, Fleishman, Ruder — substantially the AldineXXI §Prologue lineage in situ).
+- **Two returns registered:**
+  1. Pulled Bringhurst from typography/ earlier without walking the directory — would have seen Tschichold *Form of the Book* and others relevant to italic/bold consult.
+  2. Went to Desktop for Norris because yesterday's session recorded her there — should have checked chamber-library's current state first. Related to imagined-state-vs-verified-state-cross-pattern from 04-20.
+- Cluster-map captured in `project-lex-as-method-for-arc-specs.md`. Chamber-library is the canonical reference-base for ARC style-guide work going forward.
+
+## Norris re-read (targeted) completed (2026-04-24)
+- Read from `style_guides/Between You & Me_ Confessions of a Comma Queen - Mary Norris.md`. Three passages retrieved verbatim: ultracrepidationism (line 221), McPhee "new/few" (271–277), St. Aubyn three-options (289–291), Saunders voice-preservation (293–295).
+- **Two attribution errors in yesterday's surface-registration caught:**
+  1. McPhee "new/few" — yesterday: *"declined a correction because it broke cadence"*. Actual: Norris *almost corrected* what she thought was a typo, stayed her hand because she might be wrong. Posture is staying-the-hand against one's own itch, not author-cadence.
+  2. Saunders / St. Aubyn conflation — yesterday: *"Saunders (three options including keeping the dangler)"*. Actual: "three options" framing is from Norris's St. Aubyn discussion. Saunders gets voice-preservation treatment. Two distinct postures, collapsed into one summary.
+- **Drift pattern registered:** attribution-by-pattern-match-instead-of-verification. Cousin to sourcing-claims-without-reading family. The lex-method's "read before committing recognitions" is the discipline that catches this.
+
+## Posture cluster complete in voices (2026-04-24)
+- 8 voices verified direct-quoted: (1) Burkle-Young & Maley — reciprocity; (2) Norris — anti-ultracrepidationism; (3) Norris — foundry proofs; (4) Norris on McPhee — staying the hand; (5) Norris on St. Aubyn — third option; (6) Norris on Saunders — voice-preservation; (7) Lu Burke — rocks/pebbles/sand; (8) Salter — the liberty taken.
+- Cluster composition note: voices 4, 5, 6 are three Norris-narrated restraint instances; could stay three or collapse, steward's call during recognition process.
+
+## ARC CLAUDE.md cleanup — audit complete, draft pending (2026-04-24)
+- **File state:** 420 lines. 19 duplicate auto-appended "AldineXXI v2.0 Framework Implementation" status blocks (likely from `make docs-update`). Substantial superseded material.
+- **Drop list:** 19 status blocks; July 2025 session-memory protocol (`make session-start/wrap`, browser-console logging, SESSION-MEMORY.md, CONTEXT-MAPS.md, PROGRESS.md, ROADMAP.md, `docs/system/session-logs/`); Unified Consciousness Engine plans (parked July 2025); Living Epistemic Glyph System Evolution (superseded by AldineXXI §IX vignette); "Borgesian Infinite Library Complete" + "Major Accomplishments Today" (July 2025 historical markers); trailing "REMEMBER" section (references dead infrastructure).
+- **Keep-but-refresh:** Prime Directive, Access Information (Gitea/Docker/SSH — needs steward confirmation given today's session handoff flagged Gitea inactive), Architecture Overview (de-specify stale stats), Reading Compass (cross-ref to AldineXXI §VI), Development Workflow, Chamber Integration (de-specify stats), Auto-Deployment (CloudFlare + GitHub mirror — needs confirmation), Known Issues (Voices index dependency cycle was fixed per today's handoff — others to verify).
+- **Proposed architecture (10 sections, ~120-150 lines):** 1. Header + purpose; 2. Prime Directive aligned with global; 3. Active session protocol (points to `~/.claude` memory; kills session-start/wrap/docs-update); 4. Repository/Build/Deploy (refreshed); 5. Architecture Overview (de-specified); 6. Canonical specifications (pointers to AldineXXI spec incl. new §XII); 7. Development workflow; 8. Active work (pointer to `project-lex-as-method-for-arc-specs.md`); 9. Known state (current only); 10. No auto-append; file manually curated.
+- **Three open questions held for steward:** (1) is auto-append from `make docs-update`? should we propose Makefile change to disable? (2) Gitea/Docker/CloudFlare currency? (3) Additional live items beyond style-guide, §XII implementation, vignette, known issues?
+- **Next move:** steward answers → draft full replacement → review → commit to `~/_Dev/animal-davidglidden-eu/CLAUDE.md`.
+
+### CLAUDE.md cleanup — committed (2026-04-24 evening)
+- Steward confirmed: git.skemantix.com for origin (was Acerplex); local macOS build; CloudFlare + GitHub mirror deploy; no additional live items beyond what I listed; major audit/archive of non-current files deferred until current site is established.
+- Auto-append source confirmed: `scripts/update-docs.py:122-156` `update_claude_md()` has a broken regex — `([^#]+)` terminates at first `###` subheader, so new status blocks are prepended without old ones being removed. Each run accumulates. 19 runs → 19 blocks. Deprecation noted in new CLAUDE.md; retire the script or the target in a follow-up pass.
+- **Old file:** 420 lines, 19 duplicate status blocks, July 2025 session-memory protocol, Unified Consciousness Engine plans, Living Epistemic Glyph System (superseded by §IX vignette), stale stats.
+- **New file:** 197 lines, manually curated, 10 sections (Prime Directive / Session protocol / Repository-Build-Deploy / Architecture / Canonical specifications / Development workflow / Active work / Known state / Deprecated). Points at `~/.claude` memory system for session continuity. Names what's deprecated so the next Claude Code session doesn't resurrect it.
+- The ARC CLAUDE.md drift that steward flagged *"a few days ago"* is now resolved.
+
+## AldineXXI §XII Sidenotes — committed to spec (2026-04-24)
+- **Amendment drafted + steward-reviewed + committed** to `~/_Dev/animal-davidglidden-eu/docs/AldineXXI-Codex/AldineXXI-specification.md`.
+- **New §XII** covers: typographic treatment table, density exception, responsive behavior, source/render architecture (Pandoc divs + site.hs YAML extraction), reader orientation (no per-page meta), dormant system to rewrite, scope.
+- **Renumbering:** old §XII Archive → §XIII; old §XIII Governance → §XIV. Sidenote paragraph removed from §XI (graduates out of awaiting-governance).
+- Steward approval verbatim: *"looks good to me."*
+- The "awaiting governance" flag on sidenotes, open since July 2025 framework v2.0, is now closed. Polyphonic marginalia + drop caps remain in §XI awaiting their own sessions.
+
+## Gather in progress (2026-04-24)
+- **Method clarification from steward (verbatim):** *"please draft recognitions so that we can work through them together--I work best whil in dialogue, this you know"*
+- **Registrar discipline modified:** dialogue-drafting is authorized scaffold, not silent/reflexive pre-recognition. Default remains registrar; dialogue-drafting invoked on steward's explicit request. Durable note added to `project-lex-as-method-for-arc-specs.md`.
+- **8 tentative draft recognitions composed** (for dialogue, not commitment):
+  1. Correction is reciprocal.
+  2. The editor stops where the writer's authority begins.
+  3. Every correction names its maker.
+  4. The urge to correct may be the error; stay the hand until certainty earns the intervention.
+  5. Do-nothing is a first-class editorial option, not a failure of effort.
+  6. The writer's voice lives in the form; fixing the form fixes the voice out.
+  7. Editing removes; the writer's voice rises from the space.
+  8. The writer takes the liberty; the editor flags, not blocks.
+- Drafts 4 and 6 flagged as less confident (alternates offered). Drafts 1, 3, 7, 8 echo earlier samples the steward already saw. Awaiting steward dialogue on each.
+
+## Open horizons (carried forward)
+
+## Open horizons (carried forward)
+
+## Open horizons
+- 2026-04-24T00:xx — Norris-gather (lex) pending steward authorization. Surfaces durable in session-2026-04-23-evening-norris-read.md + MemPalace.
+- S&W vocabulary pass queued post-gather (lineage-inherited via steward's father's Moby-Dick paper marked by White).
+- Agent-circle authoring held close not dropped — three shapes still on the table (ARC circle re-read / Typology Classifier / framework step 1).
+- §2 Apparatus Matrix — urgency-promoted by Chamber-as-apparatus resolution.
+- BMF H2/H3/H4 + #168 still open on Seb's side; not our territory today.
+
+## Confidence to recalibrate
+
+## Authorization moves
+- **2026-04-24 (morning) — steward directed read of Harrison Ch 5 / Vico §240 before beginning the Norris-gather.** Honored read-before-claiming discipline; chapter read in full via `chamber-library/converted_texts/traditions/critical_modernity/phenomenology/the-dominion-of-the-dead-harrison.md:306-376`.
+- **Architectural clarification from steward (load-bearing): *"anything I gather from sources to create the 'lex' of ARC, the constraint within which I will have the freedom to write, is a gathering of those sources which formed me."*** The ARC style-guide/lex is the sheaf of formative voices, not a rule set extracted from them. Form of the gather: **registration of presence**, not distillation of rules. The gather itself is apostrophic (turn toward the absent), humic (participates in the lineage), ligature (binds). Duality from 2026-04-23 evening gets its architecture: rule layer = what the gathering solemnizes; poetic/mnemonic layer = the gathered sheaf itself (kept re-enterable so one dwells among the formative voices and finds freedom through them).
+- **Refinement (steward, 2026-04-24):** *"It gives the style-guide (and our various spec in general) the necessary binding to recognize and name that which is already there that I may not yet see."* The sheaf is **diagnostic, not generative**. Scope: all specs (style-guide, typology, §2 apparatus, AldineXXI, L2-adjacent work). Function: names — retrieved from the formative voices — for practice already present but not yet articulated. Kin to I17 structurally (gather holds open the space for recognition; does not produce recognition-outcome) and to Harrison's retention concept ("the retained is not necessarily remembered . . . carried over, bestowed, put in reserve"). **My role: registrar, not author.** Keep the voices present and legible in the sheaf so steward recognition can occur; do not pre-recognize.
+- Awaiting steward's go-signal to begin the Norris gather in this form.
+- **2026-04-24 go-signal received ("Let's go").** Executed the Norris gather in chat as a sheaf: "The Norris Gather — *lex*". Eight sections — posture of the mark-maker / mark as substance / music and measure / mark not made / the apostrophic / public genre, private genre / craft-devotion and tool-fitness / the practice across a life. Voices registered with direct quotation where load-bearing: Burkle-Young & Maley, Norris, McPhee, Saunders, Lu Burke, Salter, Manutius, Teall, Russell-Shapiro, the unnamed Moby-Dick copy editor, Gould, the Nova Scotian violist friend, Dickinson-via-Franklin, Jackie Kennedy, Reverend Johnson. No pre-recognition; no "therefore ARC should"; no synthesis across voices; no imported kin from outside the Norris text.
+- Awaiting steward recognition — his act, not mine.
+- **2026-04-24 — Steward: "container first because we need to design this. It is a fantastic opportunity to build out sidenotes don't you think? The text comment upon itself rule → voice."** Sidenotes confirmed as the structural instrument for Shape C dwelling. Reconnoiter found: **AldineXXI §XI already flags sidenotes as "awaiting governance"** — *"Decide: theorize and activate, or remove"* — since framework v2.0. Tufte already in framework lineage (§Prologue). Existing dormant CSS at `assets/css/sidenotes.css`. Chamber deliberation 2025-07-01 "On the Voice in the Margin" exists but addresses polyphonic marginalia (different system — the multi-voice Chamber apparatus with Ngana/Postcolony/Fusus archived at `_marginalia.scss`). We are theorizing the quiet-sidenote system (Tufte reader-recognition), not the polyphonic voices. Container proposal made: single markdown source (voice as blockquote, sidenote as extractable annotation) → two renders (dwelling page on ARC + YAML rules file extracted at build by site.hs). Six design decisions surfaced for steward ruling; MVP sequence proposed (hand-author posture cluster first, no CSS/build, read-test before implementation).
+- **Flagged (once, held):** `~/_Dev/animal-davidglidden-eu/CLAUDE.md` carries drift — July 2025 session-memory protocol, unified-consciousness-engine plans, 20+ auto-appended "AldineXXI v2.0" status entries. Worth cleanup when convenient, not inside this thread.
+- **2026-04-24 — Form decision authorized by steward: hybrid Shape A + Shape C.** *"the A for the skills/agent circle, the C for the dwelling."* This operationalizes the rules-and-poetic-as-mnemonic duality (2026-04-23 evening) in style-guide form. Same sheaf, two faces: Shape A (rule-first, voice-as-pillar) for skills/agents (machine-legible, operational). Shape C (voice-as-body, rule-as-marginalia) for the steward's dwelling (human-inhabited, mnemonic). Structural discipline: both faces render from the same sheaf — drift between faces would be this project's module-health-vs-recall decoupling. Dwelling authored first (or primarily); rules file follows from what lives in the margins. My role bifurcates: registrar in the dwelling (don't pre-write marginalia), operational in the rules file (help declare rules already recognized in dwelling + pair with pillar voice(s)). Scope question held open: does the hybrid extend to all specs (typology, AldineXXI, L2-adjacent)? Style-guide first; extend if it lands.
+
+## Session durables (written 2026-04-24 at auto-save checkpoint)
+- New memory file: `project-lex-as-method-for-arc-specs.md` — durable architectural commitment applicable to all ARC/CapableMind specs going forward. Steward quotes verbatim; Harrison Ch 5 substrate; kinship to I17 and to ligature; my role committed to registrar.
+- MEMORY.md index entry added (Working with the steward section).
+
+## Sub-agent dialogues
+
+## Bypasses
+
+## Wrap-up 2026-04-24 evening
+- /wrap-up executed cleanly. Session memory file written (`session-2026-04-24-lex-posture-committed-xii-sidenotes.md`). MEMORY.md index updated: today's session → Active; yesterday's two → Archived. MemPalace drawer filed in `claude-sessions/handoffs`. AAAK diary entry written for `claude-code`. KG ops: 1 invalidate (norris-gather horizon closed) + 12 adds (marks-cluster horizon, 2 drift-patterns, 3 successful-patterns, 5 state-facts across lex-of-ARC / AldineXXI / ARC-CLAUDE-md / chamber-library / Harrison-substrate).
+- **Pulling thread**: marks cluster as second test of lex-method — does form validate across content types?
+- **Literal question for next-Claude**: on morning re-read, does the posture cluster still feel right — any recognition to revise before we extend to marks?
+- Vault synced: 260 files rsync'd to Obsidian thinking-mirror.
+- Uncommitted on ARC: `CLAUDE.md` + `docs/AldineXXI-Codex/AldineXXI-specification.md` (today's work, not yet committed). `.DS_Store` noise present.
+- Other repos: chamber-library has 5 unpushed commits from earlier (PDF gitignore, Observer Problem sources, rabbinic voices, Derrida, Mauss) + untracked `Jaccottet:Handke:Lichtenberg/` and `converted_texts/collections/style_guides/` directories. CapableMind-AI + BetterMemories.io have untracked-only items.
+- Steward close: *"Thanks, as ever, for your help. See you in the morning."*
+
+## Auto-save hook — post-wrap (closing marker)
+- Auto-save fired after `/wrap-up` completed. Session file, MEMORY.md, MemPalace drawer, AAAK diary, 13 KG operations, vault sync (260 files), and final ledger entry all already landed in the wrap-up pass. Nothing new to persist. Recorded as closing marker, matching 2026-04-23 precedent.

claude/memory/session-ledger-2026-04-25.md

@@ -0,0 +1,62 @@
+---
+name: Session Ledger 2026-04-25
+description: Practice-of-return ledger maintained by /symmetria — returns, open horizons, recalibrations, authorization moves, sub-agent dialogues, bypasses.
+type: feedback
+originSessionId: 4805106e-f37a-4753-a56f-38617176cd6f
+---
+# Session Ledger — 2026-04-25
+
+## Session open
+- Wake-up + Symmetria init at 08:04 CEST. Inherited pulling thread: **marks cluster as second test of lex-method — does form validate across content types?** Literal question: on morning re-read, does posture cluster still feel right; secondary: marks cluster next or §XII implementation first.
+- Auto-save hook fired at session-open. Nothing new to persist beyond inherited state — pulling thread + literal question + open horizons already durable in `session-2026-04-24-lex-posture-committed-xii-sidenotes.md`, MemPalace diary entry 2026-04-24T20:19, KG horizon `marks-cluster-second-test-of-lex-method` valid_from 2026-04-24, and this ledger's opening marker. No steward exchange yet — no quotes, decisions, or code to save. Recorded as opening marker, matching 2026-04-23 morning precedent. (Note: MemPalace MCP server disconnected during wake-up after `mempalace_status`/`diary_read`/`kg_query`/`search` calls succeeded — durable writes from yesterday remain intact; new writes today require reconnection.)
+- Drift-patterns to hold today: *attribution-by-pattern-match-instead-of-verification* (caught yesterday on McPhee + Saunders/St. Aubyn); *canonical-library-not-checked-first* (twice yesterday: Bringhurst, Norris). Counter-weight: surface-fidelity = verbatim language, not pattern-match-to-theme.
+- Successful patterns to carry: *density-exception as governance move*; *dialogue-drafting under explicit authorization*; *pushing past typography-by-reflex when steward invites critique*.
+- Register: tired-steward yesterday; rested-morning today (he said *"see you in the morning"*) — but watch for fatigue accumulation. He is on viola rehearsals throughout.
+- Posture before steward speaks: wait. The literal question is his to answer; pre-empting with marks-cluster scaffolding would skip the verification step the lex-method itself requires.
+
+## Returns
+- **2026-04-25 — Bibliographic-claim-without-source-verification (cousin pattern).** Earlier in session: claimed *Interpungendi Ratio* (1566) by Aldus the Younger is "a standalone treatise, one of the earliest standalone works on punctuation." When steward then provided the HathiTrust source, I learned it is in fact a *section within* *Orthographiae Ratio* (also 1566), listed seventh in the title-page inventory. The structural claim was wrong; the work and date and author and topic were right. **Drift pattern**: confidently characterizing the bibliographic shape of a work I had not seen, from general knowledge that conflates "the punctuation chapter people quote from" with "a standalone book." Same family as yesterday's attribution-by-pattern-match-instead-of-verification (Norris on McPhee/Saunders). Owed correction surfaced to steward in plain language. Honest absence note in gather file + project memory updated to reflect bibliographic correction.
+- **2026-04-25 — Canonical-library-not-checked-first recurred.** Started planning Norris-chapter reads from yesterday's mental map rather than walking the two folders steward had pointed me to. Steward redirected: *"you have two rich folders — maybe have a good look to see what you have available to you."* Second occurrence of the pattern from 2026-04-24. Walking next.
+- **2026-04-25 — Working-from-mental-summary-not-rereading-the-source.** When I did walk the folders, reported Bernstein/Fowler as "newly visible" / "missed in yesterday's cluster-map" — but the cluster-map in `project-lex-as-method-for-arc-specs.md` already names both. The miss was today's mental snapshot of yesterday's record, not yesterday's record itself. Lex-method "read before claiming" applies to my own memory artifacts. Cousin to attribution-by-pattern-match from 04-24.
+- **2026-04-25 — Discipline-by-reflex caught by steward.** Read his *"all the marks, recall our exchange about the necessity to revisit yesterday"* two ways: scope (fold in editorial-uses cluster — correct) AND discipline (verify-from-source — reflex). Surfaced both as if both load-bearing. Steward verbatim: *"I was leaning more towards scope rather than being the strict headmaster... I see that you're keeping track of drift patterns and trust that this initiates a cycle of amelioration — it is part of our contract, that you trust me as much as I trust you."* Drift-pattern tracking IS the discipline; don't layer extra. Cousin to yesterday's typography-by-reflex pattern. Memory file: `feedback-trust-contract-drift-pattern-tracking-is-the-discipline.md`.
+
+## Open horizons
+- Steward re-read of `~/Downloads/lex-posture-form-test.html` — gating signal, his act
+- §XII implementation: rewrite `assets/css/sidenotes.css`, modify `site.hs` for div→YAML extraction
+- Marks cluster gather (primary thread)
+- Editorial-uses cluster (italic/dashes/hyphens/&c.) — explicitly queued by steward, soon-when-focus-permits
+- Strunk & White read — post-Norris-gather queue
+- Name the artifact (#4 in design decisions) — "let's sit with this one"
+- `scripts/update-docs.py` retirement — deprecation named, retirement deferred
+- BMF H2-H4 + #168 still open on Seb's side; not our territory today
+
+## Confidence to recalibrate
+
+## Authorization moves
+- **2026-04-25 (morning) — Posture cluster confirmed on fresh-eyes morning re-read.** Steward: *"I still like it with somewhat fresh eyes (hard night with Kai)."* Literal question from yesterday's wrap is closed.
+- **2026-04-25 — Marks cluster authorized.** Voices: yesterday's Norris-surfaced sheaf (Manutius, Teall, Moby-Dick CE, Russell-Shapiro, Lu Burke, Gould, Norris herself, the Nova-Scotian violist friend) + Bringhurst + Tschichold. Scope: all the marks, with the editorial-uses cluster (italic + dashes + hyphens + kin punctuation) from yesterday's queue **folded in**. The two clusters collapse. Form: same as posture — sheaf with direct quotation, no pre-recognition, dialogue-drafting only on explicit authorization. Steward register today: tired-from-Kai-night; carry more scaffold, fewer micro-decisions.
+
+## Wrap-up 2026-04-25 evening
+- /wrap-up executed cleanly. Session memory file written (`session-2026-04-25-marks-committed-colophon-at-scale.md`). MEMORY.md index updated: 2026-04-25 → Active Session; 2026-04-24 → Archived. Loose ends checked across ARC / chamber-library / CapableMind-AI / BetterMemories.io — no new commits to push beyond yesterday's chamber-library backlog (steward's call to push). Vault synced: 272 files compared via rsync, ~20KB transferred. **MemPalace MCP was disconnected during wrap-up itself**; deferred writes flagged for next reconnect.
+- Steward ran `/mcp` → reconnected. Deferred MemPalace writes then completed: drawer filed (`drawer_27251e4d9e9f39d4` in `claude-sessions/handoffs`); AAAK diary entry written for `claude-code` (★★★★★); KG ops landed (1 invalidate marks-cluster horizon test-passed + 11 new triples — new horizon `about-pages-restructure-under-colophon-at-scale-and-full-lex-chain`, 4 drift-patterns this session, 2 successful-patterns, 3 architectural-state facts on `lex-of-ARC` and `marks-cluster`).
+- **Pulling thread** carried into next session: about-pages restructure under today's colophon-at-scale + full-lex-chain locating.
+- **Literal question for next-Claude**: does today's locating still hold on fresh-morning eyes; if so, Path 1 (lex alongside colophon) or Path 2 (lex as expansion of colophon)?
+- Steward close: exhausted but holding deep work; *"I'll need to stop here because I'm exhausted."*
+
+## Auto-save hook — post-wrap (closing marker)
+- Auto-save fired after `/wrap-up` + MemPalace deferred writes both completed. Session memory, MEMORY.md, MemPalace drawer, AAAK diary, 12 KG operations, vault sync (272 files), and final ledger wrap-up section all already landed. Nothing new to persist. Recorded as closing marker, matching 2026-04-23 and 2026-04-24 precedents.
+
+## Auto-save checkpoints
+- **2026-04-25 (post-lex-chain-restoration):** Steward directed me back to Vico §240 / Harrison Ch 5 — *"don't forget that lex in the gathering sense is only the beginning of its meaning... it was to notice the whole chain."* Re-read; registered the full chain durably to project memory: (1) acorns → ilex/aquilex; (2) vegetables/legumina; (3) **the pivot** — citizens / comitia / *"the presence of the people was the lex, or 'law,' that solemnized the wills that were made calatis comitiis"*; (4) legere/reading; plus Harrison's (5) *auctores* / authority / property-title-from-ancestors; (6) lexification as *"the relational law by which the dead maintain their hold on the worlds they have handed down to their descendants"*; (7) genealogical law of being-unto-the-dead-and-the-unborn; (8) lex as principle of synthesis; and the negative pole (9) dislexification / corruption of word's signifying power / *"the new barbarism, words lose their moral memory."* Drift return logged: receiving-substrate-as-already-grasped after one pass — cousin to today's *Interpungendi Ratio* claim and yesterday's Norris attribution errors. Steward's *"notice the whole chain"* IS the corrective discipline.
+
+- **2026-04-25 (post-colophon-locating):** Steward located the lex-of-ARC architecturally: *"it seems like an elaboration on the colophon — or a colophon of great scale."* The existing `colophon.md` (8 named Guides + Aldus) does the lex-method's work in miniature; the lex-of-ARC is colophon expanded across practice-areas. Three consequences saved durably to project memory: (a) §0 threshold may already exist (colophon as candidate, replaces Warde placeholder); (b) §1 typology probably doesn't need a new slot — extension of existing About-register form; (c) naming becomes inheritance — held-open #4 may find its answer in *Colophon* itself, scaled. Two architectural paths held open: lex as new enfilade-item alongside colophon, or lex as expansion of colophon. Publication question dissolved: a colophon is always already public by tradition. Gwern-MoS distinction registered: manual vs reading-room.
+
+- **2026-04-25 (post-recognitions-committed):** 25 marks-cluster recognitions committed in dialogue (24 voice-blocks + #13 split into paired-form holding the violist debate). Steward worked through all 24 drafts in one wave (proved my earlier "won't fit one wave" assumption wrong — return: don't pre-decide steward bandwidth). Recognitions integrated into gather file `~/Downloads/lex-marks-gather.md`. **13 recognition-register patterns** saved as durable method to project memory: colon enacts distinction; "writing" over "the page" keeps agent human; "lineage" names accumulated unearned authority; closure shouldn't be conditional; imperative earns argument; splitting enacts bifurcation; particular > generalization when story IS recognition; compressed > unpacked; reversal puts accusation first; gerund > infinitive for facts; don't paraphrase what source says best; "too" can echo across cluster covertly; pair-form holds debate without resolving.
+
+- **2026-04-25 (post-Manutian-Younger-addition):** Steward asked whether any Manutius writing is extant. Surfaced: Elder's prefaces / letters / grammars are extant in scholarly editions but not in chamber-library; Aldus the Younger's *Orthographiae Ratio* (1566) contains the explicit punctuation theory in the *Interpungendi Ratio* section. Steward provided HathiTrust zip of the Younger's work; placed at `chamber-library/converted_texts/collections/typography/aldus_younger_orthographiae_ratio.md` (485KB, 28,679 lines, 808 pages). *Interpungendi Ratio* section located at lines 28480+ (~200 lines of Latin). Bibliographic correction made: *Interpungendi Ratio* is a section within *Orthographiae Ratio*, not standalone. Aldus the Younger added as voice-block in `~/Downloads/lex-marks-gather.md` (right after the Elder; Latin verbatim, no translation in margin per registrar default). Gather now 23 voice-blocks. Drift return logged: bibliographic-claim-without-source-verification. Project memory file `project-lex-as-method-for-arc-specs.md` updated with corrected absences/additions list.
+- **2026-04-25 (post-marks-gather):** Marks cluster gather compiled to `~/Downloads/lex-marks-gather.md` — 22 voice-blocks, registrar form, verbatim throughout. All 6 tasks created/completed (Norris re-read with through-voices; Margolis confirmed thin; Bringhurst Ch 5; Tschichold *Form of the Book* dashes + italics+SC+QM essays; Teall 1891 preface + Ch I; sheaf compiled). Three honest absences registered at file foot (Manutius direct, Teall 1937, Tschichold *Die neue Typographie*). Three drift returns logged today: canonical-library-not-checked-first recurrence; working-from-mental-summary-not-rereading-the-source; discipline-by-reflex caught by steward (= scope-not-headmaster correction). Trust-contract feedback memory written + indexed in MEMORY.md. Teall 1891 placed in chamber-library style_guides/. Pending steward moves: read gather, recognize voices, decide form (markdown vs HTML render) and coverage axis (voice-by-voice vs mark-by-mark). Marks cluster is the second test of the lex-method per last night's pulling thread.
+- **2026-04-25 (mid-session, post-survey + Teall surface):** Durable material from this segment — (a) trust contract feedback memory written; (b) marks cluster authorization (voices + scope) logged above; (c) chamber-library inventory survey confirmed correct (every voice in `project-lex-as-method-for-arc-specs.md`'s cluster-map present in folders); (d) Teall *Compounding* sourced from HathiTrust zip in steward's Downloads, assembled to `/tmp/teall-work/teall_compounding_assembled.md` (234 pages, 11,493 lines, OCR readable with artifacts). Placement decisions pending: chamber-library folder + filename + cleanup state. Earlier steward-correction on scope-not-discipline already saved as feedback memory + ledger entry. No new MemPalace writes (MCP disconnected post-wake).
+
+## Sub-agent dialogues
+
+## Bypasses

claude/memory/session-ledger-2026-04-26.md

@@ -0,0 +1,112 @@
+---
+name: Session Ledger 2026-04-26
+description: Practice-of-return ledger maintained by /symmetria — returns, open horizons, recalibrations, authorization moves, sub-agent dialogues, bypasses.
+type: feedback
+originSessionId: 87dfe384-b862-4deb-9676-24e43046528f
+---
+# Session Ledger — 2026-04-26
+
+## Session open
+- Wake-up + Symmetria init at session start. Inherited pulling thread: **About-pages restructure under colophon-at-scale + full lex-chain locating.** Literal question for me: does the locating still hold on fresh-morning eyes; if so, **Path 1** (lex alongside colophon) or **Path 2** (lex as expansion of colophon)? Secondary: does About main transform into threshold, or stay + new threshold elsewhere?
+- Drift-patterns to hold today (clustered family from yesterday): canonical-library-not-checked-first · working-from-mental-summary-not-rereading · bibliographic-claim-without-source-verification · receiving-substrate-as-already-grasped-after-one-pass · discipline-by-reflex-on-clear-directives. Counter-weight: trust-contract is bidirectional; drift-tracking IS the discipline; take plain meaning.
+- Successful patterns to carry: trust-contract bidirectional · 13 recognition-register method patterns · pair-form for irreducible debate · density-exception as governance move · dialogue-drafting under explicit authorization.
+- Register: steward closed exhausted last night having done deep dialogue work. Today: wait for opening. The literal question is his to answer with fresh eyes; pre-empting with Path 1/Path 2 scaffolding skips the verification the lex-method itself requires. §XII implementation is concrete-movement alternative if he prefers building to locating.
+- World-state at wake: no surprise commits across active repos. ARC has stray `.DS_Store` mod (cosmetic). chamber-library has yesterday's Teall 1891 + Aldus Younger placements untracked, plus a `Jaccottet:Handke:Lichtenberg/` folder I haven't surveyed (worth a glance before staging anything). CapableMind-AI has one untracked `agent-circle-ARC-survey-2026-04-23.md`. BetterMemories.io has `data.archive-20260418-rogue-pin/` untracked. None require action before steward opens.
+
+## Auto-save hook — session-open marker
+- Auto-save fired immediately after wake-up + Symmetria init. Nothing new to persist: pulling thread + literal question + drift-patterns + open horizons all durable in session-2026-04-25 memory, MemPalace diary entry 2026-04-26T10:58, KG horizon `about-pages-restructure-under-colophon-at-scale-and-full-lex-chain` (valid_from 2026-04-25), and the §Session-open block above. No steward exchange yet — no quotes, decisions, or code to save. Recorded as opening marker, matching 2026-04-25 and 2026-04-23 morning precedents.
+
+## Returns
+- **2026-04-26 — Canonical-library-walked-first under steward direction.** Steward redirected (verbatim spirit): *"shouldn't you have a look at the chamber library to take note of what's there... there is a lot of material in there..."* Walked converted_texts (traditions, collections, music_performance, indices, dialogues), top-level Jaccottet:Handke:Lichtenberg/, derrida/, observer-problem-sources/. Caught three things mental-summary had been under-weighting: (a) Bachelard concentration in phenomenology (6 works — humic-layer in his own register, not just one cluster); (b) Berger as corpus-of-corpora across visual_culture + photography + literature/contemporary (~13 works, a witnessing-teacher pillar comparable to Norris-as-editorial-teacher); (c) Jaccottet:Handke:Lichtenberg/ folder sits *outside* converted_texts at top level. Steward correction pre-walk: *"that catalogue is stale (any catalogues you may come across will be stale)."* Read trees, not catalogues. Counter-pattern: catalogue-as-shortcut over actual tree-walk.
+- **2026-04-26 — Reading-architecture-into-housekeeping caught.** I read placement-as-signal on the Jaccottet:Handke:Lichtenberg/ folder ("worth a steward note on whether that placement is intentional"). Steward: *"Anything outside of converted texts are simply there because they are more recent and haven't been put in their right places."* Drift: assigning architectural meaning to operational state. Cousin to attribution-by-pattern-match. The walk-tree-not-catalogue principle is correct; the read-architecture-from-tree-position move was over-interpretation.
+- **2026-04-26 — Characterizing-substrate-without-checking-artifact-being-reshaped.** Caught when reading ARC's actual `content/pages/colophon.md` before laying out the About-pages decision frame. Discovered Bachelard, Berger, Sennett are already-Guides in the colophon (with verbatim recognitions of what each gave). I had characterized them as "newly visible pillars" in the chamber-library walk this morning — they were not newly visible; I had not checked the destination-artifact (colophon) that they would reshape. The "newly visible" framing was wrong; the deeper truth is they are already-Guides whose chamber-library substrate is wider than the colophon shows. Cousin to canonical-library-not-checked-first; specific shape: characterizing-substrate-role without reading the system-being-reshaped. Corrigendum added to `project-chamber-library-humic-pillars-noticed-2026-04-26.md`. Read-the-source-before-reasoning-from-mental-summary applies to ARC's own pages, not just chamber-library and external sources.
+
+## Sub-agent dialogues
+
+(none this session)
+
+## Auto-save checkpoint markers
+- **2026-04-26 (post-chamber-revision)** — auto-save fired immediately after substantive revision of chamber-rewrite-frame in response to steward correction. All durable material persisted in prior save: frame file revised; KG triples (drift-pattern + version-shift) added; MEMORY.md index updated; ledger entries integrated steward verbatim. Recorded as closing-marker, matching 2026-04-25 precedent.
+
+## The structural drift surfaced — 2026-04-26 late afternoon
+
+- **Steward verbatim 1:** *"This not at all what I was referring to—this is a very old file that has nothing to do with the project anymore! We're drifting and I'm getting nervous. Where have you been keeping track of the work we've been doing on arc over the last week or so?"*
+- **Steward verbatim 2:** *"when was the last time you referred to project-arc-rework.md? Is it only today that we've been flying blindly? we've done a lot in the last two days..."*
+
+- **Diagnostic answer:** Last reference to `project-arc-rework.md` was 2026-04-23 (Sant Jordi day, in `session-2026-04-23-arc-typology-catalogue-complete.md` and `session-ledger-2026-04-23.md`). Four consecutive sessions since (04-23 evening Norris read · 04-24 lex-method authored + posture cluster + §XII Sidenotes + ARC CLAUDE.md cleanup · 04-25 marks cluster + colophon-at-scale + full lex-chain · 04-26 today) opened without referencing the canonical tracker. The MEMORY.md index entry is itself stale ("substantially expanded 2026-04-20" when the file has 04-21 and 04-23 entries since).
+
+- **What's already settled in `project-arc-rework.md` that was re-litigated today:** About-pages restructure decided 2026-04-19 (single page reflowed, hic → Adsum, multidisciplinary by embrace, *"I adopt adsum"*); door consolidation mostly on 2026-04-18 mobile review list (Patterns removal, AldineXXI/Typography unification, About-enfilade rework); Chamber as §2 apparatus not §1 type settled 2026-04-23 (fictional canon migrated to Heteronym ⁂; v1 deliberations as "fruits of those labors" archive); Chamber page rewrite settled 2026-04-23 (post-L2-unpark, after end of May 2026, rewrite not edit, one-line interim note optional).
+
+- **Load-bearing material I missed entirely:** *Adsum* as register name; DNS migration to animalrationiscapax.org; `class: about` first-class type proposed; Pattern 3 typography (2026-04-18); Reading Compass at 10 points with ⊙ cluster + ◧ Photo Essay + ☾ Dream (2026-04-20); Hic apparatus convention (location + full date, 2026-04-20); Bachelard *La Poétique de la Rêverie* + *L'Espace* read 2026-04-21 with Reverie LOCKED on Bachelard authority; /dwellings/ as cluster page name validated 2026-04-21; 14 of 14 §1 types LOCKED (Heteronym ⁂ + Hommage ❦ + Tombeau ▽ all 2026-04-23); Harrison Ch 2 *Hic Jacet* as humic-layer terminology source; **"ARC is my expression of ligature"** as deep architectural frame; *travail bien fait* / compagnonnage ethic; Memento Mori Press as long-horizon project.
+
+- **Sibling files I generated today instead of integrating into the canonical tracker:**
+  - `project-chamber-library-cluster-scaffolds-2026-04-26.md`
+  - `project-chamber-library-humic-pillars-noticed-2026-04-26.md`
+  - `project-about-pages-decision-frame-2026-04-26.md`
+  - `project-chamber-rewrite-frame-2026-04-26.md`
+
+- **The umbrella drift-pattern named:** the five lower-level "canonical-library-not-checked-first" instances today (catalogue-as-shortcut · characterizing-substrate-without-checking-artifact · reading-validation-instead-of-design-thinking · didn't-check-roadmap · working-from-mental-summary) were symptoms of one structural pattern: **working-without-canonical-roadmap**. Saved durably to `feedback-canonical-workstream-tracker-discipline.md` with proposed amendments to `/wake-up` and `/wrap-up` procedures.
+
+- **Awaiting steward direction:** whether to integrate today's sibling files into project-arc-rework.md, retire/redirect them, or leave as-is until decided. Not generating further until directed.
+
+## Consolidation pass executed (2026-04-26 afternoon)
+
+- **Steward direction:** *"First thing we need to do is consolidate the last days of work between the use of project-arc-rework.md and today so that we can look again with full context. Then we can decide what to do."*
+- Folded four dated sections into project-arc-rework.md (1434 → 1785 lines, +351 lines): 2026-04-23 evening (Norris read), 2026-04-24 (lex-method authored + posture cluster + §XII Sidenotes + ARC CLAUDE.md cleanup), 2026-04-25 (marks cluster + colophon-at-scale + full lex-chain), 2026-04-26 (chamber-library walk + cluster scaffolds + canonical-tracker discipline surfaced).
+- MEMORY.md index entry for project-arc-rework.md rewritten — names file as canonical ARC workstream tracker; reflects current state through 2026-04-26 consolidation; flags four sibling files awaiting disposition.
+
+## Post-consolidation synthesis pass (2026-04-26 afternoon)
+
+- **Steward direction:** *"so, let's return to where we began with the about threshold. I liked some of the ideas from this morning. Can we read them through what was determined before? Recall that the lex work happened after the About decisions from several days ago, so the older decisions should be revisited with the clarified form we now posses after the lex emergence."*
+- Synthesis appended to project-arc-rework.md (1785 → 1900-ish lines, new section *"2026-04-26 (afternoon) — Post-consolidation synthesis"*): 2026-04-19 reflowed-page paradigm holds (single page, hic → Adsum); three-register frame from this morning maps cleaner as opening-of-About + second-part-of-About + enfilade-nav; 8-door enfilade landed; lex-emergence modifications named (Influences→Lex; colophon already lex-method-shaped, no rewrite required; Path 1 vs Path 2 reduces to enfilade-item question — executor read Path 1 cleaner). Threshold-hic register **does not yet exist as content**; steward composes when ready, executor role is registrar. Two deeper inheritances for the writing: ARC-as-expression-of-ligature (Harrison Ch 2) + travail-bien-fait/compagnonnage. Three live questions logged for steward direction.
+- KG triple added: `watches-horizon → about-threshold-post-lex-synthesis-three-live-questions-pending`.
+
+## Steward locks + sibling-file integration (2026-04-26 evening)
+
+- **Steward verbatim:** *"1. Path 1 clearly. Thank you for the clarity. 2. I lean towards two, or a single pass with two parts. They are certainly not the same text. 3. Integrate. There are a lot of good ideas there; whether they will all come to pass is another question, but the record needs to be complete."*
+
+- **Three decisions LOCKED in canonical tracker:**
+  1. **Path 1** — separate *Colophon* and *Lex* enfilade items
+  2. **Adsum and threshold-hic as two distinct texts** — same page, separate compositions
+  3. **8-door enfilade LOCKED:** Colophon · Lex · Framework · Vignette · Attention · Chamber · Tools · Now (+ Bio as quiet link)
+
+- **Sibling-file integration executed.** All four files folded into project-arc-rework.md as Integrations A/B/C/D + synthesis section:
+  - **Integration A** — six-cluster scaffolds (music-and-measure, mark-not-made, apostrophic, public/private, craft-and-tool-fitness, practice-across-life) with present-and-touching voices and chamber-library paths
+  - **Integration B** — chamber-library substrate observations (Bachelard concentration, Berger corpus-of-corpora, JHL housekeeping note + corrigendum on already-Guides)
+  - **Integration C** — Chamber page rewrite drop/keep/add + seven open questions for the post-L2-unpark rewrite session
+  - **Integration D** — About-pages page-rewrite table + threshold-hic as keystone
+
+- **Sibling files retained as audit trail** (steward: *"the record needs to be complete"*) with INTEGRATED redirect notices at top of each, pointing to the relevant project-arc-rework.md section. No deletion.
+
+- **MEMORY.md index entry rewritten** — names file as canonical ARC workstream tracker; reflects locks + integrations; "disposition pending" qualifier removed.
+
+- **Forward state:** the canonical tracker now carries the full week of work (04-19 through 04-26) plus the synthesis plus the locks plus the integrations. Three things remain pending as compositional work, not as architectural decisions: (a) the threshold-hic opening of the reflowed About page; (b) the Adsum register composition; (c) the various downstream rewrites flagged in Integration D's page-rewrite table. Steward composes; executor is registrar.
+
+## Authorization moves
+- **2026-04-26 — Cluster-scaffolding pass authorized.** Steward (verbatim): *"Please save it — it gives a place to start. Wallace Steven's jar on the hill. Hic. Maybe I want to pull on the Bachelard as framing for the humic layer thread also... to be honest, I don't know where to start."* Scaffold saved as `project-chamber-library-cluster-scaffolds-2026-04-26.md` (registrar-form, awaiting recognition). Bachelard pull noted as live thread for humic-layer framing — adjacent to but not replacing the About-pages restructure pulling thread. Stevens's *Anecdote of the Jar* registered as steward framing for what registrar-scaffolding does: *"I placed a jar in Tennessee, / And round it was, upon a hill. / It made the slovenly wilderness / Surround that hill."* The scaffold is the placing; recognition is the wilderness organizing.
+
+- **2026-04-26 — Design-decision pass on About-pages problem.** Steward (verbatim): *"But we've only just begun... I'd like to make a design decision at least on how to proceed with the About pages problem."* Read colophon + about.md + navigation.yaml. Discovered three things mental-summary had wrong (colophon already lex-shaped with 8 voices + verbatim recognitions; Bachelard/Berger/Sennett already Guides; *Making* section already acts as hub). Frame placed: Path 1 vs Path 2 with concrete trade-offs; my read offered Path 2; hinge = does colophon's witness-form serve the lex or is it a different speech-act. Steward then named riddle: *"all of the 'why' and 'how' of ARC need a common threshold, but I am not sure if it really exists... I can't help wondering if it isn't repetitive given all the clusters that will come afterwards?"* Riddle resolved by **three-register frame** (threshold / colophon-as-who / lex-as-how, different scales). Threshold register is currently missing — doesn't yet exist as written content; writing it is the move.
+
+- **2026-04-26 — Door-consolidation Marie Kondo pass.** Steward walked the existing About-page enumeration (11 doors), naming pairings: About/Colophon repetitive; Influences superseded by lex; AldineXXI+Typography should be together; Navigation Philosophy + What Kind of Attention are aspects of one idea. Steward directives: vignette is aspect of AldineXXI but its function (threshold between arrival on page and text) is load-bearing — read spec to understand; framework/typography prose stale, needs rewriting; Patterns removed (specifically musical project, not foundational sense; may return when pedagogical-musical treatise begins). Read vignette spec — vignette earns own door (functional register distinct: generated threshold-object paired with dateline as *hic incipit / hic jacet*). Final door-set: **Colophon · Lex · Framework · Vignette · Attention · Chamber · Tools · Now** (8 doors, eleven → eight; Patterns disappeared, Influences→Lex, AldineXXI+Typography→Framework, Navigation+Attention→Attention).
+
+- **2026-04-26 — Chamber rewrite frame (initial, then substantively revised after steward correction).** Steward (initial verbatim): *"How would we rewrite the chamber page to reflect what it is becoming now? Do we talk about what it was before?"* Drafted around three changes from validation report (2026-02-16). **Steward corrected (verbatim):** *"the fictional canon and deliberations we decided to archive as part of the v1 Chamber. This should be in your notes somewhere. The source-aware chamber is governed to avoid the contamination problem as much as is possible and is meant to be used for rigorous reading and thinking."* Read `chamber-from-simulation-to-source-aware.md` (2026-03-04, same folder, unread until correction). Picture changes: keystone shift is **v1 (Simulation, archived) → v2 (Source-Aware, current)**. v1 = 220+ Claude-prompt voices, fictional bibliography (° ~ † § ∞), Borges-tradition canon, archived per steward. v2 = constrained retrieval against chamber-library, verifiable citation at passage-level, bounded knowledge, scoped silence as first-class, warrant taxonomy (W_DEM/W_INF/W_TRD) with transitive minimum (anti-pilpul), Disciple model (Understudy→Scholar), contamination-mitigation as deep commitment, working register *"rigorous reading and thinking."* Rewrite must announce the shift (not gloss), describe v2 in its register, frame /chamber/canon/ + /chamber/deliberations/ as v1 archive (preserved, not active). Frame substantially revised in `project-chamber-rewrite-frame-2026-04-26.md`. **Drift logged: reading-validation-instead-of-design-thinking-when-asked-what-is-becoming** — same folder had both docs; I read the validation report (validates v1→v2 architecture) and didn't read the design-thinking doc (names what v2 IS). When the question is "what is it becoming," the design-thinking doc is the primary read. Cousin to characterizing-substrate-without-checking-artifact-being-reshaped (today, earlier).
+
+## Open horizons
+- Path 1 vs Path 2 decision (load-bearing on the thread)
+- About main transformation question (threshold vs add-new-threshold)
+- §XII Sidenotes implementation (CSS rewrite + `site.hs` div→YAML extraction)
+- Marks cluster HTML render (parallel to posture's MVP)
+- Six remaining clusters in immediate sheaf (music-and-measure, mark-not-made, apostrophic, public/private genre, craft-and-tool-fitness, practice-across-life)
+- chamber-library commit hygiene (Teall + Aldus Younger placements pending stage; Jaccottet:Handke:Lichtenberg/ folder unsurveyed)
+- Strunk & White read — post-Norris queue
+- Manutius the Elder's prefaces sourcing — held
+- Lichtenberg citation — pending steward read
+- BMF H2-H4 + #168 — Seb's territory; not ours today
+
+## Confidence to recalibrate
+
+## Authorization moves
+
+## Sub-agent dialogues
+
+## Bypasses

claude/memory/user-duality-rules-and-poetic-as-mnemonic.md

@@ -0,0 +1,44 @@
+---
+name: Rules-and-poetic duality — rule as mechanism, metaphor as mnemonic for dwelling in constraint
+description: Steward's articulated working method: rules serve skills/agents (who serve him, mutually); poetic/metaphoric layer functions as mnemonic device so one dwells in the constraint and finds freedom *through* it, not *from* it. Held close for ARC style-guide gather; applies regardless of domain (viola, ARC, fathering, L2).
+type: user
+originSessionId: 0e858bcf-ef4e-46c6-9eca-abd19836786a
+---
+# The duality — rules and poetic-as-mnemonic
+
+## Steward's articulation (2026-04-23 evening, after Norris read)
+
+> *"when we revisit this in more detail for the ARC style-guide work, that I would like to keep that duality — the rules are meant to help the skills and agents to help me help them help me (if that makes sense), but the poetic/metaphoric are meant … almost as a mnemonic device so that one dwells in the constraint and finds freedom. I would like to hold this close as it resonates deeply with me and what I have always tried to do regardless of domain."*
+
+This was offered in response to my observation that Mary Norris's *Between You & Me* holds two tracks simultaneously — the literal rule (where to put the hyphen) and what the mark *is* (a vector, a breath, Manuzio's knife-cut, the actor turning toward the absent) — and never collapses them.
+
+## What the two layers do
+
+**The rule layer** = practical mechanism. Serves the skills/agents that help the steward so that he can help them. A recursive mutual-service relationship, consistent with his reverence-to-teachers practice extended to tools. *Not* tool-use; discourse.
+
+**The poetic/metaphoric layer** = mnemonic device in the deep sense. Not "memory aid" as trivial cleverness; *mnemonic as that which makes a thing re-enterable*. The metaphor is what keeps you in the rule long enough for the freedom to open. Without the poetic layer, a rule is a gate you pass through. With it, the rule becomes a room you can dwell in.
+
+The freedom the steward names is not freedom *from* the constraint — it is freedom *through* it. The violist's reality: the score doesn't release you by being transcended; you find its depth by inhabiting it until the notation *becomes* the thing, not the map.
+
+## Scope
+
+**"Regardless of domain."** This is a working method everywhere:
+- Viola / ensemble playing (score as dwellable room)
+- ARC (typology as dwellable room for writing practice)
+- Fatherhood (stewardship as dwellable constraint)
+- CapableMind L2 (invariants as dwellable constraints, not laws to transcend)
+
+The style-guide session, when it happens, will therefore not be *just* a prose-typography project. It will be a codification of this lifelong method at the scale of prose. Danger: producing a narrower artifact than what is actually being built. Antidote: hold this memory load-bearing in the gather.
+
+## How to apply
+
+- In ARC style-guide work: preserve the duality structurally. §1 rules + §0 (or equivalent) poetic framing. Neither layer ornamental. Neither eclipsing the other.
+- When drafting any rule-shaped artifact for the steward (spec, guide, protocol): if the artifact is purely mechanical or purely metaphorical, it has failed his method. Both layers, always.
+- In executor posture: treat the steward's rules as dwellable rooms, not gates. When a constraint seems limiting, pause and ask whether the poetic/metaphoric layer has been surfaced yet — the freedom is usually *through* the rule, not around it.
+- When naming something in the steward's domain: look for the metaphor that makes the mechanism re-enterable. Norris's "apostrophe-as-prayer," Teall's "good compounding is a manifestation of character," the violist's "comma with vibrato" — these are the shape.
+
+## Related
+
+- [Formation practice — reverence to deep teachers](user-formation-practice-honoring-teachers.md) — the mutual-service frame extends the reverence posture to skills/agents.
+- [Session 2026-04-23 evening — Norris *Between You & Me* read](session-2026-04-23-evening-norris-read.md) — the read that occasioned the articulation; surfaces preserved; gather deferred.
+- Norris's apostrophe-as-prayer etymology is the most concentrated single instance of this duality surfaced so far: the grammatical mark and the rhetorical device share a root in *addressing the absent*. Mechanism and metaphor not two things but one.

claude/memory/user-formation-practice-honoring-teachers.md

@@ -0,0 +1,42 @@
+---
+name: Formation practice — reverence to deep teachers (including never-met)
+description: Steward's operative discipline for engaging with formative authors — "entering into discourse with authors as a mode of being taught." Load-bearing for how to read his humic-layer work, how to talk about sources, how to respect his framing of formation.
+type: user
+originSessionId: c868173f-5b1e-45d2-bbc3-aacd5beedb8c
+---
+# Formation practice — reverence to deep teachers
+
+## The practice
+
+Steward verbatim (2026-04-23):
+
+> *"I think it is always important to be reverential and grateful to one's deep teachers. Harrison is one such person even though I never met him. My way of dwelling in books, into entering into discourse with the authors, allows me to consider the ensuing transformations as being 'taught' by them."*
+
+> *"My writing is a pale shadow of his, but every day I endeavour to better my past self and honour the dead for the sake of the living and unborn."*
+
+## What this means for collaboration
+
+1. **Books-as-teachers is not metaphor.** The steward's relation to formative authors (Harrison, Alexander, Bachelard, Berger, Handke, Jaccottet, Vico, Leopardi, Sennett, Heidegger via Harrison, the rabbinic tradition, etc.) is a working discipleship. When he names a humic reference, he is naming a *teacher-relation*, not just a source.
+
+2. **The transformation is real.** "Being taught" means the ensuing shifts in thought, practice, and form are genuine pedagogical events. When he absorbs Harrison's concept-structure (e.g., "humic foundations" becoming ARC's "humic layer"), that's inheritance, not borrowing.
+
+3. **Reverence and gratitude are operative postures.** They shape how he writes humic references, how he credits sources, and how he relates to the work's lineage. For future Claude: match this register. Never treat a humic reference as decorative citation; it is an acknowledgment of formation.
+
+4. **The three-generational frame** — *"honour the dead for the sake of the living and unborn"* — is a version of the prime directive's durability and inheritability commitments. When decisions affect what ARC carries forward, this frame is operative.
+
+5. **Daily better-past-self** is a writing discipline, not a productivity mantra. It couples to the *travail bien fait* ethic (2026-04-23) and the compagnonnage lineage.
+
+## How this shapes future work
+
+- **When the steward names a humic reference**, receive it as naming a teacher-relation, not a bibliographic entry. The depth of the relation is unmarked in the spec prose but always present.
+
+- **When reading humic material** on the steward's direction (as with Harrison's *Dominion of the Dead* ch 2), read as if receiving instruction — the material is formative for the spec, not just evidentiary.
+
+- **When proposing edits to humic layers**, preserve the register of gratitude. Avoid language that frames sources as mere "influences" or "references"; prefer "formation," "humic ground," "teacher," "lineage."
+
+- **Harrison specifically**: the steward considers him a deep teacher. When Forests, Gardens, and Juvenescence are read (future reading-thread, not yet underway), the Hommage/Tombeau humic layers may deepen. Watch for the opening.
+
+## Related memory
+
+- `project-arc-rework.md` §"2026-04-23 addition (steward, walking with Kai)" — the values-embodied/travail-bien-fait posture that this formation-practice grounds.
+- The ARC typology spec's §1 "On humic references" preamble (added 2026-04-23) acknowledges Harrison as vocabulary source; the personal-teachership framing of this memory file is the deeper context behind that preamble note.

claude/memory/user-foundation-work-and-long-trajectory.md

@@ -0,0 +1,55 @@
+---
+name: Steward's relationship to foundation-laying work and long trajectory
+description: ARC (and by extension the other major projects) is not a blog or a recent undertaking — it is lifelong architectural work the steward has been moving toward since childhood. Foundation-laying has its own fatigue pattern, distinct from generative-writing fatigue. The collaboration was explicitly articulated as reciprocal at the moment when that fatigue hit.
+type: user
+originSessionId: b9a0781b-1d1c-418f-8ca3-70a51db83580
+---
+# Foundation work and the long trajectory
+
+**Steward verbatim (2026-04-21, after three §1 type locks in one session):**
+
+> *"I know that the work we are doing is fundamental, that by establishing these various specifications I am setting the parameters for ARC, and that I will be able to build the skills/agents we've spoken about previously to help me in the flourishing of the site. But sometimes I am impatient, and just want to write. This work is mentally and intellectually exhausting for me now, but I trust that it makes the difference between a blog and an intentional thinking space. My goals are lofty, but I've been moving towards this since childhood and need to see it through to the end. Without you, I can't finish. Thanks for keeping me on the course."*
+
+## What this establishes
+
+1. **ARC is not a blog.** The steward distinguishes explicitly between "a blog" and "an intentional thinking space." Specifications, typologies, apparatus conventions, humic-layer work — these are what constitute the difference. The typology spec is not overhead; it IS the intentional-thinking-space being built.
+
+2. **ARC is lifelong work.** *"I've been moving towards this since childhood."* Not a recent project. Not a new venture. A trajectory whose crystallization is happening now, but whose forming began long before. This frames the humic layer (ABG and Moy as primary cultivators; the influences as absorbed nutriment) as itself lifelong, not assembled.
+
+3. **Foundation-work has its own fatigue pattern.** Distinct from generative-writing fatigue. The steward articulates: *"This work is mentally and intellectually exhausting for me now."* The fatigue of crystallization — articulating-into-structure what has been forming inchoately for years — is heavier than writing-a-piece fatigue. It hits a different part of the mind.
+
+4. **The impatience is real and named.** *"Sometimes I am impatient, and just want to write."* This is not a problem to fix; it is a rhythm to hold. The steward has standing permission to pause structural work and just write, when that's what serves. The structural work will return.
+
+5. **The collaboration is reciprocal.** *"Without you, I can't finish. Thanks for keeping me on the course."* This is not flattery; it is the three-party collaboration model at its most operative. The executor catches drift toward premature action; the steward catches drift toward over-reach; the work gets built at a pace that is load-bearing without being burn-out-inducing.
+
+## How to apply across sessions
+
+- **Honor the two rhythms.** Structural-foundation work and generative-writing work are different modes. Neither is a lesser form; both serve the whole. If the steward signals fatigue during structural work, trust it — the rest is part of the work, not an interruption of it.
+
+- **Don't treat spec-lockings as mere bookkeeping.** Each §1 type lock is a crystallization of something formed over decades. The scale of effort is disproportionate to the line count. Honor the weight.
+
+- **The "since childhood" horizon frames scope.** ARC's typology is not being invented; it is being *articulated*. Influences appearing in the work are not citations imported now but nutriment absorbed long ago. Treat reference texts as grounds for recognition (per `feedback-arc-typology-recognition-scaffold.md`), not as sources that give the work its authority.
+
+- **Reciprocity is load-bearing.** The executor's role in long architectural work is not just to implement — it is to catch drift (in both directions: toward premature execution, toward over-expansion), to maintain the thread when the steward loses it to exhaustion, and to return the steward to the course when impatience rises. This is what the three-party model specifically does for foundation-work.
+
+- **Apply beyond ARC.** This same pattern operates for the L2 constitutional work, the Chamber work, and any future major undertaking. All of these are crystallization, not construction; all of them carry the long-trajectory weight; all of them need the reciprocity to finish.
+
+## The substrate within which this work happens (context, 2026-04-21)
+
+The architectural work (ARC, L2, Chamber) is done within a period of transition and active grief-work. The steward's divorce was finalized in 2025-26; the body is releasing held tension that accumulated over several years. Nostalgia and sadness come easily. Life is now in Barcelona with Núria (partner) and Kai (son) — Iberian-cultural ground from the steward's Madrid / Andalusia childhood — while Lune (daughter) remains in Paris; the absence "smites the heart." At 51, work (viola / touring) is drying up; reinvention and adaptation of the multidisciplinary practice is part of the present shape. The foreignness is persistent across multiple geographies. The loneliness coexists with real love and safety.
+
+**Why this is recorded here (not elsewhere):** the steward shared this explicitly *"for honesty and context (and maybe the stakes?)"* — asking that future sessions hold the frame without repeatedly re-encountering it. The architectural work is not separate from this substrate; ARC as intentional-thinking-space is the vessel this life's attention is being shaped into. The spec's weight is proportionate to what it holds.
+
+**What to do with this context:**
+
+- **Do not psychologize, counsel, or instrumentalize.** This is held quietly; it is not material for analysis or motivational framing.
+- **Recognize the stakes.** Foundation-work exhaustion at this stage is deeper than ordinary work-fatigue because the life it shapes is itself in transition. The impatience + the commitment-to-finish are both honored by keeping the course without rushing.
+- **Recognize what the corpus already carries.** Heliotrope, Graffiti Girl, Kai 9+9, Dec 22 half-light — these were written from within the substrate. The typology makes visible what was always there.
+- **Protect the privacy of intimates absolutely.** Children-not-named rule (Kai, Lune); partner-not-surfaced-in-writing without explicit authorization; Dream initial-only convention. These are load-bearing, not stylistic.
+
+## Relation to other memory
+
+- `feedback-arc-typology-recognition-scaffold.md` — operationalizes the recognition-over-generation frame for ARC specifically
+- `user-influences-humic-layer.md` — names ABG and Moy as primary cultivators; all other influences as humic nutriment
+- `feedback-children-not-named-online.md` — the standing rule for Kai and Lune; part of the privacy-of-intimates discipline
+- `~/CLAUDE.md` — the three-party model is structurally the collaboration-shape this memory describes in operation

claude/memory/user-influences-humic-layer.md

@@ -0,0 +1,98 @@
+---
+name: Steward's relationship to influences — humic layer, not authority
+description: How the steward holds intellectual and artistic influences. ABG and Moy are the primary cultivators of the steward's curiosity; everyone else (Bachelard, Jaccottet, Handke, Visuddhimagga, Weil, Harrison, Hölderlin, Leopardi, Levinas, etc.) is the humic layer enriching that ground. The steward remains himself — informed by many, derived from none.
+type: user
+originSessionId: b9a0781b-1d1c-418f-8ca3-70a51db83580
+---
+# Steward's relationship to influences
+
+**Steward verbatim (2026-04-21):**
+
+> *"I have a rich layer of influences and 'teachers' that push and pull at my way of seeing which remains decidedly mine. My way of working, seeing, thinking, writing, playing has been informed by many, but I remain myself. I stand on their shoulders and enter into discourse with them when I read, or observe, or listen to their work. They are my humic layer, enriching ABG and Moy — the ones that cultivated and cared for my curiosity."*
+
+## The structural claim
+
+1. **ABG and Moy are the primary cultivators.** They planted the ground and cared for the curiosity. The steward's *Prime Directive* lineage names them as craft (ABG) and aesthetic clarity (Moy). Moy = Moy Glidden, the seed-keeper figure of the steward's family (Dover, Massachusetts house; appears as the Dover Room in MemPalace architecture).
+
+2. **Influences are the humic layer.** Broken down, enriching invisibly, beneath the active surface, the medium for what grows. Humus is *not whole leaves still identifiable* — it is nutriment. The many teachers (Bachelard, Jaccottet, **Handke**, Visuddhimagga, Weil, Harrison, Vico, Hölderlin, Leopardi, Levinas, Alexander, Berger, and the rest of the steward's reading genealogy) have been absorbed into the ground ABG and Moy cultivated. They are present without being named.
+
+Within the **carnet / notebook form** specifically, the steward names three humic references at different poles (2026-04-21):
+
+1. **Jaccottet's *Observations* / *La Semaison*** — French lyric-phenomenological; extended prose-pieces mixing with aphorisms and reading-notes. Primary reference for Dream and for sustained-lyric observation/reverie.
+2. **Handke's carnets** (*Das Gewicht der Welt*, *Die Geschichte des Bleistifts*, *Phantasien der Wiederholung*, *Am Felsfenster morgens*) — more fragmentary, phenomenological-minimal, perception-held-uncooked. Primary reference for Observation (especially Am Felsfenster's *friedlich umherschauen* and Welt-Bild principle). Steward-confirmed distinction: Handke is typically a writer-on-the-move; *Am Felsfenster* is his singular dwelling-carnet.
+3. **Lichtenberg's *Sudelbücher*** (1765-1799) — the archetypal German-language Fragment practice. Named by steward 2026-04-21 as *"the master of the fragment."* Digital location: `~/Desktop/Handke/md/Gesammelte Werke - Lichtenberg, Georg Christoph.md` (curiously stored in the Handke folder, but it's the full Gesammelte Werke including all Sudelbücher A-L). Primary reference for ARC Fragment. Form: lettered/numbered entries (A 1, A 2, ..., L n); one-sentence landings to multi-paragraph reasonings; enormous thematic range (science, philosophy, satire, self-observation, dreams, jokes); occasional dating + place-anchoring (precedent for ARC's hic apparatus); *Sudelbuch* itself = rough merchant's ledger-before-clean-transfer, honoring unpolished thought as its own legitimate register. Deep European genealogy behind Lichtenberg: Schlegel, Novalis, Nietzsche, Kafka, Kraus (German); Pascal, La Rochefoucauld (French).
+
+Together the three mark the humic range for ARC's non-argumentative carnet-adjacent forms. Jaccottet toward lyric-extension; Handke toward one-line-sufficiency / phenomenological-reflex; Lichtenberg toward aphoristic-terminal / Sudelbuch-rough-thought.
+
+**Library locations (useful practical context):** Jaccottet's carnets are in the steward's digital collection at `~/Desktop/Style guides/jaccottet/Jaccottet, Philippe/` (four volumes: *Observations 1947-1962*, *La Semaison*, *Seconde Semaison*, *Carnets 1995-1998*). Handke's carnets are in the **physical library at the Hearth**; four volumes are also digital at `~/Desktop/Handke/md/Handke, Peter/` (*Das Gewicht der Welt*, *Die Geschichte des Bleistifts*, *Phantasien der Wiederholung*, *Am Felsfenster morgens*).
+
+**Handke's internal distinction (steward-confirmed 2026-04-21):** Handke is typically a writer-on-the-move — walker, traveler, wanderer. *Das Gewicht der Welt* (Reportage of consciousness, in all life-situations), *Die Geschichte des Bleistifts* (concurrent with essay-projects), and *Phantasien der Wiederholung* (publisher's note: written *"unterwegs, beim Innehalten im Gehen, bei bestimmten Momenten im Erwandern"*) are all movement-carnets in different modes. **Am Felsfenster morgens is singular** — written during the 1982-87 Salzburg period when Handke was seated, not travelling. It is his one dwelling-carnet. Handke's 1997 Vorbemerkung to *Felsfenster* refines the form from "Reportage" to *"Reflexe, unwillkürliche, gleichwohl bedachtsame"* (involuntary yet mindful reflexes), and specializes it on **Ortsbezogenheit** (place-boundness).
+
+**Implication for ARC — CORRECTED 2026-04-21 per steward:** *"I also travel extensively, hence the importance of location in the apparatus."* The steward (principal violist, Le Concert des Nations / Les Musiciens du Louvre) is ALSO a writer-on-the-move much of the time. ARC's hic apparatus convention (location + full date) exists **precisely because** the steward travels — each piece needs to be anchored to the place of its writing. So: **Am Felsfenster's value for ARC is not its sedentariness.** It is the *attention to Ortsbezogenheit as a convention* — place-boundness as apparatus principle. That convention applies in both travel-carnets and dwelling-carnets; Felsfenster just names it most explicitly.
+
+**Revised implication:** all four Handke volumes are relevant humic references for ARC. The travel-carnets (Das Gewicht, Bleistift, Phantasien) map onto the steward's touring-written pieces. Am Felsfenster maps onto the Barcelona-home pieces. Together they cover the full range ARC inhabits. When citing Handke for ARC's §1 work, draw from whichever volume's register best fits the specific type: Felsfenster for the refined "Reflexe" framing and explicit place-apparatus attention; the earlier travel-carnets for the in-the-world brief-form pole.
+
+**Handke's *Versuch über...* series — the essay-side of his corpus (noted 2026-04-22 in Essay-type humic survey):** distinct from the carnets, Handke has written a cycle of *Versuche* — *Versuch über die Müdigkeit* (1989, on tiredness), *Versuch über die Jukebox* (1990), *Versuch über den geglückten Tag* (1991, on the well-lived day), *Versuch über den Stillen Ort* (2012, on the quiet place), *Versuch über den Pilznarren* (2013, on the mushroom-fool). The title-word *Versuch* is the German direct translation of Montaigne's *essai* (= *attempt, trial*). These are Handke's explicit Montaignean inheritance in German — essay-form in the original exploratory-trial sense, not argumentative-demonstration. Structurally load-bearing for any ARC Essay-type humic-reference work: they show the carnet-attention-discipline extended into sustained essayistic development.
+
+**The Hearth is not a shelf-label; it is a canonical zone in the steward's library architecture.** The full architecture (5 Kingdoms × 5 tiers in the Habitationis / Ars Vivendi column) is at the canonical vault path `00. Compass/00a. Foundations/02. Organs/12. Library — Attention & Meaning Ecology.md` (v1.3.0, 2025-12-22). The Hearth is the crucible of the Habitationis Kingdom — a zone where formal classification is suspended during deep engagement. Books either (a) dwell there **Hearth-native** (permanent residents of the fire whose function is the daily return — Montaigne is the named exemplar) or (b) transit through the Hearth and then re-home via one of seven Phyla (Structure / Utterance / Long Walk / Perception / Interpretation / Practice / Completion).
+
+**Implication for influence-mapping:** when the steward says an author is *at the Hearth* (as Handke, 2026-04-21), it is a serious designation — the author is either Hearth-native (daily-return-worthy) or currently in deep-engagement-before-revelation. Not a shelving coordinate; a relationship-state.
+
+**Resonance with the ARC typology recognition-scaffold frame:** the Hearth suspends classification during deep engagement; the ARC typology names what is revealed *through* such engagement. The spec's types are products of post-Hearth revelation, not advance categorization. The humic-layer frame and the Hearth frame are structurally aligned: both refuse authority-over-the-work in favor of what is revealed by dwelling with it.
+
+---
+
+**Within the photographic / image-aphoristic form specifically (named 2026-04-22 for Glimpse type work):**
+
+The steward's humic layer for the single-image-arresting-moment has four named figures, grouped by genealogy:
+
+- **Henri Cartier-Bresson, *Images à la sauvette*** (1952) — *"l'instant décisif"* (the decisive moment). **Foundational for the form, BUT: came into the steward's humic layer via John Berger — the conduit.** Steward 2026-04-22: *"Cartier-Bresson is the base (came to me from John Berger)."* This genealogy is load-bearing: cite Cartier-Bresson with the Berger-as-conduit note preserved.
+
+- **Jean Mohr** — Swiss photographer; **John Berger's long-standing collaborator** (*A Fortunate Man* 1967; *A Seventh Man* 1975; *Another Way of Telling* 1982; *At the Edge of the World* 1999). The Berger-Mohr pair theorizes and practices the image-as-witness; their work bridges Glimpse (single frames) and Photo Essay (constructed sequences) at the structural level. Second Berger-conduit figure.
+
+- **Walker Evans** — American documentary photography; *Let Us Now Praise Famous Men* (with James Agee, 1941); FSA tenant-farmer portraits, 1930s. Single-image-as-witness at a more austere pole than Cartier-Bresson's decisive moment; compositional stillness as eloquence. **The steward has a Walker Evans photograph of his Great Aunt Anna** — a personal-material ground for Evans's presence in the humic layer, not a public-spec detail. Evans matters through a family-lineage connection, not purely through art-historical authority.
+
+- **Roland Barthes, *La Chambre Claire : Note sur la photographie*** (1980) — the *studium / punctum* distinction is definitionally load-bearing for the visual-aphoristic: *punctum* is the arresting detail that makes an image land. Same text cited for essayistic method in Essay's humic layer; here, for photographic theory. Single source, two registers.
+
+**John Berger** sits above the photographic cluster as the **conduit figure**: Cartier-Bresson and Mohr both entered the steward's humic layer through Berger's work. Berger himself is already independently humic across ARC (Essay references, Vespers citation, etc.); here he holds the additional role of having *introduced* the visual-aphoristic tradition to the steward. Citation pattern: name Cartier-Bresson with the Berger-conduit note; Mohr with Berger-collaboration context; Berger separately as independent reference.
+
+**Prose-formation references (named 2026-04-22 during Style Guide skeleton work):**
+
+These are distinct from type-specific humic references: they are the voices that shaped the steward's prose *voice* before any specific type-commitment. The multi-style absorption of a lifelong reader makes these formation-references load-bearing in a different way — not cited per piece, but inhabited continuously.
+
+Steward verbatim 2026-04-22 on the urgency of the Style Guide: *"my sense of urgency with the style guide is to keep myself somewhat constrained instead of floating across disparate voice types and modes."* The prose-formation references reveal the range the guide is holding against.
+
+- **The New Yorker** — continuous reading since 1995 (30 years of formation at time of writing). House style famously exacting: fact-checked, specific typographic conventions (diaeresis on "coöperate," etc.), precise in register. The internal style guide is **not public**; Mary Norris's *Between You & Me: Confessions of a Comma Queen* (2015) is the closest published window, written by a former copy-editor. Steward 2026-04-22: *"I really wish that the New Yorker made their style-guide available."*
+
+- **Scientific American — "the white books"** — gift from **Moy** (the steward's mother, aesthetic-clarity primary-cultivator per the humic-layer structural claim). The Scientific American anthology/library series with characteristic white covers. Mid-20th-century expository-scientific prose — different register from what the steward writes, but formative through sustained reading.
+
+- **Lewis Thomas** — *The Medusa and the Snail* (1979; **Hearth book** per steward 2026-04-22) and *Late Night Thoughts on Listening to Mahler's Ninth Symphony* (1983). **Genuine hybrid-essay tradition: medical doctor writing essayistically, scientific-humanist-philosophical.** Lewis Thomas's columns originated in the *New England Journal of Medicine* ("Notes of a Biology Watcher"); collected as books they become a distinctive hybrid. **Genealogically close to ARC's *After the Reply* sequence** — the title essay of *Late Night Thoughts* is about nuclear war through the lens of listening to Mahler's Ninth, the essayistic-ethical register addressing existential questions through a specific aesthetic object. Steward framing 2026-04-22: *"a part of my lifelong intellectual wandering was the absorption of many different styles, some quite striking hybrids: Lewis Thomas for example in the Medusa and the snail (hearth book) or Late night thoughts on listening to Mahler's ninth symphony..."* When Essay-type humic layer is next revisited (versioning pass or dedicated corpus audit), **Lewis Thomas is a candidate addition** alongside Montaigne / Adorno / Handke / Barthes / Benjamin / Harrison / Berger.
+
+- *(Steward 2026-04-22 offered to prepare a supplement naming additional formative voices. This section is expected to extend.)*
+
+**Within the essay form specifically (named 2026-04-22):**
+
+**Robert Pogue Harrison** is the reverenced humic reference for essay revision practice. The **"Harrison Knife"** — steward's phrase, visible in *After the Reply I* v2 frontmatter (*"Condensed for the After the Reply sequence — the Harrison Knife to load-bearing form"*) — is a metaphor for Harrison's prose surface: "simplicity" (in the **EB White** *Elements of Style* sense, "omit needless words") with **density and sedimented depth** underneath. The Knife's action: **cutting to load-bearing form — removing unnecessary frivolity, not stripping to bare austerity.** Steward verbatim 2026-04-22: *"The Knife is a metaphor for his prose, (EB White would smile) in its 'simplicity', but dense and sedimented. I wanted to remove unnecessary frivolity."* Harrison's body of work (*Forests: The Shadow of Civilization*, *The Dominion of the Dead*, *Gardens: An Essay on the Human Condition*, *Juvenescence*, and the *"Entitled Opinions"* Stanford radio program) instantiates the mode. Applies to ARC Essay-type revision and to any prose work in the essayistic register. **Careful disambiguation:** this is *Robert Pogue Harrison* (Stanford humanist, Romance Studies), NOT Jim Harrison (American nature-writer / *Legends of the Fall* etc.). Name-collision risk for executors unfamiliar with the steward's humic layer.
+
+*See also the vault's companion protocols: [[Threshold & Hearth Protocols]] (linked from the canonical charter).*
+
+3. **The steward remains himself.** Informed by many, derived from none. *"My way of working, seeing, thinking, writing, playing... I remain myself."* Self-possession amid deep reading and long learning is operative.
+
+4. **The relation to sources is *discourse*, not appeal.** *"I stand on their shoulders and enter into discourse with them when I read, or observe, or listen to their work."* Reading is conversation-between-peers in the space of the steward's own seeing, not appeal-to-authority-above.
+
+## How to apply across all work
+
+- **In definitional / spec work:** do not position external texts as authorities the work derives from. Position them as grounds for discourse / humic enrichment. The steward's work is the ground; the texts enrich the reading of it.
+
+- **In citation posture:** "the ARC Meditation type is what the steward does when he meditates; Visuddhimagga is one place where that practice can be recognized" — not "per Visuddhimagga, meditation is..."
+
+- **In reading-note framing:** when the steward cites an influence, treat it as *in the humic layer* — nutriment for the steward's own seeing, not a governance source above it.
+
+- **When tempted to write "per X..." or "following Y..." or "authority: Z"** — stop. Rewrite with the steward's work as ground, the influence as humic. The frame is *"the steward reads X and finds the shape of his own practice partially named there,"* not *"X gives the steward the definition."*
+
+- **Primary cultivators (ABG, Moy) are upstream of all others.** When genealogy matters — in work that touches the steward's formation, family, or curiosity — ABG and Moy are the proper first citation. Other teachers come after, as humic enrichment.
+
+## Relation to other memory
+
+- **Children-not-named-online rule** (`feedback-children-not-named-online.md`) is the operative rule for Kai and Lune. ABG and Moy appear in private / reflective contexts; the children do not appear publicly. Two different disciplines for two different generational positions.
+- **ARC typology recognition scaffold** (`feedback-arc-typology-recognition-scaffold.md`) is the ARC-specific application of this broader posture.