The handbook may change continuously, but an assessment contract needs a version so a completion record has stable meaning.
Version Meaning#
- Patch: wording, links, or checks improve without changing competencies.
- Minor: backward-compatible competency/evidence is added.
- Major: required competencies or pass criteria change materially.
Release Checklist#
- Freeze learning objectives, rubric, fixtures, and deterministic checks.
- Run the complete Automated Validation suite.
- Reverify changed volatile claims.
- Record all untested human-only behavior as residual risk; do not invent a pilot result when a cohort is unavailable.
- Obtain lab-owner approval for policy/pass-criteria changes.
- Tag the assessment contract and update the completion-record version.
- Publish a concise change note and refresher requirement.
An automated pre-release may proceed without an alpha/beta cohort when the technical gates pass and the limitation is explicit. Production front-door cutover additionally requires the synthetic non-admin GitHub transaction in Generated Passport Deployment. Human learning validation remains required before claiming measured usability or comprehension, not before completing the implementation.
Do not invalidate an existing passport silently. State which changed competencies require a refresher.