This directory contains human-readable normative contracts. Each contract lives in exactly one family and identifies its status, semantic version, owning RFC, maintainers, schema paths, and compatibility notes.
Initial contract families:
ids/— identifiers and naming rules;manifests/— production and release manifests;context-packages/— portable context boundaries;prompt-contracts/— prompt inputs, outputs, and invariants;execution-contracts/— provider-neutral adapter, request, result, capability, parameter, extension, and error contracts;structured-output/— raw/normalized response, schema-validation, retention, and failure contracts;assets/— filenames, renditions, metadata, and provenance; andtaxonomies/— controlled vocabularies and classifications.
Copy _template.md for a new specification. A specification is
not stable until its RFC is accepted, schemas and fixtures agree, and a version
is recorded in the changelog.