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.
Compatible Copy Or New Evidence#
Moving an optional hint, improving a link or adding unsaved practice can preserve assessment meaning. Requiring a new explanation/artifact or changing accepted evidence needs a reviewed version/migration. Existing completion, draft and pending submission behavior must be specified before such a release. See the learning-evidence decision.
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.
- Confirm the launcher release notes declare the exact compatible curriculum version and that every platform asset has a GitHub SHA-256 digest.
- Test update, reopen, and forced-failure rollback on Windows, macOS, and Linux.
- 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.
An ordinary launcher patch may be offered through Update and reopen only when it can read and run the installed curriculum without changing its assessment meaning. Publish a separate migration when the curriculum version changes. Keep the previous compatible release available during rollout.
Python 3.0.0 Compatibility#
The v0.6.0 source introduces a new required Python evidence contract for new 3.0.0 assignments. The 2.1.2 curriculum is frozen separately; a launcher update preserves its original route and checks. No refresher is forced on existing students. The owner delegated review of the concrete acceptance/migration cases.
Both web bundles, protected template versions and catalogue versions must be published together with the compatible controller. Rollback cannot replace the controller with a version unable to assess already created 3.0.0 assignments. Keep both contracts available for pending submissions and historical records. See the reviewed Python contract.
Git 4.0.0 Compatibility#
The owner confirmed the Git understanding contract and deployment on 2026-10-10. New starts use 4.0.0; existing 2.1.2 and 3.0.0 Passports retain their original questions, grades, drafts, pending SHAs and completion meaning. The v0.7.0 launcher carries all three full bundles. No forced refresher. The controller uses the trusted assignment version and retains the actual published template hashes. Deploy it before the new launcher and website, then cut over the exercise default. After any 4.0.0 start, rollback must keep three-version controller support. Keep previous launcher releases available. For this rollout, the owner explicitly waived the unavailable authenticated non-admin GitHub transaction and accepted the documented offline synthetic transaction. Production authorization stays enforced. This is a release-specific exception, not a removal of the usual gate. See the Git contract review.
Euler 5.0.0 Compatibility#
The owner approved the Euler array planning contract and publication on 2026-10-12. New 5.0.0 starts use three planning decisions: combined CPU/system memory with another job, a cap within both fictional budgets, and a changed memory option. The declared cap-one repair and submitted file remain the same. The new controller matches Go's answer cardinality and strict file size below 100000 bytes. These changes are scoped to the new contract; 2.1.2, 3.0.0 and 4.0.0 keep their original questions, interpretations and completion meaning.
The v0.8.0 launcher carries all four complete bundles. No existing assignment is migrated and no refresher is forced. Preserve the actual published template hashes and all private student records. Publish controller support first, then the qualified launcher and website, then the new exercise default. After a 5.0.0 assignment exists, rollback must retain four-version support.
Following the owner's earlier instruction to use local synthetic account checks while the separate test login is unavailable, this rollout uses the recorded offline non-admin registration/assessment/reopen transaction. Production authorization stays enforced; this does not establish an actual authenticated test-account submission or measured learner comprehension. See the Euler integration evidence.
Handover 6.0.0 Compatibility#
The owner explicitly authorized activation and publication on 2026-10-12. New starts use three handover decisions and a bounded inventory-consistency check. Preparation creates a fixed synthetic Git project and a missing worksheet, while preserving any existing draft. The optional fresh-clone run introduces no Python prerequisite and installs no external packages. Neither checker executes a command supplied in a learner's document.
The v0.9.0 launcher carries five complete bundles. Existing 2.1.2, 3.0.0, 4.0.0 and 5.0.0 keep their questions, criteria, identities, routes, drafts, attempt counters, pending SHAs and completion meaning. No automatic migration or refresher. An assigned 6.0.0 learner can prepare and inspect only the fictional inventory through computer setup without regrading completed work.
Preserve actual published old template hashes. Deploy the controller before the launcher and site, then cut over the exercise default. After a 6.0.0 assignment exists, rollback must retain support for all five versions. The earlier owner-authorized offline synthetic non-admin transaction remains the substitute for the unavailable separate login; production authorization is enforced and no actual authenticated pilot is claimed. See the handover publication record.
AI Review 7.0.0 Compatibility#
The owner explicitly approved versioned integration and publication on 2026-10-13. New starts use AI mission version 5 with three scope/authorization/ evidence decisions. Duplicate selections fail in both graders for this new contract. The declared plan artifact and original seven bounded practical checks remain unchanged; human before/after Git inspection covers their limits.
The v0.10.0 launcher carries six complete bundles. Existing 2.1.2, 3.0.0, 4.0.0, 5.0.0 and 6.0.0 retain their original questions, criteria, identities, routes, drafts, attempts, pending SHAs and completion meaning. No automatic migration or forced refresher. Handover computer preparation remains available for assigned 6.0.0 and 7.0.0 learners without regrading completed work.
Preserve the actual published old template/catalogue bytes and protected private records. Qualify exact source, deploy controller support first, then launcher and site, verify them, then cut over the exercise default. After a 7.0.0 assignment exists, rollback must retain all six contracts. The earlier owner-authorized offline synthetic non-admin transaction substitutes for the unavailable separate login; production authorization remains enforced. This is not an authenticated pilot or measured learner comprehension. See the AI integration record.
GPU Review 8.0.0 Compatibility#
The owner explicitly authorized activation and publication on 2026-10-13. New starts use GPU mission version 4: three measurement-based planning decisions and the separate bounded, non-executing fictional script review. Duplicate answers, signed/Unicode CPU values, memory overflow and the strict file-byte bound agree between local and controller checks. Other parser limitations and actual performance still require personal review before a real submission.
Launcher v0.11.0 carries seven full bundles. Existing 2.1.2 through 7.0.0 retain their original questions, criteria, identities, routes, drafts, attempts, pending SHAs and completions. No automatic migration or forced refresher. Preserve the six actual published templates/catalogues and all protected records. Deploy the qualified controller first, then launcher and website; verify those products before cutting over the exercise default. Rollback must retain all seven versions once an 8.0.0 assignment exists.
The owner's previously authorized offline synthetic non-admin transaction remains the substitute for the unavailable separate test login. No production authorization bypass, live account pilot, GPU performance or comprehension claim. See the GPU integration record.
Slurm Header 9.0.0 Compatibility#
The owner authorized the targeted header-safety rollout on 2026-10-13. New starts use arrays mission version 5 and GPU mission version 5. Questions, answers, submission paths and routes stay the same. Both reviewers require unique long-form directives before any command, reject options outside the fictional exercise, and permit only one node and one Slurm task per job. Optional --nodes=1 and --ntasks=1 are accepted. This is a bounded teaching profile, not a general Slurm syntax validator or approval to run a job.
The v0.12.0 launcher carries eight complete bundles. Existing 2.1.2 through 8.0.0 keep their original criteria, questions, identity, grades, drafts, attempts, routes and pending submissions. No regrading, migration or refresher. Preserve seven actual published template/catalogue versions and private records. Publish qualified controller support before the launcher/site, then change the exercise default only after verification. Rollback must retain all eight contracts once any 9.0.0 assignment exists.
The owner's persistent offline non-admin test authorization applies while the separate test login remains unavailable. Production permissions remain intact. See the Slurm delivery record.