One file, three sources, one check
c1462026-11-13config.yaml comes from one of three places; every change to it, the person's or an agent's, passes one check; an agent drafts the whole file and the person applies it.
Source: c146 initial-prompt.md (Mark's words, 2026-11-13); c146 plan.md §Rulings R1–R8, C9, §Review stop 1 Q1–Q6, Phases 1 and 4; qnative c11 (313bd7c) crates/app/src/config/ (store, check.rs, tools.rs); qconfig on qcontrol main (file.rs, loader.rs, stock.rs); c146 intents.md and eval.md (Phase 5).
the file in an editor, with Qpoint's starters in its tray; no file opens on Pick a starter (Q3)
the plane sends it; read-only here, the other modes locked; who manages it, and who to ask (Q6: is this Policy Config? Tyler)
an address, fetched once, checked, confirmed; the origin at the top; Check for changes shows the difference (R1, Q2)
one file, as written and as it takes effect; every version kept, Restore on each (Q4); include files left as they are (R7)
asked of qcontrol (R6): each problem with its line, its key path and the nearest valid key. Until qcontrol serves it, the app's stand-in mirrors qconfig's schema, and the page and the agent call the same one
reads the file; whether a changed file is picked up without a restart, and who may write it, are engineering's asks
"send my events to my collector", "turn the tray off", "start me from the developer-laptop starter"
config-state (the mode, a waiting draft), config-read (the file, what it does)
config-reference for the sections it will touch; config-starters for a whole file to start from
config-check on the whole file; fix every problem by its line, path and nearest key
config-propose: checked again, placed on the Config page as a draft; the window opens it
the person reads the difference and presses Apply or Discard; the agent points, never presses
| Tool | Does | Changes the file? |
|---|---|---|
| config-state | the mode, the path, who manages it, a waiting draft, the versions | no |
| config-read | the file as written and as it takes effect, or the draft | no |
| config-reference | every section and key, the rule syntax, examples | no |
| config-starters | Recommended, Developer laptop, Data or analyst laptop | no |
| config-check | every problem with its line, key path and nearest key | no |
| config-propose | a checked draft on the page; refused if invalid, or if managed | a draft only: the person applies |
the draft as a difference against the file in force: who proposed it, what they were asked, one sentence on what changes
any earlier version, including what an agent proposed and the person applied
config-propose is refused with "Managed by your company. Changes are made there." The agent can still read and explain the file, and say what to ask for (C9's first pass; Mark Peterson's call)