Hour audit: 2026-09-11T10
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-11T10 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-11T10:00:00.000461986+00:00 · last event 2026-09-11T10:59:59.999765673+00:00
VOLUME 107,139,562 rows · 1,128,656,146 bytes (1.05 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 106,418,175 · f: 106,389,072 · e: 106,321,919 · g: 106,165,124 · c: 101,927,319 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 8,537,453 (7.97%) · f: 243,007 (0.23%) · e: 563,991 (0.53%) · g: 45,133 (0.04%) · c: 97,749,978 (91.24%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 107,139,562 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 f71f6adb2c492cb12e8e7d27ffdeefeefbb497ab06ba2a6c118c12668547c2c6
the corpus checksum ledger names this file with the same digest
joined 107,143,064 to merged 107,139,562, minus 3,502 (minus 0.0033%)
boundary drops 3,502 · 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-11T12:34:57Z 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 9,094,798 103,699,812 0-34 8b38b06e6e45ecfc091e4fd387bac70bf3951604d57e2704bf73058480704cb1 book 1,086,957 81,724,828 35-39 98490ef344a32e1c0e38f2ce3eeaca177a244833af5f37dc6232bb3b38cbcd56 last_trade_price 51,036 2,904,081 40-40 351a57b9e14389f3358aeee429dca887bb2f3865024eda9e97c1151da65b6002 market_resolved 665 92,658 41-41 58dc8051335ac640e53122bb3e17406c795d8adafa33bb7421b40c98885fba8b new_market 844 77,181 42-42 b27e2da3a89c4bdc46eddacb5458dfe326944d944637eca162ea2cdb932538a0 price_change 96,902,926 938,849,190 43-412 cf7620d0d1f4403340961f5ca8d4d44691cd405c43ea4956b2f8dc3ead0b59a2 tick_size_change 2,336 86,343 413-413 17bf90f3723b110983532df69c59392fe51270b4cae3f0c32cc7241d1abda2ef EVENT MIX count share price_change 96,902,926 90.45% best_bid_ask 9,094,798 8.49% book 1,086,957 1.01% last_trade_price 51,036 0.05% tick_size_change 2,336 <0.01% new_market 844 <0.01% market_resolved 665 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,095,040 9,094,798 242 638 FULL book 1,087,007 1,086,957 50 191,232 FULL last_trade_price 51,038 51,036 2 90 FULL market_resolved 665 665 0 6 FULL new_market 844 844 0 0 FULL price_change 96,906,134 96,902,926 3,208 486 FULL tick_size_change 2,336 2,336 0 16 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,687,927 8,344,882 5ms 11ms 124ms 5.0s 0 transport_latency_assumed best_bid_ask e 9,087,193 37,078 38ms 43ms 186ms 19.9s 0 transport_latency_assumed best_bid_ask f 9,091,972 10,350 45ms 54ms 203ms 5.7s 0 transport_latency_assumed best_bid_ask g 9,091,496 1,317 77ms 93ms 344ms 22.9s 0 transport_latency_assumed best_bid_ask h 9,092,090 701,171 18ms 25ms 147ms 43.8s 0 transport_latency_assumed book c 750,256 716,619 13.9min 1.1d 29.8d 104.5d 0 book_staleness book e 412,169 116,201 4.7min 20.7h 19.9d 104.5d 0 book_staleness book f 378,292 101,534 3.6min 20.0h 19.9d 104.5d 0 book_staleness book g 179,580 27,491 215ms 6.9h 16.7d 102.9d 0 book_staleness book h 410,175 125,112 3.9min 20.6h 20.1d 104.5d 0 book_staleness last_trade_price c 48,300 45,821 11ms 45ms 214ms 5.0s 0 transport_latency_assumed last_trade_price e 50,495 220 45ms 157ms 1.7s 19.9s 0 transport_latency_assumed last_trade_price f 50,986 127 54ms 158ms 2.2s 5.7s 0 transport_latency_assumed last_trade_price g 50,726 8 93ms 303ms 2.3s 22.9s 0 transport_latency_assumed last_trade_price h 50,940 4,860 24ms 67ms 295ms 31.5s 0 transport_latency_assumed market_resolved c 562 544 6ms 3.8min 6.1min 6.1min 0 transport_latency_assumed market_resolved e 560 43 39ms 195ms 58.6s 58.6s 0 transport_latency_assumed market_resolved f 560 not meas. 47ms 261ms 59.1s 59.2s 0 transport_latency_assumed market_resolved g 560 not meas. 78ms 237ms 617ms 892ms 0 transport_latency_assumed market_resolved h 560 78 19ms 116ms 1.0min 1.0min 0 transport_latency_assumed new_market c 504 270 122ms 14.7s 4.9min 4.9min 0 transport_latency_assumed new_market e 504 97 193ms 15.3s 26.3s 26.8s 0 transport_latency_assumed new_market f 504 106 202ms 18.0s 25.0s 59.4s 0 transport_latency_assumed new_market g 504 109 364ms 20.8s 23.7s 1.3min 0 transport_latency_assumed new_market h 504 262 168ms 14.1s 25.5s 1.1min 0 transport_latency_assumed price_change c 92,437,498 88,639,646 5ms 12ms 157ms 5.0s 0 transport_latency_assumed price_change e 96,768,662 410,348 38ms 46ms 304ms 19.9s 0 transport_latency_assumed price_change f 96,864,422 130,890 46ms 58ms 308ms 5.7s 0 transport_latency_assumed price_change g 96,839,922 16,208 77ms 100ms 558ms 22.9s 0 transport_latency_assumed price_change h 96,861,570 7,705,834 18ms 27ms 189ms 44.1s 0 transport_latency_assumed tick_size_change c 2,272 2,196 5ms 11ms 40ms 449ms 0 transport_latency_assumed tick_size_change e 2,336 4 38ms 49ms 105ms 834ms 0 transport_latency_assumed tick_size_change f 2,336 not meas. 46ms 55ms 121ms 457ms 0 transport_latency_assumed tick_size_change g 2,336 not meas. 77ms 93ms 215ms 1.7s 0 transport_latency_assumed tick_size_change h 2,336 136 18ms 27ms 60ms 383ms 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-11/10/2026-09-11T10.parquet sha256sum 2026-09-11T10.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.