All seven checks matter, including immutability and the ugly edge cases.
INDUSTRY NEXT / OPEN PROOF 001 / RUNS IN YOUR BROWSER
TOPCODER
Proof before pedigree.
One small system is broken. Repair it, pass seven checks, explain the move, and leave with a portable receipt. No account. No résumé theater. No speed bonus.
Open ticket 001- TIME LIMIT
- None
- UPLOADS
- None
- TOP CODER
- 90+
A short change note is part of the work. Code without a reason is unfinished proof.
This is a signal of care on one bounded task—not a universal rank or a hiring oracle.
THE LOCAL PROOF BOOK / TWO TICKETS
Build a small
body of proof.
Reconcile revisions, cancellation, priority, and time without mutating the caller.
OPEN HERE TICKET 002 / ASYNC + CONCURRENCYThe Promise PoolKeep parallel work moving without losing order, exceeding capacity, or swallowing failure.
OPEN0 sealed. 2 still open.
TICKET 001 / THE MESSY QUEUE
Repair the
release order.
Your code never leaves this page. Checks run in a disposable, network-blocked browser sandbox; your draft is stored only on this device.
Proof checks
Waiting for your first run.
- EMPTY IN / EMPTY OUTHandles the quiet case.WAITING
- LATEST REVISION WINSStale updates cannot lead.WAITING
- CURRENT CANCELLATION HOLDSDeleted work stays deleted.WAITING
- PRIORITY DESCENDSThe urgent work goes first.WAITING
- EARLIEST BREAKS A TIEEqual priority stays predictable.WAITING
- STALE PRIORITY CANNOT LEAKA previous revision cannot distort order.WAITING
- INPUT REMAINS INTACTThe caller keeps what it passed.WAITING
YOUR PORTABLE PROOF
Carry the
receipt.
The result is local and self-issued. Copy it into a portfolio, an application, a pull request, or a conversation. The receipt says exactly what happened—and what did not.
Seven correctness checks
Legible change note
Complete proof seal
RUN THE TICKET
- CHALLENGE
- Ticket 001 / The Messy Queue
- CHECKS
- 0 of 7 passed
- NOTE
- Waiting for a change note.
- BOUNDARY
- Local browser proof / not a global rank
THE HONEST BOUNDARY
A sharp signal.
Not a totalizing score.
Reading a contract, handling stale state, writing deterministic JavaScript, preserving input, and explaining a repair.
How someone collaborates over months, learns a new system, handles production pressure, or fits every engineering role.
Bring the receipt and one shipped thing. Talk through the tradeoffs. Then do a small real task together.