The delivery index gives the build sequence an order of MVP, then companion harness, then a named host; the build sequence is a DAG of numbered Go build milestones.

The delivery index gives the build sequence an order of MVP, then companion harness, then a named host; the build sequence is a DAG of numbered Go build milestones.

A premise contradiction (severity nitpick) found by the cross-document consistency pass.

• End A: .abcd/development/brief/06-delivery/README.md:10 — "The delivery order (MVP → the companion harness → Claude Code) and what ships in each step"
• End B: .abcd/development/brief/06-delivery/01-build-sequence.md:12 — "detail: what each milestone stands up in the Go core"

The chapter index says 01-build-sequence gives a delivery order from MVP to the companion harness to a named host. The page itself is a dependency DAG of build milestones (Go scaffold, install and launch, history, intent and review, spec engine, run seam, lifeboat). It mentions the companion harness only as a design-target backend inside one milestone, so the order the index describes is not on the page.

Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 938.