Hour audit: 2026-10-06T05
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-06T05 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-06T05:00:00.000045558+00:00 · last event 2026-10-06T05:59:59.999980948+00:00
VOLUME 112,654,044 rows · 1,313,128,701 bytes (1.22 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured h: 111,467,582 · m: 111,442,294 · o: 111,436,448 · i: 111,389,695 · n: 111,230,113 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 1,295,822 (1.15%) · m: 56,933,509 (50.54%) · o: 52,911,154 (46.97%) · i: 1,067,600 (0.95%) · n: 445,959 (0.40%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 44f7a3ff4f827ac454144d83ba04eac49d233238c5b7e43532c030721099cb91
the corpus checksum ledger names this file with the same digest
joined 112,655,246 to merged 112,654,044, minus 1,202 (minus 0.0011%)
boundary drops 1,202 · 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-06T07:00:30Z 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,223,714 142,603,918 0-42 546d663be06cd198c8328f6e265f07dac481405286dff7fe5e76708d0149eb72 book 2,009,874 103,270,276 43-50 197cae94974a8d5c97d8bc3de2600c28a230b13e189cdcd9e4cce800fb54a138 last_trade_price 41,373 2,399,657 51-51 9c53d1645bd211fa25f80b4b333a962b06c48fa714629b829810fb1f8572ff1f market_resolved 1,845 301,120 52-52 26bd1e6ffe773cd410cf5d514e0de3af7ca4124619dcc6ef93b4f8d416c3ecea new_market 3,154 303,868 53-53 aba98db5013a80e96478732e0293ea7154107232b0a7b5f4726d7f8722dc9314 price_change 99,369,288 1,062,789,056 54-433 1f85f363dd3b83f0b66d5beb2dd6a5756f3f3b5e79073400a8339a9670e07bed tick_size_change 4,796 176,764 434-434 71a690d5b83d1e0fffc677383b2b9ecd5c434c75377000c50620e9c34b459299 EVENT MIX count share price_change 99,369,288 88.21% best_bid_ask 11,223,714 9.96% book 2,009,874 1.78% last_trade_price 41,373 0.04% tick_size_change 4,796 <0.01% new_market 3,154 <0.01% market_resolved 1,845 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,223,866 11,223,714 152 427 FULL book 2,009,896 2,009,874 22 1,611 FULL last_trade_price 41,373 41,373 0 7 FULL market_resolved 1,845 1,845 0 6 FULL new_market 3,154 3,154 0 0 FULL price_change 99,370,316 99,369,288 1,028 790 FULL tick_size_change 4,796 4,796 0 1 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 11,213,108 73,846 18ms 29ms 396ms 55.8s 0 transport_latency_assumed best_bid_ask i 11,215,296 69,039 21ms 29ms 141ms 5.0s 0 transport_latency_assumed best_bid_ask m 11,216,048 5,771,620 4ms 12ms 109ms 8.0s 0 transport_latency_assumed best_bid_ask n 11,210,992 6,766 43ms 59ms 277ms 16.9s 0 transport_latency_assumed best_bid_ask o 11,216,745 5,302,443 4ms 13ms 126ms 9.9s 0 transport_latency_assumed book h 991,677 381,700 8.1min 1.9d 44.7d 129.3d 0 book_staleness book i 901,672 271,275 7.8min 1.7d 44.7d 129.3d 0 book_staleness book m 1,050,768 494,608 8.7min 1.9d 44.7d 129.3d 0 book_staleness book n 1,000,841 360,034 8.5min 1.8d 44.7d 129.3d 0 book_staleness book o 1,057,698 502,257 8.9min 1.8d 44.7d 129.3d 0 book_staleness last_trade_price h 41,196 431 19ms 75ms 664ms 44.5s 0 transport_latency_assumed last_trade_price i 41,123 349 23ms 103ms 741ms 5.0s 0 transport_latency_assumed last_trade_price m 41,214 21,622 5ms 25ms 225ms 4.4s 0 transport_latency_assumed last_trade_price n 40,774 46 46ms 174ms 5.7s 17.0s 0 transport_latency_assumed last_trade_price o 41,291 18,925 6ms 26ms 236ms 9.9s 0 transport_latency_assumed market_resolved h 1,834 6 20ms 59ms 32.1s 53.0s 0 transport_latency_assumed market_resolved i 1,833 53 23ms 55ms 28.2s 57.1s 0 transport_latency_assumed market_resolved m 1,834 978 5ms 14ms 36.4s 56.2s 0 transport_latency_assumed market_resolved n 1,833 1 45ms 119ms 54.6s 54.7s 0 transport_latency_assumed market_resolved o 1,835 807 5ms 17ms 44.3s 44.4s 0 transport_latency_assumed new_market h 1,971 358 178ms 31.1s 47.4s 1.6min 0 transport_latency_assumed new_market i 1,971 505 128ms 32.5s 50.3s 1.7min 0 transport_latency_assumed new_market m 1,971 1,159 62ms 30.1s 52.6s 1.4min 0 transport_latency_assumed new_market n 1,971 378 184ms 31.3s 52.4s 1.3min 0 transport_latency_assumed new_market o 1,971 754 88ms 33.1s 56.0s 1.7min 0 transport_latency_assumed price_change h 99,213,000 839,460 18ms 35ms 509ms 55.9s 0 transport_latency_assumed price_change i 99,223,004 726,338 21ms 37ms 281ms 5.0s 0 transport_latency_assumed price_change m 99,125,663 50,641,116 4ms 15ms 143ms 8.4s 0 transport_latency_assumed price_change n 98,968,910 78,726 44ms 76ms 913ms 17.6s 0 transport_latency_assumed price_change o 99,112,112 47,083,648 4ms 15ms 165ms 10.0s 0 transport_latency_assumed tick_size_change h 4,796 21 18ms 29ms 402ms 42.3s 0 transport_latency_assumed tick_size_change i 4,796 41 21ms 41ms 188ms 463ms 0 transport_latency_assumed tick_size_change m 4,796 2,406 4ms 11ms 242ms 655ms 0 transport_latency_assumed tick_size_change n 4,792 8 43ms 73ms 353ms 4.6s 0 transport_latency_assumed tick_size_change o 4,796 2,320 4ms 11ms 218ms 431ms 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-06/05/2026-10-06T05.parquet sha256sum 2026-10-06T05.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.