Hour audit: 2026-09-15T03
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-15T03 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-15T03:00:00.000000725+00:00 · last event 2026-09-15T03:59:59.999973113+00:00
VOLUME 107,559,133 rows · 1,114,395,457 bytes (1.04 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 106,937,851 · f: 106,823,932 · e: 106,607,971 · g: 102,751,355 · c: 102,501,618 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 7,500,919 (6.97%) · f: 282,326 (0.26%) · e: 769,880 (0.72%) · g: 147,259 (0.14%) · c: 98,858,749 (91.91%) (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 107,559,133 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 d322e8d86e06acb5c8749d70d430a20d886fea0ec1b918f4000f47ce7d126434
the corpus checksum ledger names this file with the same digest
joined 107,561,986 to merged 107,559,133, minus 2,853 (minus 0.0027%)
boundary drops 2,853 · 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-15T04: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 12,096,596 132,521,721 0-46 57508f61246c1199ca4fe53ead18e3a723cee38cde6856b55d7c73be7755b501 book 1,013,331 71,186,280 47-50 c6bc2ffa261c25eba9a3a7b671e49914413f7d94670e68675af1765998d9d08c last_trade_price 45,678 2,619,294 51-51 d77c3df63c86f430fd7300e64c29e789a250ee8e5f578ebff98fc61421f1f7a5 market_resolved 1,445 216,029 52-52 b3fc6608351224c775a5f9530b5427de0de31e9bd107ecebf53ce7e65b267888 new_market 1,323 133,522 53-53 3356665780f480a829bc40b372a2783e105205fa637db1b27e138f0c44abcdfd price_change 94,397,536 906,373,953 54-414 91808793381fddec07f10515d816ae8048f8df2dbac5ef13a1db438dada36221 tick_size_change 3,224 118,351 415-415 46ac4dec05d4d9e1e1bba0f997fa2fb8512520178b2e646a252abdc08eb27a6c EVENT MIX count share price_change 94,397,536 87.76% best_bid_ask 12,096,596 11.25% book 1,013,331 0.94% last_trade_price 45,678 0.04% tick_size_change 3,224 <0.01% market_resolved 1,445 <0.01% new_market 1,323 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,096,874 12,096,596 278 932 FULL book 1,013,379 1,013,331 48 167,839 FULL last_trade_price 45,679 45,678 1 135 FULL market_resolved 1,449 1,445 4 18 FULL new_market 1,323 1,323 0 1 FULL price_change 94,400,058 94,397,536 2,522 457 FULL tick_size_change 3,224 3,224 0 81 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,600,907 11,244,642 5ms 8ms 72ms 2.2s 0 transport_latency_assumed best_bid_ask e 12,094,640 76,626 40ms 47ms 130ms 5.9s 0 transport_latency_assumed best_bid_ask f 12,090,316 13,679 50ms 56ms 176ms 7.8s 0 transport_latency_assumed best_bid_ask g 11,649,351 904 82ms 100ms 307ms 12.9s 0 transport_latency_assumed best_bid_ask h 12,093,273 760,745 17ms 23ms 95ms 7.8s 0 transport_latency_assumed book c 582,206 478,911 4.9min 2.0d 34.4d 108.2d 0 book_staleness book e 99,449 5,083 43ms 123ms 3.5h 89.7d 0 book_staleness book f 367,576 146,246 1.8min 1.3d 33.5d 108.2d 0 book_staleness book g 460,633 135,630 3.2min 1.5d 34.4d 108.2d 0 book_staleness book h 442,684 247,461 3.2min 1.5d 34.3d 108.2d 0 book_staleness last_trade_price c 42,143 40,232 10ms 42ms 190ms 5.0s 0 transport_latency_assumed last_trade_price e 45,488 639 47ms 100ms 347ms 5.8s 0 transport_latency_assumed last_trade_price f 45,454 125 56ms 119ms 1.1s 7.9s 0 transport_latency_assumed last_trade_price g 44,073 32 94ms 203ms 1.3s 12.6s 0 transport_latency_assumed last_trade_price h 45,530 4,650 23ms 64ms 245ms 7.9s 0 transport_latency_assumed market_resolved c 1,343 1,307 5ms 8ms 154ms 3.6min 0 transport_latency_assumed market_resolved e 1,350 1 45ms 167ms 55.8s 59.5s 0 transport_latency_assumed market_resolved f 1,350 6 53ms 132ms 312ms 1.0s 0 transport_latency_assumed market_resolved g 1,366 42 95ms 280ms 4.2min 4.9min 0 transport_latency_assumed market_resolved h 1,348 89 22ms 64ms 51.2s 54.8s 0 transport_latency_assumed new_market c 869 556 78ms 27.8s 1.3min 3.9min 0 transport_latency_assumed new_market e 870 139 164ms 40.5s 1.5min 1.7min 0 transport_latency_assumed new_market f 870 152 166ms 40.6s 1.3min 1.5min 0 transport_latency_assumed new_market g 872 97 234ms 25.5s 1.3min 7.0min 0 transport_latency_assumed new_market h 870 379 110ms 23.2s 1.6min 1.8min 0 transport_latency_assumed price_change c 90,271,126 87,090,138 5ms 9ms 87ms 2.9s 0 transport_latency_assumed price_change e 94,362,950 687,360 41ms 51ms 176ms 7.1s 0 transport_latency_assumed price_change f 94,315,142 122,114 50ms 61ms 238ms 9.6s 0 transport_latency_assumed price_change g 90,591,956 10,554 82ms 104ms 403ms 12.9s 0 transport_latency_assumed price_change h 94,350,926 6,487,370 17ms 26ms 119ms 7.9s 0 transport_latency_assumed tick_size_change c 3,024 2,963 5ms 7ms 24ms 197ms 0 transport_latency_assumed tick_size_change e 3,224 32 41ms 49ms 91ms 133ms 0 transport_latency_assumed tick_size_change f 3,224 4 50ms 55ms 133ms 258ms 0 transport_latency_assumed tick_size_change g 3,104 not meas. 83ms 100ms 253ms 713ms 0 transport_latency_assumed tick_size_change h 3,220 225 17ms 21ms 60ms 717ms 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-15/03/2026-09-15T03.parquet sha256sum 2026-09-15T03.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.