Hour audit: 2026-10-05T05
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-05T05 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-05T05:00:00.000025084+00:00 · last event 2026-10-05T05:59:59.999886064+00:00
VOLUME 102,984,074 rows · 1,118,385,150 bytes (1.04 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 102,913,380 · m: 102,819,067 · h: 102,816,248 · i: 102,765,544 · n: 102,665,722 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 53,298,700 (51.75%) · m: 48,424,817 (47.02%) · h: 735,362 (0.71%) · i: 462,848 (0.45%) · n: 62,347 (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 102,984,074 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 4b1b093318dee6bc9d6fce2b2707f400ea4cc29d1a28dae494d0a8e7678e6be1
the corpus checksum ledger names this file with the same digest
joined 102,985,390 to merged 102,984,074, minus 1,316 (minus 0.0013%)
boundary drops 1,316 · 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-05T07:00: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 9,230,950 112,841,333 0-35 979b1907e4210e51ff4678b3adac79a8c580bd3022f1f751121f93cf22072a85 book 128,610 14,115,525 36-36 cb210d2841caa4e83ab1cee18009460ec11129e436e9f16d1633e3eed59907a8 last_trade_price 45,134 2,627,607 37-37 5c543f996995035534f2b7cf875ffd4f8672f4f21c6ef65b4f6d13cc633f7435 market_resolved 803 126,921 38-38 ff0bfc64acaffb13551b0731e51752689d0ffb7291e5048db3688681be39c836 new_market 2,179 226,985 39-39 d67432dd20c02b30b945e49187e80d1cd1587f520087108bf20fa0b84859d0e6 price_change 93,574,294 987,191,067 40-396 01271b78943884829c605b7090b822af0af52bdeddb3e5b261c9049522cc5bd7 tick_size_change 2,104 79,805 397-397 df60923d9d218b9631bf980cdb0288a8e91aa153746de415682cbc6db5d7cf2f EVENT MIX count share price_change 93,574,294 90.86% best_bid_ask 9,230,950 8.96% book 128,610 0.12% last_trade_price 45,134 0.04% new_market 2,179 <0.01% tick_size_change 2,104 <0.01% market_resolved 803 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,231,090 9,230,950 140 163 FULL book 128,612 128,610 2 14,884 FULL last_trade_price 45,134 45,134 0 0 FULL market_resolved 803 803 0 0 FULL new_market 2,179 2,179 0 0 FULL price_change 93,575,468 93,574,294 1,174 1,252 FULL tick_size_change 2,104 2,104 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 9,228,595 56,014 18ms 28ms 262ms 2.2min 0 transport_latency_assumed best_bid_ask i 9,228,233 39,447 19ms 29ms 170ms 21.7s 0 transport_latency_assumed best_bid_ask m 9,229,865 4,397,899 5ms 13ms 81ms 8.0s 0 transport_latency_assumed best_bid_ask n 9,227,140 3,368 48ms 67ms 246ms 24.2s 0 transport_latency_assumed best_bid_ask o 9,230,042 4,734,222 4ms 13ms 80ms 6.6s 0 transport_latency_assumed book h 96,139 4,481 22ms 125ms 5.7h 109.7d 0 book_staleness book i 94,366 2,545 22ms 170ms 15.4min 109.6d 0 book_staleness book m 102,556 51,970 7ms 3.3s 1.6d 109.8d 0 book_staleness book n 106,976 15,319 52ms 4.0min 12.5d 109.8d 0 book_staleness book o 99,042 54,295 6ms 98ms 17.2h 109.7d 0 book_staleness last_trade_price h 44,971 443 20ms 48ms 500ms 37.7s 0 transport_latency_assumed last_trade_price i 44,935 147 22ms 87ms 994ms 18.7s 0 transport_latency_assumed last_trade_price m 45,079 21,195 6ms 22ms 166ms 930ms 0 transport_latency_assumed last_trade_price n 44,559 26 50ms 173ms 4.7s 22.3s 0 transport_latency_assumed last_trade_price o 45,123 23,323 6ms 19ms 167ms 1.0s 0 transport_latency_assumed market_resolved h 774 12 21ms 229ms 54.7s 54.8s 0 transport_latency_assumed market_resolved i 774 79 23ms 303ms 51.0s 1.2min 0 transport_latency_assumed market_resolved m 774 343 6ms 134ms 52.8s 52.9s 0 transport_latency_assumed market_resolved n 774 11 51ms 204ms 48.0s 48.1s 0 transport_latency_assumed market_resolved o 774 358 6ms 81ms 53.4s 59.0s 0 transport_latency_assumed new_market h 1,525 182 20.6s 1.8min 2.1min 2.2min 0 transport_latency_assumed new_market i 1,525 310 35.0s 1.8min 2.1min 2.2min 0 transport_latency_assumed new_market m 1,525 789 28.1s 1.8min 2.1min 2.2min 0 transport_latency_assumed new_market n 1,525 173 35.1s 1.8min 2.1min 2.2min 0 transport_latency_assumed new_market o 1,525 725 32.1s 1.8min 2.1min 2.3min 0 transport_latency_assumed price_change h 93,442,140 674,223 18ms 33ms 351ms 2.2min 0 transport_latency_assumed price_change i 93,393,607 420,304 20ms 37ms 317ms 21.7s 0 transport_latency_assumed price_change m 93,437,164 43,951,604 5ms 16ms 95ms 8.0s 0 transport_latency_assumed price_change n 93,282,644 43,450 48ms 80ms 874ms 24.7s 0 transport_latency_assumed price_change o 93,534,770 48,484,713 5ms 15ms 93ms 6.6s 0 transport_latency_assumed tick_size_change h 2,104 7 19ms 57ms 725ms 2.0s 0 transport_latency_assumed tick_size_change i 2,104 16 20ms 61ms 383ms 492ms 0 transport_latency_assumed tick_size_change m 2,104 1,017 5ms 21ms 146ms 276ms 0 transport_latency_assumed tick_size_change n 2,104 not meas. 47ms 94ms 403ms 734ms 0 transport_latency_assumed tick_size_change o 2,104 1,064 5ms 24ms 262ms 667ms 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-05/05/2026-10-05T05.parquet sha256sum 2026-10-05T05.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.