01 / PURPOSE
What it is for
Split work across specialists when the mission has distinct domains, dependencies, or handoff boundaries.
02 · TOPOLOGY PROFILE
A-Team
Specialists, handoffs and integration.
A mission is divided across domain specialists. Explicit handoffs move work between them, then an integration step assembles the result.
PARTIAL · PARTIAL · PROOF-GATED EXECUTION02 / SELECTION
When to use it
Choose A-Team when requirements can be represented as roles and work dependencies. Text-only mission descriptions may not produce a fully validated work graph.
03 / SCIENTIFIC BASIS
Inspiration
and limits.
The technical model comes from task graphs, specialization, and dependency scheduling. Team metaphors do not guarantee that every role is staffed by an independent expert.
RUNTIME PATH
What is wired
Dedicated dispatch and coordination paths persist identities, DAG progress, handoffs, proofs and program-runner multi-team sub-runs.
KNOWN BOUNDARY
What this does not imply
Text-only formation remains lexical, generic dispatch is refused outside the qualified path, and general expertise is not established by task completion.
01 / MODELThe principle
The principle
and its equation
A-Team distributes work among specialists by domain or step. Handoff contracts define inputs and outputs; integration assembles the deliverables. Dependencies can be sequential or parallel.
SIMPLIFIED FORMALIZATION
G = (V, E) ; start(v) ≥ max(end(u) : (u,v) ∈ E) ; result = integrate({outputᵥ})
G is the work graph; E contains dependencies. Ideal duration is bounded by the critical path, while handoffs and coordination add real cost.
02 / VARIANTS AND USE CASES
Choose a policy
Select a variant to explore steps based on its documented contract. This illustration does not run agents or call runtime services.
LOCAL SIMULATION · ILLUSTRATIVE01 / 11
expert committee POLICY IMPLEMENTED
Architecture review or cross-functional audit that needs several specialties and a collective decision.
TOPOLOGY MAP · ILLUSTRATION ONLY · NO AGENT EXECUTED
1/4 · Set one shared evidence contract
The drawing changes with the topology and variant to show their documented structure and policy. It is an explanatory model; maturity labels and runtime limits still apply.
This status follows the maturity of the variant policy in GenOS’ canonical catalog. “Policy implemented” does not certify end-to-end execution: topology maturity, required adapters, permissions, and evidence remain separate runtime conditions. This illustration does not run agents; its selector is manual. In the runtime, mission signals may select a preset automatically when its preconditions are met.
FAILURE MODES
What can go wrong
- A missing specialist or invalid dependency can block downstream work.
- A handoff can lose context or provenance.
- Integration can hide disagreement or combine incompatible outputs.
EVIDENCE AND BENCHMARKS
What has been checked
Working slice: Structured work graphs, independent scheduling, versioned handoffs and program-runner multi-team sub-runs connect to proof-gated completion.
Still open: Text-only formation remains lexical; general expertise and generic dispatch outside the qualified program path remain unproven.
Linked evidence: integration. A policy for a variant does not establish a successful end-to-end mission or comparative performance.
Read the benchmark protocol ↗Read the latest evidence ↗Read the product completion contract ↗