Hour audit: 2026-10-08T10
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-08T10 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-08T10:00:00.000666187+00:00 · last event 2026-10-08T10:59:59.999874038+00:00
VOLUME 123,273,556 rows · 1,431,308,119 bytes (1.33 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured m: 122,788,107 · o: 122,780,015 · h: 122,739,407 · i: 122,534,690 · n: 119,975,276 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 64,236,723 (52.11%) · o: 56,862,819 (46.13%) · h: 1,261,921 (1.02%) · i: 713,921 (0.58%) · n: 198,172 (0.16%) (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 123,273,556 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 5c830d2b02a8ed4c4a85fb48eb0ca5951e40667bb48432c9fad4c577785320a4
the corpus checksum ledger names this file with the same digest
joined 123,275,040 to merged 123,273,556, minus 1,484 (minus 0.0012%)
boundary drops 1,484 · 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-08T12:05:54Z as himno
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 11,330,196 141,172,845 0-43 6ff90a2a2ad3188fe61b0c64575faf2e63dbbc1f4b875f2e49de596df9690df5 book 751,611 67,424,108 44-46 f909c2dc962ce2d10d5a97ac5122c6305e97534760db05bb355e2e4b9a90b95c last_trade_price 55,418 3,193,526 47-47 974aba610a6d248faca4cc8e9df7e67beaacfd731ff1eb369342bf98d9035f02 market_resolved 519 84,288 48-48 aff3851d3c9084d097ec5d08390d11f8d5a5a4b8fd207db731c3984a51bf2670 new_market 1,364 125,138 49-49 6cfd66a7f17189a027a8708b5656477922a258be9988a0f49e98f3e0fb0810cf price_change 111,131,956 1,217,812,683 50-473 038a28bc6e4aedbbdeadade3527ab9a9d8d918f2ee50977005fa1664b27220af tick_size_change 2,492 92,146 474-474 dbcc03e777c7b531079df101434cd4ec33f1dfe768ff56e02f8e3906ec2cd0d5 EVENT MIX count share price_change 111,131,956 90.15% best_bid_ask 11,330,196 9.19% book 751,611 0.61% last_trade_price 55,418 0.04% tick_size_change 2,492 <0.01% new_market 1,364 <0.01% market_resolved 519 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,330,254 11,330,196 58 99 FULL book 752,387 751,611 776 217,578 FULL last_trade_price 55,418 55,418 0 4 FULL market_resolved 519 519 0 13 FULL new_market 1,364 1,364 0 0 FULL price_change 111,132,606 111,131,956 650 52 FULL tick_size_change 2,492 2,492 0 9 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 11,327,114 94,623 18ms 32ms 273ms 1.1min 0 transport_latency_assumed best_bid_ask i 11,328,772 63,471 21ms 33ms 161ms 5.5s 0 transport_latency_assumed best_bid_ask m 11,328,515 5,830,094 6ms 16ms 107ms 4.4s 0 transport_latency_assumed best_bid_ask n 11,247,009 3,949 44ms 68ms 482ms 24.6s 0 transport_latency_assumed best_bid_ask o 11,328,574 5,338,059 6ms 16ms 120ms 11.8s 0 transport_latency_assumed book h 354,412 193,628 2.8min 6.4h 46.8d 131.5d 0 book_staleness book i 119,924 6,167 26ms 1.0s 6.3h 113.0d 0 book_staleness book m 312,703 203,820 1.7min 6.6h 46.8d 131.5d 0 book_staleness book n 305,827 155,775 2.1min 6.5h 46.8d 131.5d 0 book_staleness book o 304,492 192,221 1.5min 6.5h 46.8d 131.5d 0 book_staleness last_trade_price h 55,134 529 22ms 159ms 863ms 17.4s 0 transport_latency_assumed last_trade_price i 55,189 274 26ms 294ms 1.6s 5.5s 0 transport_latency_assumed last_trade_price m 55,252 29,106 7ms 30ms 213ms 2.0s 0 transport_latency_assumed last_trade_price n 49,590 27 57ms 1.0s 10.6s 24.1s 0 transport_latency_assumed last_trade_price o 55,226 25,482 7ms 32ms 229ms 3.5s 0 transport_latency_assumed market_resolved h 508 2 21ms 105ms 51.0s 51.0s 0 transport_latency_assumed market_resolved i 508 39 23ms 116ms 39.8s 39.8s 0 transport_latency_assumed market_resolved m 508 237 6ms 38ms 41.8s 41.8s 0 transport_latency_assumed market_resolved n 495 12 45ms 185ms 54.3s 57.4s 0 transport_latency_assumed market_resolved o 508 229 6ms 34ms 41.7s 41.8s 0 transport_latency_assumed new_market h 801 133 242ms 26.0s 41.2s 1.7min 0 transport_latency_assumed new_market i 801 231 137ms 25.6s 40.1s 1.6min 0 transport_latency_assumed new_market m 801 438 78ms 31.4s 37.0s 37.5s 0 transport_latency_assumed new_market n 801 269 197ms 29.1s 36.2s 1.5min 0 transport_latency_assumed new_market o 801 293 136ms 25.6s 37.7s 1.7min 0 transport_latency_assumed price_change h 110,998,946 973,004 19ms 39ms 455ms 1.1min 0 transport_latency_assumed price_change i 111,027,004 643,732 21ms 44ms 543ms 5.6s 0 transport_latency_assumed price_change m 111,087,836 58,171,754 6ms 18ms 120ms 5.5s 0 transport_latency_assumed price_change n 108,369,098 38,140 44ms 98ms 3.7s 24.6s 0 transport_latency_assumed price_change o 111,087,922 51,305,326 6ms 19ms 136ms 11.8s 0 transport_latency_assumed tick_size_change h 2,492 2 18ms 28ms 87ms 4.3s 0 transport_latency_assumed tick_size_change i 2,492 7 21ms 32ms 53ms 343ms 0 transport_latency_assumed tick_size_change m 2,492 1,274 6ms 13ms 35ms 62ms 0 transport_latency_assumed tick_size_change n 2,456 not meas. 44ms 67ms 1.9s 5.5s 0 transport_latency_assumed tick_size_change o 2,492 1,209 6ms 14ms 46ms 229ms 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-08/10/2026-10-08T10.parquet sha256sum 2026-10-08T10.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.