Build, as decided.
Repository-native decision infrastructure for AI coding agents.
Decision infrastructure for AI coding agents
CURRENT / v0.29.0Graph-complete federationThe product
Your agents can move fastwithout rewriting the past.
AsDecided is repository-native decision infrastructure for teams building with AI coding agents. Keep architectural decisions as validated Markdown, serve the relevant records to every agent, and enforce the consequences that can be checked against code.
Canonical answer
What is decision infrastructure for AI coding agents?
AsDecided is repository-native decision infrastructure for AI coding agents. It keeps human-reviewed engineering decisions beside the code as validated Markdown, then gives agents a deterministic, read-only way to retrieve the records that apply to a repository, path or capability. Each returned decision has a stable identity and source so an agent can cite the authority behind its plan or pull request. Where a consequence can be expressed objectively, AsDecided connects the decision to an architecture test, policy or CI check; it does not claim that a model’s judgement is proof. This separates three jobs that are often mixed together: record why the team chose a path, retrieve the current authority before code changes, and enforce only what can be checked. Core provides the CLI and read-only MCP server, while the public specification and companion tools keep the boundaries inspectable.
| Job | Repository-native output |
|---|---|
| Record | Reviewed decision with scope and lifecycle |
| Retrieve | Current applicable authority with a stable ID |
| Cite | Decision source attached to the plan or change |
| Enforce | Objective check linked to the consequence |
- Authority
- Human-reviewed records
- Context
- Scoped, read-only retrieval
- Verification
- Deterministic checks in CI
The decision control loop
How does AsDecided keep a decision attached to a code change?
The same decision can guide a person, a coding agent and a merge gate. AsDecided keeps those views connected without turning a model’s best guess into authority.
- 01
Record
Keep the why beside the code.
Write the context, decision, alternatives, consequences and lifecycle in validated Markdown that can be reviewed with the repository.
- 02
Retrieve
Find what applies before planning.
Scope a task by repository, path or capability and return the smallest relevant set of current records with a reason for each match.
- 03
Cite
Make the source visible in the change.
Give agents stable IDs they can cite in plans and pull requests so reviewers can inspect the exact authority behind an implementation.
- 04
Enforce
Check the consequences you can prove.
Connect objective rules, architecture tests and CI checks to the decision without pretending a deterministic check proves more than it does.
For whom: platform and architecture teams, staff engineers and product teams that need AI-assisted delivery without losing the reasoning behind established boundaries.
Where: in the repository, in CI and through a read-only MCP interface that can be adapted to Codex, Claude Code, Cursor and other coding-agent workflows.
The signature interaction
Ask the repository, not another model.
No embeddings. No model call. The same query returns the same cited decision.
“Can I hard-delete a user when they close their account?”
ADR-014
Soft-delete user records
No. User records remain recoverable for 30 days. New deletion work must preserve the restoration window.
How are architectural decisions enforced in CI?
Declare
Put a checkable constraint beside the decision it belongs to.
Enforce
Sentry checks changed code before it merges.
Measure
Unclassified decisions stay visible. Coverage is never implied.
Five-minute start
Put one real decision on the record.
Install Core. Create an artifact. Validate it.
Follow the complete quickstart- 01
brew install asdecided/tap/asdecided-core - 02
decided quickstart - 03
decided validate decisions/
The public system
One boundary per repository.
Core runs it. Companions own CI, integrations, and evidence.
Evidence you can inspect
Open source, explicit boundaries, no invented trust.
AsDecided’s claims are backed by public artifacts rather than a promise that a model will remember them. Start with the source, specification and release records; then decide which consequences your own repository should enforce.
The field record
The decisions behind agent-driven development.
Practical guides to decision governance, decision drift, persistent coding-agent context, deterministic retrieval and engineering constraints that can be defended in CI.
Start with the field record
Six canonical guides to decision-aware delivery.
These six pages define the governance model, the boundaries between instructions and decisions, and the route from retrieval to enforceable evidence. Supporting notes link back to them.
AS DECIDED / 001