Skip to main content
Agent Volumes decision records explain why the v0.1 release surface looks the way it does. They are decision history and review context, not standalone reference requirements. Use them to understand the rationale behind the prose specification, schemas, OpenAPI contract, conformance fixtures, and URI publication model.
Current accepted decision records control the decisions they record. Later records can refine, update, or supersede earlier records, so read the latest record in a topic area before relying on historical rationale.

​
How to use decision records

All Agent Volumes ADRs follow the MADR format, so each record uses a consistent structure for context, decision, consequences, and related discussion.
  • Read decision records when you need to understand why a behavior is in scope, out of scope, or intentionally deferred.
  • Use the prose specification and companion artifacts for the current release contract.
  • Treat deferred topics as deliberate v0.1 boundaries, not as readiness gaps, unless the relevant record’s reopening trigger has been met.
  • Add a follow-up decision record when a recorded decision needs to change. Do not silently override it in site prose.

​
Current v0.1 baseline anchors

The repository decision index groups the current baseline anchors by topic. Use these groups as the starting point for deeper review.

​
Deferred v0.1 topics

The v0.1 core intentionally leaves these topics outside the portable baseline unless their decision records are reopened:
  • common derived-judgment vocabulary;
  • scanner-finding interchange and severity normalization;
  • component-level advisory targeting;
  • source-native external advisory feed ingestion;
  • future strict, enterprise, or other profiles beyond the v0.1 core;
  • structured deprecation metadata;
  • broader MCP configuration formats such as YAML;
  • finer permission granularity beyond the read/write baseline;
  • advisory write semantics and moderation workflows;
  • registry-side potential-exposure diagnostic APIs;
  • universal prerelease-resolution policy;
  • transitive bundle semantics for role = "meta";
  • AI-specific BOM profile guarantees beyond the generic CycloneDX baseline;
  • registry-priority policy and lockfile format;
  • universal trust-root policy;
  • upload profiles beyond mandatory http-put.

​
Superseded and updated records

Some records remain useful as history even though later ADRs refined the current release direction. Do not delete or rewrite superseded records. They preserve why the project changed direction and which alternatives were rejected.

​
URI publication decisions

The publication model comes from the latest documentation and URI publication records: The current site implements release convenience aliases as /spec/latest and /spec/current. These aliases route readers to the active non-draft release but are not durable citation targets.

Specification authority

Review the source-of-truth hierarchy before using decision history to interpret release behavior.

Design principles

Read the seven principles that summarize the v0.1 design direction.

Conformance requirements

See role-scoped requirements, fixture coverage, prose-boundary behavior, and deferred topics.

Decision records on GitHub

Open the complete chronological decision record corpus.