Seven tutorials
From an empty terminal to pull requests that carry proof. Each covers one flow and ends with one artifact.
Every page below is complete and usable today. The video is its visual companion, slotted in as each is recorded — the page doubles as the recording script, which is why the two cannot drift.
The series
Getting started with recipes
Install, doctor, launch, discover, drive, prove. The whole arc, and the shortest path into everything else.
Reading the evidence
One finished run, file by file, and the two rules that make a green verdict worth believing.
Skills and your team's library
Install the skills, declare your library, prove discovery sees it. Worked through with the perps library.
Cook a recipe from an acceptance criterion
One criterion in, a rerunnable proof out. Discovery sets the boundary; you pick the template.
PR QA review from one link
One pull request URL in, a per-criterion verdict table out. Nothing gets posted without you.
Release validation
One team's changes on a frozen release candidate, reported with four verdicts including NOT RUN.
A ticket end to end
Ordinary work, start to finish: implement, cook the proof, open a pull request a reviewer can check.
Series rules
One flow per tutorial
Setup is never mixed with usage. Each ends with the artifact it produced and one command to try yourself.
Nothing is staged
Real repos, real evidence. Where a run takes minutes the recording cuts to the result; it never fakes one. Failures stay in — watching someone follow an error to its fix is the most useful thing here.