Hour audit: 2026-10-01T17
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-01T17 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-01T17:00:00.000152080+00:00 · last event 2026-10-01T17:59:59.999955054+00:00
VOLUME 121,192,375 rows · 1,307,486,862 bytes (1.22 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured m: 120,564,077 · h: 120,551,974 · i: 120,480,400 · k: 120,455,858 · g: 120,266,388 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 117,304,837 (96.79%) · h: 779,126 (0.64%) · i: 567,147 (0.47%) · k: 2,266,589 (1.87%) · g: 274,676 (0.23%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 5a66b792c9e1c5de83354406b0c6e370729a3d91afbd3ab45fe33a0baf9442a9
the corpus checksum ledger names this file with the same digest
joined 121,195,072 to merged 121,192,375, minus 2,697 (minus 0.0022%)
boundary drops 2,697 · 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-01T20:12:51Z as ghikm
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,493,870 122,481,535 0-40 e826489b276d60e87fe562de27094804da7e0b149698a9df1819a673979ddb87 book 1,109,761 84,402,112 41-45 e0c9c4bb5d5679d57f7c56ba7d5311c9dac9bb977d8997ac297af30e0649b6fa last_trade_price 64,300 3,689,978 46-46 fb3a995f076d68f774111f03f07cb70100d1dc49720a241d3413bc0e836791db market_resolved 685 113,052 47-47 3f559aa553f172104cad22ef6683ab4ac76b74364bcfdda2d50b684cce159c67 new_market 2,977 279,345 48-48 3e90479a94c3f4c446d5c73b68e8f48504a712308761f2dc810b23a5bfbc689a price_change 109,517,478 1,095,017,077 49-466 d5f1ec45caab4955b82c809feda76bd1881e50d70e3bf2d9dc25936d48d2388b tick_size_change 3,304 121,365 467-467 a4fa04a874b2574e90e7262d16e4a0b9b3c70d567b45241933b755dcd68064c9 EVENT MIX count share price_change 109,517,478 90.37% best_bid_ask 10,493,870 8.66% book 1,109,761 0.92% last_trade_price 64,300 0.05% tick_size_change 3,304 <0.01% new_market 2,977 <0.01% market_resolved 685 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,494,060 10,493,870 190 348 FULL book 1,110,283 1,109,761 522 198,249 FULL last_trade_price 64,301 64,300 1 3 FULL market_resolved 685 685 0 0 FULL new_market 2,977 2,977 0 1 FULL price_change 109,519,462 109,517,478 1,984 192 FULL tick_size_change 3,304 3,304 0 2 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 10,486,242 8,575 74ms 92ms 436ms 28.3s 0 transport_latency_assumed best_bid_ask h 10,487,491 49,286 21ms 34ms 474ms 1.4min 0 transport_latency_assumed best_bid_ask i 10,489,054 27,481 29ms 48ms 176ms 46.7s 0 transport_latency_assumed best_bid_ask k 10,489,526 176,891 15ms 24ms 248ms 1.3min 0 transport_latency_assumed best_bid_ask m 10,489,738 10,231,637 5ms 9ms 80ms 6.4s 0 transport_latency_assumed book g 457,959 168,790 4.2min 2.5d 40.2d 124.8d 0 book_staleness book h 553,496 213,639 11.0min 2.8d 40.2d 124.8d 0 book_staleness book i 449,042 255,899 4.3min 2.4d 40.1d 124.8d 0 book_staleness book k 433,059 144,470 3.4min 2.5d 40.2d 124.8d 0 book_staleness book m 548,370 326,963 10.4min 2.8d 40.2d 124.8d 0 book_staleness last_trade_price g 63,981 88 77ms 166ms 3.3s 27.4s 0 transport_latency_assumed last_trade_price h 64,258 257 22ms 37ms 822ms 49.2s 0 transport_latency_assumed last_trade_price i 64,251 176 31ms 50ms 408ms 5.1s 0 transport_latency_assumed last_trade_price k 64,267 1,056 16ms 27ms 336ms 19.9s 0 transport_latency_assumed last_trade_price m 64,268 62,723 6ms 10ms 111ms 1.3s 0 transport_latency_assumed market_resolved g 679 58 79ms 24.6s 55.2s 55.2s 0 transport_latency_assumed market_resolved h 679 5 25ms 38.2s 44.5s 49.9s 0 transport_latency_assumed market_resolved i 679 11 45ms 27.2s 33.5s 37.6s 0 transport_latency_assumed market_resolved k 679 32 17ms 26.5s 34.2s 39.4s 0 transport_latency_assumed market_resolved m 679 579 6ms 27.0s 33.2s 38.5s 0 transport_latency_assumed new_market g 1,793 373 224ms 23.9s 1.0min 1.7min 0 transport_latency_assumed new_market h 1,794 535 194ms 23.8s 58.0s 449.9d 0 transport_latency_assumed new_market i 1,794 448 186ms 25.0s 56.2s 449.9d 0 transport_latency_assumed new_market k 1,794 349 241ms 25.2s 58.9s 449.9d 0 transport_latency_assumed new_market m 1,794 1,272 67ms 24.5s 57.2s 450.0d 0 transport_latency_assumed price_change g 109,252,438 96,788 75ms 95ms 692ms 28.4s 0 transport_latency_assumed price_change h 109,440,956 515,384 21ms 35ms 535ms 1.4min 0 transport_latency_assumed price_change i 109,472,276 283,116 30ms 49ms 249ms 47.5s 0 transport_latency_assumed price_change k 109,463,233 1,943,754 15ms 25ms 262ms 1.3min 0 transport_latency_assumed price_change m 109,455,928 106,678,436 5ms 9ms 89ms 10.8s 0 transport_latency_assumed tick_size_change g 3,296 4 75ms 91ms 426ms 778ms 0 transport_latency_assumed tick_size_change h 3,300 20 21ms 34ms 272ms 12.5s 0 transport_latency_assumed tick_size_change i 3,304 16 29ms 48ms 158ms 563ms 0 transport_latency_assumed tick_size_change k 3,300 37 15ms 23ms 203ms 3.3s 0 transport_latency_assumed tick_size_change m 3,300 3,227 5ms 8ms 62ms 221ms 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-01/17/2026-10-01T17.parquet sha256sum 2026-10-01T17.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.