Hour audit: 2026-09-06T01
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-09-06T01 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-06T01:00:00.069872717+00:00 · last event 2026-09-06T01:59:59.999993457+00:00
VOLUME 134,796,362 rows · 1,400,053,055 bytes (1.30 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 132,844,024 · e: 132,839,369 · g: 132,605,433 · f: 127,672,769 · c: 107,856,780 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 9,316 (0.01%) · e: 6,579 (0.00%) · g: 132,602,427 (98.37%) · f: 678,478 (0.50%) · c: 1,499,562 (1.11%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 134,796,362 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 7732612bd4b9ae0b155846be5aac8d1613f4f0cdaa4072c0a9b9056d46cb31e5
the corpus checksum ledger names this file with the same digest
joined 134,799,484 to merged 134,796,362, minus 3,122 (minus 0.0023%)
boundary drops 3,122 · 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-09-06T05:21:27Z as cefgh
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 our incident register was checked against the venue's own status feed at 2026-09-23T20:35Z and names no event in this hour. That is a statement about what they published, not a check that every message they sent reached us.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 13,441,877 143,599,479 0-51 e96a9e028633eb171e84da52f771c6548431c44edf12c4d9ec422f654239e4fe book 1,987,751 81,421,868 52-59 15e56171eb285ab2391ce9def432b27c5c12783583065ad55596b9bdce34c567 last_trade_price 53,792 3,036,997 60-60 c4b94fc980a30e71ca7e5af62d456e9053dd9295a599ca0bc0b2e4af4a960864 market_resolved 2,444 312,375 61-61 d675c5d90d79ff2277d8a832953b73c2fe2eecf4d4c9eb01dea8206f944e3232 new_market 686 68,319 62-62 d96e981462c2e819bcdd9ef250a38d94cbfdd1a9f3ea98bb12161422a4a36fb5 price_change 119,302,696 1,169,831,098 63-518 3fbb8a789461a59c8dd9755b8547309c3778e8c9564b54f30a1b9a69b44f3418 tick_size_change 7,116 249,840 519-519 ce88c39503436155d3a5d6d3964d9feedbf9182fd5cd7a7a4112f0640f5e4625 EVENT MIX count share price_change 119,302,696 88.51% best_bid_ask 13,441,877 9.97% book 1,987,751 1.47% last_trade_price 53,792 0.04% tick_size_change 7,116 <0.01% market_resolved 2,444 <0.01% new_market 686 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,442,212 13,441,877 335 2,257 FULL book 1,987,809 1,987,751 58 180,607 FULL last_trade_price 53,793 53,792 1 365 FULL market_resolved 2,444 2,444 0 41 FULL new_market 686 686 0 0 FULL price_change 119,305,424 119,302,696 2,728 1,866 FULL tick_size_change 7,116 7,116 0 447 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,746,173 340 4ms 8ms 56ms 1.1s 0 transport_latency_assumed best_bid_ask e 13,440,598 388 40ms 46ms 111ms 1.6s 0 transport_latency_assumed best_bid_ask f 12,864,887 16,176 48ms 56ms 136ms 2.6s 0 transport_latency_assumed best_bid_ask g 13,424,545 13,424,210 81ms 102ms 335ms 9.0s 0 transport_latency_assumed best_bid_ask h 13,441,131 763 18ms 37ms 97ms 8.7s 0 transport_latency_assumed book c 1,926,380 1,495,814 25.1min 12.3h 34.6d 99.1d 0 book_staleness book e 111,375 550 41ms 73ms 1.3s 80.6d 0 book_staleness book f 474,973 368,293 2.7min 10.5h 33.2d 99.1d 0 book_staleness book g 122,503 122,495 86ms 13.3s 5.0h 80.6d 0 book_staleness book h 111,337 599 21ms 68ms 1.9s 80.5d 0 book_staleness last_trade_price c 43,662 2 9ms 39ms 265ms 5.0s 0 transport_latency_assumed last_trade_price e 53,718 16 45ms 81ms 350ms 5.0s 0 transport_latency_assumed last_trade_price f 51,830 1,736 55ms 97ms 493ms 5.0s 0 transport_latency_assumed last_trade_price g 52,028 52,027 90ms 173ms 3.0s 8.4s 0 transport_latency_assumed last_trade_price h 53,685 11 23ms 67ms 334ms 8.7s 0 transport_latency_assumed market_resolved c 2,217 440 5ms 6.3min 13.7min 14.3min 0 transport_latency_assumed market_resolved e 1,941 8 41ms 117ms 471ms 1.0min 0 transport_latency_assumed market_resolved f 1,951 55 49ms 128ms 4.1min 5.1min 0 transport_latency_assumed market_resolved g 1,941 1,941 86ms 192ms 430ms 1.0min 0 transport_latency_assumed market_resolved h 1,941 not meas. 19ms 54ms 326ms 58.5s 0 transport_latency_assumed new_market c 553 152 78ms 9.2min 3.1h 7.4h 0 transport_latency_assumed new_market e 419 21 74ms 599ms 36.8s 5.6h 0 transport_latency_assumed new_market f 436 63 84ms 14.0s 1.3min 5.6h 0 transport_latency_assumed new_market g 419 419 106ms 2.9s 22.7s 36.9s 0 transport_latency_assumed new_market h 419 31 72ms 13.4s 21.6s 5.6h 0 transport_latency_assumed price_change c 95,132,435 2,814 4ms 9ms 63ms 1.6s 0 transport_latency_assumed price_change e 119,224,202 5,596 40ms 48ms 127ms 1.9s 0 transport_latency_assumed price_change f 114,271,908 292,147 49ms 58ms 150ms 2.7s 0 transport_latency_assumed price_change g 118,996,889 118,994,227 82ms 114ms 385ms 9.6s 0 transport_latency_assumed price_change h 119,228,395 7,912 18ms 39ms 107ms 8.7s 0 transport_latency_assumed tick_size_change c 5,360 not meas. 4ms 8ms 44ms 261ms 0 transport_latency_assumed tick_size_change e 7,116 not meas. 40ms 46ms 88ms 263ms 0 transport_latency_assumed tick_size_change f 6,784 8 48ms 55ms 105ms 335ms 0 transport_latency_assumed tick_size_change g 7,108 7,108 83ms 176ms 324ms 1.4s 0 transport_latency_assumed tick_size_change h 7,116 not meas. 18ms 34ms 74ms 257ms 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-09-06/01/2026-09-06T01.parquet sha256sum 2026-09-06T01.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.