parallel-build-orchestratorlisted

# Parallel Build Orchestrator Turn an epic or issue list into landed work by splitting it into a **DAG of independently verifiable nodes**, building the disjoint ones concurrently in isolated worktrees, and refusing to accept any node until an independent reviewer has *empirically* re-proven it. The three ideas that make this work, and that everything below serves: 1. **File overlap is the scheduling primitive.** Two nodes that touch the same file cannot run in parallel no matter how unrelated they look — they will silently clobber each other at merge. Overlap analysis is not documentation; it is what decides parallel vs. sequential. 2. **A node is defined by the command that proves it.** If you cannot name one command that fails now and passes after — or show a reproduction of the defect it fixes — the node is not scoped yet. 3. **The builder is not allowed to grade itself.** Pasted verification output is a claim, not evidence. The reviewer re-runs it. ## Phase 0 — Preflight - Confirm workspace before touching anything: `git rev-parse --abbrev-ref HEAD && pwd`. Parallel agents run here; do not stomp another branch. - **Confirm the base is current** — `git fetch origin && git rev-list --left-right --count origin/main...HEAD`. A nonzero left count means you are behind; rebase before reading anything. This is one command and it is the highest-leverage line in the phase: every downstream artifact — the file sets, the overlap matrix, the pointer verification, the red-state r