Hour audit: 2026-10-06T00
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-06T00 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-06T00:00:00.000009756+00:00 · last event 2026-10-06T00:59:59.999842530+00:00
VOLUME 120,421,395 rows · 1,403,073,731 bytes (1.31 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured m: 119,610,340 · o: 119,582,471 · n: 119,565,496 · i: 119,454,939 · h: 111,102,030 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 60,756,963 (50.45%) · o: 56,278,314 (46.73%) · n: 150,021 (0.12%) · i: 1,287,168 (1.07%) · h: 1,948,929 (1.62%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 b0dc77a19e384dbab91fd6c0c9e1fc995ed922e6b012d62a131031d17a75184b
the corpus checksum ledger names this file with the same digest
joined 120,423,641 to merged 120,421,395, minus 2,246 (minus 0.0019%)
boundary drops 2,246 · 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-06T02:18:53Z 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,416,311 144,817,050 0-43 c7c474173fb3876257e9ba3051741a0e137a957fedd921c64e57a1eead79132a book 695,495 65,918,882 44-46 27ad1fc7793ac0c5cb2cfd5db9450db9992fe7daac5785a9a1270617cea70286 last_trade_price 56,874 3,299,807 47-47 1c236d493f3b7e0ff0d3ed0fbd482bde3158f8d6c98fb0dd3f880bd567ecfb63 market_resolved 1,461 222,694 48-48 d55f2959b119c9b2a5c9ba9c3c9d37db50c3843b582f8096b6fded97849c773d new_market 9,904 905,594 49-49 d00763d7416de5ad680b043ed19ac49aab421aae3354b890ab015f6763494e07 price_change 108,237,118 1,186,381,632 50-462 7f1b7f8dd508b83334bbb90363ec76ee6b33f5571713fff7c17d072b0f16d3e2 tick_size_change 4,232 157,778 463-463 faac64bd0ed4edaffcd75697041fb1c689d77541daccf9605ef3295a9408d589 EVENT MIX count share price_change 108,237,118 89.88% best_bid_ask 11,416,311 9.48% book 695,495 0.58% last_trade_price 56,874 0.05% new_market 9,904 <0.01% tick_size_change 4,232 <0.01% market_resolved 1,461 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,416,514 11,416,311 203 1,721 FULL book 695,625 695,495 130 244,208 FULL last_trade_price 56,876 56,874 2 268 FULL market_resolved 1,461 1,461 0 10 FULL new_market 9,905 9,904 1 10 FULL price_change 108,239,028 108,237,118 1,910 2,872 FULL tick_size_change 4,232 4,232 0 91 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,556,793 111,289 19ms 41ms 655ms 41.4s 0 transport_latency_assumed best_bid_ask i 11,411,322 114,210 21ms 40ms 227ms 8.6s 0 transport_latency_assumed best_bid_ask m 11,415,481 5,896,960 5ms 19ms 166ms 5.6s 0 transport_latency_assumed best_bid_ask n 11,414,269 11,251 45ms 82ms 318ms 17.6s 0 transport_latency_assumed best_bid_ask o 11,410,953 5,282,601 5ms 20ms 176ms 6.3s 0 transport_latency_assumed book h 669,501 555,963 16.8min 1.5d 44.4d 129.1d 0 book_staleness book i 134,086 9,478 29ms 3.0s 8.5h 110.6d 0 book_staleness book m 129,485 64,936 7ms 1.7s 5.4h 129.1d 0 book_staleness book n 128,534 4,025 59ms 2.9s 4.3h 129.1d 0 book_staleness book o 132,609 61,093 7ms 2.2s 8.0h 129.1d 0 book_staleness last_trade_price h 52,601 765 21ms 92ms 805ms 24.8s 0 transport_latency_assumed last_trade_price i 56,479 559 25ms 283ms 2.7s 8.6s 0 transport_latency_assumed last_trade_price m 56,771 30,244 6ms 30ms 228ms 3.8s 0 transport_latency_assumed last_trade_price n 56,478 72 56ms 839ms 8.1s 17.6s 0 transport_latency_assumed last_trade_price o 56,439 25,234 6ms 29ms 236ms 1.8s 0 transport_latency_assumed market_resolved h 1,369 78 21ms 277ms 6.2min 8.4min 0 transport_latency_assumed market_resolved i 1,369 95 23ms 104ms 41.0s 53.7s 0 transport_latency_assumed market_resolved m 1,369 662 6ms 38ms 49.4s 49.4s 0 transport_latency_assumed market_resolved n 1,369 2 48ms 202ms 51.2s 51.3s 0 transport_latency_assumed market_resolved o 1,369 624 6ms 29ms 40.9s 56.3s 0 transport_latency_assumed new_market h 5,716 1,209 90ms 55.2s 5.7min 6.6min 0 transport_latency_assumed new_market i 5,708 1,952 50ms 1.0min 1.6min 6.3min 0 transport_latency_assumed new_market m 5,708 2,736 47ms 1.1min 1.6min 6.4min 0 transport_latency_assumed new_market n 5,708 719 138ms 1.1min 1.6min 6.3min 0 transport_latency_assumed new_market o 5,717 3,288 50ms 1.1min 1.5min 6.3min 0 transport_latency_assumed price_change h 99,812,182 1,279,600 19ms 51ms 746ms 41.5s 0 transport_latency_assumed price_change i 107,841,743 1,160,825 22ms 54ms 861ms 8.6s 0 transport_latency_assumed price_change m 107,997,294 54,759,239 5ms 22ms 191ms 6.7s 0 transport_latency_assumed price_change n 107,954,906 133,934 46ms 113ms 1.7s 17.6s 0 transport_latency_assumed price_change o 107,971,152 50,903,520 5ms 22ms 204ms 6.7s 0 transport_latency_assumed tick_size_change h 3,868 25 19ms 47ms 324ms 4.7s 0 transport_latency_assumed tick_size_change i 4,232 49 21ms 40ms 182ms 2.0s 0 transport_latency_assumed tick_size_change m 4,232 2,186 5ms 15ms 98ms 993ms 0 transport_latency_assumed tick_size_change n 4,232 18 45ms 78ms 234ms 420ms 0 transport_latency_assumed tick_size_change o 4,232 1,954 5ms 33ms 370ms 461ms 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/00/2026-10-06T00.parquet sha256sum 2026-10-06T00.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.