Hour audit: 2026-09-12T16
back to the files for this hour · how the archive is audited
Every number on this page is a stored measurement read from this hour's own records: its
manifest.json, its witness
statistics sidecar, and the corpus attestation. Nothing here is computed from the served
bytes at the time you load the page, so no line below claims the bytes are correct. The
digest and the one command that checks them are printed instead.
No findings
Every check that could be evaluated for this hour passed. That is not the same as the hour being perfect: it means the records this archive keeps about it agree with each other and with the corpus ledger.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-12T16 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-12T16:00:00.000002493+00:00 · last event 2026-09-12T16:59:59.999991243+00:00
VOLUME 135,751,220 rows · 1,506,666,296 bytes (1.40 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 130,141,055 · h: 130,095,338 · g: 124,559,224 · f: 120,334,407 · c: 52,428,585 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 4,606,060 (3.39%) · h: 79,908,945 (58.86%) · g: 265,791 (0.20%) · f: 1,157,240 (0.85%) · c: 49,813,184 (36.69%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 135,751,220 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 deefc90c7b9e0b159eaeb0f46437d97079c8a8e1b8796b1516f6260a429718b6
the corpus checksum ledger names this file with the same digest
joined 135,779,062 to merged 135,751,220, minus 27,842 (minus 0.0205%)
boundary drops 27,842 · guard cache
SIDECARS none: this hour's manifest has no v31 key. The v3.1 sidecars are optional, and hours before them have none
MARKETS not measured (the per-hour market census runs on the capture host and its output is not published per hour)
HISTORY merged 2026-09-12T18:38:34Z as cefgh
layout union-event-sorted-v1
re-merges not measured (the merge ledger records the merge that produced this file, not the history of attempts)
supersessions not measured (supersession is recorded per corpus in the storage registry, not in the hour manifest)
CHECKS 8/8 pass
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
PASS every expected machine contributed
PASS the checksum ledger names this file
PASS the hour is whole
PASS a boundary guard ran
UPSTREAM our incident register was checked against the venue's own status feed at 2026-09-23T20:35Z and names no event in this hour. That is a statement about what they published, not a check that every message they sent reached us.The words in this report
Each line in the CHECKS block states what was found, not what was
hoped for: a check that passes is named for the thing that is true, and a check that does
not is renamed to the thing that is wrong. So FINDING never sits beside a
sentence asserting the opposite of the one below it.
The report above is fixed-width text, so nothing in it can be clicked. The same terms are linked here instead. Its verdict is a statement about minutes and nothing else. The row it reports comes from this hour's own manifest and its witness-statistics sidecar, and the completeness line comes from the corpus attestation. The gap between the joined and merged counts is deduplication, not loss, and the boundary drops are the duplicates discarded at the seam with the hour before. Where the history line names a supersession, this hour was rebuilt to a better state after it was first published. The precision is the timestamp resolution these files carry.
Detail
The same records, per product. A product holding no rows renders its zero rather than
being dropped: dropped and empty are indistinguishable to a reader, and only one of them is
a defect. A cell reading not meas. is one nothing published, which is a third
thing again and never a zero.
The class column is the merger's own verdict for that product, and it is
keyed to CONTRIBUTION rather than presence. FULL means every machine expected to
be capturing this hour delivered rows for that product; PARTIAL means some did
and some did not; SINGLE-BY-DESIGN means only one machine was ever expected, and
SINGLE-BY-DEFECT means several were and one delivered. So PARTIAL
here is a statement about the fleet, not about the product being damaged or truncated: the
rows that are present are whole.
PRODUCT rows bytes row groups sha256 best_bid_ask 13,719,998 156,465,265 0-52 ea06259d57b8c60e04672a7516559364fca8ee3882a9351312a4c7374be4b8d0 book 5,701,785 155,302,663 53-74 8ec9f449a47c2e69586499582cd32359bf87b0368fdabde30322f6f49353ae5d last_trade_price 60,400 3,636,440 75-75 815d6132e5e9623fb45d33b5302dc13ff39044706a5cd884b1b353e131699f41 market_resolved 5,805 549,884 76-76 75f6b1a751a33fe1a6eb56ee2109c06902de5af752fb7a80ecff2876fad9c667 new_market 21,644 424,248 77-77 154a448d43eb386b159ef121fd43eebc7460e1cf72e2fb77a617ffc89e5ac68b price_change 116,233,980 1,188,466,923 78-521 00b9f1ff6ac5bd9678ee1aff5e9b17a3c407d81a537bf7eaf2e3c9c5ff7b4d11 tick_size_change 7,608 277,474 522-522 420c18ca67f7853789296db3faaf49d201b7028d9e9714a54155173abcb08fb6 EVENT MIX count share price_change 116,233,980 85.62% best_bid_ask 13,719,998 10.11% book 5,701,785 4.20% last_trade_price 60,400 0.04% new_market 21,644 0.02% tick_size_change 7,608 <0.01% market_resolved 5,805 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,720,262 13,719,998 264 25,986 FULL book 5,722,651 5,701,785 20,866 199,625 FULL last_trade_price 60,402 60,400 2 2,420 FULL market_resolved 5,805 5,805 0 1,029 FULL new_market 21,658 21,644 14 316 FULL price_change 116,240,676 116,233,980 6,696 21,345 FULL tick_size_change 7,608 7,608 0 1,314 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 5,062,480 4,812,124 6ms 14ms 109ms 8.1s 0 transport_latency_assumed best_bid_ask e 13,717,929 456,829 39ms 46ms 258ms 4.7s 0 transport_latency_assumed best_bid_ask f 12,647,361 79,291 47ms 56ms 303ms 5.7s 0 transport_latency_assumed best_bid_ask g 13,105,995 8,843 77ms 99ms 601ms 22.7s 0 transport_latency_assumed best_bid_ask h 13,718,600 8,362,911 18ms 30ms 366ms 58.3s 0 transport_latency_assumed book c 5,335,152 5,130,066 18.8min 22.8h 31.9d 105.8d 0 book_staleness book e 144,348 14,512 42ms 20.4s 22.6h 87.2d 0 book_staleness book f 943,411 304,065 6.7min 22.5h 31.1d 105.8d 0 book_staleness book g 554,102 163,257 3.2min 18.6h 27.5d 105.7d 0 book_staleness book h 163,133 89,885 25ms 40.1min 5.2d 105.7d 0 book_staleness last_trade_price c 21,043 19,697 13ms 48ms 241ms 4.9s 0 transport_latency_assumed last_trade_price e 60,311 2,364 46ms 119ms 761ms 5.0s 0 transport_latency_assumed last_trade_price f 55,417 573 55ms 133ms 741ms 5.0s 0 transport_latency_assumed last_trade_price g 57,358 66 92ms 259ms 3.2s 23.0s 0 transport_latency_assumed last_trade_price h 60,316 37,700 25ms 72ms 642ms 40.0s 0 transport_latency_assumed market_resolved c 3,440 3,375 8.7min 26.7min 32.5min 33.2min 0 transport_latency_assumed market_resolved e 3,182 138 63ms 184ms 590ms 60.0s 0 transport_latency_assumed market_resolved f 3,016 292 71ms 249ms 5.4min 6.3min 0 transport_latency_assumed market_resolved g 3,157 43 122ms 350ms 4.4min 7.7min 0 transport_latency_assumed market_resolved h 3,182 1,957 33ms 78ms 55.9s 1.0min 0 transport_latency_assumed new_market c 21,311 19,972 28.2min 56.7min 1.3h 1.4h 0 transport_latency_assumed new_market e 1,729 472 225ms 4.2min 4.6min 12.9min 0 transport_latency_assumed new_market f 1,960 451 324ms 5.7min 8.7min 8.8min 0 transport_latency_assumed new_market g 1,734 337 378ms 4.3min 4.7min 1.5h 0 transport_latency_assumed new_market h 1,729 412 205ms 4.2min 4.7min 9.7min 0 transport_latency_assumed price_change c 41,982,767 39,825,647 7ms 15ms 124ms 8.1s 0 transport_latency_assumed price_change e 116,205,948 4,131,429 40ms 50ms 351ms 4.9s 0 transport_latency_assumed price_change f 106,675,946 772,538 47ms 62ms 387ms 5.8s 0 transport_latency_assumed price_change g 110,829,578 93,245 77ms 116ms 804ms 23.1s 0 transport_latency_assumed price_change h 116,140,770 71,411,121 19ms 34ms 398ms 58.9s 0 transport_latency_assumed tick_size_change c 2,392 2,303 6ms 14ms 51ms 240ms 0 transport_latency_assumed tick_size_change e 7,608 316 39ms 45ms 129ms 245ms 0 transport_latency_assumed tick_size_change f 7,296 30 47ms 54ms 179ms 454ms 0 transport_latency_assumed tick_size_change g 7,300 not meas. 77ms 100ms 347ms 3.7s 0 transport_latency_assumed tick_size_change h 7,608 4,959 18ms 33ms 150ms 980ms 0 transport_latency_assumed
Captured and supplied are different numbers
Captured is how many rows each machine's own feed carried. Redundant capture means these OVERLAP, heavily and on purpose, so they do not partition the file and their sum is larger than it. Two machines each capturing nearly every event is the archive working, not double counting.
Supplied is how many rows of the merged file actually came from that machine. This one does partition: it sums to the file's row count exactly. But it is decided by the merge's tie-break, so a machine can capture almost everything and supply almost nothing. Read alone, either number tells a false story about the fleet, which is why both are printed and neither is called "the witness share".
What the skew columns mean
Arrival skew is the receipt timestamp minus the venue timestamp, in milliseconds. For six of the seven products the sidecar interprets it as transport latency, and marks that interpretation assumed: it rests on the venue timestamp being emit time, which we cannot verify from outside.
book is not latency and must not be read as latency. Its
venue timestamp is the last time the book changed, so the sidecar interprets it as book
staleness and warns in its own note that large values mean a quiet book rather than slow
transport. Its maximum runs to weeks for that reason. This is why the table above gives a
row per product per machine and never one figure for the hour: percentiles do not average,
and these seven do not measure the same quantity.
Check it yourself
The digest above is a claim. This is how you refuse to take our word for it:
curl -O https://archive.pendulumflow.com/v3/2026-09-12/16/2026-09-12T16.parquet sha256sum 2026-09-12T16.parquet # compare with the sha256 line in the report above
A range digest certifies bytes. That those bytes are the product the manifest names comes from the manifest, which is why both are published and both are checkable.