Home / Fleet Architecture

Fleet Architecture · one system, live

Every worker in the AIDP fleet, grouped by tier, with live /health status. This is the runtime architecture — the master router fans out to agents, the orchestrator drives the lifecycle DAG, testing-master fans out to the disciplines, and knowledge is shared memory across all of them.

🗺 Architecture diagram 🔀 Program flow diagram 🎛 Console

How it's wired (runtime data flow)

• NL → fleet: the master router classifies a request and routes to the right agent (incl. program_* → orchestrator, tm_run_discipline → testing-master).
• Spine: orchestrator.program_run_full drives discovery → requirements → architecture → SOW → governance → IaC → test-design → testdata → disciplines, writing one lineage graph + a correlation trace.
• Testing fan-out: testing-master dispatches the 8 discipline agents (real CI tools), normalizes results into the defect manifest, and runs the Defect → CR/Patch/Requirement escalation loop.
• Shared memory: agents write entities into knowledge (Vectorize) and read them back (e.g. test-design recalls similar past requirements/defects before generating).
• Audit: every escalation chains through exception for an immutable chain_hash ledger.