Documentation
Install Rationale, understand its governance model, operate the CLI and MCP boundary, and verify what the project knows.
01Five-minute quickstartInstall Rationale, connect your agent, make the first governed change, and watch it live in the Control Room.02Core conceptsThe small model behind Rationale — Records, bindings, provenance, authority, relationships, and operations.03Master promptThe invocation protocol that install-agent writes for your agents — prepare, change, capture, and hand conflicts to a person.04The rationale skillOne Agent Skill that teaches your agent every Rationale operation — loaded only when a task needs it, in the same folder for Claude Code and Codex.05The prepare → change → capture loopA complete change with Rationale — context before the edit, durable memory after it, and a person only where authority is at stake.06Control Roomrationale ui — the working subgraph, causal memory, and live agent activity, served read-only from your machine.07Agents and MCPConnect Claude Code, Codex, or Cursor — one user-scoped registration, a protocol in the project, and a human boundary that stays human.08CLI referenceEvery rationale command — setup, context, the Control Room, human authority, migration, and maintenance.09MCP referenceThe five tools and six prompts at the agent boundary — inputs, outputs, and what MCP will never decide.10What is versionedCanonical knowledge in Git, local traces on your machine, and how releases and channels work from 1.0.11TroubleshootingDiagnose provider coverage, MCP registration, missing memory, conflicts, and the Control Room without guessing.12Known limitsWhat Rationale 1.0 deliberately does not claim — stated plainly so you can calibrate trust.13In the next releaseWhat the release after v1.1.0 changes in the context agents receive, the commands that keep the canon true, and the evidence behind it.14Factual architectureHow Git, Codebase Memory, the canon, the context compiler, MCP, local activity, and the Control Room fit together.15Evidence and release statusWhat 1.0 was verified against, how, and what remains open — coverage and uncertainty attached.