What problem does it solve? Sonder Runtime exposes dozens of SONDER_* environment variables, TOML keys, and consent gates spread across two configuration layers, making it hard to know which knob controls what, what its default is, and where it is validated. This Skill provides a source-verified catalog so you can answer configuration questions and add new config options correctly. ## Core Features & Use Cases - Complete variable catalog: Every SONDER_* environment variable with its default, validation guard, and exact file:line source citation, organized by domain (paths, HTTP server, Ollama, consent gates, secrets, tuning, unsafe lab). - Two-layer config model: Explains the split between fail-closed startup config and the hot-reloadable runtime_policy.json, including precedence order from built-in defaults up to --set CLI overrides. - Config authoring checklist: An 8-step procedure for adding a new configuration axis, covering typed fields, env mapping, validation, export bridging, redaction, and tests. - Use Case: A user asks "how do I change the port" or "what does SONDER_ALLOW_CLOUD do" — the Skill returns the exact variable, default (11435), guard rules, and the source lines that enforce them. ## Quick Start Ask the assistant to explain what a specific SONDER_ environment variable does and what its default and validation rules are.