Hour audit: 2026-10-02T12
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-02T12 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-02T12:00:00.000087468+00:00 · last event 2026-10-02T12:59:59.999632653+00:00
VOLUME 117,874,498 rows · 1,324,850,683 bytes (1.23 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured h: 117,118,196 · m: 116,897,111 · i: 116,524,386 · g: 115,900,469 · k: 110,317,421 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 2,948,036 (2.50%) · m: 105,728,861 (89.70%) · i: 1,154,573 (0.98%) · g: 335,739 (0.28%) · k: 7,707,289 (6.54%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 07cb17db8d54c7d5147d9e357f92808e832c1fb7fa5bf8c6d75149290c752f1b
the corpus checksum ledger names this file with the same digest
joined 117,876,693 to merged 117,874,498, minus 2,195 (minus 0.0019%)
boundary drops 2,195 · 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-02T14:46:58Z 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,435,755 114,824,328 0-35 88c39c9e16df3da86e4773398280c9396b4ac45e4dc46214678b75bc35325457 book 1,457,354 94,700,770 36-41 7628dda899d4884609344ec634d6013f8a4f94240a94da429ac50e0c997ab65c last_trade_price 62,633 3,612,345 42-42 8dc6c735a7357ce35671a113a6c4386807ef9061627f9d702f8bd899c49e07f4 market_resolved 707 103,042 43-43 671a90634744415ad25d20813c168abd9ed619dcc6dfa43951b2d4a958e101f8 new_market 1,059 102,611 44-44 1640b980e0418a3aa5371a3f761233314ccc7f6119c94606a7433b6a414db1f8 price_change 106,914,086 1,110,059,953 45-452 05f461bb69c1c16b4a7f9308e0fb2546d2bc34cff8492a590fdd6d4fea380888 tick_size_change 2,904 105,921 453-453 01fe9e5a59fdf41ab626d1dc9cd139f978fd1144d2203f5a040d2aad90c8f70e EVENT MIX count share price_change 106,914,086 90.70% best_bid_ask 9,435,755 8.00% book 1,457,354 1.24% last_trade_price 62,633 0.05% tick_size_change 2,904 <0.01% new_market 1,059 <0.01% market_resolved 707 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,435,909 9,435,755 154 1,721 FULL book 1,457,744 1,457,354 390 228,700 FULL last_trade_price 62,634 62,633 1 161 FULL market_resolved 707 707 0 2 FULL new_market 1,059 1,059 0 0 FULL price_change 106,915,736 106,914,086 1,650 1,252 FULL tick_size_change 2,904 2,904 0 26 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,414,336 1,110 79ms 120ms 874ms 32.4s 0 transport_latency_assumed best_bid_ask h 9,431,672 194,345 19ms 36ms 262ms 1.3min 0 transport_latency_assumed best_bid_ask i 9,434,880 82,765 23ms 43ms 234ms 52.6s 0 transport_latency_assumed best_bid_ask k 8,885,068 557,735 14ms 29ms 184ms 1.0min 0 transport_latency_assumed best_bid_ask m 9,433,784 8,599,800 5ms 16ms 157ms 8.3s 0 transport_latency_assumed book g 695,328 319,408 25.6min 1.0d 41.0d 125.6d 0 book_staleness book h 753,910 389,530 29.0min 1.1d 40.9d 125.6d 0 book_staleness book i 140,649 7,817 37ms 3.3s 3.9d 125.6d 0 book_staleness book k 855,754 418,241 39.8min 1.4d 40.9d 125.6d 0 book_staleness book m 505,946 322,358 9.3min 14.3h 40.9d 125.6d 0 book_staleness last_trade_price g 58,814 37 91ms 2.0s 13.7s 32.5s 0 transport_latency_assumed last_trade_price h 62,561 2,105 21ms 97ms 823ms 30.2s 0 transport_latency_assumed last_trade_price i 62,618 929 29ms 153ms 2.1s 3.9s 0 transport_latency_assumed last_trade_price k 57,904 4,953 16ms 57ms 351ms 56.0s 0 transport_latency_assumed last_trade_price m 62,604 54,609 6ms 34ms 352ms 1.3s 0 transport_latency_assumed market_resolved g 625 1 88ms 35.4s 54.1s 1.7min 0 transport_latency_assumed market_resolved h 625 11 26ms 29.1s 50.8s 52.7s 0 transport_latency_assumed market_resolved i 625 4 40ms 23.3s 44.8s 51.8s 0 transport_latency_assumed market_resolved k 628 103 17ms 41.2s 5.4min 5.9min 0 transport_latency_assumed market_resolved m 625 588 6ms 17.0s 37.8s 44.6s 0 transport_latency_assumed new_market g 650 63 315ms 1.3min 14.1min 14.6min 0 transport_latency_assumed new_market h 650 191 216ms 13.0min 14.2min 14.5min 0 transport_latency_assumed new_market i 650 114 168ms 59.7s 14.1min 14.5min 0 transport_latency_assumed new_market k 661 185 166ms 6.2min 14.1min 14.6min 0 transport_latency_assumed new_market m 650 506 31ms 45.8s 14.1min 14.7min 0 transport_latency_assumed price_change g 105,727,812 15,112 80ms 199ms 6.3s 32.6s 0 transport_latency_assumed price_change h 106,865,874 2,361,792 20ms 42ms 420ms 1.4min 0 transport_latency_assumed price_change i 106,882,060 1,062,908 23ms 48ms 533ms 53.9s 0 transport_latency_assumed price_change k 100,514,606 6,725,910 14ms 33ms 249ms 1.1min 0 transport_latency_assumed price_change m 106,890,598 96,748,364 5ms 19ms 192ms 8.5s 0 transport_latency_assumed tick_size_change g 2,904 8 78ms 98ms 280ms 12.7s 0 transport_latency_assumed tick_size_change h 2,904 62 19ms 36ms 178ms 448ms 0 transport_latency_assumed tick_size_change i 2,904 36 24ms 50ms 296ms 593ms 0 transport_latency_assumed tick_size_change k 2,800 162 14ms 24ms 115ms 142ms 0 transport_latency_assumed tick_size_change m 2,904 2,636 5ms 15ms 275ms 602ms 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-02/12/2026-10-02T12.parquet sha256sum 2026-10-02T12.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.