Continuity without sludge
Compact event summaries carry the thread. Raw transcripts stay out of the default path.
OAC visual map // public-safe topology
Omnichannel Agent Continuity.
One agent, many rooms, less amnesia. OAC is the small local layer that remembers the live thread across surfaces without spraying private context everywhere like a confetti cannon full of bad decisions.
Privacy by surface
A Signal DM, Telegram group, CLI session, and cron job do not get the same disclosure budget.
Boring failure mode
If the layer times out, errors, or is disabled, the agent keeps responding with no OAC context.
Interactive architecture map
Click a module. Follow the continuity current.
OAC is the anti-amnesia layer: compact cross-channel state, strict disclosure boundaries, and no raw transcript swamp. The map below shows the hot path from incoming message to surface-filtered brief.
Operating rules
The map is useful because the rules are boring.
record compact summaries only
state current focus, questions, decisions, promises
brief surface-filtered, max-char bounded markdown
inject current user turn, not system prompt cache
Record
Write compact turn summaries into a local append-only ledger and rolling state.
Resolve
Map explicit sender aliases and likely topics without guessing strangers in group chats.
Filter
Apply surface policy and sensitivity tiers before anything crosses rooms.
Brief
Inject a bounded Markdown continuity brief into only the current user message.
Public mask boundary
What this page intentionally does not show.
No secrets, no private chat IDs, no exact host paths, no live hook wiring, no provider keys, and no operational rituals that turn a helpful diagram into a treasure map for goblins. This is the architecture pattern, not the private brainstem.