Hour audit: 2026-10-06T09
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-06T09 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-06T09:00:00.000013959+00:00 · last event 2026-10-06T09:59:59.999929236+00:00
VOLUME 108,110,999 rows · 1,213,871,227 bytes (1.13 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured i: 107,799,404 · o: 107,788,612 · h: 107,780,599 · m: 107,746,504 · n: 107,370,454 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 472,297 (0.44%) · o: 47,050,871 (43.52%) · h: 615,137 (0.57%) · m: 59,801,436 (55.31%) · n: 171,258 (0.16%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 108,110,999 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 a66b9adec2a955870b45abbbabcfd54e12260e9f6dc3984f89d4af6ae36bcfe0
the corpus checksum ledger names this file with the same digest
joined 108,115,853 to merged 108,110,999, minus 4,854 (minus 0.0045%)
boundary drops 4,854 · 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-06T11:01:38Z 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 10,999,276 135,123,917 0-41 95779d798b6bfb67de162ca968f6b1fe892de00a5572d67ac604e0dd9ec55348 book 415,711 39,784,138 42-43 80b037a44fa2e8a13a88c65d0fd65760d9f8c52f93a4ab2ac62b0de6f5ea8ff6 last_trade_price 50,030 2,899,258 44-44 63b4b9ff01fe925c2f1c25a5589af12346cfa012f16b5f1d8dbe60494107c8c3 market_resolved 758 113,305 45-45 c9eb9ee421b20c425dc8c225182239a1bd9ef4c440ad6b1710e34d05e59621de new_market 838 86,589 46-46 cbce3d513f996ce5ff97505456730f0fd5532ee34a9d3c68f37e0f9455bb7669 price_change 96,640,526 1,034,491,634 47-415 74ea4c059b4618adcb328adf287e2eb78554eb3616491aed25270aee2cbecaff tick_size_change 3,860 140,292 416-416 85238622f4e55ded72f5d4e869559b0dceee43e72de5a3bc1886425980d8a781 EVENT MIX count share price_change 96,640,526 89.39% best_bid_ask 10,999,276 10.17% book 415,711 0.38% last_trade_price 50,030 0.05% tick_size_change 3,860 <0.01% new_market 838 <0.01% market_resolved 758 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,999,380 10,999,276 104 114 FULL book 419,619 415,711 3,908 134,127 FULL last_trade_price 50,030 50,030 0 7 FULL market_resolved 758 758 0 20 FULL new_market 838 838 0 0 FULL price_change 96,641,368 96,640,526 842 122 FULL tick_size_change 3,860 3,860 0 3 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,997,996 53,076 18ms 26ms 136ms 22.5s 0 transport_latency_assumed best_bid_ask i 10,996,464 35,581 21ms 28ms 124ms 6.0s 0 transport_latency_assumed best_bid_ask m 10,996,971 6,173,442 4ms 11ms 66ms 4.6s 0 transport_latency_assumed best_bid_ask n 10,972,341 1,992 43ms 53ms 191ms 11.8s 0 transport_latency_assumed best_bid_ask o 10,998,118 4,735,185 5ms 12ms 75ms 14.8s 0 transport_latency_assumed book h 127,846 21,389 26ms 1.1h 27.0d 111.0d 0 book_staleness book i 222,298 100,762 18.6s 14.1h 41.6d 129.5d 0 book_staleness book m 135,368 78,788 8ms 2.6h 28.9d 129.5d 0 book_staleness book n 253,214 147,424 1.3min 18.4h 44.8d 129.5d 0 book_staleness book o 129,702 67,348 8ms 1.5h 27.0d 111.0d 0 book_staleness last_trade_price h 49,772 444 20ms 82ms 839ms 7.6s 0 transport_latency_assumed last_trade_price i 49,749 172 25ms 170ms 1.4s 4.0s 0 transport_latency_assumed last_trade_price m 49,684 26,674 6ms 21ms 203ms 1.4s 0 transport_latency_assumed last_trade_price n 48,512 28 47ms 480ms 5.2s 11.8s 0 transport_latency_assumed last_trade_price o 49,861 22,712 6ms 22ms 209ms 1.6s 0 transport_latency_assumed market_resolved h 691 7 20ms 57ms 51.8s 54.4s 0 transport_latency_assumed market_resolved i 691 50 23ms 87ms 50.1s 53.3s 0 transport_latency_assumed market_resolved m 691 348 5ms 22ms 54.8s 58.1s 0 transport_latency_assumed market_resolved n 711 20 45ms 125ms 5.1min 6.1min 0 transport_latency_assumed market_resolved o 691 333 5ms 11ms 97ms 33.1s 0 transport_latency_assumed new_market h 554 132 116ms 26.3s 58.6s 1.6min 0 transport_latency_assumed new_market i 554 104 94ms 29.2s 1.2min 1.7min 0 transport_latency_assumed new_market m 554 363 40ms 18.6s 1.2min 1.6min 0 transport_latency_assumed new_market n 554 44 191ms 16.4s 59.4s 1.5min 0 transport_latency_assumed new_market o 554 195 49ms 493ms 53.6s 1.2min 0 transport_latency_assumed price_change h 96,599,880 540,058 18ms 31ms 248ms 26.6s 0 transport_latency_assumed price_change i 96,525,788 335,628 21ms 35ms 426ms 6.2s 0 transport_latency_assumed price_change m 96,559,376 53,519,834 5ms 13ms 80ms 4.7s 0 transport_latency_assumed price_change n 96,091,274 21,750 44ms 68ms 1.2s 11.8s 0 transport_latency_assumed price_change o 96,605,826 42,223,256 5ms 13ms 89ms 14.8s 0 transport_latency_assumed tick_size_change h 3,860 31 19ms 27ms 104ms 283ms 0 transport_latency_assumed tick_size_change i 3,860 not meas. 22ms 45ms 99ms 573ms 0 transport_latency_assumed tick_size_change m 3,860 1,987 5ms 14ms 67ms 1.5s 0 transport_latency_assumed tick_size_change n 3,848 not meas. 44ms 54ms 135ms 2.7s 0 transport_latency_assumed tick_size_change o 3,860 1,842 5ms 12ms 55ms 239ms 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/09/2026-10-06T09.parquet sha256sum 2026-10-06T09.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.