Specifications
Specifications describe a change before it is implemented. Each one states its status, the problem it solves, the exact behavior it adds, and what it deliberately does not establish. Reference and how-to documentation in docs/ describes the toolkit as it currently works; a specification becomes reference material only after it is implemented.
| Specification | Status | Summary |
|---|---|---|
| Contract sidecars | Implemented, unreleased | schema and example references that attach a JSON Schema and example payloads to a contract, and the checks AG runs on them |
| Maintaining contract sidecars | Implemented, unreleased | How the bundled skill creates, backfills and updates sidecars during discovery and everyday changes |
| Website and viewer | In progress: site skeleton and browser-safe core implemented | architecturegraph.dev: home page, rendered docs, examples, and a browser viewer that runs AG's own validation |
The architecture records for these changes are in AG's own graph as decision:contract-sidecars, decision:sidecar-maintenance-workflow, decision:website-and-viewer and decision:browser-safe-core.