Hour audit: 2026-10-07T22
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.
1 finding
- the checksum ledger and the manifest disagree on this file's digest. The checksum ledger and this hour's manifest publish DIFFERENT digests for the same file. One of the two is wrong and the file should not be trusted until that is resolved.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-10-07T22 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-10-07T22:00:00.000037699+00:00 · last event 2026-10-07T22:59:59.999848135+00:00
VOLUME 105,001,176 rows · 1,172,850,943 bytes (1.09 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured i: 104,851,972 · m: 104,842,449 · o: 104,825,391 · n: 104,528,037 · h: 104,463,997 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 861,209 (0.82%) · m: 52,282,432 (49.79%) · o: 51,088,793 (48.66%) · n: 59,384 (0.06%) · h: 709,358 (0.68%) (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 105,001,176 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 c82a43edc71825e5ca1f1f69362dadc97c263038aae21ac7bf2b81ba35d4fb38
the corpus checksum ledger names this file with a DIFFERENT digest
joined 105,002,190 to merged 105,001,176, minus 1,014 (minus 0.0010%)
boundary drops 1,014 · 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-09T04:44:37Z 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 7/8 pass, 1 finding
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
FINDING the checksum ledger and the manifest disagree on this file's digest
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,906,344 125,452,611 0-37 b16ea33cac613bf46ba80bc7e4046decf6a7de3a406cf4db10a7ad9b8abfb534 book 195,788 19,834,453 38-38 9ed8b23a0a25520342b307c7082bc7aef68246c452242f1d3d7f8b793dc386be last_trade_price 50,004 2,849,438 39-39 c3c790a0a24800539126e45eedf26e3354d39754f9bd6323c8fe92d70d690725 market_resolved 593 93,135 40-40 9cc1083034408a329b5d5c86ee745c2a775ad17ce8d205f2ab1e21b1cb87c6a3 new_market 3,299 302,318 41-41 4446ff4645cd8349d59792cafc24716b4c7c5ba983f54af1682294130c52f37e price_change 94,842,720 1,023,031,630 42-403 50ff1ad1bebea5fd3ca06dcebcb4e853321131c0133d4a264c17be2238e23df5 tick_size_change 2,428 90,486 404-404 fa84b339854649198482120e3d83b83d3f6d1a6d3ac6f3aa25661cd1fee4424b EVENT MIX count share price_change 94,842,720 90.33% best_bid_ask 9,906,344 9.43% book 195,788 0.19% last_trade_price 50,004 0.05% new_market 3,299 <0.01% tick_size_change 2,428 <0.01% market_resolved 593 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,906,434 9,906,344 90 89 FULL book 195,798 195,788 10 37,824 FULL last_trade_price 50,004 50,004 0 0 FULL market_resolved 593 593 0 0 FULL new_market 3,299 3,299 0 0 FULL price_change 94,843,634 94,842,720 914 87 FULL tick_size_change 2,428 2,428 0 3 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 9,892,823 64,590 18ms 31ms 597ms 2.2min 0 transport_latency_assumed best_bid_ask i 9,904,409 72,231 21ms 31ms 170ms 7.4s 0 transport_latency_assumed best_bid_ask m 9,905,353 4,964,762 4ms 13ms 158ms 44.7s 0 transport_latency_assumed best_bid_ask n 9,901,646 3,984 44ms 65ms 418ms 52.7s 0 transport_latency_assumed best_bid_ask o 9,905,054 4,800,777 4ms 13ms 160ms 12.6s 0 transport_latency_assumed book h 117,526 16,913 25ms 1.1min 1.9d 112.5d 0 book_staleness book i 163,400 60,299 69ms 7.1h 30.5d 131.0d 0 book_staleness book m 106,232 49,365 7ms 78ms 2.0h 112.5d 0 book_staleness book n 111,947 10,617 58ms 6.1s 2.0d 112.5d 0 book_staleness book o 108,306 58,594 7ms 123ms 8.5h 112.5d 0 book_staleness last_trade_price h 48,651 207 20ms 310ms 1.8s 46.7s 0 transport_latency_assumed last_trade_price i 49,738 390 24ms 207ms 1.6s 6.0s 0 transport_latency_assumed last_trade_price m 49,803 23,386 6ms 27ms 246ms 10.9s 0 transport_latency_assumed last_trade_price n 48,789 58 55ms 1.0s 7.0s 52.7s 0 transport_latency_assumed last_trade_price o 49,768 25,963 6ms 27ms 237ms 4.4s 0 transport_latency_assumed market_resolved h 567 21 20ms 77ms 57.0s 58.1s 0 transport_latency_assumed market_resolved i 567 27 24ms 103ms 47.8s 1.1min 0 transport_latency_assumed market_resolved m 567 275 5ms 25ms 50.7s 50.7s 0 transport_latency_assumed market_resolved n 567 10 47ms 199ms 635ms 51.4s 0 transport_latency_assumed market_resolved o 567 260 5ms 22ms 48.0s 48.1s 0 transport_latency_assumed new_market h 1,954 345 181ms 1.7min 4.1min 238.1d 0 transport_latency_assumed new_market i 1,954 492 111ms 1.5min 4.2min 238.1d 0 transport_latency_assumed new_market m 1,954 1,189 64ms 2.3min 4.4min 238.1d 0 transport_latency_assumed new_market n 1,954 349 108ms 1.5min 4.0min 238.1d 0 transport_latency_assumed new_market o 1,954 924 64ms 1.8min 4.2min 238.1d 0 transport_latency_assumed price_change h 94,400,060 627,266 18ms 42ms 906ms 2.2min 0 transport_latency_assumed price_change i 94,729,476 727,766 21ms 40ms 417ms 7.4s 0 transport_latency_assumed price_change m 94,776,112 47,242,284 4ms 15ms 176ms 45.1s 0 transport_latency_assumed price_change n 94,460,706 44,366 44ms 99ms 1.8s 53.2s 0 transport_latency_assumed price_change o 94,757,314 46,201,038 4ms 15ms 177ms 13.0s 0 transport_latency_assumed tick_size_change h 2,416 16 18ms 29ms 987ms 1.0s 0 transport_latency_assumed tick_size_change i 2,428 4 21ms 28ms 71ms 170ms 0 transport_latency_assumed tick_size_change m 2,428 1,171 4ms 9ms 67ms 192ms 0 transport_latency_assumed tick_size_change n 2,428 not meas. 43ms 53ms 120ms 609ms 0 transport_latency_assumed tick_size_change o 2,428 1,237 4ms 9ms 51ms 184ms 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/22/2026-10-07T22.parquet sha256sum 2026-10-07T22.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.