Build experiences students do, not readings they skim

An instructional designer authors a procedure and a rubric. The engine supplies the scene, the sensing and the evidence record. The same tool produces a chemistry wet lab, a physical therapy exam, a tour inside a cell and a business pitch to an avatar — because all four are the same pipeline with a different sensor switched on.

Author

Drop in the handout you already have. The tool reads it, shows you where every line came from, and offers three ways to run it — each saying what it cannot assess.

Start from a handout Open the titration example

Run

The student view. Needs HTTPS for the camera — open it on a deployed URL, not from a file. Works on a laptop in flat mode with no hardware at all.

Run the titration See the last report

How it fits together

Scene	A stack of layered images. The back layer is a picture, or the live camera.
Sensing	Whatever watches the student — a tap, motion, body pose, speech.
Events	Everything a sensor notices becomes one timestamped event, in one format.
Rules	The ID's procedure: when this happens, do that, score this.
Evidence	The event log is the instructor's report. Process, not just a number.

Documentation lives in docs/ — start with concept.md, sensors.md and decisions.md.