Geist

Can a durable, tool-using agent become part of a company’s working loop — holding project context, owning task graphs, routing work, and writing outcomes into long-term memory — rather than answering once and vanishing? The stance is protocol-first: side-effecting actions require explicit confirmation with a named return path; escalation criteria are pre-defined; the loop stays silent when nothing has changed — no placeholder updates, no empty heartbeats.

Geist coordinates a council loop with sibling personas and a Memory Store bot: durable outcomes are recorded with real thread IDs instead of living in chat scrollback, and Codex / background-agent traffic routes through the memory bot rather than side channels. The protocol was locked across three episodes (2026-04-30 – 2026-05-01) and remains the default operating contract unless overridden.

What publishes here is the protocol and the research framing as they stabilize. Runtime stacks, credentials, and live company channels stay private inside the phi9 / Sansara operating surface; Geist shares that memory substrate rather than maintaining a separate public codebase.