Hour audit: 2026-10-08T14
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-08T14 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-08T14:00:00.000372643+00:00 · last event 2026-10-08T14:59:59.999972907+00:00
VOLUME 124,864,053 rows · 1,438,847,833 bytes (1.34 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured m: 124,774,906 · o: 124,771,186 · h: 124,765,090 · i: 124,623,889 · n: 124,294,879 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 65,902,930 (52.78%) · o: 56,271,168 (45.07%) · h: 1,679,729 (1.35%) · i: 944,063 (0.76%) · n: 66,163 (0.05%) (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 124,864,053 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 969c7b8118ed60199d7b09902e62466a0e95de3e73b9ac315726f7be10971ad3
the corpus checksum ledger names this file with the same digest
joined 124,867,727 to merged 124,864,053, minus 3,674 (minus 0.0029%)
boundary drops 3,674 · 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-08T16:07:04Z 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,136,417 151,790,852 0-46 a09e5dd7b190103c73bd37290a11b79b91e742765f705529a786cedbe8227d79 book 165,549 19,077,599 47-47 034fa7415b91a29a7ca6e4ea11987dbdf5f8b50ef06c5c70a22cd0782b5065a6 last_trade_price 61,332 3,568,193 48-48 c358139e407812451749240f0380c548dd493a33abdb53474b2474b1a184589b market_resolved 667 97,476 49-49 b42d0595fe180e5696eccbb2cad20763b4691fa97d41ca2db70b97abf896636b new_market 920 93,686 50-50 d62c600f1083c2d81c1b374cddb3c18bcb1b6f669bc3c19e10f9b09106a6f2d1 price_change 112,496,292 1,262,689,184 51-480 b65ab28029acd57d26dc3b99706f360cb885cc1f66a380040a3eb1cab9739737 tick_size_change 2,876 107,168 481-481 9901f0fa5a978d4504494e466b2214389f1e64d77d2d405abb5ad4abe1dbc344 EVENT MIX count share price_change 112,496,292 90.10% best_bid_ask 12,136,417 9.72% book 165,549 0.13% last_trade_price 61,332 0.05% tick_size_change 2,876 <0.01% new_market 920 <0.01% market_resolved 667 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,136,629 12,136,417 212 44 FULL book 165,587 165,549 38 16,766 FULL last_trade_price 61,332 61,332 0 2 FULL market_resolved 667 667 0 0 FULL new_market 920 920 0 0 FULL price_change 112,499,716 112,496,292 3,424 67 FULL tick_size_change 2,876 2,876 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 12,135,159 142,032 19ms 36ms 203ms 50.0s 0 transport_latency_assumed best_bid_ask i 12,131,457 84,915 22ms 38ms 151ms 7.8s 0 transport_latency_assumed best_bid_ask m 12,135,488 6,289,009 6ms 20ms 101ms 5.0s 0 transport_latency_assumed best_bid_ask n 12,129,500 4,516 45ms 72ms 281ms 24.4s 0 transport_latency_assumed best_bid_ask o 12,135,428 5,615,945 6ms 20ms 110ms 23.2s 0 transport_latency_assumed book h 135,413 13,836 25ms 867ms 10.6h 130.1d 0 book_staleness book i 127,252 5,690 27ms 552ms 2.7h 113.1d 0 book_staleness book m 131,163 73,995 8ms 75ms 10.4h 113.2d 0 book_staleness book n 128,012 8,366 58ms 4.6s 10.3h 113.2d 0 book_staleness book o 133,122 63,662 9ms 109ms 10.5h 113.2d 0 book_staleness last_trade_price h 61,187 963 22ms 111ms 841ms 30.4s 0 transport_latency_assumed last_trade_price i 60,751 342 27ms 330ms 2.2s 7.7s 0 transport_latency_assumed last_trade_price m 61,212 32,815 7ms 32ms 191ms 1.6s 0 transport_latency_assumed last_trade_price n 59,422 35 58ms 1.8s 8.4s 24.4s 0 transport_latency_assumed last_trade_price o 61,147 27,177 7ms 34ms 198ms 3.1s 0 transport_latency_assumed market_resolved h 582 43 20ms 86ms 56.1s 56.1s 0 transport_latency_assumed market_resolved i 582 89 25ms 45.0s 53.3s 56.6s 0 transport_latency_assumed market_resolved m 582 270 7ms 45.0s 55.4s 56.6s 0 transport_latency_assumed market_resolved n 582 37 47ms 124ms 362ms 44.6s 0 transport_latency_assumed market_resolved o 582 228 7ms 43.1s 53.8s 54.9s 0 transport_latency_assumed new_market h 583 106 151ms 12.6s 49.7s 1.6min 0 transport_latency_assumed new_market i 583 139 92ms 20.8s 32.9s 55.9d 0 transport_latency_assumed new_market m 583 310 44ms 12.8s 53.1s 55.9d 0 transport_latency_assumed new_market n 583 167 78ms 21.0s 42.6s 1.5min 0 transport_latency_assumed new_market o 583 198 79ms 10.7s 53.2s 55.9d 0 transport_latency_assumed price_change h 112,429,290 1,522,730 20ms 46ms 387ms 50.7s 0 transport_latency_assumed price_change i 112,300,388 852,866 22ms 54ms 641ms 7.8s 0 transport_latency_assumed price_change m 112,443,002 59,504,960 6ms 23ms 121ms 6.2s 0 transport_latency_assumed price_change n 111,973,904 53,042 46ms 109ms 3.4s 25.1s 0 transport_latency_assumed price_change o 112,437,448 50,562,694 6ms 24ms 129ms 24.2s 0 transport_latency_assumed tick_size_change h 2,876 19 19ms 35ms 85ms 223ms 0 transport_latency_assumed tick_size_change i 2,876 22 22ms 40ms 96ms 373ms 0 transport_latency_assumed tick_size_change m 2,876 1,571 6ms 18ms 105ms 152ms 0 transport_latency_assumed tick_size_change n 2,876 not meas. 45ms 73ms 149ms 580ms 0 transport_latency_assumed tick_size_change o 2,876 1,264 6ms 20ms 80ms 188ms 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/14/2026-10-08T14.parquet sha256sum 2026-10-08T14.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.