I build software that can prove it works.
Two projects, a pipeline that gates them, and the agents that do most of the typing.
Work
Two projects, both about the pipeline around them.
Each one is public, gated, and documented where the decisions were made.
acceptance-gate
A monorepo whose subject is its own pipeline: a visual-regression differ, a Gherkin acceptance suite, and the gate that reads them.
Next.jsPlaywrightStorybooktrucutru
A reading app for one household, and the measurement that turned its CI bill into a post about how GitHub Actions is actually billed.
Next.jsPythonThe rule the whole repository is arranged aroundA decision that is not written down is a decision someone will make again, differently, in six months.
How I work
Draw it, make it mechanical, let the gate answer.
The same three stages on every change, whoever or whatever is typing.
Step 01
Draw it on the board
Tokens, components and screens are decided in the design file and never re-decided in code.
Step 02
Make the rule mechanical
Every decision that can be a test becomes one, so the next change meets it rather than a comment.
Step 03
Let the gate answer
The pipeline runs on the machine that made the commit and leaves a receipt saying it did.
What it cost
A pipeline is billed by the job, not by the minute.
Seeding a private repository from a public one, with its workflows intact, spent a month of CI in two days.
- Jobs billed
- 2,351 jobs
- In 48 hours, from 440 runs.
- Real minutes
- 702 min
- Billed as 2,000, at the per-job floor.
- Runs that passed
- 35 of 189
- A failed run bills the same as a green one.
Questions
The ones I am actually asked.
Next
Tell me what you are building.
I am interested in work where the pipeline is part of the product, and in teams that want the agents accountable to it.