What Is DecisionOps
Start with the product model, what a decision record is, and the two main ways teams use DecisionOps.
DecisionOps helps teams make important decisions visible, reusable, and enforceable.
It is not just a document repository. It is a workflow layer that connects decision records to onboarding, pull requests, and coding-time context.
DecisionOps helps teams turn important product, technical, business, and governance choices into searchable decision records. Those records are not just static documents. They carry scope, status, revision history, review timing, and the governance context needed to reuse a decision later when a team is coding, reviewing a pull request, or planning a change.
Most teams meet DecisionOps in one of two places. Platform and governance work usually starts in the web app, where you sign in, create or join a workspace, organize projects and repositories, and configure integrations such as GitHub and MCP clients. Day-to-day delivery work often happens in an IDE, where developers search previous decisions, draft a new one from active coding context, validate it against organization constraints, and publish it through the MCP workflow.
What DecisionOps Covers
DecisionOps is built around a simple lifecycle:
- Draft a decision
- Review and refine it
- Accept or supersede it
- Reuse it later during coding, policy review, and governance work
Decisions can be organization-wide or repository-specific. They can be created directly in the web editor or through an IDE workflow. Once they exist, they become part of the searchable record your team uses to stay consistent over time.
Who Uses It
- Platform admins set up the workspace, connect repositories, invite members, create API keys, and configure organization rules.
- Approvers and architects review, approve, supersede, and govern the decision record.
- Contributors and developers search prior decisions, create drafts, and work with decision-aware checks during delivery.
Start Here
If you are not sure where to begin, read choose-your-path.md next. If you already know you are starting in the dashboard, go to ../web/sign-in-and-onboarding.md. If you want to use DecisionOps from an IDE, start with ../ide/ide-overview.md.