Everything your team needs to keep architectural decisions current.

Most teams join Dossier with years of undocumented decisions already baked into their codebase. Archaeology scans git history, commit messages, PR titles, and comments to infer what was decided and when — generating a set of draft ADRs for you to review, edit, or discard. Nothing is published without your approval.

Writing ADRs from scratch is the primary reason teams don't do it. Describe a decision in plain language and Dossier generates a complete structured draft — context, decision, consequences, alternatives considered. You review and refine before proposing.

ADRs are synced to your repo as Markdown files in a configurable directory (default: /docs/decisions/). Changes in Dossier commit to the repo. Edits to the Markdown files in the repo reflect in Dossier. ADRs live where your code lives.

Every ADR moves through a clear lifecycle: Draft → Proposed → Accepted (or Deprecated / Superseded). Comments on Proposed ADRs are part of the permanent record — the argument for and against a decision is preserved alongside the decision itself.

Expose your ADR index to AI coding agents. Claude Code, Cursor, and other MCP-compatible tools can query Dossier for architectural context before generating code, and push draft ADRs back when they make significant suggestions.

An ADR in your API Gateway can link to one in your Auth Service. Cross-project links are navigable in both directions — you can see what downstream decisions would be affected by changing an upstream one before anything is merged.