Hour audit: 2026-10-08T22
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-08T22 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-08T22:00:00.000002104+00:00 · last event 2026-10-08T22:59:59.998214926+00:00
VOLUME 112,419,480 rows · 1,266,188,934 bytes (1.18 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 112,203,939 · m: 112,158,503 · n: 112,143,193 · i: 111,961,208 · h: 111,910,467 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 55,539,397 (49.40%) · m: 55,166,638 (49.07%) · n: 119,762 (0.11%) · i: 696,428 (0.62%) · h: 897,255 (0.80%) (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 112,419,480 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 615cabf005bfca98f6934800731d767033d2764acbfe90d2eed10ece75ae9310
the corpus checksum ledger names this file with the same digest
joined 112,421,021 to merged 112,419,480, minus 1,541 (minus 0.0014%)
boundary drops 1,541 · 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-09T00:02:31Z 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 12,134,613 151,714,423 0-46 6d99b210e8a27e49fcf3abe30fdf85667f979366d8af21368ad47f54b7b2fe48 book 169,641 17,152,737 47-47 42881e956cee2429506ec97b936129afff8e2c61ed0cda4223ac295402d68bd4 last_trade_price 60,990 3,434,007 48-48 37774eef1df5dba24e8eff725c53cb140d995c509934306025c6e09f5331e0fb market_resolved 720 117,846 49-49 5a42157b995a50e2fafdfb201454ff9f1ed7a125922d987085e0f1ba7b04659c new_market 2,010 192,581 50-50 9a88c02fe25633756e2d05c4ee777e798fc3f8b4551ddc589b0b6740c2c0bc4f price_change 100,049,170 1,092,208,903 51-432 a1cbad4b1f67266a38d3394142aee6871f89b64991034ad924c3a8060065ec75 tick_size_change 2,336 86,495 433-433 7da1b41f2476b9cd6c5295337f02210278cd4eb7b4b188f3bb410b6a4066387d EVENT MIX count share price_change 100,049,170 89.00% best_bid_ask 12,134,613 10.79% book 169,641 0.15% last_trade_price 60,990 0.05% tick_size_change 2,336 <0.01% new_market 2,010 <0.01% market_resolved 720 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,134,812 12,134,613 199 74 FULL book 169,674 169,641 33 15,549 FULL last_trade_price 60,991 60,990 1 1 FULL market_resolved 720 720 0 0 FULL new_market 2,010 2,010 0 0 FULL price_change 100,050,478 100,049,170 1,308 181 FULL tick_size_change 2,336 2,336 0 1 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 12,120,328 88,939 18ms 34ms 423ms 49.7s 0 transport_latency_assumed best_bid_ask i 12,122,077 68,407 21ms 34ms 209ms 11.8s 0 transport_latency_assumed best_bid_ask m 12,127,076 6,020,971 5ms 15ms 118ms 5.3s 0 transport_latency_assumed best_bid_ask n 12,127,577 7,478 45ms 65ms 309ms 16.1s 0 transport_latency_assumed best_bid_ask o 12,127,537 5,948,818 5ms 15ms 121ms 10.5s 0 transport_latency_assumed book h 131,483 8,840 25ms 2.3s 10.3h 124.3d 0 book_staleness book i 131,531 9,454 28ms 3.3s 15.3h 113.4d 0 book_staleness book m 133,141 69,123 7ms 202ms 15.1h 132.0d 0 book_staleness book n 133,090 13,604 60ms 9.4s 18.8h 113.5d 0 book_staleness book o 131,844 68,620 7ms 195ms 17.9h 113.5d 0 book_staleness last_trade_price h 59,680 383 21ms 530ms 3.9s 35.2s 0 transport_latency_assumed last_trade_price i 59,580 312 27ms 631ms 6.8s 11.8s 0 transport_latency_assumed last_trade_price m 60,264 29,410 6ms 27ms 251ms 2.1s 0 transport_latency_assumed last_trade_price n 58,954 187 57ms 1.3s 10.9s 16.1s 0 transport_latency_assumed last_trade_price o 59,814 30,698 6ms 28ms 266ms 10.6s 0 transport_latency_assumed market_resolved h 708 17 24ms 159ms 40.6s 49.5s 0 transport_latency_assumed market_resolved i 708 50 30ms 241ms 47.3s 51.8s 0 transport_latency_assumed market_resolved m 708 295 5ms 52ms 49.0s 53.8s 0 transport_latency_assumed market_resolved n 708 not meas. 61ms 369ms 37.0s 57.1s 0 transport_latency_assumed market_resolved o 708 358 5ms 62ms 49.6s 54.7s 0 transport_latency_assumed new_market h 1,200 164 154ms 28.1s 1.8min 2.3min 0 transport_latency_assumed new_market i 1,200 255 106ms 51.2s 2.0min 2.3min 0 transport_latency_assumed new_market m 1,200 720 56ms 28.5s 1.8min 2.3min 0 transport_latency_assumed new_market n 1,200 245 203ms 52.0s 2.0min 2.3min 0 transport_latency_assumed new_market o 1,200 626 85ms 54.2s 2.1min 2.4min 0 transport_latency_assumed price_change h 99,594,736 798,900 18ms 46ms 899ms 49.9s 0 transport_latency_assumed price_change i 99,643,776 617,930 21ms 48ms 1.1s 11.8s 0 transport_latency_assumed price_change m 99,833,778 49,044,992 5ms 17ms 149ms 6.5s 0 transport_latency_assumed price_change n 99,819,328 98,248 45ms 92ms 1.9s 16.1s 0 transport_latency_assumed price_change o 99,880,500 49,489,100 5ms 18ms 148ms 10.6s 0 transport_latency_assumed tick_size_change h 2,332 12 18ms 30ms 77ms 357ms 0 transport_latency_assumed tick_size_change i 2,336 20 21ms 32ms 112ms 527ms 0 transport_latency_assumed tick_size_change m 2,336 1,127 5ms 13ms 79ms 255ms 0 transport_latency_assumed tick_size_change n 2,336 not meas. 44ms 55ms 125ms 260ms 0 transport_latency_assumed tick_size_change o 2,336 1,177 5ms 12ms 73ms 9.3s 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/22/2026-10-08T22.parquet sha256sum 2026-10-08T22.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.