Hour audit: 2026-09-25T06
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-25T06 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-25T06:00:00.000019829+00:00 · last event 2026-09-25T06:59:59.999892674+00:00
VOLUME 115,076,701 rows · 1,203,384,244 bytes (1.12 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured i: 114,633,709 · c: 114,625,426 · h: 114,610,057 · g: 114,601,621 · k: 110,183,277 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 1,101,084 (0.96%) · c: 107,763,157 (93.64%) · h: 1,030,088 (0.90%) · g: 9,628 (0.01%) · k: 5,172,744 (4.50%) (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 115,076,701 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 17899ce4c16d6cb9337e73a4e507abe6fa91033a0a5ae8aed46cffac843eb561
the corpus checksum ledger names this file with the same digest
joined 115,079,099 to merged 115,076,701, minus 2,398 (minus 0.0021%)
boundary drops 2,398 · 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-25T09:06:19Z as cghik
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 13,320,362 150,330,487 0-50 84ed9586067ec2eab8ff3397f864dc466c99596f69dffe3ad79efb4606a89769 book 525,102 52,382,718 51-53 1a835d2fb00716043f3b88ae7df4d97deed40037ad7a5fd4e1ca68ccba1b73f2 last_trade_price 47,439 2,699,962 54-54 c981e5115e7eef1bde44a13ea651d696b37c4a00ac78ea7a6c798ffc9703e659 market_resolved 761 117,423 55-55 4658478ad85b4105f34641179f4f129c314611e2fc7bef71d04642ce76db90cb new_market 483 54,114 56-56 05e9d60fa9aed8a747586886bd85fb84e2bfd31553d3638da12176ca3c178e10 price_change 101,180,666 996,420,080 57-442 2d9906c9235e5ca874cd78ad569bf29099079876bb3e825c72aff4dfad334cee tick_size_change 1,888 70,015 443-443 57a8c855db65602a730151ab148629786b5cc766b6094946435bda60cf948b8a EVENT MIX count share price_change 101,180,666 87.92% best_bid_ask 13,320,362 11.58% book 525,102 0.46% last_trade_price 47,439 0.04% tick_size_change 1,888 <0.01% market_resolved 761 <0.01% new_market 483 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,320,710 13,320,362 348 534 FULL book 525,112 525,102 10 205,818 FULL last_trade_price 47,439 47,439 0 58 FULL market_resolved 761 761 0 5 FULL new_market 483 483 0 0 FULL price_change 101,182,706 101,180,666 2,040 367 FULL tick_size_change 1,888 1,888 0 14 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 13,319,738 12,614,975 5ms 9ms 76ms 3.4s 0 transport_latency_assumed best_bid_ask g 13,318,326 334 79ms 96ms 231ms 6.8s 0 transport_latency_assumed best_bid_ask h 13,318,872 99,125 18ms 42ms 108ms 18.2s 0 transport_latency_assumed best_bid_ask i 13,319,349 107,978 19ms 24ms 81ms 3.8s 0 transport_latency_assumed best_bid_ask k 12,751,374 497,950 13ms 18ms 72ms 2.3s 0 transport_latency_assumed book c 100,658 90,526 7ms 52ms 2.4d 99.8d 0 book_staleness book g 101,297 3,487 84ms 427ms 3.3d 99.8d 0 book_staleness book h 98,809 3,908 22ms 89ms 9.2h 99.7d 0 book_staleness book i 96,000 1,948 21ms 61ms 598ms 55.9d 0 book_staleness book k 513,374 425,233 5.8min 3.4d 33.7d 118.3d 0 book_staleness last_trade_price c 47,318 43,265 6ms 20ms 186ms 1.7s 0 transport_latency_assumed last_trade_price g 47,260 28 83ms 233ms 1.2s 6.8s 0 transport_latency_assumed last_trade_price h 47,204 607 20ms 66ms 260ms 6.2s 0 transport_latency_assumed last_trade_price i 47,410 634 21ms 55ms 266ms 1.9s 0 transport_latency_assumed last_trade_price k 45,832 2,905 15ms 33ms 206ms 880ms 0 transport_latency_assumed market_resolved c 722 603 5ms 23.6s 48.3s 50.7s 0 transport_latency_assumed market_resolved g 722 24 94ms 14.7s 40.8s 44.6s 0 transport_latency_assumed market_resolved h 722 3 32ms 15.9s 41.6s 44.6s 0 transport_latency_assumed market_resolved i 722 82 26ms 14.5s 39.9s 42.8s 0 transport_latency_assumed market_resolved k 717 49 17ms 37.5s 4.9min 4.9min 0 transport_latency_assumed new_market c 354 172 48ms 10.8s 27.3s 1.8min 0 transport_latency_assumed new_market g 354 29 208ms 12.6s 26.6s 1.6min 0 transport_latency_assumed new_market h 354 61 104ms 11.3s 25.7s 1.3min 0 transport_latency_assumed new_market i 354 124 60ms 9.8s 49.9s 1.5min 0 transport_latency_assumed new_market k 354 97 66ms 10.9s 45.9s 1.6min 0 transport_latency_assumed price_change c 101,154,748 95,011,778 5ms 11ms 95ms 4.5s 0 transport_latency_assumed price_change g 101,131,774 5,726 80ms 101ms 325ms 6.8s 0 transport_latency_assumed price_change h 101,142,208 926,368 18ms 46ms 138ms 18.3s 0 transport_latency_assumed price_change i 101,167,986 990,314 20ms 27ms 113ms 3.9s 0 transport_latency_assumed price_change k 96,869,794 4,246,480 13ms 21ms 93ms 2.3s 0 transport_latency_assumed tick_size_change c 1,888 1,838 5ms 7ms 27ms 75ms 0 transport_latency_assumed tick_size_change g 1,888 not meas. 79ms 94ms 205ms 333ms 0 transport_latency_assumed tick_size_change h 1,888 16 18ms 43ms 106ms 304ms 0 transport_latency_assumed tick_size_change i 1,888 4 19ms 22ms 45ms 491ms 0 transport_latency_assumed tick_size_change k 1,832 30 13ms 18ms 51ms 77ms 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-25/06/2026-09-25T06.parquet sha256sum 2026-09-25T06.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.