Hour audit: 2026-10-08T03
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-08T03 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-08T03:00:00.000583243+00:00 · last event 2026-10-08T03:59:59.999711625+00:00
VOLUME 126,486,896 rows · 1,448,383,809 bytes (1.35 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured i: 126,272,854 · h: 125,940,938 · m: 125,913,467 · o: 125,846,672 · n: 125,769,898 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 1,283,757 (1.01%) · h: 1,407,985 (1.11%) · m: 61,393,850 (48.54%) · o: 62,328,978 (49.28%) · n: 72,326 (0.06%) (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 126,486,896 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 8331d33691b4b3841d554e76b6cc0427693057e5c75da933674aee5f3d0daa16
the corpus checksum ledger names this file with the same digest
joined 126,488,696 to merged 126,486,896, minus 1,800 (minus 0.0014%)
boundary drops 1,800 · 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-08T05:31:51Z 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,693,225 148,514,561 0-44 26c7b3d5706034b8ae0483c7badb84450fd58876bea015f27ff7ff8697c89be5 book 595,955 60,238,888 45-47 74f19c95fd62d0db804a09c04bd088360620d0d30ddeb672ba6b989aec359119 last_trade_price 47,530 2,724,535 48-48 b699523153256ca83b96aa940d4d38e4eb1887c2da6d22bcc14085713c8a3564 market_resolved 834 119,277 49-49 268dd454413e2bc34884299700efc218d3c341516eda8b5c539fb25b7982a2b0 new_market 806 81,973 50-50 0de0da765ec674d1e6d87ddfa763bb72f5d935ea41865a635e0e90a0902011d6 price_change 114,144,290 1,235,105,147 51-486 528afeb212f577e0d3c8148d535bb4eb9f126afd5e3d1e75993da7e3f5092e79 tick_size_change 4,256 157,660 487-487 5fb2a481e5a46fd6d70b5e30f05f4eac7e1e46fc968f48be8cab6322fb23aabd EVENT MIX count share price_change 114,144,290 90.24% best_bid_ask 11,693,225 9.24% book 595,955 0.47% last_trade_price 47,530 0.04% tick_size_change 4,256 <0.01% market_resolved 834 <0.01% new_market 806 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,693,402 11,693,225 177 75 FULL book 596,329 595,955 374 213,545 FULL last_trade_price 47,531 47,530 1 0 FULL market_resolved 834 834 0 0 FULL new_market 806 806 0 0 FULL price_change 114,145,538 114,144,290 1,248 93 FULL tick_size_change 4,256 4,256 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 11,692,360 112,649 18ms 32ms 194ms 30.4s 0 transport_latency_assumed best_bid_ask i 11,686,963 67,270 21ms 33ms 131ms 3.9s 0 transport_latency_assumed best_bid_ask m 11,691,656 5,833,976 5ms 17ms 110ms 6.5s 0 transport_latency_assumed best_bid_ask n 11,689,895 4,321 44ms 60ms 214ms 18.2s 0 transport_latency_assumed best_bid_ask o 11,691,847 5,675,009 5ms 17ms 108ms 6.4s 0 transport_latency_assumed book h 98,165 3,282 22ms 101ms 40.8min 112.7d 0 book_staleness book i 569,357 466,109 7.7min 1.8d 46.6d 131.2d 0 book_staleness book m 104,435 53,357 7ms 187ms 1.2d 112.7d 0 book_staleness book n 114,503 16,533 51ms 10.3min 18.5d 112.7d 0 book_staleness book o 107,645 56,674 8ms 17.1s 6.1d 112.7d 0 book_staleness last_trade_price h 47,453 836 20ms 72ms 439ms 11.3s 0 transport_latency_assumed last_trade_price i 47,087 424 24ms 81ms 576ms 3.9s 0 transport_latency_assumed last_trade_price m 47,290 23,046 6ms 28ms 206ms 1.4s 0 transport_latency_assumed last_trade_price n 46,832 45 48ms 258ms 3.5s 18.2s 0 transport_latency_assumed last_trade_price o 47,272 23,179 6ms 30ms 201ms 4.3s 0 transport_latency_assumed market_resolved h 727 82 21ms 1.2s 48.0s 56.4s 0 transport_latency_assumed market_resolved i 727 165 28ms 45.2s 55.7s 55.7s 0 transport_latency_assumed market_resolved m 727 292 7ms 36.4s 51.8s 57.7s 0 transport_latency_assumed market_resolved n 727 17 47ms 193ms 56.6s 57.2s 0 transport_latency_assumed market_resolved o 727 278 7ms 36.5s 51.9s 57.7s 0 transport_latency_assumed new_market h 522 48 135ms 20.0s 35.5s 1.8min 0 transport_latency_assumed new_market i 522 136 75ms 24.4s 1.2min 1.8min 0 transport_latency_assumed new_market m 522 219 47ms 22.0s 36.2s 1.5min 0 transport_latency_assumed new_market n 522 74 78ms 12.9s 35.9s 1.5min 0 transport_latency_assumed new_market o 522 329 51ms 29.1s 1.2min 1.6min 0 transport_latency_assumed price_change h 114,097,455 1,291,030 18ms 36ms 248ms 33.1s 0 transport_latency_assumed price_change i 113,963,942 749,633 22ms 39ms 210ms 3.9s 0 transport_latency_assumed price_change m 114,064,581 55,480,814 5ms 19ms 120ms 7.3s 0 transport_latency_assumed price_change n 113,913,163 51,336 44ms 73ms 697ms 21.1s 0 transport_latency_assumed price_change o 113,994,403 56,571,477 5ms 19ms 119ms 6.7s 0 transport_latency_assumed tick_size_change h 4,256 58 19ms 42ms 85ms 388ms 0 transport_latency_assumed tick_size_change i 4,256 20 22ms 40ms 111ms 438ms 0 transport_latency_assumed tick_size_change m 4,256 2,146 5ms 18ms 92ms 234ms 0 transport_latency_assumed tick_size_change n 4,256 not meas. 45ms 62ms 140ms 516ms 0 transport_latency_assumed tick_size_change o 4,256 2,032 6ms 21ms 80ms 250ms 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/03/2026-10-08T03.parquet sha256sum 2026-10-08T03.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.