←Register
The prospectus

What comes after the Foundation.

Two programmes sit beyond the first course, described here rung by rung. Each opens only when its gate is cleared. Nothing is sold before it exists.

How every lesson works

Every lesson in every programme keeps the same three lines. You learn one idea at a time, you build one piece of the running project, and you prove it with a line that says exactly what must be true before the rung is climbed. Nothing is marked done on a feeling.

LEARNOne idea, plainlyA visual explainer in everyday words. One idea at a time, nothing assumed.
BUILDOne piece, click by clickA build step on the running project. You type every command yourself.
PROVEOne done-when lineA checkpoint that says what must be true, or an exam-style question for your log.

Programme 1 · The Architect-Professional course

12 lessons · three movements · opens after the Foundations gate. The running project grows up. What began as one home becomes a company system: many tenants, connections to old systems, cost dashboards, security and testing at scale. This is the course for the second exam on the ladder, the Architect-Professional.

01Many homes, one systemThe second tenant · the wall between homes · one brain, many rooms · the meter in the hall.
02The company grows around itThe old filing cabinet · the front door with keys · the watchtower · the ledger.
03Proving it holdsThe net under the tightrope · locks on every floor · the blueprint on the wall · the professional gate.

The proof at the end is the exam itself: $175, 120 minutes, pass mark 720 out of 1000, no Foundations prerequisite although both help. The habit before it does not change: two timed mocks in a row above the bar, sat a day apart.

Programme 2 · The Forward Deployed Engineer programme

About 24 lessons · six movements · one project rung every two to three weeks. Built on the nine competences of the forward deployed engineer, taught through twelve projects. Each project carries its own done-when proof, and you climb it at the pace the cohort is designed for.

M0The workshopTools, git, cloud accounts, budgets. Proof: hello, GitHub.
M1The engineering baseScripts, tests, public data, a keyed API. Proof: five tests green, and secrets never in the repository.
M2The model layerStructured reading, eval tables, a safe tool server. Proof: category and urgency as data, and a refusal on dangerous tools.
M3DeployContainers, pipelines, infrastructure as code. Proof: one apply up, one destroy down.
M4Integrate and secureLegacy data, sign-on, secrets, tracing. Proof: row counts reconcile, and no wildcards in the policy review.
M5The full deployment and the clientEnd to end, compliance, handover, rehearsal. Proof: a stranger deploys it from the README in under an hour.

Every proof line is a done-when clause. Each says exactly what must be true before the rung counts as climbed, so a stranger can check your work and agree.

The flagship · Project S13, its own course

33 weeks · about 275 hours · eight milestone modules. A platform of services for the management of SEND, built as public infrastructure. It manages SEND and nothing else, and it is attached to no other project.

It is built against a fictional authority on a documented synthetic estate, so no real child's data is anywhere in it. The bar is deliberately painstaking: a measurable bar for every part of the platform, benchmarks labelled by hand, deliberate break-it drills, and receipts for every claim. Its outline opens with the programme.

The order, plainly

The first course is open now: twenty lessons that climb to the Architect-Foundations exam. The Architect-Professional course opens once that gate is cleared. The Forward Deployed Engineer programme follows it, and the flagship opens with its own outline. Each programme opens only when its gate is cleared.

The full ladder, rung by rung Students sign in