Certification
How proof-based certification works
Five steps from enrolment to a certificate anyone can check. The certificate is earned by a working project that passes three stages of review, never by attendance.
The five steps
Step 1
Enroll
Pick a premium course. Before you pay, you can read its brief: the project you will build, how it will be tested and the rubric reviewers use.
- You get
- Course modules, the project brief and rubric, mentor access
- You need
- The free notes the course builds on, or the same background
- Takes
- 6–12 weeks, at your pace
Step 2
Build the project
Build something that works: a pipeline, a model, a service, a notebook. Mentors review your build as you go, so problems surface before formal review, not during it.
- The brief says
- What it must do, on which data, and how it will be tested
- Mentor feedback
- Written, on your repository, at each milestone
- Leaves on the record
- Nothing yet. Your work stays private until you submit
Step 3
Submit your proof
Submit the code, a demo and a short write-up of what it does and how you tested it. Your submission gets a proof ID and a version, and goes on the public ledger.
- You submit
- Code · demo · write-up · test results
- It gets
- AI-PRF-0042 · v1.0.0
- Leaves on the record
- The proof, public from this point on
Step 4
Three-stage review
Your proof is reviewed by the Institute, then the Community, then the Public. Each stage must pass before the next one opens. Every review stays on the record, including requests for changes.
InstituteCommunityPublicStage 1 · InstituteThe Institute’s editorial board.
It installs from your instructions, runs, and does what the brief asks on the test data. Every source is cited.
about 1 weekStage 2 · CommunityTwo or three community reviewers with experience in the field.
They test it against the rubric, try to break it, and accept it or request changes in writing.
2–3 weeksStage 3 · PublicAnyone. The proof, the code and the reviews so far are public.
Anyone can rerun it and comment. An unresolved objection holds the certificate until it is answered.
at least 2 weeks openStep 5
Certificate issued
Your certificate says what you proved, carries the Verified Proof Seal and a certificate ID, and links to the proof and every review. Anyone can check it by ID, for as long as it stands.
Example
Applied Cybersecurity Engineering
Built a working intrusion-detection pipeline, reviewed in public. See the certificate and its record
The rules
When review says no
The full protocol is published as a paper: AI-PRF-0005, Certification by proof.
Changes requested
Reviewers say exactly what to change. Your course includes one resubmission; the new version is reviewed at the stage that asked for it.
Not certified
If the proof still does not pass, no certificate is issued. You keep the course and everything you built, and the reviews tell you what was missing.
Revoked later
If someone later shows the proof does not hold, review reopens. A certificate that no longer stands is marked Revoked, publicly, with the reason. See an example
Public ledger
Proofs in review now
Public review is open to anyone. Read a proof, rerun it, and leave a review.
| ID | Proof | Review | Status | Updated |
|---|---|---|---|---|
| AI-PRF-0049 | DNS tunnelling detector for a campus networkApplied Cybersecurity Engineering | Public | In review | 2026-10-08 |
| AI-PRF-0047 | Support-ticket router with a published evaluationApplied AI Systems | Community | In review | 2026-10-06 |
| AI-PRF-0046 | Flood extent mapping from Sentinel-1 radarEarth Observation with Public Data | Community | In review | 2026-10-01 |
| AI-PRF-0045 | Phishing URL classifier with model cardApplied AI Systems | Institute | In review | 2026-09-29 |