Documentation
¶
Overview ¶
Command fenced-orchestrator runs the durable workflow orchestrator: it decides which workflow steps execute when and creates ordinary Tasks for them. Scheduling (where a Task runs) stays with the scheduler. The reconcile loop is stateless and durable — restarts and concurrent instances converge without double dispatch.
The orchestrator's guarded dynamic-spawn surface: the runtime adapter calls SpawnStep when a sandboxed agent invokes the brokered fenced.task.spawn system tool. All guards (recursion depth, dynamic-step caps, workflow budgets, spawn idempotency) run inside the kernel store transaction; this facade only maps the fenced request onto it.
Click to show internal directories.
Click to hide internal directories.