Hour audit: 2026-10-03T02
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-10-03T02 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-03T02:00:00.004251908+00:00 · last event 2026-10-03T02:59:59.999960113+00:00
VOLUME 101,995,541 rows · 1,060,508,962 bytes (1011.38 MiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured k: 101,898,175 · h: 101,890,932 · i: 101,859,357 · g: 101,792,677 · m: 101,746,191 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 3,127,979 (3.07%) · h: 767,455 (0.75%) · i: 524,438 (0.51%) · g: 19,138 (0.02%) · m: 97,556,531 (95.65%) (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 101,995,541 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 bded5db247dd73dc3ea2922f1dbfd412ec570fcb952cc80ac4a89dbee4ddcafe
the corpus checksum ledger names this file with the same digest
joined 101,998,313 to merged 101,995,541, minus 2,772 (minus 0.0027%)
boundary drops 2,772 · 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-10-03T04:44:14Z as ghikm
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 9,455,896 108,915,226 0-36 2754f0754f6f1ff2e67c0bcebbbb8f60576748834b7cc8e797695a80379062c7 book 168,940 16,712,306 37-37 e7fc1a117651eb90a6782440cc5b5996d43d2006c372375ce1d3902aebdd4a56 last_trade_price 44,643 2,551,419 38-38 5ada15976521da59f005a520e498f9d8b732e212ed11b74b82d7e1bcb33c4605 market_resolved 1,043 160,054 39-39 f7c9404807f892864571dd4e1a41b3bfd995f9446c2fc43e8cb1ce52843b3de1 new_market 1,693 158,697 40-40 992929271fe682a31a7201b96e8c3e34008e4fb24a450d9ce82fed505b97eabb price_change 92,320,278 930,732,907 41-393 ff5ea38246ca66e2082f1158c70e555750c94e75262d9f03d55ad2934428031d tick_size_change 3,048 111,508 394-394 d3180aac555b4f12d09e643ffdb7fd350476f004b2ccf59f47abc2ab111eb9e7 EVENT MIX count share price_change 92,320,278 90.51% best_bid_ask 9,455,896 9.27% book 168,940 0.17% last_trade_price 44,643 0.04% tick_size_change 3,048 <0.01% new_market 1,693 <0.01% market_resolved 1,043 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,456,096 9,455,896 200 167 FULL book 169,596 168,940 656 33,428 FULL last_trade_price 44,643 44,643 0 0 FULL market_resolved 1,043 1,043 0 1 FULL new_market 1,693 1,693 0 0 FULL price_change 92,322,194 92,320,278 1,916 211 FULL tick_size_change 3,048 3,048 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,454,066 962 79ms 96ms 405ms 16.5s 0 transport_latency_assumed best_bid_ask h 9,454,509 64,023 17ms 23ms 246ms 52.8s 0 transport_latency_assumed best_bid_ask i 9,454,484 40,059 19ms 25ms 125ms 17.7s 0 transport_latency_assumed best_bid_ask k 9,454,197 273,191 13ms 21ms 131ms 45.7s 0 transport_latency_assumed best_bid_ask m 9,450,666 9,077,661 4ms 9ms 62ms 4.5s 0 transport_latency_assumed book g 97,588 6,728 83ms 582ms 1.1d 107.7d 0 book_staleness book h 93,089 3,532 20ms 52ms 1.2h 107.7d 0 book_staleness book i 94,312 4,493 21ms 60ms 5.3h 107.7d 0 book_staleness book k 140,437 53,100 22ms 5.2h 27.5d 108.1d 0 book_staleness book m 108,121 101,087 7ms 11.3min 6.4d 55.7d 0 book_staleness last_trade_price g 44,609 34 81ms 182ms 2.4s 16.6s 0 transport_latency_assumed last_trade_price h 44,585 588 18ms 33ms 377ms 16.9s 0 transport_latency_assumed last_trade_price i 44,556 483 21ms 35ms 251ms 5.0s 0 transport_latency_assumed last_trade_price k 44,508 2,146 14ms 28ms 222ms 1.6s 0 transport_latency_assumed last_trade_price m 44,155 41,392 5ms 13ms 119ms 1.2s 0 transport_latency_assumed market_resolved g 992 26 82ms 38.0s 52.1s 52.2s 0 transport_latency_assumed market_resolved h 993 11 20ms 28.4s 47.5s 55.5s 0 transport_latency_assumed market_resolved i 993 21 21ms 20.3s 47.1s 47.3s 0 transport_latency_assumed market_resolved k 993 42 14ms 30.0s 51.4s 51.5s 0 transport_latency_assumed market_resolved m 993 943 5ms 19.2s 46.3s 46.4s 0 transport_latency_assumed new_market g 1,014 126 385ms 22.5s 1.1min 1.6min 0 transport_latency_assumed new_market h 1,014 182 180ms 19.7s 1.1min 1.4min 0 transport_latency_assumed new_market i 1,014 349 146ms 20.8s 55.8s 1.7min 0 transport_latency_assumed new_market k 1,014 331 158ms 17.7s 53.0s 1.7min 0 transport_latency_assumed new_market m 1,014 705 70ms 18.7s 1.1min 1.8min 0 transport_latency_assumed price_change g 92,191,360 11,262 79ms 101ms 689ms 16.6s 0 transport_latency_assumed price_change h 92,293,694 699,098 17ms 24ms 324ms 52.8s 0 transport_latency_assumed price_change i 92,260,950 479,028 19ms 27ms 222ms 17.7s 0 transport_latency_assumed price_change k 92,253,978 2,799,072 13ms 22ms 156ms 49.6s 0 transport_latency_assumed price_change m 92,138,194 88,331,818 4ms 9ms 66ms 6.6s 0 transport_latency_assumed tick_size_change g 3,048 not meas. 78ms 93ms 123ms 336ms 0 transport_latency_assumed tick_size_change h 3,048 21 17ms 21ms 68ms 258ms 0 transport_latency_assumed tick_size_change i 3,048 5 20ms 25ms 51ms 164ms 0 transport_latency_assumed tick_size_change k 3,048 97 13ms 23ms 54ms 312ms 0 transport_latency_assumed tick_size_change m 3,048 2,925 5ms 9ms 32ms 106ms 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-10-03/02/2026-10-03T02.parquet sha256sum 2026-10-03T02.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.