Proof and capabilities

Studio → Proof (the page is titled Capabilities). A capability is a real skill your team must prove — *"Start with one real skill your team must prove — not a course title."* Creating requires Edit content (content:write).

1. Add a capability

Enter a name (for example *Safe knife handling*) and choose Add capability.

2. Create the rubric

Open the capability. The rubric defines what evidence is scored against — the starter form suggests three weighted criteria (for example Safety 40%, Technique 40%, Communication 20%). Name the rubric and criteria, then choose Create rubric. Criteria appear as badges like Safety · 40%.

3. Create a proof gate

The gate is what learners actually receive — *"Learners submit evidence against the rubric in the learner app (Tasks → Proofs). Publish a gate, then assign it."*

1. Pick the Rubric (when more than one exists).
2. Enter a Gate title (for example *Close-out walkthrough*).
3. Write Instructions for learners — the default is *"Record a short video (under 2 min) showing the full standard. Speak the steps out loud."*
4. Choose Create proof gate.

New gates are configured for AI-then-manager scoring with a 70% pass threshold, and accept video, photo, and text evidence. The gate's badges show its status, scoring mode, and pass mark.

Publish and assign

Choose Publish on the gate, then Assign — you will see *"Assigned "{title}" to {n}. Learners open it under Tasks → Proofs."* Open learner link previews exactly what learners see.

The review loop

Learners capture evidence and submit (see Submitting proof). Automated scoring runs first where configured, then managers with Review proofs permission confirm or send back from Approvals. Passed proofs complete the learner's task and any course/program step built on the gate.