dashboard admin/config contract, or ratified descope, before the 5.4 cutover #1678

Closed
opened 2026-10-27 13:41:21 +00:00 by sam · 0 comments
Owner

The UI Service's /api/config routes (read/write, repo editing, overlay reset,
reload status) require the admin/config contract the extraction gate 4 names,
and it does not exist on either proto. Without it the config page, repo editing,
overlay reset and reload status are permanently 503, and handleConfig returns {}
with a nil Cfg, so the setup checklist renders as 'nothing configured' rather
than 'unavailable'.

The scope could instead ratify an explicit descope in the PRD: the config page
is unavailable in the UI process and the SPA hides the entry. That is a
decision, not a default; ui-service-boundary.md currently leaves the admin
contract as the intended path and does not settle which surface owns reconcile
/ reload.

Status: prerequisite of archie-core-8cda.5.4. Either the contract lands (a
State Store or Gateway amendment), or an explicit descope is ratified before
5.4 closes.

Close reason

Ratified descope rather than a contract. Configuration page is read-only in the UI process for Phase 3: reads cross as a daemon-published ConfigView snapshot over two new State Store RPCs (the projection already exists and is already secret-free, so nothing is designed, only moved); writes are descoped, answering 503 with the SPA hiding the controls, because the update policy is daemon-local and contracting it verbatim would build a Configuration Service inside a migration bead. Rejected a config admin service on archied: it would make the daemon a gRPC server for the first time, adding a listener, port, token and interceptor. Decision recorded in migration-decisions.md; ui-service-boundary.md's route table and configuration-ownership section amended, since the ratified text had assumed one contract carrying both read and write. Revisit with archie-core-1786637498420-327 (dashboard config editing as a feature). Implementation assigned to 8cda.5.4; nothing built here.


Imported from beads archie-core-ymut · GitHub #816 · type task · priority P2 · created 2026-09-08 · closed 2026-09-08

The UI Service's /api/config routes (read/write, repo editing, overlay reset, reload status) require the admin/config contract the extraction gate 4 names, and it does not exist on either proto. Without it the config page, repo editing, overlay reset and reload status are permanently 503, and handleConfig returns {} with a nil Cfg, so the setup checklist renders as 'nothing configured' rather than 'unavailable'. The scope could instead ratify an explicit descope in the PRD: the config page is unavailable in the UI process and the SPA hides the entry. That is a decision, not a default; ui-service-boundary.md currently leaves the admin contract as the intended path and does not settle which surface owns reconcile / reload. Status: prerequisite of archie-core-8cda.5.4. Either the contract lands (a State Store or Gateway amendment), or an explicit descope is ratified before 5.4 closes. ### Close reason Ratified descope rather than a contract. Configuration page is read-only in the UI process for Phase 3: reads cross as a daemon-published ConfigView snapshot over two new State Store RPCs (the projection already exists and is already secret-free, so nothing is designed, only moved); writes are descoped, answering 503 with the SPA hiding the controls, because the update policy is daemon-local and contracting it verbatim would build a Configuration Service inside a migration bead. Rejected a config admin service on archied: it would make the daemon a gRPC server for the first time, adding a listener, port, token and interceptor. Decision recorded in migration-decisions.md; ui-service-boundary.md's route table and configuration-ownership section amended, since the ratified text had assumed one contract carrying both read and write. Revisit with archie-core-1786637498420-327 (dashboard config editing as a feature). Implementation assigned to 8cda.5.4; nothing built here. --- _Imported from beads `archie-core-ymut` · GitHub #816 · type task · priority P2 · created 2026-09-08 · closed 2026-09-08_
sam added the mediumtask labels 2026-10-27 13:41:21 +00:00
sam self-assigned this 2026-10-27 13:41:21 +00:00
sam closed this issue 2026-10-27 13:41:21 +00:00
sam added a new dependency 2026-10-27 13:42:17 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: sam/archie#1678