Hour audit: 2026-09-23T20
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-23T20 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-23T20:00:00.000031693+00:00 · last event 2026-09-23T20:59:59.999965763+00:00
VOLUME 120,285,766 rows · 1,360,810,256 bytes (1.27 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured h: 116,721,420 · i: 112,215,529 · g: 111,970,408 · k: 107,525,407 · c: 87,998,559 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 5,368,384 (4.46%) · i: 3,243,645 (2.70%) · g: 169,383 (0.14%) · k: 31,826,336 (26.46%) · c: 79,678,018 (66.24%) (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 120,285,766 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 b97c0fbf300fc8d4b750463697308c32efa8e16bc32504d6347345394f2efac3
the corpus checksum ledger names this file with the same digest
joined 120,294,284 to merged 120,285,766, minus 8,518 (minus 0.0071%)
boundary drops 8,518 · 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-24T05:12:40Z as cghik
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 status feed unobserved for this hour. Our incident register was last checked against the venue's feed at 2026-09-23T20:35Z, before this hour ended, so nothing has looked yet. This is a could-not-look and never an all-clear.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 11,054,803 137,700,014 0-42 1cbc6012b3dd213688a061b43aea34b9671b60e1f7c5bcde1092a9c9f381fad9 book 3,263,109 123,801,492 43-55 b31023ce7c4d4a52354b393bb94ec67318bd9e2d1293a051ffcf8121eaa80b36 last_trade_price 53,234 3,064,779 56-56 e463595aaa021142c41b5c674cf02c7683b5793c5622dd73dc67b35f75599b6a market_resolved 3,328 309,072 57-57 b704ddf983747c49d524d0a7b25ffd5f902759f6d8d412b29bbbd42662102e94 new_market 5,382 476,095 58-58 b207f39f9ec3483308a63c104c67a940cde5e4486c0991519e0c567e45f26cda price_change 105,901,814 1,093,938,271 59-462 984913dfd711d355f9b04ac9d5ef77fd6e5e4d59eeb3b4795d57fa5639f9e64b tick_size_change 4,096 151,167 463-463 a11910cc58d7add0b252f16e204c93debfc3bd4e6ee07a56976d97c4c1fbe4ae EVENT MIX count share price_change 105,901,814 88.04% best_bid_ask 11,054,803 9.19% book 3,263,109 2.71% last_trade_price 53,234 0.04% new_market 5,382 <0.01% tick_size_change 4,096 <0.01% market_resolved 3,328 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,055,277 11,054,803 474 4,812 FULL book 3,268,344 3,263,109 5,235 174,844 FULL last_trade_price 53,234 53,234 0 626 FULL market_resolved 3,356 3,328 28 490 FULL new_market 5,515 5,382 133 264 FULL price_change 105,904,462 105,901,814 2,648 1,096 FULL tick_size_change 4,096 4,096 0 208 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,232,132 7,510,753 5ms 15ms 212ms 9.1s 0 transport_latency_assumed best_bid_ask g 10,612,637 2,565 80ms 142ms 1.1s 49.4s 0 transport_latency_assumed best_bid_ask h 11,038,409 469,595 18ms 42ms 604ms 1.7min 0 transport_latency_assumed best_bid_ask i 10,615,551 257,600 22ms 33ms 199ms 8.3s 0 transport_latency_assumed best_bid_ask k 10,154,531 2,814,290 12ms 20ms 188ms 23.0s 0 transport_latency_assumed book c 2,558,521 2,406,518 3.0min 4.3d 43.1d 116.9d 0 book_staleness book g 538,425 112,192 1.4min 3.0d 38.0d 116.9d 0 book_staleness book h 162,875 35,784 64ms 18.4h 16.4d 116.9d 0 book_staleness book i 565,202 250,449 1.4min 2.8d 38.0d 116.9d 0 book_staleness book k 932,048 458,166 1.8min 3.3d 42.1d 116.9d 0 book_staleness last_trade_price c 37,523 33,772 6ms 24ms 295ms 5.3s 0 transport_latency_assumed last_trade_price g 49,208 152 90ms 1.3s 18.3s 49.0s 0 transport_latency_assumed last_trade_price h 51,747 2,090 20ms 268ms 1.7s 40.0s 0 transport_latency_assumed last_trade_price i 49,886 1,267 26ms 201ms 1.2s 6.7s 0 transport_latency_assumed last_trade_price k 48,824 15,953 14ms 40ms 314ms 11.3s 0 transport_latency_assumed market_resolved c 2,588 2,332 4.9min 20.7min 36.6min 38.3min 0 transport_latency_assumed market_resolved g 1,636 100 82ms 4.6min 6.1min 7.6min 0 transport_latency_assumed market_resolved h 1,540 208 18ms 20.9s 1.0min 1.0min 0 transport_latency_assumed market_resolved i 1,512 193 23ms 3.2min 4.8min 4.8min 0 transport_latency_assumed market_resolved k 1,502 495 13ms 31.4s 4.0min 7.0min 0 transport_latency_assumed new_market c 3,902 2,423 435ms 13.4min 31.6min 33.7min 0 transport_latency_assumed new_market g 2,745 558 349ms 56.1s 3.4min 5.3min 0 transport_latency_assumed new_market h 2,739 732 168ms 45.5s 3.4min 3.5min 0 transport_latency_assumed new_market i 2,739 613 140ms 58.7s 3.0min 3.8min 0 transport_latency_assumed new_market k 2,740 1,056 94ms 47.7s 3.5min 1.0h 0 transport_latency_assumed price_change c 77,160,397 69,719,022 5ms 18ms 255ms 12.9s 0 transport_latency_assumed price_change g 100,761,785 53,816 81ms 206ms 4.1s 49.7s 0 transport_latency_assumed price_change h 105,460,014 4,859,860 18ms 55ms 843ms 1.7min 0 transport_latency_assumed price_change i 100,976,651 2,733,494 22ms 45ms 307ms 9.7s 0 transport_latency_assumed price_change k 96,381,794 28,535,622 13ms 24ms 226ms 25.5s 0 transport_latency_assumed tick_size_change c 3,496 3,198 5ms 13ms 356ms 8.9s 0 transport_latency_assumed tick_size_change g 3,972 not meas. 80ms 106ms 822ms 1.6s 0 transport_latency_assumed tick_size_change h 4,096 115 19ms 33ms 331ms 2.4s 0 transport_latency_assumed tick_size_change i 3,988 29 22ms 29ms 242ms 426ms 0 transport_latency_assumed tick_size_change k 3,968 754 12ms 19ms 120ms 550ms 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-23/20/2026-09-23T20.parquet sha256sum 2026-09-23T20.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.