Hour audit: 2026-10-06T12
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-06T12 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-06T12:00:00.000075717+00:00 · last event 2026-10-06T12:59:59.999951483+00:00
VOLUME 115,541,854 rows · 1,302,811,450 bytes (1.21 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured m: 115,396,576 · h: 115,384,371 · o: 115,379,673 · i: 115,366,084 · n: 115,268,796 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 56,200,846 (48.64%) · h: 798,817 (0.69%) · o: 57,831,469 (50.05%) · i: 644,146 (0.56%) · n: 66,576 (0.06%) (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 115,541,854 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 93859e3d9ae7b79000782ac95ca7582b951b82e78fa94fc95c09707437637222
the corpus checksum ledger names this file with the same digest
joined 115,543,116 to merged 115,541,854, minus 1,262 (minus 0.0011%)
boundary drops 1,262 · 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-06T14:04:18Z 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 11,090,433 139,940,023 0-42 f92cea7cfb9a5a9416071f3ea05b8cf98ddd0950300a1619475659a6a041786d book 231,372 24,109,610 43-43 e10082180a6c15a8db0eac7e61fbfb357072e0ae3659fb4a80d3bde3c4f8352d last_trade_price 55,915 3,237,046 44-44 9ff9c4c4d53a5abac973c03af95dd77ca1f4f3ce02775c4e7ea2a5de94c998cf market_resolved 936 151,509 45-45 32907976736450460ba4e4b09762a749f8183dae3dea3e0afa245a3776202112 new_market 1,166 114,708 46-46 ac981f89a5b7e518d422dda65f42d7282b5571536a09b612bbffca451186fe9a price_change 104,157,436 1,133,774,804 47-444 76c10804c09d96ac791912ef69e1aa9852245cbd97d341e65462d5b41d3c443f tick_size_change 4,596 166,019 445-445 8dc90e693dd5a015373fbadc1e8bc19a73dc48e57dba4c39131ce45fb75f6ecd EVENT MIX count share price_change 104,157,436 90.15% best_bid_ask 11,090,433 9.60% book 231,372 0.20% last_trade_price 55,915 0.05% tick_size_change 4,596 <0.01% new_market 1,166 <0.01% market_resolved 936 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,090,519 11,090,433 86 91 FULL book 231,372 231,372 0 53,359 FULL last_trade_price 55,915 55,915 0 1 FULL market_resolved 936 936 0 0 FULL new_market 1,166 1,166 0 0 FULL price_change 104,158,612 104,157,436 1,176 115 FULL tick_size_change 4,596 4,596 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 11,088,890 67,844 18ms 29ms 253ms 28.0s 0 transport_latency_assumed best_bid_ask i 11,087,112 52,457 21ms 30ms 142ms 6.7s 0 transport_latency_assumed best_bid_ask m 11,089,213 5,360,333 5ms 13ms 88ms 5.3s 0 transport_latency_assumed best_bid_ask n 11,087,708 3,220 44ms 57ms 264ms 8.2s 0 transport_latency_assumed best_bid_ask o 11,088,995 5,606,579 5ms 13ms 95ms 5.3s 0 transport_latency_assumed book h 124,352 11,743 25ms 843ms 2.9d 111.1d 0 book_staleness book i 160,045 47,059 35ms 4.9h 29.1d 129.6d 0 book_staleness book m 131,150 72,205 8ms 2.7min 9.5d 129.6d 0 book_staleness book n 139,755 26,395 55ms 42.4min 26.1d 129.6d 0 book_staleness book o 132,286 73,970 8ms 5.2min 7.6d 111.1d 0 book_staleness last_trade_price h 55,802 460 21ms 103ms 622ms 21.0s 0 transport_latency_assumed last_trade_price i 55,564 320 25ms 138ms 1.4s 3.9s 0 transport_latency_assumed last_trade_price m 55,824 27,720 6ms 24ms 237ms 1.5s 0 transport_latency_assumed last_trade_price n 55,612 49 49ms 709ms 5.6s 8.2s 0 transport_latency_assumed last_trade_price o 55,785 27,366 6ms 27ms 260ms 3.2s 0 transport_latency_assumed market_resolved h 911 2 21ms 210ms 52.6s 52.6s 0 transport_latency_assumed market_resolved i 911 92 22ms 236ms 44.6s 55.9s 0 transport_latency_assumed market_resolved m 911 391 6ms 67ms 48.0s 53.6s 0 transport_latency_assumed market_resolved n 911 10 46ms 195ms 50.3s 50.4s 0 transport_latency_assumed market_resolved o 911 441 6ms 30ms 48.9s 56.8s 0 transport_latency_assumed new_market h 728 95 167ms 16.0s 49.9s 1.6min 0 transport_latency_assumed new_market i 728 208 127ms 13.6s 25.5s 1.5min 0 transport_latency_assumed new_market m 728 445 54ms 15.3s 44.1s 1.6min 0 transport_latency_assumed new_market n 728 84 228ms 15.7s 50.8s 1.8min 0 transport_latency_assumed new_market o 728 334 81ms 17.0s 27.6s 1.8min 0 transport_latency_assumed price_change h 104,109,092 718,628 19ms 34ms 385ms 28.5s 0 transport_latency_assumed price_change i 104,057,128 543,992 21ms 37ms 409ms 7.5s 0 transport_latency_assumed price_change m 104,114,154 50,737,378 5ms 15ms 108ms 5.5s 0 transport_latency_assumed price_change n 103,979,486 36,818 44ms 76ms 1.4s 8.2s 0 transport_latency_assumed price_change o 104,096,372 52,120,620 5ms 15ms 121ms 5.7s 0 transport_latency_assumed tick_size_change h 4,596 45 18ms 27ms 133ms 11.3s 0 transport_latency_assumed tick_size_change i 4,596 18 21ms 39ms 123ms 309ms 0 transport_latency_assumed tick_size_change m 4,596 2,374 5ms 12ms 46ms 153ms 0 transport_latency_assumed tick_size_change n 4,596 not meas. 44ms 55ms 123ms 2.5s 0 transport_latency_assumed tick_size_change o 4,596 2,159 5ms 14ms 48ms 1.8s 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-06/12/2026-10-06T12.parquet sha256sum 2026-10-06T12.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.