Registry stack documentation: machine-readable Markdown.
Index of all pages: https://docs.registrystack.org/preview/llms.txt
Full corpus: https://docs.registrystack.org/preview/llms-full.txt

# Configuration reference

> Generated field reference for Registry Stack authored project files and Relay and Notary runtime configuration.

import AuthoringConfigurationReference from '../../../components/AuthoringConfigurationReference.astro';

This generated reference documents every reachable path in seven Registry Stack configuration
schemas: the five project-authoring schemas plus the Relay and Notary runtime schemas.
Use the purpose, reviewed intent profile, and ownership metadata to choose a field.
Then use `registryctl check` for a complete project or the product configuration checks for Relay
and Notary runtime configuration.

## Contract status

- Status: current, experimental
- Reference format: `1.0`
- Generated by: Main source (unreleased)
- Published release containing this generator: none
- Field release history: not verified
- Compared releases: none
- Generator: `registryctl authoring reference`
- Coverage gate: `registryctl authoring reference --coverage`
- Country workspace or runtime configuration reads: none

The generated reference is next-release candidate evidence from current source.
Its field entries use `history_status: not_verified`, `introduced_in: null`, and an empty
`version_history`.
Per-field release history is not published until a release-schema comparison establishes the
versions.

The generator joins the five committed project-authoring JSON Schemas, the Relay and Notary schemas
produced directly by their Rust schema APIs, the typed field-knowledge index, and reviewed
product-owned human-intent metadata.
JSON Schema and Rust validation remain the configuration authority.
The reference does not inspect a project, live runtime configuration, environment variables, secret
stores, or country values.

The five project-authoring sections describe configuration people commit in a country project.
The Relay and Notary sections describe product-owned runtime contracts generated by `registryctl`;
they are not additional country-authored files. Their intent sidecars are documentation knowledge
only and are never loaded by either product at runtime.

{/* Generated from the five crates/registryctl/schemas/project-authoring schemas,
    registry_relay::config::schema::document(), registry_notary_core::config::schema::document(),
    parity-coverage.json#field_knowledge, and the three product-owned intent sidecars.
    Run npm run generate from docs/site. */}

<AuthoringConfigurationReference />

## Validation boundary

The generated field entries describe schema facts and exact reviewed intent.
Relay and Notary fields carry a product-owned intent profile, while schema or reviewed override
flags explicitly identify the source of purpose and default behavior.
Runtime entries show the human-facing configuration `key_path` separately from the authoritative
JSON Schema `pointer`; authored entries use their JSON Schema pointer directly.
Runtime schema defaults are described without publishing their values.
The coverage report counts reviewed intent assignments, distinct intent texts, reused intent texts,
and assignments that use reused text separately.
Assignment coverage does not claim that every path has unique prose.
They do not prove that a complete project satisfies cross-file semantics, fixtures pass, an
environment resolves required secret references, or a generated product configuration is valid.
Run the authoring, fixture, preflight, and build commands for those separate gates.

## Next

- [Connect your data](../../configure/)
- [registryctl CLI reference](../registryctl/)
- [Errors and status codes](../errors/)
- [Generated artifacts](../../generated-artifacts/)