[ ] CONFERRED
[ ] WITHHELD
Work clears the production bar or it doesn't. There is no partial credit, no 'mostly done', no 'we'll fix it in prod'.
How judgment is measured.
The gate is rubric-as-code. Every exit is the same question: would this ship? The rubric is versioned, published, and forkable.
Incident Days
We inject real failures into your workspace — a leaked secret, a runaway agent loop. You diagnose under time pressure.
Rubric-as-code
The gate: automated checks + agent first-review + human sign-off. First-pass feedback in minutes, not days.
The signed credential
Your diploma is a cryptographically signed artifact on your own domain — verifiable, federated, owned by you.
Run on your metal
The whole stack is FOSS and self-hostable. Learn to operate it without renting anyone's cloud or trusting anyone's model blindly.
Gate questions
What does CONFERRED mean exactly?
CONFERRED means the automated checks passed, the agent first-review found no blockers, and a human signed off. The credential is cryptographically signed and published to the register. It means the work cleared a production bar, not just a rubric.
What happens when work is WITHHELD?
You receive a written finding: what the rubric flagged, what the agent review caught, what the human saw. You have one resubmission included. After a second WITHHELD, you repeat the module — not the program. The Incident Day that caused the WITHHELD becomes your case study.
Can I see the rubric before I submit?
Yes. The rubric is code, versioned, and published. Read it at gitea.aipe.dev/moderncodingschool/rubric. You're graded against the version current at your submission time — no retroactive changes.
What is an Incident Day?
An Incident Day is an unscheduled 2–4 hour session where we inject a real failure into your workspace: a leaked secret, a runaway agent loop, a broken deploy. You diagnose under time pressure. The record of your response is part of the capstone gate.