Hour audit: 2026-10-08T16
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-08T16 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-08T16:00:00.000027832+00:00 · last event 2026-10-08T16:59:59.999865127+00:00
VOLUME 131,144,683 rows · 1,531,502,656 bytes (1.43 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 130,975,459 · m: 130,974,860 · i: 130,935,643 · h: 130,922,499 · n: 130,405,424 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 63,125,857 (48.13%) · m: 63,937,588 (48.75%) · i: 1,621,775 (1.24%) · h: 2,340,609 (1.78%) · n: 118,854 (0.09%) (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 131,144,683 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 fd38129a3636ae4bcbb3abf20ee232e9b1ae0a1e0ee09134c74f39072c4bb7aa
the corpus checksum ledger names this file with the same digest
joined 131,158,533 to merged 131,144,683, minus 13,850 (minus 0.0106%)
boundary drops 13,850 · 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-08T18:07:32Z 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,826,786 164,689,126 0-48 a44c670fd70407df9c3debc0e2fe4a30f340fa003b8ebc74e57d3775ccc60eb2 book 273,692 29,932,473 49-50 8800bcdb5f65de45fd37d52318f76b61c08ad9a6b0566c80713cfa8e99c3a17c last_trade_price 72,713 4,165,705 51-51 2ed5e36e55e6b3fb5eae39812295b8e5dfb0955b6fa840b164d96fe9ce154770 market_resolved 871 139,068 52-52 4389a0558e84e753e913948c63f4774873fd2078049c420afba1dfa764c62e8b new_market 1,823 171,282 53-53 14a65d6625173c8d9b8dc148f7d4ce08d7fef70a1f9bccafbb8f18a15c109776 price_change 117,965,742 1,330,798,982 54-504 03f17dba99c1f723cb666b85e70bc12bccc0cb7f1e086ff7feda3341501d559c tick_size_change 3,056 111,827 505-505 f8c37468ad40895c34e18835ad147977bdd02e397dc4e07eccfaf2604077a1c2 EVENT MIX count share price_change 117,965,742 89.95% best_bid_ask 12,826,786 9.78% book 273,692 0.21% last_trade_price 72,713 0.06% tick_size_change 3,056 <0.01% new_market 1,823 <0.01% market_resolved 871 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,827,727 12,826,786 941 93 FULL book 273,898 273,692 206 54,421 FULL last_trade_price 72,714 72,713 1 2 FULL market_resolved 871 871 0 2 FULL new_market 1,823 1,823 0 2 FULL price_change 117,978,444 117,965,742 12,702 88 FULL tick_size_change 3,056 3,056 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 12,825,027 210,646 20ms 45ms 300ms 57.5s 0 transport_latency_assumed best_bid_ask i 12,823,864 147,081 22ms 44ms 153ms 3.8s 0 transport_latency_assumed best_bid_ask m 12,825,240 6,273,857 6ms 26ms 120ms 7.9s 0 transport_latency_assumed best_bid_ask n 12,816,659 7,050 46ms 79ms 327ms 25.9s 0 transport_latency_assumed best_bid_ask o 12,825,019 6,188,152 6ms 27ms 132ms 17.2s 0 transport_latency_assumed book h 159,903 14,716 28ms 511ms 12.5h 131.8d 0 book_staleness book i 166,878 22,314 29ms 1.2min 2.9d 113.2d 0 book_staleness book m 179,576 101,108 11ms 18.3min 18.7d 113.3d 0 book_staleness book n 182,141 38,448 83ms 1.0h 26.1d 131.8d 0 book_staleness book o 175,132 97,106 11ms 8.0min 15.9d 113.3d 0 book_staleness last_trade_price h 72,481 1,441 23ms 101ms 622ms 41.6s 0 transport_latency_assumed last_trade_price i 72,307 874 27ms 147ms 1.1s 3.8s 0 transport_latency_assumed last_trade_price m 72,552 35,179 8ms 38ms 183ms 1.7s 0 transport_latency_assumed last_trade_price n 70,318 54 61ms 1.6s 9.4s 25.9s 0 transport_latency_assumed last_trade_price o 72,496 35,165 8ms 40ms 196ms 4.8s 0 transport_latency_assumed market_resolved h 857 8 23ms 103ms 26.2s 50.8s 0 transport_latency_assumed market_resolved i 857 47 25ms 132ms 32.7s 52.2s 0 transport_latency_assumed market_resolved m 855 408 7ms 38ms 19.1s 52.1s 0 transport_latency_assumed market_resolved n 857 2 51ms 261ms 33.9s 35.2s 0 transport_latency_assumed market_resolved o 857 406 8ms 36ms 33.7s 53.2s 0 transport_latency_assumed new_market h 1,067 266 153ms 32.0s 49.9s 1.6min 0 transport_latency_assumed new_market i 1,069 419 109ms 30.9s 38.7s 64.2d 0 transport_latency_assumed new_market m 1,069 570 56ms 33.0s 38.8s 64.2d 0 transport_latency_assumed new_market n 1,069 240 87ms 33.2s 51.1s 64.2d 0 transport_latency_assumed new_market o 1,069 328 100ms 32.4s 40.1s 64.2d 0 transport_latency_assumed price_change h 117,860,108 2,113,510 21ms 55ms 426ms 58.3s 0 transport_latency_assumed price_change i 117,867,612 1,451,032 23ms 56ms 354ms 3.8s 0 transport_latency_assumed price_change m 117,892,512 57,524,836 7ms 29ms 133ms 7.9s 0 transport_latency_assumed price_change n 117,331,324 73,060 47ms 116ms 3.4s 25.9s 0 transport_latency_assumed price_change o 117,897,830 56,803,304 7ms 30ms 148ms 17.2s 0 transport_latency_assumed tick_size_change h 3,056 22 20ms 38ms 235ms 7.2s 0 transport_latency_assumed tick_size_change i 3,056 8 22ms 40ms 87ms 342ms 0 transport_latency_assumed tick_size_change m 3,056 1,630 6ms 15ms 55ms 146ms 0 transport_latency_assumed tick_size_change n 3,056 not meas. 45ms 69ms 124ms 845ms 0 transport_latency_assumed tick_size_change o 3,056 1,396 6ms 16ms 56ms 170ms 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/16/2026-10-08T16.parquet sha256sum 2026-10-08T16.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.