Hour audit: 2026-10-01T00
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-01T00 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-01T00:00:00.000019030+00:00 · last event 2026-10-01T00:59:59.999946707+00:00
VOLUME 102,397,484 rows · 1,117,902,468 bytes (1.04 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured h: 94,655,440 · m: 94,333,485 · i: 92,806,962 · g: 91,304,567 · k: 89,140,403 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 6,121,434 (5.98%) · m: 79,829,360 (77.96%) · i: 3,335,939 (3.26%) · g: 224,108 (0.22%) · k: 12,886,643 (12.58%) (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 102,397,484 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 3cf8af889a66959da63b4115d4161feee3447e8ba3cbb8239fc201023eae41b3
the corpus checksum ledger names this file with the same digest
joined 102,402,777 to merged 102,397,484, minus 5,293 (minus 0.0052%)
boundary drops 5,293 · 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-01T03:42:53Z 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 10,234,447 119,024,445 0-39 8e891a37a152e8f0c5282ef19abe9ba96efdfe78000d6bbe7a0b432f1ee940fd book 904,580 71,858,715 40-43 d5f85e894dba425b8a174eb64b6ddb306afc0ddc6ba1d152d0a7dcb8797f70e5 last_trade_price 46,074 2,639,256 44-44 5dfc8a08b39c04539f004927804d3490fdf39b726800625308b938c1650ddcf5 market_resolved 967 148,977 45-45 08bf9af912bcfccfb1317758ef87b13995f4a57fa7161f7ac04f65d249ca7806 new_market 1,040 107,267 46-46 a74d90b7bd4c33da486e77bf61c724aa926a923ec70f763e885d55d4fe16fb01 price_change 91,207,800 922,860,324 47-394 321a5f678ea29616d77ea4a4d378c961e3c492fa9240028a5544a79f84f5864a tick_size_change 2,576 95,224 395-395 3a2280c689bd13048d5c69ed8b1dc69a8f2d3e8893bf310c57ce5eccd79413f0 EVENT MIX count share price_change 91,207,800 89.07% best_bid_ask 10,234,447 9.99% book 904,580 0.88% last_trade_price 46,074 0.04% tick_size_change 2,576 <0.01% new_market 1,040 <0.01% market_resolved 967 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,234,687 10,234,447 240 296 FULL book 905,962 904,580 1,382 162,775 FULL last_trade_price 46,075 46,074 1 10 FULL market_resolved 967 967 0 0 FULL new_market 1,040 1,040 0 0 FULL price_change 91,211,470 91,207,800 3,670 12,131 FULL tick_size_change 2,576 2,576 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 10,204,437 3,315 81ms 103ms 336ms 13.1s 0 transport_latency_assumed best_bid_ask h 10,220,392 308,966 18ms 39ms 200ms 54.0s 0 transport_latency_assumed best_bid_ask i 10,215,839 186,512 20ms 54ms 149ms 8.2s 0 transport_latency_assumed best_bid_ask k 10,207,853 1,242,898 13ms 30ms 140ms 20.3s 0 transport_latency_assumed best_bid_ask m 10,216,707 8,492,756 5ms 21ms 102ms 5.0s 0 transport_latency_assumed book g 508,490 116,776 36.5min 2.6d 39.4d 124.1d 0 book_staleness book h 600,276 240,176 51.3min 2.8d 39.4d 124.1d 0 book_staleness book i 484,233 130,724 27.9min 2.6d 39.4d 124.1d 0 book_staleness book k 545,365 155,118 40.5min 2.6d 39.4d 124.1d 0 book_staleness book m 491,626 261,786 20.2min 2.5d 39.4d 124.1d 0 book_staleness last_trade_price g 45,972 49 85ms 183ms 2.5s 13.0s 0 transport_latency_assumed last_trade_price h 46,014 1,384 20ms 52ms 271ms 44.7s 0 transport_latency_assumed last_trade_price i 45,968 572 22ms 71ms 471ms 3.5s 0 transport_latency_assumed last_trade_price k 45,991 4,535 15ms 44ms 185ms 9.1s 0 transport_latency_assumed last_trade_price m 45,922 39,534 6ms 22ms 176ms 3.6s 0 transport_latency_assumed market_resolved g 922 10 84ms 32.2s 52.3s 57.5s 0 transport_latency_assumed market_resolved h 922 51 21ms 28.6s 48.5s 55.0s 0 transport_latency_assumed market_resolved i 922 14 24ms 35.1s 51.1s 51.1s 0 transport_latency_assumed market_resolved k 922 132 15ms 24.7s 52.7s 52.7s 0 transport_latency_assumed market_resolved m 922 760 7ms 32.3s 48.7s 48.8s 0 transport_latency_assumed new_market g 666 130 182ms 23.3s 52.7s 1.6min 0 transport_latency_assumed new_market h 666 120 185ms 21.1s 44.9s 1.6min 0 transport_latency_assumed new_market i 666 120 117ms 20.7s 40.0s 1.7min 0 transport_latency_assumed new_market k 666 263 69ms 18.6s 51.4s 1.5min 0 transport_latency_assumed new_market m 666 407 60ms 13.4s 48.7s 1.1min 0 transport_latency_assumed price_change g 80,541,504 103,828 82ms 116ms 928ms 13.1s 0 transport_latency_assumed price_change h 83,784,594 5,570,670 19ms 44ms 373ms 55.3s 0 transport_latency_assumed price_change i 82,056,758 3,017,968 21ms 58ms 336ms 12.7s 0 transport_latency_assumed price_change k 78,337,030 11,483,382 14ms 35ms 208ms 20.4s 0 transport_latency_assumed price_change m 83,575,066 71,031,952 5ms 23ms 154ms 5.0s 0 transport_latency_assumed tick_size_change g 2,576 not meas. 81ms 103ms 492ms 1.2s 0 transport_latency_assumed tick_size_change h 2,576 67 19ms 41ms 327ms 762ms 0 transport_latency_assumed tick_size_change i 2,576 29 21ms 59ms 123ms 366ms 0 transport_latency_assumed tick_size_change k 2,576 315 14ms 31ms 98ms 4.5s 0 transport_latency_assumed tick_size_change m 2,576 2,165 5ms 19ms 68ms 155ms 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-01/00/2026-10-01T00.parquet sha256sum 2026-10-01T00.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.