Reference
Exhaustive lookup material — configuration keys, CLI, error codes, the API/transport surface, and terminology.
Reference pages are for lookup, not learning. When you already know the concept and just need the exact key, flag, code, endpoint, or term, this is where to find it.
The public vocabulary — Work, Route,
Settlement — is a reading layer over stable API and domain names;
the glossary carries the bridge from each primitive
to the type it maps onto (Work is a Routable, and so on). Reference pages use
the technical names, because that is what you type.
What lives here:
- Configuration — every
DUCTOR_*variable and YAML key, per subsystem. - CLI — every
ductorsubcommand, flag, and exit code. - Errors & status codes — the stable error catalog and its wire mapping.
- API surface — how methods are served (ConnectRPC / gRPC / REST), the interceptor chain, versioning, rate limits, pagination, and health endpoints.
- Glossary — the vocabulary used across the docs and product.
Configuration
Every DUCTOR_* environment variable and YAML key, grouped by subsystem,
with types and defaults — including AI, MCP, entitlements, and BYOK.
CLI
Every ductor subcommand and its flags — serve, dev, migrate, schema,
health, validate-config, workflow, and more, with exit codes.
Errors & status codes
The RFC 9457 Problem Details model, the stable error catalog, and the sentinel → Connect → HTTP mapping.
API surface
Tri-protocol serving, the external/internal plane split, the interceptor chain, versioning, rate limiting, pagination, and health endpoints.
API surface map
Find every API tag, its capability, and the narrative documentation that explains it.
Glossary
The vocabulary — coordinator, pool, recipient, strategy, connector, MCP, entitlement, bridge, and more.