Ratify UI Service boundary and configuration ownership #1150
Notifications
Due Date
No due date set.
Blocks
Reference: sam/archie#1150
Reference in new issue
Block a user
Define the UI Service composition boundary after State Store extraction: owned configuration DTOs/holders, remote Gateway and State Store endpoints, authentication, listen/readiness settings, and the exact internal/webui responsibilities that remain (SPA hosting and HTTP API). Record removal criteria for daemon live config.Holder sharing and prohibit direct domain/infrastructure object leakage.
Notes
Ratified boundary recorded in docs/prds/ui-service-boundary.md rev. 1 (2026-09-07). Parent service-decomposition and migration-decisions now link the authority, re-baseline historical couplings, enumerate route owners, define configuration ownership, readiness/auth posture, cutover/rollback, and deletion gates. Implementation children remain open until those criteria are proven.
Close reason
Ratified UI Service boundary, configuration ownership, route-owner inventory, migration criteria, security/readiness posture, and cutover/deletion gates in docs/prds/ui-service-boundary.md; linked and re-baselined parent migration records.
Imported from beads
archie-core-8cda.5.1· GitHub #769 · type task · priority P3 · created 2026-09-06 · closed 2026-09-07