feat(controlplane): check and report a live persona replacement before switching #1476

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

Split out of archie-core-nwa0, which landed the build-and-probe step for workflow-execution-settings only. personas is the second live-watched kind and did not get it.

Worker: internal/app/archied/gateway_runtime.go:37 watches personas and :79-86 (applyPersonas) replaces the running gateway.PersonaRegistry in place with no check and with NO apply-status report at all, so a rejected persona edit would be invisible on the settings page. Both processes that apply it build through setupChatRuntime (archied daemon and the standalone Gateway).

Scope:

  • stage the candidate collection and probe it before switching (the check has real content here: the built registry's default persona and per-persona lookups must resolve, and the component that consumes them is the registry sessions read);
  • retain the previous registry when the check fails;
  • report both outcomes through the apply-status surface, which means personas must report apply status at all (its own kind, reported by each composing process).

Not in scope: the watch-reconnect defect, filed as archie-core-yrmr.

Close reason

Superseded: personas are replaced by SOUL and identity-per-action (docs/prds/soul.md, Persona removal gate); the persona surface itself is removed under archie-core-7ftt. The personas apply-status gap this bead fixes is moot once the watched kind no longer exists.


Imported from beads archie-core-nw7t · GitHub #1149 · type feature · priority P2 · created 2026-09-21 · closed 2026-09-29

Split out of archie-core-nwa0, which landed the build-and-probe step for workflow-execution-settings only. personas is the second live-watched kind and did not get it. Worker: internal/app/archied/gateway_runtime.go:37 watches personas and :79-86 (applyPersonas) replaces the running gateway.PersonaRegistry in place with no check and with NO apply-status report at all, so a rejected persona edit would be invisible on the settings page. Both processes that apply it build through setupChatRuntime (archied daemon and the standalone Gateway). Scope: - stage the candidate collection and probe it before switching (the check has real content here: the built registry's default persona and per-persona lookups must resolve, and the component that consumes them is the registry sessions read); - retain the previous registry when the check fails; - report both outcomes through the apply-status surface, which means personas must report apply status at all (its own kind, reported by each composing process). Not in scope: the watch-reconnect defect, filed as archie-core-yrmr. ### Close reason Superseded: personas are replaced by SOUL and identity-per-action (docs/prds/soul.md, Persona removal gate); the persona surface itself is removed under archie-core-7ftt. The personas apply-status gap this bead fixes is moot once the watched kind no longer exists. --- _Imported from beads `archie-core-nw7t` · GitHub #1149 · type feature · priority P2 · created 2026-09-21 · closed 2026-09-29_
sam added the mediumfeature labels 2026-10-27 13:40:33 +00:00
sam self-assigned this 2026-10-27 13:40:33 +00:00
sam closed this issue 2026-10-27 13:40:33 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1476