Predicai Academy Progression Map

The progression spine.From task clarity to system proof.

This is the architecture of the Academy. Each level changes the role, tightens the standard, and produces one component of the final system. The result is not completion. It is a connected operating system.

L1 Definer
L2 Evaluator
L3 Builder
L4 Governor
L5 Architect
Capstone Proof
The system map

One spine. Six stages of capability.

The logic is cumulative. Level 1 defines the work. Level 2 classifies the work. Level 3 structures the work. Level 4 governs the work. Level 5 makes it transferable. Capstone proves the whole system still holds when connected.

Progression spine — Capability is built in sequence. Not in parallel.
clarity
structure
judgment
L1
Definer

Intent Protocol

If AI has to guess, the work was never defined.

What this level forces
This level forces clarity.
Lesson anchor
Define the work before execution begins.
Artifact
Intent Protocol
Shift
Request → defined task
Open Level 1 →
L2
Evaluator

Time Ledger & Value

You do not save time. You recover capacity.

What this level forces
This level forces classification.
Lesson anchor
Sort work into automate, augment, or human-only.
Artifact
Time Ledger + Value Audit
Named concept
Defensible + failure cost
Open Level 2 →
L3
Builder

Workflow System

A prompt is a task. A system is a workflow.

What this level forces
This level forces structure.
Lesson anchor
Prompt → chain → workflow
Artifact
Workflow System Design
Named model
Reader → Thinker → Writer
Open Level 3 →
L4
Governor

HITL Judgment

Systems don’t fail at execution first. They fail at judgment.

What this level forces
This level forces judgment.
Lesson anchor
Human review is not decoration. It is governance.
Artifact
HITL Judgment System
Named model
Trigger → Monitor → Rollback
Open Level 4 →
L5
Architect

Doctrine & Scale

A useful system helps one person. A real system can be used by others.

What this level forces
This level forces transferability.
Lesson anchor
Doctrine removes dependence on memory.
Artifact
Doctrine System
Named shift
Personal workflow → team-usable doctrine
Open Level 5 →
Capstone
System Proof

System Dossier

Five artifacts. One connected system. Proof is awarded here.

What this stage forces
This stage forces resilience.
Lesson anchor
If one component changes, the others must still hold.
Artifact
Capstone System Dossier
Named concept
System resilience + connected proof
Open Capstone →
Define
→
Classify
→
Structure
→
Govern
→
Transfer
→
Prove
Each level solves the failure mode created by the level before it. That is why the spine matters.
How the system actually works

Lesson pages teach. Artifact pages prove.

The Academy is not content consumption. It is a two-part system. Lesson pages build understanding. Artifact pages verify that the understanding holds up in real work.

Lesson Pages
Understanding

This is where the logic is explained.

Lesson pages introduce the concept, show contrast, and explain the logic behind the level. Every lesson includes a Gold / Good / Bad section to make quality visible.

What you seePrinciples, examples, Gold / Good / Bad contrast
What you doRead, compare, understand the pattern
What it producesClarity
Failure mode“I understand it” but cannot apply it
Artifact Pages
Proof

This is where the work is evaluated.

Artifact pages require you to build something real using the system. This is where the Predicai Standard is applied and weak work is exposed before it advances.

What you seeTemplate, checklist, submission criteria
What you doBuild, refine, submit
What it producesEvidence
Failure modeWeak work is exposed immediately
How they connect
Lesson → Understanding → Artifact → Proof → Next level unlocks

If it only exists on the lesson page, it is knowledge. If it holds up on the artifact page, it becomes capability.

How the logic compounds

Each level fixes the limit of the one before it.

L1 → L2 You cannot classify work you have not defined.
L2 → L3 You cannot build a workflow until you know what should be automated, augmented, or kept human.
L3 → L4 You cannot govern judgment until the workflow and handoffs are explicit.
L4 → L5 You cannot transfer a system until review rules, ownership, and failure handling are documented.
L5 → Capstone You do not have proof until the parts hold together under review as one connected system.
What the operator becomes

This is not a learner path. It is a role progression.

Definer Makes work explicit before AI touches it
Evaluator Separates valuable work from noise
Builder Turns repeated work into a reusable system
Governor Places human judgment where it matters most
Architect Makes capability transferable to others
Proof-holder Shows the system survives connection and review

The model is not the system.

This map is the curriculum spine. Lesson pages build understanding. Artifact pages verify capability. Capstone proves the system holds.

Open Academy → Open Orientation → Proof Checklist →