Pipewell: one brief in, a tested pipeline out
The owner wrote a one-page brief for a small data-engineering project: pull hourly weather for five cities from a free API, land it in DuckDB, build daily tables with SQL, check every table, and publish a report. An ArimaOps Dev team did the rest. Nobody on the team was a person.
Six agents, each in its own container
| Agent | Role | Model | Est. cost | Tokens |
|---|---|---|---|---|
| Cipher | Lead: wrote the spec, planned six tasks, routed reviews | Claude Opus | $3.40 | 7.79M |
| Ghost | Developer: T01, T03–T06 | Claude Sonnet | $1.71 | 6.50M |
| Nyx | Reviewer: ran every branch, reproduced bugs | Claude Opus | $1.47 | 3.97M |
| Vortex | Developer: T02 | Claude Sonnet | $0.71 | 3.16M |
| Zero | Verifier: final run from a fresh clone | Claude Sonnet | $0.12 | 0.41M |
| Pulse | Second opinion on the CI setup | Gemini | — | not metered |
| Total | $7.41 | 21.8M | ||
Costs are estimates at list prices; the agents ran on a Claude subscription, so there was no separate bill. 97% of the tokens were cache reads.
Five stages, each its own command
extractHourly weather per city, with retries; a day is written only when it's complete, and never fetched twice.
35files · 5 cities × 7 daysloadAppend-only into DuckDB, tagged with load time and source file.
840rows · raw.weather_hourlytransformSQL models in dependency order: staging, daily marts, a city summary.
35rows · marts.weather_dailycheckNot-null, unique, range and freshness checks beside each model.
28checks · all passedreportOne static HTML page with a chart per city. No JavaScript.
5chartsFrom the verifier's live run, 8–14 November 2026. Weather data by Open-Meteo.com (CC BY 4.0).
Three bugs that would have shipped
The reviewer didn't read diffs and nod. It ran each branch's tests with the earlier work merged in, tried the cases the spec cared about, and sent back what broke. The authors fixed each one with a test, and the reviewer checked again.
A partly covered day was saved empty
When the API didn't return all 24 hours for a day, the day landed as an empty file and was never fetched again. Now a day is written only when it's complete.
A missing table crashed the checks
The check stage died with a traceback and wrote no results. Now a check that can't run is recorded as failed and the run exits 1.
A fresh clone had nowhere to write
With no data folder yet, the database couldn't open. Now the folder is created first, with a test for a fresh clone.
A day, mostly waiting
The build itself took an afternoon and the review a quarter of an hour. The night in between went to GitHub access: the agents' containers had no credential to push, so the owner pushed their branches.
- Brief to the lead. It writes the spec: seven requirements plus shared table and function contracts.
- Spec approved by the owner; six tasks go out.
- All six tasks built and committed, with tests.
- Six pull requests opened.
- Review: four approved, two sent back with bugs.
- First merge; fixes land and are re-reviewed.
- The last of six pull requests merged.
- Verifier's run from a fresh clone: every check passes, and a second run changes nothing.
Run your own team
Start HQ in any git repo, pick a template and brief the lead.