> ## Documentation Index
> Fetch the complete documentation index at: https://docs.agentvolumes.org/llms.txt
> Use this file to discover all available pages before exploring further.
# Specification authority and source of truth
> How to read the Agent Volumes v0.1.0-rc.1 release archive, decision records, prose specification, companion artifacts, and site pages without confusing their authority.
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](https://github.com/agent-volumes/agent-volumes-spec/tree/main/docs/decisions)** control the project decisions they record. Later decision records can refine, update, or supersede earlier records.
2. **[The prose specification](https://github.com/agent-volumes/agent-volumes-spec/blob/main/agent-volumes-spec.md)** 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](/spec/0.1.0-rc.1/conformance/schema-artifacts), [the Bibliotheca OpenAPI contract](/spec/0.1.0-rc.1/api/overview), [conformance fixtures](/spec/0.1.0-rc.1/conformance/fixtures), [coverage maps](/spec/0.1.0-rc.1/conformance/requirements), and [release publication artifacts](/spec/0.1.0-rc.1/uri-publications).
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](https://github.com/agent-volumes/agent-volumes-spec/issues) and [planning notes](https://github.com/agent-volumes/agent-volumes-spec/blob/main/ROADMAP.md)** provide context only unless the specification and companion artifacts are updated.
## What each source is for
| Source | Use it for | Do not use it for |
| ---------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------- |
| [Decision records](https://github.com/agent-volumes/agent-volumes-spec/tree/main/docs/decisions) | Understanding why a decision exists, whether a topic is accepted, updated, superseded, or deferred | Replacing current prose, schemas, OpenAPI, or fixtures with historical wording |
| [Prose specification](https://github.com/agent-volumes/agent-volumes-spec/blob/main/agent-volumes-spec.md) | Interpreting normative requirements and release behavior | Ignoring a current accepted decision record that fixed the same issue more specifically |
| [JSON Schemas](/spec/0.1.0-rc.1/conformance/schema-artifacts) | Validating structured payload shapes and schema-backed artifacts | Inferring prose-only semantic rules that the schema cannot express |
| [OpenAPI contract](/spec/0.1.0-rc.1/api/overview) | Checking Bibliotheca HTTP operation shapes, parameters, security, and Problem Details responses | Treating generated publication copies as the canonical source |
| [Conformance fixtures](/spec/0.1.0-rc.1/conformance/fixtures) | Exercising deterministic offline vectors, warnings, mappings, and role-scoped coverage | Claiming certification, hosted-service approval, or live interoperability |
| Site pages | Finding release-specific explanations, URI publication pages, API guidance, and reader-oriented summaries | Creating new requirements or changing published identifiers |
## Canonical source links
* [Decision records](https://github.com/agent-volumes/agent-volumes-spec/tree/main/docs/decisions)
* [Agent Volumes prose specification](https://github.com/agent-volumes/agent-volumes-spec/blob/main/agent-volumes-spec.md)
* [JSON Schema artifacts](https://github.com/agent-volumes/agent-volumes-spec/tree/main/schemas)
* [Bibliotheca OpenAPI contract](https://github.com/agent-volumes/agent-volumes-spec/blob/main/openapi/bibliotheca.openapi.yaml)
* [Conformance fixtures and reports](https://github.com/agent-volumes/agent-volumes-spec/tree/main/conformance)
## How to resolve drift
If two sources disagree, fix the source with the lower authority or add the required follow-up decision record.
Start with the [decision rationale index](/spec/0.1.0-rc.1/design-rationale) and the
repository's decision records. Later records can update or supersede earlier records.
Use the release prose as the final normative interpretation where no accepted decision record
fixes the same project decision more specifically.
Compare the relevant schemas, OpenAPI paths, conformance fixtures, and coverage maps. These
artifacts are release-aligned structured contracts, not independent policy documents.
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.
## Related pages
Find ADR topic groups, deferred topics, and URI publication decisions.
See the schema families that define structured companion contracts.
Connect role-scoped requirements to fixtures, schemas, OpenAPI, and prose-boundary behavior.
Distinguish canonical identifiers, rendered documentation pages, and machine-readable artifact
URLs.