Tutorial Design Baseline
The functional direction comes from v1.2; the current v1.3 specification adds the editorial style accepted after three sample reviews on 19 October 2026. A specification records intent, not proof of implementation, chapter approval, accessibility conformance, or learning effectiveness.
- Reusable specification template: a starting point for another tutorial.
- Lab specification: reader outcomes, curriculum, and acceptance criteria.
- Audit and backlog: the seven coordinated workstreams and their original observations.
- Design decisions: dated direction, conservative defaults, and details awaiting owner review.
- v1.3 editorial audit: original observations, reconciled with the deployed v1.2 baseline.
- Accepted editorial samples: owner-approved examples and the boundaries of that approval.
- Editorial review: chapter-by-chapter changes and regression evidence.
Baseline Reconciliation
Implementation started from a clean main at a7b88a8. At that revision, Chapter 12 had already been removed and published. Its seven slide-source references, quiz, navigation, and counts had been reconciled; three legacy URLs redirect to the first-increment reference. The package’s observations about a remaining remote chapter describe an earlier inspection, not the current state.
The current sequence contains eleven chapters. Existing historical measurement snapshots retain their original counts and paths. Review current behavior against the specification rather than treating the audit as a live status report.
Ownership and Review
The tutorial owner reviews the resulting chapter text, scenario wording, guided explorer entry, and visual treatment. Technical checks establish working behavior, not educational effectiveness. No external learner study is a release prerequisite.
See the implementation review for changed files, local preview links, verification evidence, and remaining owner decisions.
That review describes v1.2. The v1.3 pass starts from clean main at 6d8ee1d; it preserves all existing interactions and source IDs, and returns substantively revised chapters to review.
Use the project source map to locate maintained sources and checks. Keep specific writing rules in CONTRIBUTING.md and terminology in GLOSSARY.md, rather than duplicating them here.