Hour audit: 2026-10-05T23
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-05T23 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-05T23:00:00.000109716+00:00 · last event 2026-10-05T23:59:59.999978955+00:00
VOLUME 108,846,668 rows · 1,199,383,597 bytes (1.12 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured i: 108,654,617 · o: 108,652,199 · m: 108,539,392 · n: 108,203,575 · h: 108,005,077 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 603,369 (0.55%) · o: 50,637,705 (46.52%) · m: 56,715,958 (52.11%) · n: 70,688 (0.06%) · h: 818,948 (0.75%) (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 108,846,668 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 83d18c154dbdb5f093e29b221bdb94bed84b6b3a287a7252a53068d409b9221e
the corpus checksum ledger names this file with the same digest
joined 108,847,720 to merged 108,846,668, minus 1,052 (minus 0.0010%)
boundary drops 1,052 · 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-06T00:59:56Z 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 9,693,765 119,343,867 0-36 a8341bc60160c72db087e6d2ad008d0f2d7559cc895b879603ccf51fbcd7307f book 156,657 15,432,935 37-37 e8295fda13e8184ae4763aef22bbdb21c81928f11c490fd0824340f7db765fd9 last_trade_price 59,690 3,342,526 38-38 4ac1d31a34c75762866c32fc819a19b3bf59f9cf0595be01307af873b0a21d83 market_resolved 1,131 180,996 39-39 8a5f7a1d5d86cfabc9e583cc89c3a4f093945ef91234dd5ebf030aeb95ced53d new_market 1,877 175,020 40-40 2fadc37ce1e6b7db837c6c903d0c297f5d46942769251557ca100bdc3713041c price_change 98,930,892 1,059,568,946 41-418 a1d981e2b41a0b38ad2d487e6cf854faa11e933f4955da7d3b6a96410ef2ef60 tick_size_change 2,656 98,229 419-419 0c9af03d2aef939f9dfb7e9f04b018329620d463714e106efcdffdc62e6767d2 EVENT MIX count share price_change 98,930,892 90.89% best_bid_ask 9,693,765 8.91% book 156,657 0.14% last_trade_price 59,690 0.05% tick_size_change 2,656 <0.01% new_market 1,877 <0.01% market_resolved 1,131 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,693,849 9,693,765 84 388 FULL book 156,665 156,657 8 11,040 FULL last_trade_price 59,690 59,690 0 12 FULL market_resolved 1,133 1,131 2 2 FULL new_market 1,877 1,877 0 1 FULL price_change 98,931,850 98,930,892 958 1,473 FULL tick_size_change 2,656 2,656 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 9,624,758 60,154 19ms 28ms 255ms 1.0min 0 transport_latency_assumed best_bid_ask i 9,690,733 50,138 21ms 30ms 123ms 3.6s 0 transport_latency_assumed best_bid_ask m 9,687,868 5,046,948 4ms 13ms 87ms 7.1s 0 transport_latency_assumed best_bid_ask n 9,674,226 3,330 44ms 62ms 276ms 19.9s 0 transport_latency_assumed best_bid_ask o 9,691,640 4,533,195 4ms 13ms 99ms 7.2s 0 transport_latency_assumed book h 127,307 9,236 21ms 187ms 11.9h 110.5d 0 book_staleness book i 127,037 7,384 24ms 289ms 6.6h 110.5d 0 book_staleness book m 128,374 69,473 6ms 90ms 9.9h 110.5d 0 book_staleness book n 126,792 8,594 48ms 1.2s 7.3h 110.5d 0 book_staleness book o 126,683 61,970 6ms 54ms 6.2h 110.5d 0 book_staleness last_trade_price h 58,992 914 20ms 56ms 458ms 29.8s 0 transport_latency_assumed last_trade_price i 59,344 468 23ms 93ms 883ms 3.6s 0 transport_latency_assumed last_trade_price m 59,060 31,012 6ms 24ms 195ms 1.2s 0 transport_latency_assumed last_trade_price n 58,278 60 48ms 336ms 7.6s 19.9s 0 transport_latency_assumed last_trade_price o 59,421 27,236 6ms 23ms 206ms 3.4s 0 transport_latency_assumed market_resolved h 1,115 5 28ms 130ms 48.7s 48.7s 0 transport_latency_assumed market_resolved i 1,115 112 36ms 251ms 45.3s 54.6s 0 transport_latency_assumed market_resolved m 1,114 521 6ms 371ms 52.8s 52.9s 0 transport_latency_assumed market_resolved n 1,116 not meas. 64ms 311ms 53.1s 53.1s 0 transport_latency_assumed market_resolved o 1,114 493 6ms 37ms 43.1s 43.2s 0 transport_latency_assumed new_market h 1,102 181 196ms 26.8s 1.3min 3.1min 0 transport_latency_assumed new_market i 1,103 237 101ms 19.6s 2.7min 3.1min 0 transport_latency_assumed new_market m 1,103 670 50ms 16.8s 2.4min 3.1min 0 transport_latency_assumed new_market n 1,103 199 213ms 19.0s 2.4min 3.1min 0 transport_latency_assumed new_market o 1,103 590 61ms 23.2s 2.3min 3.1min 0 transport_latency_assumed price_change h 98,189,147 748,446 19ms 32ms 327ms 1.0min 0 transport_latency_assumed price_change i 98,772,629 545,014 21ms 35ms 275ms 3.7s 0 transport_latency_assumed price_change m 98,659,217 51,565,972 4ms 14ms 102ms 7.6s 0 transport_latency_assumed price_change n 98,339,404 58,505 45ms 75ms 1.0s 19.9s 0 transport_latency_assumed price_change o 98,769,582 46,012,955 5ms 15ms 111ms 8.1s 0 transport_latency_assumed tick_size_change h 2,656 12 19ms 29ms 76ms 6.5s 0 transport_latency_assumed tick_size_change i 2,656 16 21ms 31ms 68ms 676ms 0 transport_latency_assumed tick_size_change m 2,656 1,362 5ms 16ms 40ms 244ms 0 transport_latency_assumed tick_size_change n 2,656 not meas. 44ms 58ms 116ms 249ms 0 transport_latency_assumed tick_size_change o 2,656 1,266 5ms 13ms 50ms 95ms 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-05/23/2026-10-05T23.parquet sha256sum 2026-10-05T23.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.