Source: c146 Config File — Phase 2, 2026-11-13 · the plan · built on c121's Policy Config › Config File · this machine's file from the bridge beside meridian-day90

c146's Config page, under This machine (R3). This machine's file is the world's own, from the bridge (app/data/worlds/bridge/meridian-day90.json, /api/config); fresh has none, so qcontrol's stock document is in force. The starters, HQ's file, the fetched files and the agent's draft are fixtures (app/data/config-c146.ts). The check is the lab's stand-in for qcontrol's (R6): the strict schema from qconfig on main, with the line and a nearest key. The editor is a plain field here; the app uses gpui-component's Editor and diff (R8). Mode and State are lab knobs; the page's own buttons move between states too. Assumed: HQ's file is labelled "Policy Config v13", as if the company's Policy Config (c121) reaches this machine as this config.yaml; Tyler is asked (review stop 1, Q6).