Infra — Process, Transports, Storage, Extensions - Monad

Infra is everything that exists before a single agent turn runs: the process itself, how it binds and speaks, where it keeps state, and how third-party code is loaded into it.

The two axes people confuse

Physical transport is how bytes travel: tcp or uds. Semantic transport is who may write a session: http, acp, or channel. Both TCP and UDS connections are http semantically. Read runtime.md before touching either.

Realtime: two planes, never merged

A token flood must never starve approval delivery — that is the entire reason for the split. Rules, resume semantics, and the conformance checklist: realtime-channels.md.

Documents

Doc	Covers
runtime.md	Binding, physical transports, configuration, env vars, security posture
daemon-architecture.md	Startup graph, lifecycle module table, hot reload, ownership rules
realtime-channels.md	Channel map, message lifecycle, client state machine, recovery
model-providers.md	Provider catalog as source of truth, native vs OpenAI-compatible, auth
atoms.md	Atom pack manifest gate, atom kinds, conflict semantics, installation
hooks.md	The thirteen lifecycle events, hook value contract, dispatch
third-party-commands.md	`defineCommand()` slash commands from atom packs
channel-conformance.md	Normalization and routing contract for IM adapters
host-interactions.md	Schema-driven user input across Web, TUI, CLI, ACP

Documented with their package

Single-package detail lives next to the code that implements it:

Doc	Covers
`apps/web/docs/router.md`	The embedded TanStack Router SPA: routes, dev server, code splitting, production serving
`packages/sandbox/docs/hardening.md`	Per-platform confinement status, egress filtering, known gaps
`packages/sandbox-vm/docs/conformance.md`	What counts as VM-sandbox confinement evidence, and how to produce it

Related: ../../engineering/architecture.md for package boundaries, ../../usage/mcp.md for connecting MCP servers.