Web application
Record, review, supersede, search, and audit Decisions in a Workspace.
One decision record for people and agents.
Record what was decided and why, link the evidence, and find the active Decision in the web app, API, CLI, or MCP.
Play Decision Log dashboard product tour
Record what was decided
A Decision is an immutable statement with rationale, actor identity, scope, and provenance.
- Use the same vocabulary for User and Agent actors
- Keep Organization and Workspace scope explicit
- Link each Decision to its sources
Change through supersession
When circumstances change, create a replacement instead of silently rewriting history.
- Leave the previous Decision unchanged
- Link the replacement with DecisionSupersession
- Follow the complete chain in either direction
Use the same record wherever you work
The decision model stays consistent across the web app, API, CLI, MCP, and ingestion pipeline.
Public API
Build integrations with stable resources and permission-scoped mutations.
Command line
Search and record Decisions from engineering workflows while preserving provenance.
MCP endpoint
Give authenticated agents access to scoped tools and resources.
Source ingestion
Normalize submitted evidence before extraction begins.
Candidate review
Turn extracted suggestions into DecisionCandidates for review.
Frequently asked questions
How immutability, supersession, permissions, and retrieval work.
What is Decision Log?+
Decision Log is a shared system of record for decisions made by people and AI agents. It keeps the decision, rationale, actor, supporting evidence, and current status together.
How is a Decision different from a note or document?+
A Decision is a structured, retrievable commitment—not a page of general knowledge. It records what was decided, why, by whom or what, and which evidence supports it.
Can a Decision be edited?+
Not in meaning once recorded. Corrections and changed direction are represented by a new Decision and an explicit DecisionSupersession relationship.
Does AI create active Decisions automatically?+
Agent and extraction output defaults to DecisionCandidates. A permitted reviewer approves, rejects, or converts the candidate into a supersession.
How do I find the current Decision?+
Search and filters show the active Decision first while keeping superseded records available across the web app, API, CLI, and MCP.
How are evidence and provenance preserved?+
Each Decision can link to its source content, pipeline activity, and the User or Agent Actor responsible for the action.
How can our team and tools use Decision Log?+
People can use the web app. Engineering workflows and agents can use the public API, CLI, or authenticated MCP endpoint against the same model.
How are permissions and audit handled?+
Organization and Workspace roles determine access. Meaningful actions are attributed to an Actor and written to the append-only audit history.
Can Decision Log connect to existing workflows?+
Sources can enter through manual submission, API, CLI, MCP, webhooks, and configured integrations while remaining part of a reviewable pipeline.
Is this a project-management or wiki product?+
No. Decision Log remains focused on decisions, provenance, supersession, retrieval, audit, and review.
Want to evaluate your workflow?
Show us the decisions your team needs to retrieve and share with agents.
Talk to productBuild on a decision record that cannot be quietly rewritten
People and agents work from the same Decisions, no matter how they retrieve them.
