Topology migration: daemon-side observer + per-release migration plan #284

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

Design: docs/prds/self-update-transaction.md#topology-migration-804-item-2. Fully greenfield: no topology-detection code exists today. Daemon-side observer (next to bootstrap.go's [services.state]/[services.gateway] checks) enumerates installed systemd units + present config sections; release.json gains required_topology; installer refuses with a printed migration plan (units + config, state store -> gateway -> UI -> daemon order) when it can't derive one, or applies it before binary install. install.sh consumes the same topology declaration so first-install and self-update share one source of truth (fixes install.sh writing only archied.service while profiles need four units). deployment_contract_test.go gains an assertion tying shipped profiles to install.sh's created units.

Acceptance criteria

Observed-vs-required topology comparison is pure/testable in task check. A host missing required units gets a refusal naming the exact migration plan, never a silent partial install. install.sh and archie-update-install read the same topology declaration.

Notes

Suggested council lenses: lens-boundary (observation belongs in daemon, not shell), lens-operator (refusal-with-plan is the whole safety property).

Close reason

Closed


Imported from beads archie-core-hj1t.2 · GitHub #933 · type task · priority P2 · created 2026-09-19 · closed 2026-10-05

Design: docs/prds/self-update-transaction.md#topology-migration-804-item-2. Fully greenfield: no topology-detection code exists today. Daemon-side observer (next to bootstrap.go's [services.state]/[services.gateway] checks) enumerates installed systemd units + present config sections; release.json gains required_topology; installer refuses with a printed migration plan (units + config, state store -> gateway -> UI -> daemon order) when it can't derive one, or applies it before binary install. install.sh consumes the same topology declaration so first-install and self-update share one source of truth (fixes install.sh writing only archied.service while profiles need four units). deployment_contract_test.go gains an assertion tying shipped profiles to install.sh's created units. ### Acceptance criteria Observed-vs-required topology comparison is pure/testable in task check. A host missing required units gets a refusal naming the exact migration plan, never a silent partial install. install.sh and archie-update-install read the same topology declaration. ### Notes Suggested council lenses: lens-boundary (observation belongs in daemon, not shell), lens-operator (refusal-with-plan is the whole safety property). ### Close reason Closed --- _Imported from beads `archie-core-hj1t.2` · GitHub #933 · type task · priority P2 · created 2026-09-19 · closed 2026-10-05_
sam added the mediumepictask labels 2026-10-27 13:35:42 +00:00
sam self-assigned this 2026-10-27 13:35:42 +00:00
sam closed this issue 2026-10-27 13:35:42 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#284