Hour audit: 2026-10-04T19
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-04T19 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-04T19:00:00.000081181+00:00 · last event 2026-10-04T19:59:59.999959752+00:00
VOLUME 133,849,521 rows · 1,603,270,800 bytes (1.49 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured i: 132,549,075 · m: 132,374,475 · h: 132,248,603 · o: 124,773,391 · n: 119,402,978 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 1,194,227 (0.89%) · m: 70,178,116 (52.43%) · h: 1,570,974 (1.17%) · o: 59,783,018 (44.66%) · n: 1,123,186 (0.84%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 d12fcc0e18ee168c9c1307d504635c5ecfd953c72138cda19dc314705e4b6340
the corpus checksum ledger names this file with the same digest
joined 133,850,997 to merged 133,849,521, minus 1,476 (minus 0.0011%)
boundary drops 1,476 · 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-04T21:22:46Z 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,606,868 134,814,865 0-40 60d4139645cd5493ded4899c9e8993ed45e369c9ca1a987c5ca90256561c98a7 book 1,271,872 84,174,843 41-45 d21ae4e4ac6d41f3d99298420e1ce48b518e079d69fa491609c22f52fdfb478e last_trade_price 67,323 3,909,437 46-46 e9472685a4cd7da0cb9bc78761997367835376d909912dbaa196ffedaca80ed0 market_resolved 2,799 313,971 47-47 fc657362f71a982eaa9df96b74cd87fb43081327cebe551acec09e854a00222a new_market 5,309 514,969 48-48 4a8d1f8f665329ce65883500978d20b55bfcfbc6ac37cde125296034229d01c4 price_change 121,889,622 1,377,807,792 49-513 50a5d5fca9c70a415c957aba8704f297164f9fa1ee478a42a71fe67361be5f2c tick_size_change 5,728 214,023 514-514 a92ca3a20b506def126eebbc6e8f36b0afb9a2e7ce74c5d894fffd2f69439559 EVENT MIX count share price_change 121,889,622 91.06% best_bid_ask 10,606,868 7.92% book 1,271,872 0.95% last_trade_price 67,323 0.05% tick_size_change 5,728 <0.01% new_market 5,309 <0.01% market_resolved 2,799 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,606,984 10,606,868 116 2,614 FULL book 1,271,896 1,271,872 24 235,043 FULL last_trade_price 67,323 67,323 0 360 FULL market_resolved 2,799 2,799 0 27 FULL new_market 5,309 5,309 0 0 FULL price_change 121,890,958 121,889,622 1,336 3,862 FULL tick_size_change 5,728 5,728 0 219 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,583,307 124,238 19ms 41ms 961ms 1.7min 0 transport_latency_assumed best_bid_ask i 10,595,427 87,827 21ms 41ms 386ms 1.4min 0 transport_latency_assumed best_bid_ask m 10,590,931 5,673,740 6ms 20ms 196ms 9.7s 0 transport_latency_assumed best_bid_ask n 9,475,277 12,310 48ms 93ms 612ms 23.2s 0 transport_latency_assumed best_bid_ask o 9,921,518 4,708,753 6ms 20ms 230ms 12.7s 0 transport_latency_assumed book h 153,994 14,446 28ms 7.2s 19.7h 109.4d 0 book_staleness book i 146,006 8,010 26ms 605ms 6.7h 109.4d 0 book_staleness book m 150,771 77,517 9ms 1.4s 6.7h 109.2d 0 book_staleness book n 1,093,245 942,029 19.5min 1.7d 43.2d 127.9d 0 book_staleness book o 617,383 229,870 7.0min 1.1d 43.2d 127.9d 0 book_staleness last_trade_price h 66,348 766 21ms 247ms 3.6s 1.1min 0 transport_latency_assumed last_trade_price i 67,026 820 23ms 144ms 1.4s 16.6s 0 transport_latency_assumed last_trade_price m 66,689 33,335 7ms 34ms 336ms 4.6s 0 transport_latency_assumed last_trade_price n 59,094 146 58ms 714ms 9.5s 23.2s 0 transport_latency_assumed last_trade_price o 63,415 32,256 7ms 31ms 331ms 7.3s 0 transport_latency_assumed market_resolved h 1,860 13 23ms 31.3s 51.4s 1.5min 0 transport_latency_assumed market_resolved i 1,865 7 24ms 32.0s 49.4s 58.8s 0 transport_latency_assumed market_resolved m 1,860 1,153 8ms 31.4s 56.2s 2.0min 0 transport_latency_assumed market_resolved n 2,438 682 129ms 16.7min 27.4min 30.7min 0 transport_latency_assumed market_resolved o 1,991 944 8ms 53.1s 9.9min 11.4min 0 transport_latency_assumed new_market h 3,332 1,239 28.1s 1.3min 1.5min 1.7min 0 transport_latency_assumed new_market i 3,332 816 25.9s 1.3min 1.6min 1.7min 0 transport_latency_assumed new_market m 3,332 1,172 33.0s 1.2min 1.6min 1.8min 0 transport_latency_assumed new_market n 4,198 909 52.9s 10.3min 25.2min 27.9min 0 transport_latency_assumed new_market o 3,364 1,173 33.8s 1.3min 1.8min 4.5min 0 transport_latency_assumed price_change h 121,434,042 1,430,180 20ms 54ms 1.5s 1.9min 0 transport_latency_assumed price_change i 121,729,691 1,096,690 21ms 49ms 520ms 1.4min 0 transport_latency_assumed price_change m 121,555,168 64,388,079 6ms 22ms 216ms 9.8s 0 transport_latency_assumed price_change n 108,763,646 167,106 49ms 124ms 1.7s 23.5s 0 transport_latency_assumed price_change o 114,160,216 54,807,567 6ms 22ms 243ms 12.8s 0 transport_latency_assumed tick_size_change h 5,720 92 20ms 73ms 1.4s 18.2s 0 transport_latency_assumed tick_size_change i 5,728 57 21ms 50ms 626ms 2.5s 0 transport_latency_assumed tick_size_change m 5,724 3,120 6ms 27ms 354ms 4.0s 0 transport_latency_assumed tick_size_change n 5,080 4 49ms 134ms 805ms 1.5s 0 transport_latency_assumed tick_size_change o 5,504 2,455 6ms 34ms 274ms 682ms 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-04/19/2026-10-04T19.parquet sha256sum 2026-10-04T19.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.