orchestrate-build

orchestrate-build

The Tier-1 orchestrator loop. Permanently lean: it never reads a slice SPEC.md body, never writes product code, never trusts a worker's self-report. It walks the dependency graph in agent-control/slice-status.md, hands paths (not contents) down to per-slice managers, then re-runs each slice's verifier itself before flipping a status row.

The invariant

Information flows down as file paths, not file contents. The orchestrator passes a slice id and a list of paths to its manager. Each lower tier reads what it needs by path. Nobody pastes a 400-line spec into a prompt.

Topology

Tier 1 — orchestrate-build (this skill, you)
  holds: dep graph + 1-line statuses (agent-control/slice-status.md)
  does:  dispatch managers, re-run verifiers, flip statuses
        |
        | slice id + paths only
        v
Tier 2 — dispatch-manager (per slice, disposable)
  holds: ONE slice SPEC.md
  does:  build worker prompt, dispatch worker, return one-line summary
        |
        | scoped prompt
        v
Tier 3 — worker (composer-2-fast, best-of-n-runner)
  holds: ONE SPEC + in-scope files
  does:  write code, commit, emit <adam>COMPLETE</adam>

Fallback path: when topology_depth: 2 is set in adam.json, the orchestrator dispatches workers directly via dispatch-builder / dispatch-parallel and skips the manager hop.

Preconditions

Before running this skill:

• slice-to-tasks has produced slices/<id>/SPEC.md + slices/<id>/verify.sh (or an inline verify one-liner in SPEC.md) for every slice.
• tests-first has populated slices/<id>/tests/ with red tests.
• agent-control/slice-status.md exists (created by setup-adam, one row per slice).
• agent-control/human-queue.md exists (seeded by adam-foundation-sync) for batched operator items.
• adam.json has topology_depth (default 3) and verifier_convention (default slices/<id>/verify.sh).