Configuration Reference¶
Last verified: 2026-07-26 against current checkout c09254f.
This page maps configuration areas to their owning documentation.
| Area | Owner doc |
|---|---|
| Fresh clone and local dev setup | Root README |
| Python package inner loop | docgen/README.md |
| Template/document authoring | Authoring and config API |
| Org/spec seeding | Seeding and platform tools |
| MCP transport | MCP transport and library enforcement |
| MCP per-user auth | MCP per-user auth |
| Observability and secrets | Observability and secrets setup |
| Demo app architecture | Demo app reference |
| Domain vocabulary | Domain model |
Environment Principles¶
apps/web/.env.localis the canonical local env file for the dev server, Python service, real-LLM tests, and probes.- Secrets belong in local env or vault-backed deployment config, not in docs or committed specs.
- Template specs should hold non-secret configuration.
- Tool credentials are injected from environment/vault at registration/use time.
- MCP URLs and auth mode should follow the standard transport docs.
Submodules and Built Artifacts¶
Fresh clones must initialize submodules and build vendored/workspace packages
before docgen-ui or the demo app can typecheck. The root README owns the
exact command order.