Hour audit: 2026-10-07T08
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-07T08 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-07T08:00:00.000008910+00:00 · last event 2026-10-07T08:59:59.999776092+00:00
VOLUME 114,886,373 rows · 1,330,232,893 bytes (1.24 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured i: 114,680,310 · m: 114,281,004 · o: 114,258,187 · h: 114,210,438 · n: 113,768,011 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 1,276,384 (1.11%) · m: 57,562,147 (50.10%) · o: 55,059,290 (47.92%) · h: 928,102 (0.81%) · n: 60,450 (0.05%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 114,886,373 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 ac3752ac59c218d1cac23b20267e285e79368a7d4ee1efca2087a228549609a1
the corpus checksum ledger names this file with the same digest
joined 114,887,950 to merged 114,886,373, minus 1,577 (minus 0.0014%)
boundary drops 1,577 · 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-07T10:03:29Z 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 10,541,686 133,147,677 0-40 db809c6c28191ef9fc6794d373fa697106c3c05a90184c2fdd9d4596b6020230 book 679,062 63,418,007 41-43 cc0aade260782be8102450d5f2d8f7409b205b209a41806c153c77537514f350 last_trade_price 52,607 3,035,725 44-44 db22816925ef38dca37cf431477fdee6020441d5bc24928e7f7476549f30bb73 market_resolved 576 95,434 45-45 da9a0156e8c948321ebd7b6185bada17c0964febdf72f558e232bfad8c99a9ad new_market 2,492 228,273 46-46 07e659b8dbabe4aac3b29a0db6406d51d2517b187be3ce2f8ee8104b9a3965a4 price_change 103,606,698 1,128,875,733 47-442 7a51fcfdf9004f6b43f5daea0bdb2feb0d1c98e0521d91a03afa64d2cef14bfa tick_size_change 3,252 120,203 443-443 6134ac4b8131d23f921aa159de70bfab65a340ddd512245ea6ce45de6dbe5a71 EVENT MIX count share price_change 103,606,698 90.18% best_bid_ask 10,541,686 9.18% book 679,062 0.59% last_trade_price 52,607 0.05% tick_size_change 3,252 <0.01% new_market 2,492 <0.01% market_resolved 576 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,541,804 10,541,686 118 293 FULL book 679,484 679,062 422 225,046 FULL last_trade_price 52,608 52,607 1 2 FULL market_resolved 576 576 0 0 FULL new_market 2,492 2,492 0 0 FULL price_change 103,607,734 103,606,698 1,036 259 FULL tick_size_change 3,252 3,252 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,539,168 79,369 18ms 32ms 374ms 1.5min 0 transport_latency_assumed best_bid_ask i 10,535,933 65,263 22ms 34ms 204ms 11.8s 0 transport_latency_assumed best_bid_ask m 10,540,378 5,223,173 5ms 16ms 119ms 6.0s 0 transport_latency_assumed best_bid_ask n 10,532,608 4,165 43ms 66ms 446ms 35.1s 0 transport_latency_assumed best_bid_ask o 10,539,918 5,169,716 5ms 16ms 133ms 17.4s 0 transport_latency_assumed book h 114,924 6,848 25ms 848ms 22.2h 111.9d 0 book_staleness book i 660,181 546,094 14.3min 1.7d 45.8d 130.4d 0 book_staleness book m 114,755 58,401 8ms 146ms 18.9h 111.9d 0 book_staleness book n 115,764 8,432 56ms 6.2s 1.9d 122.7d 0 book_staleness book o 116,328 59,287 8ms 240ms 1.4d 111.9d 0 book_staleness last_trade_price h 52,299 472 21ms 182ms 2.5s 1.0min 0 transport_latency_assumed last_trade_price i 51,985 283 27ms 335ms 3.2s 11.8s 0 transport_latency_assumed last_trade_price m 52,424 25,536 7ms 32ms 236ms 1.7s 0 transport_latency_assumed last_trade_price n 51,298 52 54ms 1.0s 7.6s 26.4s 0 transport_latency_assumed last_trade_price o 52,480 26,264 6ms 33ms 252ms 5.7s 0 transport_latency_assumed market_resolved h 558 3 21ms 97ms 38.1s 41.6s 0 transport_latency_assumed market_resolved i 558 40 25ms 144ms 57.5s 58.4s 0 transport_latency_assumed market_resolved m 558 264 6ms 30ms 36.7s 55.8s 0 transport_latency_assumed market_resolved n 558 1 47ms 237ms 51.3s 54.8s 0 transport_latency_assumed market_resolved o 558 268 6ms 25ms 41.8s 45.4s 0 transport_latency_assumed new_market h 1,457 448 186ms 37.8s 42.5s 1.6min 0 transport_latency_assumed new_market i 1,457 276 139ms 38.2s 45.8s 1.7min 0 transport_latency_assumed new_market m 1,457 911 61ms 36.6s 44.3s 1.6min 0 transport_latency_assumed new_market n 1,457 222 285ms 39.1s 43.2s 1.6min 0 transport_latency_assumed new_market o 1,457 635 101ms 37.7s 42.5s 1.3min 0 transport_latency_assumed price_change h 103,498,780 840,948 19ms 44ms 660ms 1.6min 0 transport_latency_assumed price_change i 103,426,944 664,428 22ms 48ms 776ms 11.8s 0 transport_latency_assumed price_change m 103,568,180 52,252,306 5ms 18ms 149ms 7.4s 0 transport_latency_assumed price_change n 103,063,074 47,578 44ms 115ms 3.3s 36.8s 0 transport_latency_assumed price_change o 103,544,194 49,801,438 5ms 18ms 163ms 17.5s 0 transport_latency_assumed tick_size_change h 3,252 14 18ms 27ms 146ms 4.4s 0 transport_latency_assumed tick_size_change i 3,252 not meas. 22ms 33ms 75ms 742ms 0 transport_latency_assumed tick_size_change m 3,252 1,556 5ms 12ms 37ms 1.0s 0 transport_latency_assumed tick_size_change n 3,252 not meas. 43ms 53ms 120ms 444ms 0 transport_latency_assumed tick_size_change o 3,252 1,682 5ms 13ms 50ms 985ms 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-07/08/2026-10-07T08.parquet sha256sum 2026-10-07T08.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.