Skip to content

Classroom follow-on: Author and validate the first production staged KT Case Study #317

Open

Description

@MajorIncident

Roadmap status — deliberately deferred

Do not begin this issue until both #316 is complete and the approved pre-production hardening sequence #328 → #329 → #330 has landed. The first production case should be authored against the final access, maintenance, and startup contracts rather than temporary compatibility behavior.

Canonical planning contract: docs/preproduction-hardening.md.

Goal

Turn the completed #313 staged-simulation engine into a real Instructor-runnable KT exercise by authoring the first production simulation definition from authoritative instructional source material.

Preconditions

Depends on protected rich staged-content/asset delivery. Do not work around missing asset support by flattening or guessing source material.

Required work

  • select the first official Case Study only from authoritative participant/instructor source material supplied for the repository;
  • define source-faithful stage boundaries, Student objectives, initial/optional releases, suggested timing, debrief edit policy, Intake targets, and Instructor facilitation/debrief/exemplar references;
  • attach reviewed protected pages/images/tables/evidence by stable asset IDs;
  • explicitly document which source page(s)/section(s) justify each stage/release;
  • review the staged definition against Instructor material before making it production-selectable;
  • run a complete Instructor + multi-team Student browser rehearsal from Start Class through final debrief/completion;
  • prove future-stage and Instructor-only material remain inaccessible;
  • validate late join, reassignment, Ready, freeze/unfreeze, checkpoint-vs-live, mobile, and accessibility using the actual authored case;
  • keep completed Intake state separate from the staged Student feed.

Must not do

  • do not infer official stage boundaries from a completed Intake;
  • do not invent case evidence, teaching points, or model answers;
  • do not assume similarly named cases across KT books are identical unless the supplied sources establish that;
  • do not expose a full protected case payload as a shortcut.

Done when

At least one official Case Study appears in the Instructor staged selector and can be run end-to-end without manual PDF/page coordination or unreleased-content leakage.

Relationship

Follow-on to #313. Production official-case staging was intentionally deferred throughout PR #315 until authoritative material could be supplied and reviewed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions