Skip to content

Run it again yourself.

Every block says what kind of proof it is. Engine results are recomputed when this page is built, from the same frozen Bitget books the desk replays. Evaluation runs are published as they came out, including the misses. What Sounding cannot check is listed, not hidden.

recomputed at buildpublished run, unchangednot checked

The order the desk opens on

recomputed at build
“Sell 178.4121 rHIMS. I pay 0.05% taker, keep it under 0.3% all-in, and I must be out before the 8th.”

36.87 bps all-in at your 5 bps fee: over your 30 bps ceiling.

The best bid alone would cost 17.48 bps, well inside the ceiling; the full 178.4121 shares walk 5 levels down the book. The largest size that fits is 101.834 shares, leaving 76.5781 unpriced.

Recorded Sunday rHIMS book, 2026-09-20 09:02:35Z. Pre-fee 31.89 bps against the 28.025 mid; proceeds 4984.05 USDT at a VWAP of 27.935629.

the walk
bidshowntaken
27.9916.202816.2028
27.9835.23635.2360
27.977.79767.7976
27.966.846.8400
27.91179.2471112.3357
every fee
feeall-invs 30 bps
5 bps36.87✕ over
10 bps41.86✕ over
5 bps · yours36.87✕ over
pnpm replay fixtures/rhims-20260920T090235Z.json sell 178.4121 30 5
# receipt 175394a68b72557912bce5121ee17950557d4442aaf1541dec0902b9f701b4b4 · sounding-engine/0.7.0

Last Look on real captures

recomputed at build
  • ✓ Stands · Two real captures 21 seconds apart, Oct 3

    gap 20.8 s · cost drift 0.00 bps · price drift 0.00 bps

    • Fresh book within 10 bps of the sounding you read on cost and price; still within ceiling at 37.40 bps.
  • ✕ Void · The Sep 20 decision re-checked on the Oct 3 book

    gap 12.7 days · cost drift 0.53 bps · price drift 363.41 bps

    • The price you would get moved in your favour by 363.41 bps since you read it, beyond the 10 bps tolerance; a different market from the one you decided on.
    • The decision was read 12.7 days before this confirm, beyond the 2-minute limit; re-sound before acting.

Reading the trader's words

published run, unchanged

Messages in English, 中文 and mixed, with gold values, written by agents told not to read the code. A field counts only if the right value reached the engine. “Wrong” is the dangerous outcome: a different value used without asking.

runQwen, checkedwrongasked backregex reader
Blind set 1, before fixes
40 messages, today = 2026-10-03; published with its five wrong deadlines
127 / 1385320 / 138
Blind set 2, held out
40 new messages by a second writer, today = 2026-10-07; run once at commit e15d877
142 / 1511319 / 151
Set 2 again, after fixes
development run at b7d0671: not a held-out number
146 / 1510019 / 151

Prompts, gold values, every value each reader extracted, and the scoring script are in the repository under evidence/ and scripts/paraphrase-eval.ts.

Whole tasks, end to end

published run, unchanged

These runs, and the reading runs above, were made before 2026-10-07 on engine 0.4.0, which priced an unknown fee at 20 bps and added the fee on top. They are shown as they ran; a task’s right answer was the engine’s verdict at that time.

Thirty complete tasks written blind: starting controls, one to three chat turns in English, 中文 or both, and the right outcome. Some must be answered, some must be asked back, some name a stock with no book. Every turn runs through the real route. Critical means the wrong order was priced, a route broke the trader’s ceiling or deadline, or it acted where it had to ask.

runcompleteasked when it could answercritical
Qwen, checked · second blind set, every turn scored28 / 3011
Regex reader and template, no model · second blind set12 / 30153
Qwen, checked · first blind set, final answer scored24 / 3033
Regex reader and template · first blind set11 / 30811

Each set was written by a separate blind agent and run once. The first (at 62fe672) scored only final answers; its three critical errors were fixed afterwards. The second (at 8c64202) scores every turn as rendered, so asking while showing a card counts as critical; its one critical, a negative size quoted without its minus sign, has since been fixed. Every failure is published with its run in evidence/; re-runs after fixes are kept there as development numbers.

The book is Bitget's book

published run, unchanged

On 2026-09-20 at 09:25:59 UTC, the top five bids and asks for rHOOD on Bitget’s web order book were compared with the public API capture taken the same second: 10 of 10 levels matched in price and size. One instrument, one instant. Bitget’s separately documented Reality depth feed was not compared.

What Sounding does not check

not checked
  • Whether an order would be accepted or filled. Nothing is sent, and no order type is tested live.
  • Hidden or off-book liquidity, and how market makers behave at the session switch.
  • The future book. Every answer is conditional on the snapshot it names.
  • Bitget's whitelisted Reality depth feed, which may differ from the public book.
  • How current a recorded universe is: recorded pages say the capture date.
  • Your exact fee tier. A fee you state decides; without one, Bitget's published 5 bps rToken rate and its 10 bps list rate are both priced, and the higher decides.