Hour audit: 2026-09-08T15
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-08T15 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-08T15:00:00.000002672+00:00 · last event 2026-09-08T15:59:59.999999774+00:00
VOLUME 105,733,062 rows · 1,127,675,087 bytes (1.05 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 104,590,097 · f: 104,566,760 · g: 104,556,205 · e: 104,537,340 · c: 92,743,307 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 17,104,092 (16.18%) · f: 626,370 (0.59%) · g: 74,662 (0.07%) · e: 725,825 (0.69%) · c: 87,202,113 (82.47%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 105,733,062 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 c3e583a7ade730adae8b171d532f9dcdf1bd210199ff7ccade07ed0da50b57ba
the corpus checksum ledger names this file with the same digest
joined 105,735,877 to merged 105,733,062, minus 2,815 (minus 0.0027%)
boundary drops 2,815 · 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-08T16:57:31Z 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 10,503,274 117,127,961 0-40 aa9584359983c8130683ea3a7db0b19ce7951f0e20195906f8b85d54759afb6e book 1,264,906 76,789,953 41-45 24f0b4f0e3f9be69396077b94419667828abb8111f11e299490be3420f321c51 last_trade_price 77,195 4,302,501 46-46 abd2aa494c9e109f2f296e17a453dbb0c9bbc4ad94a9b984e6a6f2e2096a910a market_resolved 952 124,651 47-47 f37ad0675ac742ac8e2a8269a0d626c51180baf80774b67c9caf44cec928d2eb new_market 859 86,385 48-48 a5db9987032765c2148aaf50c116e9cd930f9d35355906ec9493ade76009d5bc price_change 93,882,184 927,901,892 49-407 4bb8950ba2df3695c30ea8605470b83851412a77779680f8dd7febbd840c786a tick_size_change 3,692 134,855 408-408 6f0548b241680a70aaf29342573bdb65a421b3c947e9199154fa053cdebcc315 EVENT MIX count share price_change 93,882,184 88.79% best_bid_ask 10,503,274 9.93% book 1,264,906 1.20% last_trade_price 77,195 0.07% tick_size_change 3,692 <0.01% market_resolved 952 <0.01% new_market 859 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,503,484 10,503,274 210 1,159 FULL book 1,264,918 1,264,906 12 178,436 FULL last_trade_price 77,196 77,195 1 320 FULL market_resolved 952 952 0 19 FULL new_market 859 859 0 2 FULL price_change 93,884,776 93,882,184 2,592 807 FULL tick_size_change 3,692 3,692 0 134 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,194,880 8,729,140 6ms 14ms 122ms 5.0s 0 transport_latency_assumed best_bid_ask e 10,500,692 46,669 45ms 53ms 195ms 6.3s 0 transport_latency_assumed best_bid_ask f 10,500,285 38,500 45ms 56ms 215ms 7.1s 0 transport_latency_assumed best_bid_ask g 10,498,671 2,924 84ms 101ms 333ms 13.6s 0 transport_latency_assumed best_bid_ask h 10,502,461 1,686,041 18ms 26ms 150ms 16.3s 0 transport_latency_assumed book c 1,234,875 1,220,335 17.7min 1.1d 31.0d 101.7d 0 book_staleness book e 162,863 5,258 48ms 199ms 27.5min 83.2d 0 book_staleness book f 160,120 2,997 48ms 241ms 5.5s 83.2d 0 book_staleness book g 177,111 10,834 92ms 3.2s 1.2d 83.2d 0 book_staleness book h 160,847 25,482 22ms 108ms 2.7s 83.2d 0 book_staleness last_trade_price c 66,977 63,342 11ms 44ms 199ms 5.0s 0 transport_latency_assumed last_trade_price e 77,004 958 52ms 160ms 1.5s 6.4s 0 transport_latency_assumed last_trade_price f 76,951 711 53ms 227ms 3.6s 7.2s 0 transport_latency_assumed last_trade_price g 77,028 161 97ms 248ms 1.9s 13.7s 0 transport_latency_assumed last_trade_price h 77,096 12,023 23ms 106ms 597ms 7.5s 0 transport_latency_assumed market_resolved c 850 826 6ms 7.4min 15.1min 15.3min 0 transport_latency_assumed market_resolved e 751 12 46ms 367ms 56.6s 56.6s 0 transport_latency_assumed market_resolved f 750 40 46ms 352ms 56.6s 56.6s 0 transport_latency_assumed market_resolved g 751 not meas. 86ms 381ms 1.1s 4.5s 0 transport_latency_assumed market_resolved h 751 74 18ms 123ms 1.0min 1.0min 0 transport_latency_assumed new_market c 679 406 124ms 8.1min 10.8min 1.0h 0 transport_latency_assumed new_market e 546 78 150ms 655ms 1.1min 1.8min 0 transport_latency_assumed new_market f 546 101 170ms 16.8s 28.4s 1.3min 0 transport_latency_assumed new_market g 546 37 270ms 736ms 26.4s 1.0min 0 transport_latency_assumed new_market h 546 237 85ms 16.9s 57.4s 1.8min 0 transport_latency_assumed price_change c 82,241,890 77,185,010 6ms 19ms 235ms 5.5s 0 transport_latency_assumed price_change e 93,791,792 672,838 45ms 72ms 388ms 7.4s 0 transport_latency_assumed price_change f 93,824,416 584,008 45ms 77ms 491ms 7.1s 0 transport_latency_assumed price_change g 93,798,406 60,706 85ms 131ms 551ms 13.7s 0 transport_latency_assumed price_change h 93,844,704 15,379,622 18ms 38ms 292ms 16.9s 0 transport_latency_assumed tick_size_change c 3,156 3,054 6ms 11ms 48ms 1.4s 0 transport_latency_assumed tick_size_change e 3,692 12 45ms 50ms 116ms 304ms 0 transport_latency_assumed tick_size_change f 3,692 13 45ms 53ms 127ms 325ms 0 transport_latency_assumed tick_size_change g 3,692 not meas. 83ms 101ms 440ms 1.1s 0 transport_latency_assumed tick_size_change h 3,692 613 18ms 22ms 82ms 6.8s 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-08/15/2026-09-08T15.parquet sha256sum 2026-09-08T15.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.