Chandra Teja Pannem

1. 01RecordSubmission and judge job are written to Postgres in one transaction.
2. 02RunA worker claims the job and runs submitted code in a restricted Docker container.
3. 03ReturnThe verdict is saved and status updates reach the web app over SSE.

Workers use expiring leases and heartbeats; fencing prevents a stale attempt from overwriting a newer verdict.

1. 01MarkChoose the subject in a frame with a point prompt.
2. 02TrackPropagate the mask through the clip.
3. 03ReviewInspect and correct masks where they drift.
4. 04ExportCreate transparent video, image sequences, or mask data.

The studio has a CPU baseline and an optional SAM 2 tracking path. A FastAPI service handles video work while the browser receives progress updates.

1. 01PlayA Python rules engine owns the game state and serves real-time matches over WebSockets.
2. 02InspectA replay interface shows the moves and state changes from a match.
3. 03MeasureA seeded experiment runner records outcomes with confidence intervals.

The game uses a deterministic 4×4 probability model. A separate Qiskit/Aer circuit demo explores measurement; the game itself is not a quantum circuit simulator.