Step 2 · measurement-grade residual run (synthetic · education / therapy shaped)

Residual ops · timed last-mile

After robot event → portal context → observation log → notifications → evidence → human gate → confirm. Timers record practice measurements. Not a live district or clinical system.

From event

Event: —
Robot: —
Student: —
Classroom: —
Trigger: —
Baseline (plan): 9-14 min / event

1 Context 2 Portal fields 3 Notifications 4 Evidence 5 Verify 6 Human gate

Run timer: 0.0s · Step: 0.0s · context

1 · Event context (robot session already complete)

No educational or clinical re-determination. Confirm residual still required on the operational side.

Support / case portal reference Student ID as shown on portal (synthetic)

2 · Portal residual fields

Session / lesson code

Escalation level

Observation / case note (portal)

3 · Draft notifications (staged, not sent)

These drafts are proposed only. External send requires human gate approval.

Teacher / SPED draft Caregiver / family draft

4 · Evidence package

Evidence / session packet / dossier notes

5 · Verification & quality

Residual value is accuracy, consistency, verification, and documentation — not only minutes.

Optical verification (inputs / outputs confirmed on screen) Telephony / voice coordination (if used) Execution quality (accuracy, consistency, completeness)

6 · Human gate (irreversible)

I approve irreversible residual actions (portal log submit + external notifications) for this synthetic case. Without this check, submit is rejected — same discipline as production.

← Event