Documentation
Documentation
Install Rationale, understand its governance model, operate the CLI and MCP boundary, and verify what the project knows.
01Five-minute quickstartInstall Rationale, initialize a project, connect the optional structural provider, and run the first health check.02Core conceptsThe small canonical model that separates identity, evidence, authority, and derived state.03Master promptA reusable starting protocol for coding-agent conversations that combine Codebase Memory and Rationale.04CLI referenceThe commands that initialize, inspect, prepare, review, and maintain a Rationale project.05MCP referenceTool-by-tool behavior at the agent boundary, including what MCP can never approve.06The propose → review → approve cycleA complete change lifecycle with explicit human authority and honest uncertainty.07What is versionedA practical boundary between canonical project knowledge, derived caches, and machine-local traces.08TroubleshootingDiagnose provider coverage, MCP silence, stale links, and review state without guessing.09Known limitsWhat Rationale deliberately does not claim to solve yet.10Factual architectureHow Git, Codebase Memory, the canonical store, derived retrieval, MCP, and human review connect.11Agents and MCPConnect Claude Code, Codex, or Cursor without handing approval to the protocol.12Evidence and release statusRead the project’s current evidence with coverage, uncertainty, and open gates attached.