Reference

The services, commands, and surfaces the runtime actually ships. Grounded against real code — we mark what's live and what's still landing, rather than list plausible-but-wrong names.

Services

A service is the one primitive — an owned unit with a boundary, a job, and a body (data, a model, code, or a human). You compose services into a vertical. They group by role:

• Governance floor — the door (authorize · record · trace), the append-only log and the fold that computes state from it, the reaction cascade, the clock. Everything rides this. (live)
• Knowledge — capture & intake, curation, facts, links, freshness, verify-status. (live, expanding)
• Attention & self — the attention selector, the me-node (your typed self-model), context assembly, advisory concerns. (selector live; me-node early)
• Calibration & adaptation — track-record calibration, adaptation, chronicle, supervisor. (live)
• Federation — co-sign (an authorized-assent tally across principals). (core live; full federation designed)
• Verticals — worked examples built on the same floor: a narrative game engine and a wargame. (live)

Runtime commands

One engine, several entry points — each a small node you run:

• mcp — the MCP server (stdio); every governed op becomes an octos_* tool for your agent.
• daemon (octosd) — the standing process: the clock ticks, freshness re-checks, scheduled work.
• serve — the HTTP door (a general API, default localhost:7810) for embedding the runtime.
• action — the CLI door: the one write-path for non-TypeScript callers.
• projection — generate a plain-file view of the graph to @-include (e.g. in CLAUDE.md).
• chronicle — read the decision/audit record.
• cycle / cycled — drive a research loop; rl-export / rl-ingest — training data in and out.
• seed-demo — spin up a demo graph to explore.

Surfaces & tools

The same governed core, reached four ways — the door holds across all of them:

• MCP — register once (claude mcp add octos -- node <octos>/dist/runtime/octos-mcp.js); identity is pinned at launch, with a default session tier (allowlist) and a principal tier for "this mouth is my keyboard."
• CLI — octos-action, the only door for scripts and non-TS callers.
• HTTP — a general API for your own stack.
• Web — a local debug environment to watch the graph and cascade.

The tools your assistant sees include octos_workspace (one-glance session prime), octos_state, octos_facts, octos_friction, octos_trace, plus governed writes like octos_intake_capture, octos_assembler_declareProject, and octos_cosign_sign. Signing signs as the pinned principal regardless of any payload claim — impersonation is structurally impossible.

Next steps