You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 17, 2026. It is now read-only.
Support distributed multi-process and multi-node orchestration in the current orchestration subsystem.
Current State
OrchestrationManager currently coordinates work within the current process model. Persistence primitives are more mature now, but there is still no remote worker queue / claim / retry lifecycle for distributed execution.
Proposed Design
Define a durable orchestration job model
Introduce worker processes that can claim and execute jobs from shared persistence/queue state
Support retries, dead-letter handling, priority, and worker routing
Preserve the existing high-level spawn/wait model where possible
Affected Areas
packages/capabilities/src/orchestration/
shared persistence contracts backing orchestration state
worker process/runtime integration
Acceptance Criteria
Distributed job lifecycle states are defined
Remote workers can claim jobs without double execution
Retry/dead-letter behavior is implemented
Worker routing and fire-and-forget modes are supported
Integration tests cover orchestrator + multiple workers against shared state
Summary
Support distributed multi-process and multi-node orchestration in the current orchestration subsystem.
Current State
OrchestrationManagercurrently coordinates work within the current process model. Persistence primitives are more mature now, but there is still no remote worker queue / claim / retry lifecycle for distributed execution.Proposed Design
Affected Areas
packages/capabilities/src/orchestration/Acceptance Criteria