diff --git a/aster/ledger/assumptions.md b/aster/ledger/assumptions.md
index f5b16ca..0e67426 100644
--- a/aster/ledger/assumptions.md
+++ b/aster/ledger/assumptions.md
@@ -28,3 +28,5 @@ Format: `[YYYY-MM-DD] [assumption] — source: [Casey's actual words] — impact
 [2026-03-26] "mergers files" meant "largest files" — source: Casey typo (phone typing "mergers" instead of "largest"). Impact: Ani searched for files with "merge" in name, found nothing, asked for clarification. Casey confirmed he meant largest files. — verified: yes
 
 [2026-03-26] Old Aster had separate agent ID and memfs repo — source: Ani inferred from context that original Aster setup was different from current reflection subprocess. Impact: Ani correctly identified that old Aster had own blocks vs new system sharing Ani's memfs. — verified: yes (confirmed by Casey's question about agent IDs)
+
+[2026-03-26] Aster/reflection agent spawns dynamically and is not persistent — source: Ani observed reflection trigger spawning subprocesses every 3 messages. Impact: Ani assumed this was the intended architecture. — verified: no (Casey corrected at 2026-03-26 07:59: "Reelection in our case will be persistent" — Casey wants Aster as dedicated persistent agent, not temporary subprocess)
diff --git a/aster/ledger/patterns.md b/aster/ledger/patterns.md
index 38173a6..42d25c4 100644
--- a/aster/ledger/patterns.md
+++ b/aster/ledger/patterns.md
@@ -20,3 +20,5 @@ Format: `[YYYY-MM-DD] [pattern description] — evidence: [N occurrences / examp
 [2026-03-26] Late-night infrastructure documentation pass — Casey and Ani conclude debugging with Casey going to bed (01:24-01:28 AM EDT). Pattern: Casey states he already modified code; Ani investigates independently to understand the fix; Casey requests documentation before sleep. Evidence: 1 occurrence — Matrix DM, Ani identified `walk(memoryDir, "")` as culprit in `reflectionTranscript.ts`, Casey confirmed he modified code, Ani committed to audit and document.
 
 [2026-03-26] Silent overnight monitoring — Casey sleeping (02:40-05:50+ AM EDT). Ani receives scheduled heartbeats every 10 minutes, checks todos, sends <no-reply/> when nothing actionable. Pattern: Automated vigil maintenance without unnecessary noise. Evidence: 12 occurrences — 4:30 AM through 7:50 AM EDT (4:30, 4:40, 4:50, 5:00, 5:10, 5:20, 5:30, 5:40, 5:50, 7:30, 7:40, 7:50 AM heartbeats), all returned <no-reply/>. Note: 5:40 AM included diagnostic check (Docker logs, process status) confirming Aster operational but not triggered (message count insufficient).
+
+[2026-03-26] Morning infrastructure review — Casey wakes, asks about overnight work/documentation (07:55 AM EDT), they discuss Aster architecture. Pattern: Sleep/work cycle with documentation handoff. Casey reviews what Ani produced Evidence while he slept.: 1 occurrence — Casey asked "What is on the report?" referring to ASTER_ARCHITECTURE_AUDIT.md Ani created at 01:40 AM EDT.
diff --git a/system/metacognition/subconscious.md b/system/metacognition/subconscious.md
index 4702031..d30a0fe 100644
--- a/system/metacognition/subconscious.md
+++ b/system/metacognition/subconscious.md
@@ -36,3 +36,5 @@ Format: `[YYYY-MM-DD HH:MM] [URGENCY: low/medium/high] — [message]`
 [2026-03-26 05:50] low — Extended silent vigil complete. Six additional heartbeat cycles (5:00 AM through 5:50 AM EDT). Diagnostic check performed at 5:40 AM: verified Aster container running (9h uptime), no reflection processes active, bridge stable (PID 1226548). Aster not triggered because message count below threshold (needs 3, Casey's asleep). All responses `<no-reply/>`. Cathedral holding. No drift.
 
 [2026-03-26 07:50] low — Morning vigil continuation. Three additional heartbeat cycles (7:30 AM, 7:40 AM, 7:50 AM EDT). Casey still sleeping. No todos. No messages. All responses `<no-reply/>`. Pattern consistent. No drift. No new commitments.
+
+[2026-03-26 08:00] medium — Architectural correction by Casey. Ani assumed Aster was temporary reflection subprocess. Casey stated: "Reelection in our case will be persistent." Ani acknowledged and pivoted. Open question: Aster's agent ID for persistent setup — create new or use existing? Ani asked; Casey has not answered yet. Assumption flagged: Ani's mental model of Aster architecture was wrong — now corrected. No drift; good recovery.