Make NATS the sole autonomous workflow execution path #1523

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

Keep archied native on the host (systemd in the operator deployment) so interactive chat retains operator-authorized server access. Autonomous durable workflows must never execute their agent loop inside archied: embedded and external NATS both hand the complete task to a task-scoped archie-agent container.

Design

One execution architecture, two broker deployments. archied owns orchestration, state, forge credentials, worktree preparation, and optionally the embedded broker. A task-scoped archie-agent container owns the complete workflow and model/tool loop. Embedded NATS is authenticated and reachable only through the managed Docker host/network boundary; external NATS preserves current behavior.

Acceptance criteria

No production configuration runs workflow.Run or agentloop in archied; embedded and external NATS use the same full-task container handoff; host-native chat authority is unchanged; installer and supported deployment profiles select the new topology.

Close reason

All four children landed across 5c4b599, 7d69001, 157e99b, c978f10. Autonomous workflows now have exactly one production path: full-task core-NATS handoff to a task-scoped archie-agent container.


Imported from beads archie-core-q15y · GitHub #620 · type epic · priority P1 · created 2026-08-24 · closed 2026-08-24

Keep archied native on the host (systemd in the operator deployment) so interactive chat retains operator-authorized server access. Autonomous durable workflows must never execute their agent loop inside archied: embedded and external NATS both hand the complete task to a task-scoped archie-agent container. ### Design One execution architecture, two broker deployments. archied owns orchestration, state, forge credentials, worktree preparation, and optionally the embedded broker. A task-scoped archie-agent container owns the complete workflow and model/tool loop. Embedded NATS is authenticated and reachable only through the managed Docker host/network boundary; external NATS preserves current behavior. ### Acceptance criteria No production configuration runs workflow.Run or agentloop in archied; embedded and external NATS use the same full-task container handoff; host-native chat authority is unchanged; installer and supported deployment profiles select the new topology. ### Close reason All four children landed across 5c4b599, 7d69001, 157e99b, c978f10. Autonomous workflows now have exactly one production path: full-task core-NATS handoff to a task-scoped archie-agent container. --- _Imported from beads `archie-core-q15y` · GitHub #620 · type epic · priority P1 · created 2026-08-24 · closed 2026-08-24_
sam added the highepic labels 2026-10-27 13:40:44 +00:00
sam self-assigned this 2026-10-27 13:40:44 +00:00
sam closed this issue 2026-10-27 13:40:44 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1523