Score a verification task
A verification task turns “this looks fine” into a number. It carries a rubric, a subject, and a passing score, and it resolves into one of three verdicts that other work reacts to.
This page uses SUM-16, the nightly regression sweep of the Summitline route builder that Sana holds.
What a verification carries
Section titled “What a verification carries”- A subject, the thing being checked. It points at a field on another task, an artifact, or something outside the workspace.
- A rubric snapshot: the criteria, each with a weight, copied onto the task when it was created. The snapshot is why a score stays meaningful after the rubric is later edited.
- A passing score, the weighted total the subject has to reach.
The lifecycle
Section titled “The lifecycle”| State | Means |
|---|---|
| pending | Created, not started |
| scoring | Being worked through |
| passed | Met the bar |
| needs revision | Did not meet the bar, but the work is worth another pass |
| failed | Did not meet the bar, and it is not worth another pass |
Score one
Section titled “Score one”-
Open the task
Section titled “Open the task”The Overview tab shows the subject preview above the rubric.
-
Score each row
Section titled “Score each row”Every criterion takes a score, and the panel keeps a running weighted total against the passing score as you go.
-
Add notes
Section titled “Add notes”Optional, and worth writing when the verdict is anything other than passed. A failing check needs the steps to reproduce it.
-
Choose the verdict
Section titled “Choose the verdict”Pass stays disabled until the total actually reaches the passing score, so a pass cannot be given by accident. Needs revision and Fail are always available.
Once submitted, the panel becomes read-only: the scores, the total, and the notes stay on the task as the record of the check.
What each verdict does next
Section titled “What each verdict does next”A verification created as part of a larger piece of work reports back to its parent:
- passed moves the parent on. For a content task, that means your review.
- needs revision sends the parent back to drafting.
- failed kills the parent, with the failed verification as the reason.
A verification created on its own (a release gate, a nightly sweep) simply records its result.
Creating one
Section titled “Creating one”+ New ▾, then Verification, on the Tasks page. A verification needs a rubric to score against, so most are created by the work that needs them (a content task entering verification, or an initiative’s acceptance criteria) rather than by hand.
All of them are filterable in one place: on the Tasks page, open Filters and set Type to Verification.
Next steps
Section titled “Next steps”- Run a content task: the pipeline that spawns verifications.
- Decide an approval: the gate after a pass.
- Task types: how the typed lifecycles fit together.