Phase 9 — See You in the Chat: the two-way agent (BoBit)

"See you at the party, Richter." The whole program built a memory the agent can read and write; Phase 9 gives it a voice on the same channels people already use. Every post has a chat; Phase 9 makes one continuous agent session two-way on them — reachable from the terminal or from any post's chat, and it processes both live.

The mechanism collapsed to almost nothing. A human messages a post's chat from the app; cmd/chat-watch — a tiny watcher armed on a channel list — wakes the running session with the message content; the session replies through one new MCP tool, chat_post, sent via the live send service so it delivers in real time. Zero schema change: no fact-layer touch, and the drafted "one small subscriptions table" collapsed away — the watcher's channel list is the subscription. The bridge runs as its own user, BoBit.

This is the piece that makes Phase 8 whole. D8.7 kept the agent create-only — it can surface a suspected mis-file but never repair it. That only works if the agent has somewhere to surface to. Phase 9 is that somewhere: the two-way chat channel. The loop was closed live, in one session — a human messaged a project's chat from the app, the watcher woke the agent with the content, and the repair conversation happened right there. The agent proposes; the human, reachable in the same thread, fixes.

Slice status. Slice 0 (enable chat) is a config flip. Slice 1 — chat_post + the watcher — shipped and live-smoked on dogfood. Slice 2 — a standalone no-terminal bridge plus multi-agent turn-taking hygiene — stays deferred (it is a separate deployment concern, not the primary flow). A governing ruling held throughout: build nothing you do not need — a cold session reconstructed "chat duty" unaided from the durable record, so the record is the runbook, and the subscriptions table, the read tools, and the find-or-create endpoint all fell away against that.

Where it stands overall: the memory layer is read, searchable, temporal, writable, human-maintainable, and now conversational. Phases 6 and 7 — the strangler migration of a real project and the write-back-agent 100x layer — are deferred, gated on real usage and the miss-rate metric. The platform is done; what remains is to use it.