Hour audit: 2026-10-09T09
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 does not name this file. No line in the corpus checksum ledger names this file, so the documented verification step passes over it in silence rather than checking it. The manifest below still carries the digest.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-10-09T09 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-10-09T09:00:00.000014348+00:00 · last event 2026-10-09T09:59:59.999996891+00:00
VOLUME 116,333,228 rows · 1,385,684,745 bytes (1.29 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured i: 115,417,814 · o: 115,343,486 · h: 115,317,522 · n: 115,172,751 · m: 110,644,572 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 967,867 (0.83%) · o: 59,318,884 (50.99%) · h: 1,273,827 (1.09%) · n: 232,183 (0.20%) · m: 54,540,467 (46.88%) (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 116,333,228 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 91d8dabe67ab7575c2a632f4f1dd732eafa79c2736745d46d794e58ab055bd99
no line in the corpus checksum ledger names this file
joined 116,335,280 to merged 116,333,228, minus 2,052 (minus 0.0018%)
boundary drops 2,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-10T01:26:07Z 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 does not name 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,113,004 154,632,502 0-46 3940dedd962a29007b7c6a2f3d4bc5c7753b7d4231db5fba4ffbd4e915046e56 book 1,290,850 95,480,545 47-51 bcfc6d7215f6522242ca4994439d6b920d1204733e0f8df135fdb393486329cf last_trade_price 48,801 2,896,325 52-52 5d9ce3c6f4eb4ad46ef0b417fe56ea7c72c3e6ce6196c5ea10be45b55c1f5632 market_resolved 659 103,580 53-53 bf2c766af6d92a22c3ad319fc0f5d6e871a9db65b50c40bd8e3e264bb9b297d4 new_market 886 83,786 54-54 8edec5d03483b2782875ee8adc86e5380bba13fe8a66ff70d3ec88767e1a8da9 price_change 102,875,156 1,131,019,142 55-447 6eddd51ac9a3ac6f8ce052142c7bca24c3ddc94e22cea7fac046f3654f0620e1 tick_size_change 3,872 142,433 448-448 80cb5c27aee5a0d2dde7436fb742fb5b88cad34fba4738e9ab0ce1b7b2044329 EVENT MIX count share price_change 102,875,156 88.43% best_bid_ask 12,113,004 10.41% book 1,290,850 1.11% last_trade_price 48,801 0.04% tick_size_change 3,872 <0.01% new_market 886 <0.01% market_resolved 659 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,113,128 12,113,004 124 1,854 FULL book 1,291,910 1,290,850 1,060 263,483 FULL last_trade_price 48,801 48,801 0 78 FULL market_resolved 659 659 0 0 FULL new_market 886 886 0 0 FULL price_change 102,876,024 102,875,156 868 2,074 FULL tick_size_change 3,872 3,872 0 41 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 12,109,517 102,913 18ms 29ms 244ms 50.7s 0 transport_latency_assumed best_bid_ask i 12,108,958 66,979 21ms 29ms 175ms 8.0s 0 transport_latency_assumed best_bid_ask m 11,567,018 5,747,536 5ms 14ms 158ms 7.1s 0 transport_latency_assumed best_bid_ask n 12,109,801 8,280 44ms 58ms 291ms 13.5s 0 transport_latency_assumed best_bid_ask o 12,110,575 6,187,296 5ms 14ms 144ms 6.7s 0 transport_latency_assumed book h 353,905 160,895 3.5min 1.2d 47.8d 132.5d 0 book_staleness book i 539,516 251,666 6.0min 1.2d 47.8d 132.5d 0 book_staleness book m 816,970 550,318 6.7min 1.2d 47.8d 132.5d 0 book_staleness book n 273,349 109,314 1.7min 1.1d 47.8d 132.5d 0 book_staleness book o 372,630 218,657 3.9min 1.2d 47.8d 132.5d 0 book_staleness last_trade_price h 48,507 504 20ms 75ms 1.0s 34.5s 0 transport_latency_assumed last_trade_price i 48,493 239 23ms 144ms 1.2s 8.0s 0 transport_latency_assumed last_trade_price m 46,491 21,252 6ms 21ms 219ms 1.8s 0 transport_latency_assumed last_trade_price n 48,284 56 47ms 274ms 3.4s 13.4s 0 transport_latency_assumed last_trade_price o 48,600 26,750 6ms 21ms 245ms 2.4s 0 transport_latency_assumed market_resolved h 628 7 21ms 97ms 52.1s 57.2s 0 transport_latency_assumed market_resolved i 628 34 23ms 119ms 41.8s 45.2s 0 transport_latency_assumed market_resolved m 640 320 6ms 96ms 6.7min 6.7min 0 transport_latency_assumed market_resolved n 628 1 50ms 218ms 53.6s 57.2s 0 transport_latency_assumed market_resolved o 628 297 5ms 22ms 47.5s 51.1s 0 transport_latency_assumed new_market h 535 80 173ms 36.0s 1.1min 358.5d 0 transport_latency_assumed new_market i 535 185 113ms 33.4s 1.0min 358.5d 0 transport_latency_assumed new_market m 543 282 78ms 36.1s 6.6min 358.5d 0 transport_latency_assumed new_market n 535 140 220ms 36.2s 1.0min 358.5d 0 transport_latency_assumed new_market o 535 199 70ms 33.3s 58.9s 358.5d 0 transport_latency_assumed price_change h 102,800,558 1,009,396 18ms 35ms 572ms 51.3s 0 transport_latency_assumed price_change i 102,715,812 648,752 21ms 38ms 615ms 8.0s 0 transport_latency_assumed price_change m 98,209,202 48,219,004 5ms 16ms 255ms 7.2s 0 transport_latency_assumed price_change n 102,736,282 114,392 45ms 72ms 1.3s 13.5s 0 transport_latency_assumed price_change o 102,806,646 52,883,612 5ms 16ms 240ms 6.8s 0 transport_latency_assumed tick_size_change h 3,872 32 18ms 30ms 74ms 208ms 0 transport_latency_assumed tick_size_change i 3,872 12 21ms 33ms 106ms 271ms 0 transport_latency_assumed tick_size_change m 3,708 1,755 5ms 15ms 56ms 162ms 0 transport_latency_assumed tick_size_change n 3,872 not meas. 44ms 55ms 128ms 2.1s 0 transport_latency_assumed tick_size_change o 3,872 2,073 5ms 14ms 56ms 301ms 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-09/09/2026-10-09T09.parquet sha256sum 2026-10-09T09.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.