chore(memory): Basic Memory trial begins — sync normalization baseline (283 files)

Basic Memory v0.21.6 first sync over the live memory dir (steward-authorized
live-dir trial, Option A 2026-06-06): adds permalink: to frontmatter, refolds
long YAML description lines, strips final newlines. Bodies untouched —
verified via full diff classification. From this commit forward, any diff in
claude/memory shows only what Basic Memory or the session writes.

Trial design: MemPalace untouched as incumbent; git status check on this dir
at every wrap; end-of-day evaluation (recall quality, sync robustness,
rebuild-from-files, malformed-file behavior).

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

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

@@ -1,9 +1,12 @@
 ---
 name: Session Ledger 2026-04-19
-description: Practice-of-return ledger maintained by /symmetria — returns, open horizons, recalibrations, authorization moves, sub-agent dialogues, bypasses.
+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
+permalink: claude-memory/session-ledger-2026-04-19
 ---
+
 # Session Ledger — 2026-04-19
 
 ## Returns
@@ -54,4 +57,4 @@ originSessionId: a3ddbf34-da48-4129-acba-658f2f869783
 
 - **~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.
+- **~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.