04 Human proctoring
A person signs the result. Always.
A proctor session runs one of two ways, and both end at the same place: a named human explicitly accepting, correcting or rejecting every result.
Manual proctoring
No participant devices required, and no network. The proctor runs a roster, drives timers and repetition counts by hand, records invalid attempts, and attests each result. Every increment, decrement, invalidation and correction is retained as an append-only action history, so a final count can always be reconstructed.
Paired athlete devices
Up to thirty roster positions, each bound to one athlete and one active event. Devices estimate locally and send authenticated aggregate events — counts, timing, state, confidence. The dashboard labels every live value an estimate until the proctor acts on it.
Athlete device
- Captures and estimates locally
- Buffers when the link drops
- Proposes — never finalises
Authenticated aggregate
counts · timing · state · confidence
Never transmitted
video · depth maps · face geometry
Proctor dashboard
- Issues the authoritative start and finish
- Shows no camera feed by default
- Requires an explicit human decision
Athlete-event states the dashboard must distinguish
- Paired
- Ready
- Calibrating
- Active
- Offline
- Awaiting review
- Attested
A disconnected device is marked offline and its evidence is buffered — never auto-finalised. Conflicting values are shown side by side with timestamps and the correction reason; they are never silently overwritten.