Crate Engine — a complete engineering team, shipped as one

PACKING LIST

What's in the crate

Not five chatbots in a trench coat — one assembly. Each seat has a duty, a sandbox, and a tested harness; the orchestrator composes them into build → review → test loops so the team runs as one unit.

Part No.	Seat	Duty
CE-01	Orchestrator	the team lead you talk to — plans the loop, dispatches the seats, holds every decision for you
CE-02	Coder	implements on a branch, proves the build, merges only on your word
CE-03	Reviewer	adversarial code review, read-only by construction — approval is a verdict, never a merge
CE-04	Designer	visual & UX design, mobile-first, locked with you before a line is built
CE-05	QA	drives the real app in a real browser — screenshots, console, verdicts it refuses to fake

Fuel not included — by design. The seats run on your own AI agents and subscriptions (Claude Code, Pi, Codex CLI). Crate Engine never installs or signs into anything on your behalf; it detects your crew and staffs it.

START PROCEDURE

How it fires

A crate engine isn't a kit — it arrives assembled and tuned. Three steps between the crowbar and your first shipped feature.

STEP 1 / UNCRATE

One line installs it

Terminal, engine, workspace, the crate command — everything laid down, your existing AI agents detected and reported honestly.

curl -fsSL … | bash

STEP 2 / FIRE UP

Staff and boot

Five clicks through the wizard — staff the seats from your detected agents, point at a repo, boot. Five panes come up, orient themselves, and report ready.

→ "the rig is up — what shall we build first?"

STEP 3 / DRIVE

Direct in plain English

Say what you want. The team designs, builds, reviews and tests in parallel — then holds at the merge gate until you say the word.

→ "Merge it."

SCRUTINEERING

The deal, in writing

Racing has scrutineering; so does your codebase. These aren't features — they're the rules the machine is built to obey.

▪ Your agents, your accounts

Crate Engine ships the crate; you bring the crew. It never installs an agent, never touches a sign-in, and tells you exactly what it detected.

▪ Sandboxed seats

Every seat works behind an OS-level wall — writes stay inside your project. Full autonomy inside; containment outside.

▪ Nothing merges without you

Review approval is a verdict, not a trigger. The team holds at the gate; only your explicit go releases a merge.

▪ Honest to a fault

Seats refuse loudly, name their blockers, and never fake evidence — a QA that can't capture a screenshot says so instead of pretending.

CRATE—ENGINE