THE COMMON BUILD STANDARD
Learn the whole loop: diagnose, build, operate, transfer.
The program is structured around production evidence, not course completion. Whatever your entry point — team cohort or solo — the standard you graduate against is the same.
CURRICULUM · FOUR UNITS, ONE STANDARD
What the 90 days are made of.
UNIT 1 · WEEKS 1–3
Diagnose
Read a job as a system. Map the flow as it actually happens, find where hours leak, and choose the right problem — the one worth building for.
▸You must be able to show: a mapped workflow with the friction quantified
UNIT 2 · WEEKS 3–7
Build
Assemble a pragmatic stack with minimum viable governance. Ship something observable early; iterate against real exceptions, not imagined ones.
▸You must be able to show: a working system with its failure modes documented
UNIT 3 · WEEKS 7–11
Operate
Run it in production. Measure adoption, costs, exceptions. Learn what silent failure looks like and how to catch it before a customer does.
▸You must be able to show: a 30-day production log with exceptions handled
UNIT 4 · WEEKS 11–13
Transfer
Document and hand over so the system survives you. For teams, this is where the internal referent takes the ledger. This is graduation.
▸You must be able to show: a handover another person actually ran with
BUILD REVIEW · A REAL MOMENT
“The system works on the happy path. Now show what happens when data is missing, who gets alerted, and how you roll it back.”
That is the level of conversation that separates professional practice from a polished demo. Every builder faces it, on their own system, several times.
DELIVERY INFRASTRUCTURE · NOT THE PRODUCT
Sensei remembers, so sessions compound.
Between sessions, Sensei — the same guide walking this site with you — keeps track of each builder’s progress and blockers. Reviews start where the last one ended instead of from zero.
To be clear: Sensei is delivery infrastructure, not the product. The product is your people, changed.
B · SOLO PATH
You want to become the person who knows how to build.
A demanding professional path for employees, independents, and career changers. Same loop, same reviews, same standard — but the portfolio is yours: you build, document, and defend real systems you can show to any employer or client.
Real systems, not exercises
You automate real work — yours, or a partnered problem — to the production standard.
A defended portfolio
Every unit ends in a documented system you defend in review. That portfolio is the credential.
The same graduation
You leave able to diagnose, build, operate and transfer — the whole loop, alone if needed.