agent-fractal-orchestrator-architecture

Build an autonomous multi-agent orchestrator by designing a depth-2 hierarchy that dispatches coordinators and specialists via status.json routing signals. This pattern enables end-to-end automation with crash resumability and convergence detection across complex, multi-phase tasks.

Fractal orchestration is a self-contained coordination pattern using a depth-2 hierarchy of session orchestrators, coordinators, and specialists. It routes tasks through filesystem artifacts and status.json signals, enabling multi-pass pipelines with no human-in-the-loop intervention.

Crash resumability in multi-agent workflow automation relies on read-modify-write filesystem artifacts and prepend-only audit logs. These ensure traceability and allow the orchestrator to resume interrupted multi-phase tasks without losing progress or state data.

Yes, a fixed agent vocabulary standardizes coordinator and specialist roles for codebase modernization and security audits. This ensures consistent routing via status.json signals across discovery, analysis, planning, execution, and verification phases.

Route specialists using status.json routing signals within a depth-2 orchestrator hierarchy. This approach manages complex domains by coordinating discovery, analysis, planning, execution, verification, and delivery through filesystem-based read-modify-write artifacts.

Yes, you need a bootstrapped domain environment to start a fractal orchestrator. You must fill in context.json and start the session orchestrator to run the full autonomous pipeline for multi-phase task execution.