Hour audit: 2026-10-07T05
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-07T05 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-07T05:00:00.001933910+00:00 · last event 2026-10-07T05:59:59.999847022+00:00
VOLUME 102,166,687 rows · 1,114,202,724 bytes (1.04 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 102,094,740 · m: 102,089,170 · h: 102,063,401 · i: 101,994,948 · n: 101,994,195 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 50,045,830 (48.98%) · m: 50,769,788 (49.69%) · h: 720,653 (0.71%) · i: 540,717 (0.53%) · n: 89,699 (0.09%) (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 102,166,687 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 deb3fd82c684568c09418f37e5f1d808dd87bc9c3b3eea15857441ed014a2fa7
the corpus checksum ledger names this file with the same digest
joined 102,168,727 to merged 102,166,687, minus 2,040 (minus 0.0020%)
boundary drops 2,040 · 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-07T06:59:10Z 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,771,458 132,391,417 0-41 a3b4144a89cd635c67fcf05c2566e9c4c387ca9bc49d45389a5fdcfbe29c623c book 139,758 14,752,264 42-42 e01f68f2d0b45ddb86f31a9134b1ce060f840c777beb6737e9b0b52d85192a5f last_trade_price 43,412 2,481,551 43-43 33d206b828274c8afc2b96a201791298c14229f770021a55900aa9a0b4afed66 market_resolved 1,142 178,773 44-44 1a56b09a4cd390a3beb0ce87df47bb3624d6c254e1c9e4d1df4421b9b8cc5612 new_market 1,707 157,900 45-45 19dc2d42c92b4c68f43757d78c86f0959b1f8cde36350db48501b00110ad693e price_change 91,205,218 962,930,252 46-393 73b88b82d775d525f40f49d02a26a66c7f9237f13cf59c4f084473391ea39740 tick_size_change 3,992 143,922 394-394 4efe73e26ddcd517b4937551a587629ff3cfb0b81dcb27547aeaa73533542cda EVENT MIX count share price_change 91,205,218 89.27% best_bid_ask 10,771,458 10.54% book 139,758 0.14% last_trade_price 43,412 0.04% tick_size_change 3,992 <0.01% new_market 1,707 <0.01% market_resolved 1,142 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,771,719 10,771,458 261 180 FULL book 139,851 139,758 93 22,619 FULL last_trade_price 43,414 43,412 2 1 FULL market_resolved 1,142 1,142 0 0 FULL new_market 1,707 1,707 0 0 FULL price_change 91,206,902 91,205,218 1,684 101 FULL tick_size_change 3,992 3,992 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,769,580 61,282 17ms 25ms 274ms 2.1min 0 transport_latency_assumed best_bid_ask i 10,768,718 47,649 21ms 28ms 129ms 3.6s 0 transport_latency_assumed best_bid_ask m 10,770,109 5,281,687 4ms 11ms 97ms 5.3s 0 transport_latency_assumed best_bid_ask n 10,769,312 5,591 43ms 53ms 234ms 6.6s 0 transport_latency_assumed best_bid_ask o 10,769,946 5,375,249 4ms 11ms 111ms 7.8s 0 transport_latency_assumed book h 95,846 7,935 22ms 348ms 1.3d 111.8d 0 book_staleness book i 95,008 7,230 24ms 312ms 23.0h 111.8d 0 book_staleness book m 102,116 54,414 7ms 2.0min 5.2d 130.3d 0 book_staleness book n 94,886 6,681 46ms 1.6s 1.2d 111.8d 0 book_staleness book o 106,741 63,498 7ms 13.5min 17.5d 111.8d 0 book_staleness last_trade_price h 43,240 428 19ms 47ms 385ms 40.4s 0 transport_latency_assumed last_trade_price i 43,245 245 23ms 63ms 480ms 1.9s 0 transport_latency_assumed last_trade_price m 43,324 20,303 6ms 19ms 194ms 1.9s 0 transport_latency_assumed last_trade_price n 43,248 31 46ms 173ms 3.3s 6.4s 0 transport_latency_assumed last_trade_price o 43,328 22,405 5ms 18ms 163ms 1.7s 0 transport_latency_assumed market_resolved h 1,104 6 20ms 27.9s 50.6s 50.7s 0 transport_latency_assumed market_resolved i 1,104 183 22ms 26.0s 46.8s 46.8s 0 transport_latency_assumed market_resolved m 1,104 470 5ms 26.8s 47.8s 47.9s 0 transport_latency_assumed market_resolved n 1,104 14 45ms 35.5s 57.0s 57.7s 0 transport_latency_assumed market_resolved o 1,104 469 5ms 23.3s 44.7s 55.8s 0 transport_latency_assumed new_market h 1,023 198 169ms 29.8s 57.8s 1.5min 0 transport_latency_assumed new_market i 1,023 354 109ms 22.8s 49.5s 1.6min 0 transport_latency_assumed new_market m 1,023 655 62ms 25.7s 56.8s 1.5min 0 transport_latency_assumed new_market n 1,023 140 211ms 22.4s 36.9s 1.6min 0 transport_latency_assumed new_market o 1,023 360 84ms 27.3s 57.3s 1.7min 0 transport_latency_assumed price_change h 91,148,616 650,784 18ms 29ms 485ms 2.1min 0 transport_latency_assumed price_change i 91,081,858 485,056 21ms 32ms 328ms 3.9s 0 transport_latency_assumed price_change m 91,167,502 45,410,250 4ms 12ms 152ms 6.7s 0 transport_latency_assumed price_change n 91,080,630 77,242 44ms 62ms 896ms 6.6s 0 transport_latency_assumed price_change o 91,168,606 44,581,886 4ms 13ms 170ms 8.3s 0 transport_latency_assumed tick_size_change h 3,992 20 18ms 23ms 60ms 302ms 0 transport_latency_assumed tick_size_change i 3,992 not meas. 21ms 27ms 55ms 322ms 0 transport_latency_assumed tick_size_change m 3,992 2,009 4ms 10ms 37ms 79ms 0 transport_latency_assumed tick_size_change n 3,992 not meas. 43ms 56ms 113ms 237ms 0 transport_latency_assumed tick_size_change o 3,992 1,963 4ms 10ms 42ms 261ms 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-07/05/2026-10-07T05.parquet sha256sum 2026-10-07T05.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.