Start here (judge path)
A short path through GAVEL for judges, with the status stated plainly.
A short path through the project. Everything is PayPal only. A bid is a hold (an ); nothing is charged before at the .
Status, in four lines
- G0 PASS G1 PASS G2 PASS G4 PASS ran against the real PayPal sandbox. Committed run logs exist for G0, G1, G2 and G4.
- G3 IN PROGRESS: the probe started on 7 Nov 2026 at 03:06 UTC, day 0 is recorded, and its final reading is about 12 Nov. No result is claimed before then.
- G5 PARTIAL: speech accuracy is measured on synthetic, noise-free audio and live-room confirmation is the next step, so every voice bid waits for a confirmation.
- of a whole auction and crash recovery are verified with the project's , plus one lot and one in-process crash on the real sandbox. The 30 day run is SIMULATED.
The five minute path
The path below is the intended flow. A recorded click-through of it on the hosted web app is the next step.
| Step | Persona | What to do | Expected outcome |
|---|---|---|---|
| 1 | Judge | Open the hosted web URL (see above). | The landing page shows "Start a demo auction". |
| 2 | Judge | Press "Start a demo auction". | A demo room opens with a link for each role. |
| 3 | Auctioneer | Open the console link. | The console shows the lot and its controls. |
| 4 | Bidder | Open a bidder link in a second tab and place a bid. | The bid shows on the big screen. A bid is a hold, held and not charged until the hammer. |
| 5 | Auditor | Open the link. | The entries show, chained by hash. |
The nightly judge-smoke workflow walks this journey on the public site with qa/live-redteam/run.mjs (its own steps 1 to 17: start a room, hub, join, register, bid, hammer, screen, receipt). packages/e2e/specs/judge-walkthrough.spec.ts covers steps 1 and 2 on the fake stack.
What you can do right now
- Read How it works: one diagram, where the money is at each moment.
- Read Crash recovery: the page for a skeptical reader.
- Read Proof: every gate, with its caveats.
- Run the fake-PayPal demo locally if you have Node 22.
Verify the audit trail yourself
A replay bundle carries a redacted, hash-chained public export of the ledger. verifyPublicExport in @gavel/engine checks its version, sequence numbers, links and hashes and returns { ok: true } or the first bad index and the reason (bad_hash, bad_prev, bad_seq, bad_version or truncated). Any edit to an entry makes the result ok: false at that index.
- docs/JUDGES.mdthe judge walkthrough this page is distilled from
- packages/engine/src/ledger/public-export.tsverifyPublicExport
- packages/engine/test/public-export.test.tsworking calls, including tampered and truncated chains
Last updated on