Hour audit: 2026-10-02T02
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-02T02 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-02T02:00:00.000541146+00:00 · last event 2026-10-02T02:59:59.999978835+00:00
VOLUME 121,300,573 rows · 1,266,288,017 bytes (1.18 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured m: 120,765,489 · i: 120,757,643 · h: 120,755,366 · g: 120,743,550 · k: 115,266,114 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 118,038,151 (97.31%) · i: 123,837 (0.10%) · h: 456,807 (0.38%) · g: 27,677 (0.02%) · k: 2,654,101 (2.19%) (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 121,300,573 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 837a92ac04984ea9dcdb3a7df0bff5ecdfd581578e9c8ddec15da9cdd4dc4722
the corpus checksum ledger names this file with the same digest
joined 121,302,028 to merged 121,300,573, minus 1,455 (minus 0.0012%)
boundary drops 1,455 · 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-02T04:48:49Z 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,814,049 110,905,239 0-37 f4537703c777147d224d64f5014b714062cb2289fadd3ad90ca4b38ebede59f4 book 663,637 63,913,325 38-40 22fe7a094655ef17ead353af5121cd74270042b0134c394b9bd48cbbe8f4a38f last_trade_price 67,037 3,551,498 41-41 6c9574c745d3945bac51f83813854fa8c6a8cd89688a2aa7b197b4100bca838a market_resolved 1,002 144,692 42-42 ef4df9bca1127d895e0196a8443750e039ab4f2ee5d6f05ead109ae8abbf9b06 new_market 1,142 126,115 43-43 2df0417f29a1489a9b47487ec756061a25ab4a052df3170d08986572d3ca192c price_change 110,751,238 1,086,173,139 44-466 a3d38917898ba2c7356f64024a994dc3db602309791a8a4e11f4775970884bba tick_size_change 2,468 91,110 467-467 04745fb3ca1d014c8e5f0f1999da76e87e32ddc6462e5de02502cb611304488e EVENT MIX count share price_change 110,751,238 91.30% best_bid_ask 9,814,049 8.09% book 663,637 0.55% last_trade_price 67,037 0.06% tick_size_change 2,468 <0.01% new_market 1,142 <0.01% market_resolved 1,002 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,814,173 9,814,049 124 927 FULL book 663,675 663,637 38 234,314 FULL last_trade_price 67,038 67,037 1 85 FULL market_resolved 1,002 1,002 0 240 FULL new_market 1,160 1,142 18 133 FULL price_change 110,752,512 110,751,238 1,274 667 FULL tick_size_change 2,468 2,468 0 39 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,811,600 1,724 75ms 91ms 238ms 13.0s 0 transport_latency_assumed best_bid_ask h 9,812,486 33,656 17ms 31ms 149ms 56.6s 0 transport_latency_assumed best_bid_ask i 9,812,247 9,504 30ms 49ms 86ms 54.1s 0 transport_latency_assumed best_bid_ask k 9,348,478 165,758 12ms 19ms 119ms 37.8s 0 transport_latency_assumed best_bid_ask m 9,812,455 9,603,407 5ms 8ms 35ms 8.2s 0 transport_latency_assumed book g 150,526 7,561 78ms 3.3s 2.9d 106.7d 0 book_staleness book h 160,947 12,891 21ms 18.3min 14.3d 125.2d 0 book_staleness book i 155,295 9,991 31ms 2.4min 5.5d 125.2d 0 book_staleness book k 620,164 482,277 22.8min 22.4h 40.5d 125.2d 0 book_staleness book m 174,534 150,917 6ms 1.2h 22.8d 125.2d 0 book_staleness last_trade_price g 67,001 23 77ms 94ms 286ms 7.0s 0 transport_latency_assumed last_trade_price h 67,004 360 18ms 31ms 180ms 23.3s 0 transport_latency_assumed last_trade_price i 67,010 54 29ms 48ms 109ms 5.8s 0 transport_latency_assumed last_trade_price k 62,106 1,309 14ms 22ms 117ms 2.6s 0 transport_latency_assumed last_trade_price m 67,011 65,291 5ms 9ms 30ms 3.4s 0 transport_latency_assumed market_resolved g 665 54 78ms 252ms 58.4s 58.4s 0 transport_latency_assumed market_resolved h 665 3 21ms 38.9s 52.5s 53.1s 0 transport_latency_assumed market_resolved i 665 40 42ms 33.8s 50.6s 55.6s 0 transport_latency_assumed market_resolved k 899 288 20ms 17.0min 30.2min 30.2min 0 transport_latency_assumed market_resolved m 665 617 5ms 33.7s 55.0s 55.1s 0 transport_latency_assumed new_market g 720 209 565ms 21.4s 48.5s 1.7min 0 transport_latency_assumed new_market h 720 97 226ms 20.4s 26.5s 1.7min 0 transport_latency_assumed new_market i 720 134 227ms 21.5s 44.4s 1.6min 0 transport_latency_assumed new_market k 860 257 286ms 10.3min 24.8min 25.3min 0 transport_latency_assumed new_market m 720 445 64ms 20.6s 43.1s 1.6min 0 transport_latency_assumed price_change g 110,710,570 18,106 76ms 93ms 342ms 13.4s 0 transport_latency_assumed price_change h 110,711,076 409,776 17ms 31ms 156ms 56.8s 0 transport_latency_assumed price_change i 110,719,238 104,110 30ms 49ms 112ms 54.1s 0 transport_latency_assumed price_change k 105,231,295 2,004,168 13ms 20ms 121ms 44.2s 0 transport_latency_assumed price_change m 110,707,636 108,215,078 5ms 8ms 36ms 8.2s 0 transport_latency_assumed tick_size_change g 2,468 not meas. 75ms 92ms 217ms 938ms 0 transport_latency_assumed tick_size_change h 2,468 24 18ms 31ms 74ms 1.0s 0 transport_latency_assumed tick_size_change i 2,468 4 31ms 50ms 84ms 462ms 0 transport_latency_assumed tick_size_change k 2,312 44 13ms 23ms 116ms 129ms 0 transport_latency_assumed tick_size_change m 2,468 2,396 5ms 8ms 26ms 477ms 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/02/2026-10-02T02.parquet sha256sum 2026-10-02T02.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.