Challenge-Based Certification
Certification earned through submitted proof of real work, challenge by challenge. Attendance proves you were in the room. Artifacts prove you can do the work, and the certificate certifies something that exists.
Five steps, repeated per mission
The AI Officer program runs as six missions, each ending in a real artifact. The loop below runs inside every one of them, and each artifact becomes raw material for the next mission.
How the loop works
Mission one is program planning: the learner picks a real workflow from their own team and writes a 5D brief for it. That choice matters, because the same workflow is what they build, wire, and ship across the remaining missions. Nothing in the program is hypothetical.
Each mission is a set of guided challenges done alongside an AI thinking partner. The learner is practicing the three skills of the AI Officer craft: workflow design, organizing information, and creating instructions.
Every mission ends in an artifact: a program brief, a packaged AI tool a teammate can run, an automated workflow, an agent with guardrails, and finally working code on a real stack. The artifact is the submission.
The test is simple and honest: can you complete the challenge? The AI Buddy checks that the artifact is genuinely complete, with a concrete goal and a real number where one is required, not a vague idea. Complete work passes.
A passed mission unlocks the next. At the end, the learner holds a certification backed by a portfolio, and their team holds something better: an AI program running on their actual work.
The seven elements
Every workflow we document has the same anatomy: seven elements, each assigned to a human, a machine, or both. This is the Centaur Map from our workflow design method.
A learner starts a mission. Each mission targets one real workflow from their own team.
The textbook, the guided prompt, and the learner’s real work: their team’s workflows, data, and goals.
Does the deliverable pass? The AI Buddy checks completeness against the challenge; humans certify the program.
A passed challenge unlocks the next mission. The artifact from each mission feeds the one after it.
Proof artifacts: a 5D program brief, a packaged prompt, a wired workflow, and finally a program running in production.
Certification plus a portfolio of artifacts the learner keeps and their team keeps using.
Completeness per challenge, and the only metric that matters at the end: is the program shipped and running?
The standing rules
- Every challenge is worked on the learner's real team workflows
- Every mission ends in a submitted artifact
- Grading is completeness: can you do the thing, yes or no
- The final mission ships to production, not to a slide deck
Why it works
- Artifacts compound: each mission builds on the last one's output
- Real work means the ROI arrives during the program, not after it
- Completeness grading removes subjectivity from certification
- The portfolio outlives the course and keeps working
This is the same method documented across this whole section. Explore the Training & Certification program →