Configuration and Secrets
Configuration and Secrets
Document configuration requirements and safe secret management practices.
Status: Partial implementation reference — Code-confirmed; operational validation pending
Last reviewed: 2026-10-19
Scope
Variable names, bindings, required settings, provisioning and rotation without sensitive values. The source-confirmed baseline below covers part of this scope; remaining operational details are unknown.
Current implementation baseline
Configuration names and bindings are listed in each Worker reference and repository wrangler.jsonc. Registration, Corpus and Resources load JSON NODE_CONFIG with base_url, name and description. Corpus also needs externally maintained CORPUS_ID and HISTORY_LINEAGE matching its database witness.
Ingress/Corpus internal calls use INTERNAL_SHARED_SECRET. Ingress recognizes WRITE_FENCE=true; this is an admission fence, not a complete freeze of cron/operator writers. MCP uses TOASTMACHINE_API_URL, optional ingress URL/bindings and MCP_RESOURCE_URL, plus OAuth KV and Event Hub bindings. Defaults and local overrides differ by Worker.
Evidence: Corpus lineage, Ingress router, MCP client, MCP configuration. Secret provisioning/rotation and deployed values were not verified; no secret values are included here.
