The four stages

The same steps, every time, in that order.

FOUR STAGES
ON THIS BUILD
PARTIAL
WHERE IT RUNS
Client build · provision → build → audit → ship

What it is

The four scripted stages a client build runs, in order: provision, build, audit, ship. The runner is real; the studio's own site uses the same build and audit gates, not the provisioner.

What it does for your business

For your business it means the work does not depend on whose week it is. There is no queue, no handoff between three people, and no stage that quietly does less than the last one did.

Why it earns its place

A build should not be a sequence somebody remembers. Four stages with one order make the work reproducible and the failure point visible.

The four stages are real in the client runner. This site's own rebuild used the same build and audit gates, not the provisioner; and no client has walked all four with us yet, so the track record is still ahead.

Real stages, honest record

PARTIAL

Stages

4 stages

Default

dry-run

Failure

stops the run

Client builds walked

not yet

The four stages are not the five client stations. They are the internal runner and the client-facing view of the work, respectively.

How it runs here

The stage runner loads the brief and config, runs `provision`, `build`, `audit` and `ship` in order, writes a stage event for each, and stops on the first failure. Dry-run is the default for a reason: it touches nothing.

RUN THE FOUR

TS
const { results } = await runPipeline(briefId, {  stages: ["provision", "build", "audit", "ship"],});// dry-run is the default; execute runs refuse test-looking names.

When it runs

A client build after the brief is accepted. The studio's own site is not provisioned by this runner; it uses the same gates.

Who owns it

Build owns the runner. Ops owns the credentials. The client sees the portal state, not the internals.

What it does not claim

No client has walked all four stages with us yet. The runner is real; the track record is not something this page can invent.

THE REFERENCE

The manual above is ours. The vendor's reference is the place to check an API, a version or a limit.

Open the official docs →

This is the tool. The process is what turns it into your business.

File the brief
The four stages — Nimos