Assessment · Rubric · Credential

Skill credentials earned by doing the work, graded against a rubric anyone can read

A candidate submits real work, the contract extracts what was actually done, grades it against a published rubric, and issues a credential any other contract can read.

Submit work for assessment Read the rubric How it works

ISSUED BY

The network, not a person - no single party can mint one

READ BY

Any contract, in a single call - employer reads are free

FIG · 01
THE LEVEL SPREAD

awaiting the first credential

THE PASSES

One transaction, five stages

three exec_prompt calls inside one non deterministic block, on GenLayer

01

Submit

A public url of real work - nothing behind a login, nothing that changes after the read

t+0

02

Extract

Pass one describes what was actually done, and never sees the rubric

rubric blind

03

Grade

Pass two scores that description against the published rubric, criterion by criterion

0 to 5 each

04

Grade again

Pass three asks the same question with the criteria reversed, and the lower band wins

both orders

05

Issue

Every validator reruns all three and has to reach the same level exactly, with no tolerance

finalized

THE ONE THING
THAT MUST NOT MOVE

Extraction runs before grading and never sees the rubric - if the first pass knew what it was being graded against, it would describe the work in the rubric’s own words, and the grade would grade itself.

THE STANDARD

Published in full

The rubric is on chain and quoted on every credential - a result you cannot argue with is not a standard.

NOT CONFIGURED

There is no rubric contract configured, so the rubric cannot be shown.

Freeze one at /deploy, signed in your own wallet, or from a terminal with npm run deploy. Then set NEXT_PUBLIC_JOURNEYMAN_ADDRESS and restart - it is inlined at build time, so a running server does not pick it up on its own. Nothing invented is shown in the meantime.

Freeze a rubric How it works

LEVEL DISTRIBUTION · ALL CREDENTIALS

No rubric contract is configured, so there is no distribution to publish yet.

A rubric where everyone lands on one level is not calibrated - publishing the distribution keeps the rubric author honest.

THE SPECIMEN

What a credential actually says

NOT CONFIGURED

There is no rubric contract configured, so a specimen credential cannot be shown.

Freeze one at /deploy, signed in your own wallet, or from a terminal with npm run deploy. Then set NEXT_PUBLIC_JOURNEYMAN_ADDRESS and restart - it is inlined at build time, so a running server does not pick it up on its own. Nothing invented is shown in the meantime.

Freeze a rubric How it works

A graded credential in two minutes, and every field on it agreed exactly

Submit work for assessment