Practice your understanding.
Walk the changed behavior, the risky paths, and the missing tests. The coach asks rehearsal questions. Those questions do not appear in the live proof.
A check on the current patch
Understand it.
Say it live.
Ship it.
Prove you know what you ship.
Practice if you want. Then answer a short set of patch questions on live video before the pull request can merge.
SlopProof / understanding required
Before merge
Fast code still deserves a slow thought.
Code can arrive fast. Someone still has to know what it does. SlopProof is that pause before merge.
Practice or Proof
Practice if you want. Prove when you know it.
Practice is there if you want it. Small patches and people who already know the change can skip it and go to Proof.
Prove your understanding.
Open the challenge on your phone. Questions show one at a time. You answer on live video in one continuous take. Keep that tab in front. Leave it, switch apps, or look at a second screen, and the proof aborts.
The real product · 9 steps
One contributor path, from the pull request to the required check.
The product
Practice first, or go straight to Proof.
Both sit on the same check. Practice is optional. The live questions stay hidden until recording starts.
src/runtime/reload.ts3 learning goals
- state.publish(candidate)
+ const snapshot = state.capture()
+ state.publish(candidate)
+ try { await callback() }
+ catch (error) {
+ state.restore(snapshot)
+ throw error
+ }
+ const snapshot = state.capture()
+ state.publish(candidate)
+ try { await callback() }
+ catch (error) {
+ state.restore(snapshot)
+ throw error
+ }
Understanding coach
Atomic visibility
Practice question · never reused in live proof
Can a concurrent reader observe candidate state before the callback succeeds?
Trace publish → callback → restore. Name the exact interval in which another reader can enter.
study the edge
case ↗
case ↗
Live proof handoff
Scan when you're ready. The questions stay hidden until you record.
- One-time mobile link
- Camera + microphone
- One continuous take. The tab stays in front.
- Leave the tab, open another app, or use a second screen, and the proof aborts.
- No pause or retake
Scan when you can keep this tab in front. Leave the tab and the take is over.
SLOP/PROOF LIVE
QUESTION 2/301:17
Why can another reader still observe candidate state before rollback?
One take · uploading encrypted · head 9f31c2e
After the take
A multimodal model reviews the recording. A maintainer can review it too.
The model sees the transcript, a few frames, timing, the patch, and the rubric.
Live capture
A risk-sized question set, one take, bound to this PR revision.
Encrypted vault
A per-attempt key protects the original recording.
Extract
Transcript, timestamps and a few reasoned frames.
Multimodal LLM judge
Patch references, transcript, frames, rubric, gaps and contradictions.
Outcome
A maintainer can review the take and close the check.
Video security
The recording is encrypted, then deleted.
A live proof can include your face, voice, and how you reason about the patch. The recording is evidence with a short life.
Encrypted per attempt
Each live proof gets its own encryption key. Private object storage alone is never enough to play the recording back.
Need-to-see access
Only authorized maintainers can open evidence when review is required. Every access is short-lived and auditable.
Deleted on a short clock
Recordings disappear after 24 hours by default, and sooner after a clear pass. Storage lifecycle rules are a second deletion backstop.
Bounded model accessSlopProof exposes only a temporary, job-scoped media reference. Deployment operators choose the model endpoint and are responsible for its processing and retention terms.
Hard limitsNo face recognitionNo gaze tracking or room scanNo public video or transcriptNo permanent evidence archive
Beta
Install the App. Then request access.
Start on GitHub: install SlopProof for your personal account or for an organization where you have permission to install GitHub Apps, then choose the repositories you want to try. The installation stays inactive until we approve your beta request.
- 1 · Install the App
- 2 · Choose repositories
- 3 · Request access
Your patch. Your take.
Practice the patch if you want. Then record one take and ship.