Work becomes proof.
Proof compounds.

Five stages connect realistic product work to a career-ready record an outsider can verify.

01
Learn
Understand what the job actually asks of you.
02
Work
Do realistic product work with real constraints.
03
Build
Turn what you did into an explainable record.
04
Prove
A coach confirms it. An outsider attests to it.
05
Advance
Use it in interviews, applications and live work.

No silent promotion from a self-report, AI draft or score to Verified.

THE DELIVERX EVIDENCE PRINCIPLE
1

Do realistic work

Work through product situations with real constraints, stakeholders, and consequences. In Experience, this means joining a simulated company — MediFlow, GreenGrid, or LearnFlow — as a Product Manager. In the Workspace, this means your actual delivery role. Either way: the work happens first. Evidence doesn't exist before you act.

ExperienceWorkspaceCoaching capstone
Trust note: The hiring interview and entry ceremony are narrative context. Neither creates evidence, capability, or Verified status.
2

Capture the artefact

When you complete and submit work, an immutable artefact version is created. An artefact_version_id is assigned at the moment of submission — this version is locked. It carries the source type (Experience simulation, coaching submission, or Workspace observation), the framework version it will be judged against, and the timestamp.

Trust note: Evidence is private by default. Nothing is shared without your explicit decision to share it.
3

Judge capability

Evidence is assessed against pm-core@2026.1, the versioned capability framework for this framework. A two-pass AI scoring system runs: a primary grader assesses each dimension, and an adversarial verifier challenges the assessment. The result is a confidence band — explainable, never decorative.

For coaching submissions, a human coach reviews the AI draft and must confirm before any ledger entry is created. Coach confirmation is the only pre-condition that cannot be bypassed.

Capability EngineScoreRunCoach-confirmed
Trust note: The Capability Engine is the only component that writes capability levels. UI, ceremony, interview, learning, and recommendations never write capability.
4

Package readiness

Strong evidence becomes an explainable portfolio and a career readiness narrative. Launchpad surfaces which claims are evidence-backed, which are still heuristic (always labelled), and where evidence is thin. Interview Lab connects your STAR stories to real artefacts you can defend.

Trust note: Readiness uses labelled heuristics where ScoreRun data is thin. No unexplained percentages. Every signal is either evidenced or flagged.
5

Verify externally

Only an independent person outside DeliverX can activate the Verified signal. You request attestation via Launchpad. Your attestor receives a secure token, reviews the specific evidence you've selected, and confirms it reflects demonstrated capability they've witnessed. On confirmation, the ledger entry receives an external_verification record and Verified lights.

Trust note: Verified is never lit by a ScoreRun, by coach confirmation, by Experience completion, or by any action inside the platform. External attestation is the only gate — enforced at the architecture level.