Gantry

Gantry is the orchestrator over the eleven engines. A build opens as a record, is routed to the engine cells that can do the work, and moves through six stages — scoping, research, design, build, review, live. Each stage closes only when it can name a call, a URL or a commit. Gantry is the only seat that speaks to Ben; the engines do not.

The engines existed as a registry with no owner above them: nobody routed a task, nobody checked whether the wiring was still live, and nobody could answer 'is it actually done?' Gantry exists to make the answer a record, not a status update.

`gantry open --brief` opens the record; `gantry stage start` and `stage done --evidence` move it; `engctl awaken <engine>` checks wiring and activates the cell; `gantry qa --dir` runs the review corridor; `gantry complete --live-url` closes it. The state lives on disk; the MCP surface exposes the same nine tools to agents.

$ gantry open --brief brief.json$ gantry status --ref nw-20261018-flagship --json$ gantry stage start build --ref nw-20261018-flagship$ gantry stage done build --ref nw-20261018-flagship --evidence "tsc 0 · build 0 · screenshots 1440/390"$ gantry qa --dir . --audit$ gantry complete --ref nw-20261018-flagship --live-url https://nimoswebsites.com --evidence "corridor PASS"

Gantry is an internal system; the commands are shown because the process should be inspectable, not because this is a public CLI download.

The app opens a job, the division does the work, and every stage reports to the same writer the ops console uses. A stage report is not a status sentence: it carries the evidence that closed it. The key is not published; the shape is.

POST /api/gantry/stage
X-Gantry-Key: ••••
content-type: application/json

{
  "brief_id": "…",
  "stage": "build",
  "state": "done",
  "detail": "C1–C8 live on the preview",
  "evidence": "tsc 0 · build 0 · screenshots at 1440 + 390"
}

The route writes through the same build-record writer as the ops console, so there is one row and one story. No stage is set by a claim.

Every engine answers the same five questions: what, why, how, when and who. The status on the right is the proof ledger for this build — not a brochure badge. Open any engine for the full manual, the tool list and the evidence.

• —Gantry is an internal system, not a product you can install today.
• —The record above is a published snapshot, not a live request.
• —Org cells are a spec until they are pushed to the live fleet.
• —The laptop and cloud boxes can differ; the cloud is the source of truth.
• —No client data or task IDs are published on this page.
• —Five client stations and six build-protocol stages are different views, not two counts of the same thing.