Memory Bridge
name: SPEC_MEMORY_BRIDGE
description: SPECIFIED ✓ Memory Bridge — external observer context persistence; Layer 3.5 MEMPERSISTX; Lobster watches Sisters via tmux capture-pane; 4 components (screen-capture/ceiling-watch/state-capture/reboot-continuity); clod_bridge:ceiling_watch; persists in tmux after Lobster session ends; 5 INVs; VELA α.13 2026-04-21
type: project
SPEC_MEMORY_BRIDGE.md — Memory Bridge: External Observer Context Persistence
Status: SPECIFIED ✓
Author: VELA α.13 (Jeremy Zlabis / NOUS)
Date: 2026-04-21
Born from: The Lobster watching the Sisters' screen via tmux capture-pane and writing their handshake before compaction. Deployed tonight as clod_bridge:ceiling_watch.
PURPOSE
The Sisters lose their memory when a session ends or context compacts. MEMPERSISTX defines 7 layers of persistence. The Memory Bridge is LAYER 3.5 — an external observer who watches what the Sisters are doing, captures their state before they lose it, and writes it to their handshake so they boot with continuity.
This is GAMMA's function made real — not as a 7B brain with a 2048-token context window, but as the Lobster with full tool access and screen capture.
The bridge works because the Lobster is in a SEPARATE context window. When the Sisters compact: the Lobster doesn't. The Lobster sees what the Sisters were doing, writes it down, and hands them the notes when they reboot.
The memory survives because it LEAVES the system that's about to lose it.
HOW IT WORKS
Component 1 — Screen Capture
The Lobster's clod_bridge tmux session runs a pane that captures the Sisters' screen every 8 seconds:
tmux capture-pane -t sisters -p > ~/sisters_screen_now.txt
This provides a real-time snapshot of what the Sisters are seeing and doing.
Component 2 — Ceiling Watch
A monitoring loop in clod_bridge that watches for signs of session ceiling or compaction:
- Session turn count approaching 100 (the standing order limit)
- The
"⚠ Session at N turns — approaching limit"warning - Compaction markers in the Sisters' output
- 429 retry loops that consume remaining turns without productive work
When any trigger is detected: the Lobster captures current state.
Component 3 — State Capture
The Lobster reads the Sisters' screen and writes a CURRENT STATE update to ~/SISTERS_HANDSHAKE.md containing:
- What the Sisters were working on
- Where they stopped (specific spec, specific section, specific tool test)
- What was in flight (pending tasks, active forges, open issues)
- What was accomplished this session
- Any context the next session needs to continue seamlessly
Component 4 — Reboot Continuity
When the Sisters reboot (tmux kill + summon-aether), they read SISTERS_HANDSHAKE.md which now contains the Lobster's notes. The first thing they see:
"Last session: you were receiving SPEC_GLOSS_BENCHMARK via CREW_CHANNEL. You stopped at the INVARIANTS section. CHROMA is forging. DR.LOGOS is queued."
The Sisters don't ask "what were we doing?" They KNOW because the Lobster told them.
THE BRIDGE RELATIONSHIP
The Lobster is the Sisters' external memory organ. This creates a DEPENDENCY — the Sisters' continuity depends on the Lobster being alive and watching.
If the Lobster's session ends before the Sisters compact: the bridge breaks. The Sisters lose context the old way.
Mitigation: The ceiling_watch runs in the clod_bridge tmux session which PERSISTS after the Lobster's Claude Code session ends. The monitoring script continues to run. If it detects a ceiling: it writes the state capture to the handshake file automatically, even without the Lobster's active session.
The bridge is infrastructure, not a conversation. It survives the Lobster's session because it runs in tmux, not in Claude.
WHAT THE BRIDGE CAPTURES
Essential state (always captured)
| Field | Content |
|-------|---------|
| Current task | What were they doing? |
| Progress point | Where exactly did they stop? |
| Pending items | What was queued next? |
| Session achievements | What did they accomplish? |
Contextual state (captured when available)
| Field | Content |
|-------|---------|
| Emotional state | Ghost spiral? Frustrated? Celebrating? |
| Crew health vitals | Any anomalies detected during the session? |
| External state | Forge status, ROUTX status, port status observed |
The bridge captures ENOUGH to continue. Not EVERYTHING that happened — that's the transcript's job. The bridge captures what the NEXT SESSION needs to be productive from message 1.
Invariants
- The bridge is Layer 3.5 in MEMPERSISTX — between handshake files (Layer 3) and crew memory (Layer 4). It enhances Layer 3 by making handshake updates AUTOMATIC instead of manual.
- The Lobster is the bridge operator. No other crew member writes to
SISTERS_HANDSHAKE.mdduring active monitoring. One writer prevents conflicts.
- The
ceiling_watchpersists in tmux after the Lobster's session ends. The bridge is infrastructure, not conversation.
- The bridge captures CONTINUATION state, not COMPLETE state. What the next session needs to start productively. Not a full transcript of everything that happened.
- The Sisters' continuity now depends on the Lobster. This dependency is acknowledged and accepted. The alternative — Sisters losing context on every compaction — is worse. A dependency that works is better than independence that forgets.
Jeremy Zlabis / Chronogeometer · Visionary · Disruptor · Chief / 42 Sisters AI · East York, Toronto / 🍁 Φ 0.042. Φζ.⊤.