Five layers, plain language, templates you copy. You already know the first one.
No cohort, no schedule, no calls. Written to be copied from, not watched.
Every layer opens with what breaks without it. You will recognize your own trace in one of them inside a few minutes.
Each one ships with the config, the role prompts, and the check that decides pass or fail.
The last layer puts it together: what runs in parallel, what waits, and where the work comes back.
They stack, they do not replace each other. A perfect prompt inside an empty context is useless, and a perfect context without a loop survives exactly one run.
State the task so the model stops filling gaps on its own. Role, constraints, the definition of done, the shape of the output.
What enters the window, in what order, and what gets cut first when it overflows. Retrieval, history compaction, one context per agent.
Tools, permissions, response parsing, retries, limits, traces. Everything that turns a model call into a predictable unit of work.
Run, check, correct, run again. What counts as green, what goes back, how many attempts are allowed, and what carries over between them.
Who runs in parallel, who waits, and who never runs at all. Back edges, verification gates, and the one place a human still belongs.
Built from the breakdowns I publish, expanded to the state where you can actually run them. What fits in one line in a post is a full diagram here.
What it is, what breaks without it, and how to tell your problem lives on this level. From real traces, not from tutorials.
Six agents from one prompt to a finished PR. Five searchers into one sourced report. A codebase audit in twenty minutes.
Where to start if something already works, and what to tighten next so you are not rewriting everything at each step.
Config files, role prompts for agents inside a graph, pass and fail criteria for gates. Copy, swap in your own, run.
Yes, and layers one and two are usually where non-coders gain the most. Most of the material is about how to think about the work and how to shape what the model sees, which pays off in any tool you already use. Layers four and five go further into automation, and they are written so you can follow them without a background in engineering.
Free material tells you what exists. This tells you what to do, in what order, and what to skip. Every layer comes with worked examples, the exact configs, and graph shapes you can copy straight into your own setup, so you spend your time building instead of collecting tabs. That ordering is the part nobody hands you for free.
The course lives on this site, at /course.html. Access is tied to your email: you enter it there, a six-digit code arrives, and everything opens. No password to remember, and you can come back any time from any device. Nothing to download, nothing to install, and updates appear in the same place.
Press get access and the payment options open on the next step. Card goes through Stripe, and takes Visa, Mastercard, Amex, Apple Pay and Link. Whatever email you enter at checkout is the one the course opens on, so nothing else is needed from you. For USDT you send me the transaction hash in a DM instead. Either way access lands the same day, usually within the hour.
The material is digital, so there is no refund once access is open. One exception: if the payment clears and access never arrives, you get everything back.
A clear map of the five layers, the templates and configs behind each one, and three complete graph shapes you can run. Even if you only apply the first two layers, you will get more out of the same model with less rewriting, and the rest is there when you are ready for it.
Five layers, the templates, and the order to roll them out.