Hour audit: 2026-09-30T15
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-30T15 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-30T15:00:00.002139579+00:00 · last event 2026-09-30T15:59:59.999003307+00:00
VOLUME 123,139,330 rows · 1,372,999,722 bytes (1.28 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured h: 122,541,115 · m: 122,539,561 · g: 122,538,279 · i: 122,424,269 · k: 116,557,894 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 4,976,154 (4.04%) · m: 96,913,087 (78.70%) · g: 105,472 (0.09%) · i: 2,231,980 (1.81%) · k: 18,912,637 (15.36%) (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 123,139,330 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 eeb89eaf0180447532b8b335006c4dd520d0948174c7529fe62f0985fe52e19d
the corpus checksum ledger names this file with the same digest
joined 123,150,544 to merged 123,139,330, minus 11,214 (minus 0.0091%)
boundary drops 11,214 · 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-30T21:36:28Z 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 11,285,204 135,175,230 0-43 fb2740c3b1d7c81be37040226af16005c2a7560352046560886086d823044712 book 821,065 72,665,716 44-47 b7f3546503cdf2dd77e3a2ebbaa14ef08b4c0edc83421d1de30069aeb6746f36 last_trade_price 63,448 3,621,953 48-48 20ca716339c3fc857490e879ed10ddfdb569b97805a5d1b43c99947ab4dd7468 market_resolved 974 153,085 49-49 33c8b45ecbbbdfdd69409067baa0bbe8f8fdd9c393b9f6c7ad0ba7c472bea58a new_market 759 82,764 50-50 660684638e1baf8acf918cff1aa3c3a02f0979ac04b5efc46b114b2320ec6b4a price_change 110,964,264 1,159,761,544 51-474 c0c3608b58522afa1bc28d9324dfa69d91a8483a29f689efeb31dcefe465bdf1 tick_size_change 3,616 133,421 475-475 b361cf73da78b79d636c62bd4baa6099e820fc06778794c0026668dc38ae6003 EVENT MIX count share price_change 110,964,264 90.11% best_bid_ask 11,285,204 9.16% book 821,065 0.67% last_trade_price 63,448 0.05% tick_size_change 3,616 <0.01% market_resolved 974 <0.01% new_market 759 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,285,426 11,285,204 222 1,109 FULL book 828,051 821,065 6,986 228,060 FULL last_trade_price 63,448 63,448 0 130 FULL market_resolved 974 974 0 139 FULL new_market 767 759 8 101 FULL price_change 110,968,262 110,964,264 3,998 1,408 FULL tick_size_change 3,616 3,616 0 40 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 11,280,851 1,045 79ms 104ms 268ms 13.1s 0 transport_latency_assumed best_bid_ask h 11,283,745 435,963 20ms 47ms 149ms 20.6s 0 transport_latency_assumed best_bid_ask i 11,284,562 169,298 25ms 57ms 133ms 2.3s 0 transport_latency_assumed best_bid_ask k 10,731,028 1,480,189 14ms 34ms 124ms 6.5s 0 transport_latency_assumed best_bid_ask m 11,283,862 9,198,709 6ms 25ms 99ms 3.1s 0 transport_latency_assumed book g 329,966 92,484 1.3min 1.7d 39.1d 123.7d 0 book_staleness book h 244,677 62,030 114ms 1.1d 35.9d 123.7d 0 book_staleness book i 130,168 4,424 28ms 85ms 1.6h 105.2d 0 book_staleness book k 657,691 511,765 23.9min 2.4d 39.0d 123.7d 0 book_staleness book m 252,704 150,362 137ms 1.3d 37.9d 123.7d 0 book_staleness last_trade_price g 62,972 6 87ms 298ms 5.6s 13.2s 0 transport_latency_assumed last_trade_price h 63,365 3,079 22ms 62ms 291ms 7.7s 0 transport_latency_assumed last_trade_price i 63,426 1,590 27ms 73ms 304ms 1.4s 0 transport_latency_assumed last_trade_price k 59,691 14,683 16ms 41ms 141ms 1.4s 0 transport_latency_assumed last_trade_price m 63,389 44,090 9ms 38ms 134ms 1.4s 0 transport_latency_assumed market_resolved g 826 not meas. 85ms 358ms 52.7s 53.9s 0 transport_latency_assumed market_resolved h 826 11 21ms 111ms 50.4s 51.2s 0 transport_latency_assumed market_resolved i 826 1 29ms 123ms 50.4s 51.0s 0 transport_latency_assumed market_resolved k 929 217 18ms 8.0min 16.0min 16.0min 0 transport_latency_assumed market_resolved m 826 745 6ms 39ms 44.9s 45.4s 0 transport_latency_assumed new_market g 444 35 235ms 13.0s 1.3min 1.6min 0 transport_latency_assumed new_market h 444 113 58ms 11.5s 55.4s 1.6min 0 transport_latency_assumed new_market i 444 86 73ms 11.3s 52.9s 1.1min 0 transport_latency_assumed new_market k 545 201 116ms 9.6min 12.8min 12.9min 0 transport_latency_assumed new_market m 444 324 32ms 14.5s 1.0min 1.4min 0 transport_latency_assumed price_change g 110,859,604 11,902 80ms 121ms 797ms 13.2s 0 transport_latency_assumed price_change h 110,944,442 4,474,818 20ms 50ms 202ms 21.1s 0 transport_latency_assumed price_change i 110,941,227 2,056,552 25ms 60ms 181ms 4.1s 0 transport_latency_assumed price_change k 105,104,554 16,904,994 14ms 36ms 140ms 6.5s 0 transport_latency_assumed price_change m 110,934,720 87,515,998 6ms 29ms 122ms 3.1s 0 transport_latency_assumed tick_size_change g 3,616 not meas. 79ms 95ms 193ms 373ms 0 transport_latency_assumed tick_size_change h 3,616 140 20ms 43ms 115ms 262ms 0 transport_latency_assumed tick_size_change i 3,616 29 26ms 55ms 92ms 189ms 0 transport_latency_assumed tick_size_change k 3,456 588 15ms 34ms 125ms 169ms 0 transport_latency_assumed tick_size_change m 3,616 2,859 6ms 23ms 69ms 139ms 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-30/15/2026-09-30T15.parquet sha256sum 2026-09-30T15.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.