API and UI are one control plane with two frontends; neither is the lesser one. Every configuration and mutable setting is available on both. A setting that exists only in a file or a flag is the defect.
ARCHITECTURE.md 2.9 and SPEC.md R45 now carry the rule. This issue is the gap in the new binary today: settings with a route but no control in the dashboard.
Done when: every row has both a route and a dashboard control (bootstrap shown read-only with what a change needs, plus token rotation), the current value and who changed it are shown, and the gate passes. The judge is a control, so its model, endpoint and standing are on the Controls page.
API and UI are one control plane with two frontends; neither is the lesser one. Every configuration and mutable setting is available on both. A setting that exists only in a file or a flag is the defect.
ARCHITECTURE.md 2.9 and SPEC.md R45 now carry the rule. This issue is the gap in the new binary today: settings with a route but no control in the dashboard.
| Setting | API | UI today |
| --- | --- | --- |
| Organisation settings (deadlines, escalation, timing, budgets, freeze) | GET/PUT /api/settings | Settings page |
| People | GET/PUT /api/people | People page |
| Action classes | GET /api/classes, reset | Classes page |
| Hard rules, change-request rules | GET/PUT /api/policies/* | Controls page |
| Agent model (endpoint, model, key) | GET/PUT /api/settings/agent-model | none |
| Connectors | PUT/DELETE /api/connectors/{name} | none; no list route |
| Guards, including their judge (judge_api, judge_model, judge_base_url, policy text, eval standing) | PUT/DELETE /api/guards/{name} | none; no list route |
| Secret engines | PUT/DELETE /api/secret-engines/{name} | none |
| MCP servers | PUT/DELETE /api/mcp-servers/{name} | none |
| Credentials | GET/PUT /api/credentials/{name} | none |
| Sources and their verification | PUT /api/sources/{name} | none |
| Source key fields | PUT /api/sources/{name}/key-fields | none |
| Triggers | PUT /api/triggers/{name} | only by publishing an unmatched draft |
| Events | GET /api/events | none |
| Bootstrap (listen, database URLs, admin token hash, sealing identity) | config.toml, read via no route | not shown; no token rotation |
Done when: every row has both a route and a dashboard control (bootstrap shown read-only with what a change needs, plus token rotation), the current value and who changed it are shown, and the gate passes. The judge is a control, so its model, endpoint and standing are on the Controls page.
Corrected the rule with the maintainer: the API and the dashboard are one control plane with two frontends, and neither is the lesser one. What is a defect is a setting that exists only in a file or a flag. The done-when is parity in both directions, not 'the UI catches up to the API'.
Corrected the rule with the maintainer: the API and the dashboard are one control plane with two frontends, and neither is the lesser one. What is a defect is a setting that exists only in a file or a flag. The done-when is parity in both directions, not 'the UI catches up to the API'.
Landed in 21de660ae and deployed to staging (migration 00034, container clean). Verified on staging: GET /api/connectors, /api/guards, /api/secret-engines, /api/mcp-servers, /api/credentials, /api/sources, /api/triggers, /api/events, /api/controls/judges and /api/system/bootstrap all answer; the credential and source lists return only 'stored'/'token_set'; bootstrap returns listen, database host and port, schema count and the token hash prefix, no URLs or passwords. Dashboard pages: Extensions (connectors, guards and their judge, secret engines, MCP), Settings > Agent model with a test call, Settings > System (bootstrap read-only, token rotation writing only the new hash to config.toml), Sources with key fields, Triggers, Events, Credentials (write-only), and the judge standing on Controls.
Still open, and why: the workflow picker and the agent-model provider class are free text because no route lists installed workflows or provider classes; a guard's judge settings appear only when that guard declares them through the new Describe contract (none do yet); credentials can be listed and replaced but not removed, because the API has no delete; MCP settings can be edited at acceptance but adding a new key needs re-acceptance.
Landed in 21de660ae and deployed to staging (migration 00034, container clean). Verified on staging: GET /api/connectors, /api/guards, /api/secret-engines, /api/mcp-servers, /api/credentials, /api/sources, /api/triggers, /api/events, /api/controls/judges and /api/system/bootstrap all answer; the credential and source lists return only 'stored'/'token_set'; bootstrap returns listen, database host and port, schema count and the token hash prefix, no URLs or passwords. Dashboard pages: Extensions (connectors, guards and their judge, secret engines, MCP), Settings > Agent model with a test call, Settings > System (bootstrap read-only, token rotation writing only the new hash to config.toml), Sources with key fields, Triggers, Events, Credentials (write-only), and the judge standing on Controls.
Still open, and why: the workflow picker and the agent-model provider class are free text because no route lists installed workflows or provider classes; a guard's judge settings appear only when that guard declares them through the new Describe contract (none do yet); credentials can be listed and replaced but not removed, because the API has no delete; MCP settings can be edited at acceptance but adding a new key needs re-acceptance.
Scope is now a separate slice: packages are accepted at the instance, installations of them are owned by the instance, an organisation or a person (new issue 2027, ARCHITECTURE 2.11, SPEC principle 9 and R47). The Extensions page built here is instance-level and will become the package catalogue plus installations once that lands; nothing here is thrown away.
Scope is now a separate slice: packages are accepted at the instance, installations of them are owned by the instance, an organisation or a person (new issue 2027, ARCHITECTURE 2.11, SPEC principle 9 and R47). The Extensions page built here is instance-level and will become the package catalogue plus installations once that lands; nothing here is thrown away.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
API and UI are one control plane with two frontends; neither is the lesser one. Every configuration and mutable setting is available on both. A setting that exists only in a file or a flag is the defect.
ARCHITECTURE.md 2.9 and SPEC.md R45 now carry the rule. This issue is the gap in the new binary today: settings with a route but no control in the dashboard.
Done when: every row has both a route and a dashboard control (bootstrap shown read-only with what a change needs, plus token rotation), the current value and who changed it are shown, and the gate passes. The judge is a control, so its model, endpoint and standing are on the Controls page.
Corrected the rule with the maintainer: the API and the dashboard are one control plane with two frontends, and neither is the lesser one. What is a defect is a setting that exists only in a file or a flag. The done-when is parity in both directions, not 'the UI catches up to the API'.
Landed in
21de660aeand deployed to staging (migration 00034, container clean). Verified on staging: GET /api/connectors, /api/guards, /api/secret-engines, /api/mcp-servers, /api/credentials, /api/sources, /api/triggers, /api/events, /api/controls/judges and /api/system/bootstrap all answer; the credential and source lists return only 'stored'/'token_set'; bootstrap returns listen, database host and port, schema count and the token hash prefix, no URLs or passwords. Dashboard pages: Extensions (connectors, guards and their judge, secret engines, MCP), Settings > Agent model with a test call, Settings > System (bootstrap read-only, token rotation writing only the new hash to config.toml), Sources with key fields, Triggers, Events, Credentials (write-only), and the judge standing on Controls.Still open, and why: the workflow picker and the agent-model provider class are free text because no route lists installed workflows or provider classes; a guard's judge settings appear only when that guard declares them through the new Describe contract (none do yet); credentials can be listed and replaced but not removed, because the API has no delete; MCP settings can be edited at acceptance but adding a new key needs re-acceptance.
Scope is now a separate slice: packages are accepted at the instance, installations of them are owned by the instance, an organisation or a person (new issue 2027, ARCHITECTURE 2.11, SPEC principle 9 and R47). The Extensions page built here is instance-level and will become the package catalogue plus installations once that lands; nothing here is thrown away.