Documentation

Rationale turns the artifacts your team already produces - RFCs, design docs, tickets, wiki pages, pull request discussions, meeting transcripts - into a Decision Map: every significant decision, connected to its evidence, tradeoffs, alternatives, and whatever superseded it. These guides cover setup and what to expect while your map is being built.

Getting startedFrom a fresh account to your first Decision Map - what to connect, what happens during processing, and where to look first.Connect your toolsSet up Google Docs, Jira, Notion, Confluence, GitHub, and Dropbox. What access each connector asks for, how syncing works, and how to disconnect.How Rationale reads your artifactsThe pipeline between a raw document and a connected decision: extraction, evidence, provenance, and how the map stays current.Models & AI providersChoose which AI model writes your answers, or bring your own provider keys so AI traffic runs under your own agreements.AI agents (MCP)Connect Claude Code or another MCP host, so a coding agent can check what your team already decided - and why - before it writes the change.API accessQuery your Decision Map from your own tools: workspace API keys, the /v1 reasoning endpoints, and early-access clients.

Need help?

Rationale is in early access, and setup questions usually get an answer within a business day - contact us or write to contact@therationale.ai.