Why it exists
Proof anyone can open.
Graduates leave with graded work records. The capstone is the public piece — inspectable, scored, and linked to a receipt. Employers and graders do not take attendance as proof.
- Artifact must be public on a STEADYWRK surface or linked static receipt
- Fictional or first-party targets only — no live customer names
- Rubric scores filled before instructor re-grade
- Verify path required (/verify or durable receipt URL)
Template
Five sections. Fill every one.
01
Brief
One paragraph: what you were asked to do, for which surface, and what “done” means. Name the product or ops lane (Store Guard, dispatch evals, handbook note) — not a private client.
02
Method
Numbered steps you actually ran. Include tools, prompts you verified, and where you caught a bad answer. A peer should be able to follow the same path.
03
Evidence
Public links, HTML/JSON artifacts, or live pages. Private practice logs alone do not pass. Prefer a STEADYWRK surface or a static demo file under /public.
04
Receipt / verify
A durable receipt URL or certificate check at /verify. Graders open this first — if they cannot verify, the artifact is incomplete.
05
Rubric score fields
Self-score each rubric row before submission. Instructors re-grade against the same fields. Completion needs a passing public artifact — not attendance alone.
Rubric
Score fields
Self-score each row. Instructors re-grade on the same fields. Blank scores fail submission.
Brief clarity
States the problem, scope, and success condition without fluff.
__ / 5
Method discipline
Shows steps a peer could rerun — tools, checks, and decision points.
__ / 5
Evidence quality
Public, inspectable artifacts — not screenshots of private chats alone.
__ / 5
Receipt / verify
Links a verifiable receipt or /verify surface anyone can open.
__ / 5
Operational English
Client-ready language: precise, calm, zero-loss notes.
__ / 5
Earn the seat. Then ship the proof.
Apply through the repaired intake. Read the offer. Study the fictional demo before you write yours.