Configuration reference
api/app/config.py, gateway/app/config.py (the Pydantic settings models: field, type, default, description) plus gateway.yaml.example and mcp.yaml.example reproduced verbatim with their commentsLook up configuration settings, skill fields, and recorded design decisions — the tables here come
from the source version this site was built against. The pages under /reference/ are not written
by hand. Each is generated at build time from
a specific file (or set of files) elsewhere in the repository, so it cannot drift from the
code the way a hand-maintained reference can — it can only be as current as the file it
reads, which the page’s own commit stamp names. That stamp is the newest commit on
main that touched the page’s source files at the time the site was published — not
the release you are running. Before you rely on a generated setting, compare the stamp
against your installed image tag: a page can describe a setting that arrived after your
release, or one that has since been renamed.
Configuration reference
api/app/config.py, gateway/app/config.py (the Pydantic settings models: field, type, default, description) plus gateway.yaml.example and mcp.yaml.example reproduced verbatim with their commentsSkill frontmatter schema
api/app/skills/schema.pySKILL.md frontmatter block can carry — for anyone authoring a skillADR index
docs/adr/Understand the version numbers
The first three rows are built by scripts, not by a writer; there is no full docs/site/
source page behind them to link to directly, so the table above links to the code they
read instead. Configuration reference is the one exception with hand-written material: a
short docs/site/reference/configuration.intro.md supplies the tier-direction and
env-forwarding notes that precede its generated tables, but the tables themselves are
still script output, not a page a writer maintains. Once the site is built, they live at
/reference/configuration/, /reference/skill-frontmatter/ and /reference/adr-index/.
Two further references that earlier planning for this site considered — an error-vocabulary table and a playbook-position schema reference — are not built in this draft. Nothing on this page links to them; treat their absence as scope not yet taken up, not as a broken link.
api/app/config.py — the source the configuration
reference is generated from, if you need it before the generated page exists.