Hour audit: 2026-10-08T19
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-08T19 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-08T19:00:00.000008261+00:00 · last event 2026-10-08T19:59:59.999917961+00:00
VOLUME 115,682,753 rows · 1,318,819,077 bytes (1.23 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured m: 115,404,995 · o: 115,313,809 · h: 115,013,749 · n: 114,997,386 · i: 114,577,706 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 58,458,958 (50.53%) · o: 54,749,292 (47.33%) · h: 1,039,506 (0.90%) · n: 206,640 (0.18%) · i: 1,228,357 (1.06%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 0859efe3e8224ec7ab9e134a1bf46c093b01f0917b83092d0bb24f3e4ffd5e57
the corpus checksum ledger names this file with the same digest
joined 115,684,954 to merged 115,682,753, minus 2,201 (minus 0.0019%)
boundary drops 2,201 · 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-08T21:03:26Z 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,046,579 150,190,111 0-45 a665487ba2cf702afdb6ac865f167d5495c71490afa695a436282dd11e84311c book 227,161 24,083,903 46-46 aa2708eb03113112363f85aa7e4fd243fa3544b4b2830d0aef241e12fc3beb45 last_trade_price 53,186 3,120,873 47-47 ed62006fa5a55651f28c921fdeb0e3cc2297d07c526ee9bdc56dab0ba4906c08 market_resolved 582 96,533 48-48 69a01b58c5244f4e77ba57fed195e7f048dacece802a48a5e8c6ced289962e47 new_market 3,812 370,801 49-49 fa91b8223d6ca309b09b1d55958e59f7cdcd9b4b7d25573cd2fbd3b5260f9c90 price_change 103,349,085 1,139,550,998 50-444 da4d74942a6b9c57234834c0ebe1b05ce184800c6a6d2f8549cd6d11a7512df0 tick_size_change 2,348 88,476 445-445 d23574fc594518905ec3a081d4c29682463699b483a5c40252bfc7977108bb05 EVENT MIX count share price_change 103,349,085 89.34% best_bid_ask 12,046,579 10.41% book 227,161 0.20% last_trade_price 53,186 0.05% new_market 3,812 <0.01% tick_size_change 2,348 <0.01% market_resolved 582 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,046,822 12,046,579 243 165 FULL book 227,187 227,161 26 47,871 FULL last_trade_price 53,186 53,186 0 0 FULL market_resolved 582 582 0 0 FULL new_market 3,812 3,812 0 0 FULL price_change 103,351,017 103,349,085 1,932 150 FULL tick_size_change 2,348 2,348 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 12,030,711 92,606 19ms 45ms 1.1s 1.8min 0 transport_latency_assumed best_bid_ask i 12,021,119 115,355 22ms 36ms 292ms 18.8s 0 transport_latency_assumed best_bid_ask m 12,042,266 6,099,319 5ms 17ms 196ms 10.9s 0 transport_latency_assumed best_bid_ask n 12,037,732 10,219 45ms 75ms 570ms 23.3s 0 transport_latency_assumed best_bid_ask o 12,039,004 5,729,080 5ms 19ms 260ms 27.5s 0 transport_latency_assumed book h 133,795 24,615 34ms 25.3min 18.2d 113.3d 0 book_staleness book i 145,901 38,079 54ms 2.2h 29.5d 131.9d 0 book_staleness book m 123,698 69,388 8ms 6.0s 15.6h 113.4d 0 book_staleness book n 139,252 31,557 119ms 1.5h 29.4d 131.9d 0 book_staleness book o 125,169 63,522 9ms 58.9s 15.7h 131.9d 0 book_staleness last_trade_price h 52,235 575 22ms 283ms 2.9s 1.1min 0 transport_latency_assumed last_trade_price i 51,748 462 27ms 436ms 3.5s 18.7s 0 transport_latency_assumed last_trade_price m 52,938 27,845 7ms 36ms 312ms 8.9s 0 transport_latency_assumed last_trade_price n 51,299 137 63ms 1.2s 9.6s 21.8s 0 transport_latency_assumed last_trade_price o 52,679 24,167 7ms 49ms 432ms 24.3s 0 transport_latency_assumed market_resolved h 564 19 22ms 98ms 40.0s 44.1s 0 transport_latency_assumed market_resolved i 564 39 23ms 140ms 51.1s 51.2s 0 transport_latency_assumed market_resolved m 564 276 6ms 61ms 53.5s 2.4min 0 transport_latency_assumed market_resolved n 564 3 48ms 262ms 31.8s 59.9s 0 transport_latency_assumed market_resolved o 564 245 6ms 117ms 52.6s 52.6s 0 transport_latency_assumed new_market h 2,307 362 258ms 32.7s 40.1s 1.7min 0 transport_latency_assumed new_market i 2,307 553 174ms 16.3s 40.4s 1.7min 0 transport_latency_assumed new_market m 2,307 1,427 90ms 32.1s 38.5s 1.6min 0 transport_latency_assumed new_market n 2,307 528 171ms 12.2s 40.5s 1.8min 0 transport_latency_assumed new_market o 2,307 942 162ms 32.8s 42.5s 1.5min 0 transport_latency_assumed price_change h 102,791,789 921,305 19ms 67ms 1.8s 2.0min 0 transport_latency_assumed price_change i 102,353,719 1,073,826 22ms 61ms 1.8s 18.8s 0 transport_latency_assumed price_change m 103,180,874 52,259,498 6ms 21ms 227ms 11.2s 0 transport_latency_assumed price_change n 102,763,884 164,188 46ms 151ms 3.1s 23.6s 0 transport_latency_assumed price_change o 103,091,738 48,930,268 6ms 24ms 306ms 29.1s 0 transport_latency_assumed tick_size_change h 2,348 24 20ms 57ms 424ms 34.2s 0 transport_latency_assumed tick_size_change i 2,348 43 22ms 39ms 144ms 360ms 0 transport_latency_assumed tick_size_change m 2,348 1,205 6ms 16ms 173ms 250ms 0 transport_latency_assumed tick_size_change n 2,348 8 45ms 76ms 235ms 488ms 0 transport_latency_assumed tick_size_change o 2,348 1,068 6ms 24ms 240ms 559ms 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/19/2026-10-08T19.parquet sha256sum 2026-10-08T19.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.