Skip to main content
This page explains which Agent Volumes sources control a question when release pages, decision history, schemas, OpenAPI, fixtures, or website text appear to overlap. Use it before changing implementation behavior or citing a requirement from the documentation site.
The Mintlify site is a publication layer. It helps you find and understand the release, but it does not replace the prose specification, companion artifacts, or current accepted decision records.

​
Authority order

Read Agent Volumes sources in this order:
  1. Current accepted decision records control the project decisions they record. Later decision records can refine, update, or supersede earlier records.
  2. The prose specification defines the current release requirements and interpretation where decision records have not fixed the matter more specifically.
  3. Companion artifacts define structured contracts: JSON Schemas, the Bibliotheca OpenAPI contract, conformance fixtures, coverage maps, and release publication artifacts.
  4. This document site explains and publishes the release for readers and tools. If site prose appears to conflict with the sources above, align the site with the canonical source or correct the underlying source drift.
  5. GitHub issues and planning notes provide context only unless the specification and companion artifacts are updated.

​
What each source is for

​
How to resolve drift

If two sources disagree, fix the source with the lower authority or add the required follow-up decision record.
1

Check decision history

Start with the decision rationale index and the repository’s decision records. Later records can update or supersede earlier records.
2

Check the prose specification

Use the release prose as the final normative interpretation where no accepted decision record fixes the same project decision more specifically.
3

Check companion artifacts

Compare the relevant schemas, OpenAPI paths, conformance fixtures, and coverage maps. These artifacts are release-aligned structured contracts, not independent policy documents.
4

Fix publication drift

If a site page disagrees with current decisions, prose, or companion artifacts, update the site page or regenerate the derived publication artifact. Do not cite the site text as a competing requirement.

​
Release archive boundary

Pages under /spec/0.1.0-rc.1/... describe the v0.1.0-rc.1 release surface. Treat these pages as durable citation and discovery targets for this release. The convenience aliases /spec/latest and /spec/current can move when a newer non-draft release becomes active, so do not cite them as immutable release URLs.

Design rationale

Find ADR topic groups, deferred topics, and URI publication decisions.

Schema artifact inventory

See the schema families that define structured companion contracts.

Requirement inventory

Connect role-scoped requirements to fixtures, schemas, OpenAPI, and prose-boundary behavior.

URI publications

Distinguish canonical identifiers, rendered documentation pages, and machine-readable artifact URLs.