The Forge Ladder — how you actually earn a rung

The Forge is a proving ground, not a course. You earn a rung by shipping real governed work and defending it — never by attendance.

Most credentials certify that you sat through something. This one certifies that you did something and could explain why, under questioning, to someone qualified to disagree with you.

Learn = prove = deliver, in one motion

The same supervised build does three jobs at once:

  1. It develops your capability.
  2. It is the certification evidence.
  3. It is real delivery.

That’s what makes it proof-of-doing rather than proof-of-attendance — the same logic as OSCP or CREST, where nobody cares how you prepared, only whether you can do it.

The grid: courses certify cells, certs certify roles

Capability is a route × depth grid. Each cell — one route at one depth — is a certifiable competency.

Build Operate Assure Direct
T1 governed workflows coordinates a service reviews against policy frames a use-case
T2 owns builds runs a book of clients threat-models owns a business case
T3 designs systems owns delivery ops sets controls owns strategy
T4 authors standards head of delivery head of governance Chief AI Officer
  • Courses certify cells — granular, stackable.
  • Certs certify roles — a shape across the grid, not a point.
  • You stack cells to become a role.

A few of the flagship shapes:

Role Shape
AI Builder Build T2 (+ Floor)
Solo Integrator T2 across all four routes
AI Solution Architect Build T3 + T2 in the other three
Master T4 in a primary route, T3 across the rest

This is how the badge answers “how integrated are you?” — a Specialist is deep and narrow, an Integrator is wide. Enterprises hire specialists, one per seat. Solo and micro operations need integrators.

The dual gate

Every rung has two gates, and they’re deliberately different in kind:

Portfolio — the work itself. What you shipped, in the real world, with real constraints.

Viva — a live defence. Someone qualified asks why you made those calls, and what you’d do differently.

The viva exists because portfolios can be bought, borrowed, or generated. A live defence of your own reasoning cannot. We score the thinking, not the polish — a rough build you can fully justify beats a beautiful one you can’t.

Why it can’t be rushed

You climb by shipping work in that layer. A governed build feeds Build. A threat model feeds Assure. A scoped business case feeds Direct. A mapped process feeds Operate.

There’s no way to accumulate that in a weekend, and that’s the point. Time cannot be compressed — the whole model is built on the observation that removing the supervised middle rung is what broke the expert pipeline in the first place. Rebuilding it means actually doing the reps.


Post your work here. Portfolio is for evidence, in progress or finished. The most useful posts show the decisions and the dead ends, not just the result — because that’s what a viva will ask about anyway.