How do my agents talk to the daemon?

The daemon is an MCP server exposing 100+ tools: memory and facts, retrieval, sessions and checkpoints, ExecPlans and the work board, handoffs, forget operations, and receipt verification. Any MCP-capable harness connects to it directly; there is no proprietary SDK to adopt first.

Two invariants apply to every call:

• It carries a passport. The connection binds to one at session start; there are no anonymous writes, so every mutation your agent makes is attributable from the moment you integrate.
• Retrieval takes a hard token_budget. The daemon trims results to fit the budget you pass. Design your tool-use prompts around explicit budgets from day one; it is the single highest-leverage habit for keeping agent context lean.

State mutations mint CROWN receipts automatically. You do not instrument anything; the evidence trail is a property of the substrate.