D666DestructoR666

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.

Open the mapRead the rules
//

Continuity without sludge

Compact event summaries carry the thread. Raw transcripts stay out of the default path.

//

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.

Omnichannel Agent Continuity architecture mapA visual flow showing surfaces, gateway, hook adapter, identity and topic stitching, local store, privacy filter, digest synthesizer, continuity brief, and smoke lanes.Flow 1: incoming turnFlow 2: gateway eventFlow 3: resolve speakerFlow 4: record / readFlow 5: surface-safe sliceFlow 6: allowed detailFlow 7: render markdownFlow 8: inject current turnFlow 9: prove behaviorFlow 10: leak checkssurfaceSurfacesTelegram · Signal · SMSCLI · cron · voiceruntimeGateway /agent shellmodel turn owns replyhookGateway hookadapteragent:start / agent:endengineIdentity + topicstitcheraliases · token matchstoreLocal OACstoreledger + rolling stateguardrailPrivacy filtersurface policysensitivity tiersengineDigestsynthesizerstructured operating picbriefContinuitybriefbounded Markdowncurrent user turnproof laneSmoke + synclanesproof + safe backfillFlow 1: incoming turn1Flow 2: gateway event2Flow 3: resolve speaker3Flow 4: record / read4Flow 5: surface-safe slice5Flow 6: allowed detail6Flow 7: render markdown7Flow 8: inject current turn8Flow 9: prove behavior9Flow 10: leak checks10

Connector legend

Numbered badges keep the map readable; full flow labels live here instead of fighting the wires.

  1. 1incoming turn
  2. 2gateway event
  3. 3resolve speaker
  4. 4record / read
  5. 5surface-safe slice
  6. 6allowed detail
  7. 7render markdown
  8. 8inject current turn
  9. 9prove behavior
  10. 10leak checks

Operating rules

The map is useful because the rules are boring.

oac://hot-path

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

01

Record

Write compact turn summaries into a local append-only ledger and rolling state.

02

Resolve

Map explicit sender aliases and likely topics without guessing strangers in group chats.

03

Filter

Apply surface policy and sensitivity tiers before anything crosses rooms.

04

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.