Hour audit: 2026-09-06T09
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-06T09 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-06T09:00:00.065057502+00:00 · last event 2026-09-06T09:59:59.999126214+00:00
VOLUME 115,205,941 rows · 1,201,545,085 bytes (1.12 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 113,413,949 · h: 113,412,609 · g: 113,374,697 · e: 113,197,935 · c: 92,980,307 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 399,662 (0.35%) · h: 23,905,842 (20.75%) · g: 46,016 (0.04%) · e: 1,338,259 (1.16%) · c: 89,516,162 (77.70%) (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 115,205,941 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 d8fdd11fbe9b3af803c9baffea7d5f0e4d1fdbc28a3bc10fb587a2fb5c6fd184
the corpus checksum ledger names this file with the same digest
joined 115,208,840 to merged 115,205,941, minus 2,899 (minus 0.0025%)
boundary drops 2,899 · 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-06T20:43:40Z 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 11,562,818 127,077,817 0-44 73f2549471d7210dab38c0112964c90275c4a337f27a60f15841c8c5f8932966 book 1,871,438 80,798,598 45-52 624ec538514e4e753ad07c06e01b205d5f3ba7f6d8ba60ca68b2059c70a075bd last_trade_price 59,323 3,375,943 53-53 e826ca52b667d0953004b8bf9e938fce8c38dc53dc151986f77effcf4ad802f6 market_resolved 1,446 199,800 54-54 d432256bc828ec53fda5a2c7b876f07c786cf1b8d6fa724dacf5b7a98225475b new_market 2,864 265,683 55-55 3e6adf754c0f5440db1dea3b4456e195682b8ef7144ccea472382194fa070683 price_change 101,704,152 988,370,963 56-443 99b07ec256bfc24027170705bc2c530227a3a2f4af0c92a11df9ce0b5716ea8e tick_size_change 3,900 143,680 444-444 322e0dcfbb5d949d7ae79fecf47a63dd7d5246f467f60a81d18f0c57b276aae1 EVENT MIX count share price_change 101,704,152 88.28% best_bid_ask 11,562,818 10.04% book 1,871,438 1.62% last_trade_price 59,323 0.05% tick_size_change 3,900 <0.01% new_market 2,864 <0.01% market_resolved 1,446 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,563,128 11,562,818 310 2,225 FULL book 1,871,443 1,871,438 5 171,517 FULL last_trade_price 59,323 59,323 0 379 FULL market_resolved 1,446 1,446 0 106 FULL new_market 2,864 2,864 0 0 FULL price_change 101,706,736 101,704,152 2,584 1,479 FULL tick_size_change 3,900 3,900 0 134 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,216,972 8,883,100 4ms 10ms 118ms 3.4s 0 transport_latency_assumed best_bid_ask e 11,557,551 142,090 38ms 44ms 228ms 24.2s 0 transport_latency_assumed best_bid_ask f 11,559,449 39,755 48ms 56ms 252ms 7.5s 0 transport_latency_assumed best_bid_ask g 11,558,184 4,285 80ms 99ms 520ms 24.8s 0 transport_latency_assumed best_bid_ask h 11,559,875 2,493,588 18ms 25ms 251ms 53.6s 0 transport_latency_assumed book c 1,837,328 1,829,111 6.4min 19.3h 34.9d 99.5d 0 book_staleness book e 124,593 3,976 40ms 165ms 4.3s 34.9d 0 book_staleness book f 125,467 2,350 50ms 177ms 6.7s 80.9d 0 book_staleness book g 130,903 4,907 87ms 765ms 11.1h 81.0d 0 book_staleness book h 131,391 31,094 22ms 144ms 11.9h 81.0d 0 book_staleness last_trade_price c 47,402 44,823 10ms 42ms 278ms 5.0s 0 transport_latency_assumed last_trade_price e 59,064 745 44ms 134ms 2.1s 23.8s 0 transport_latency_assumed last_trade_price f 59,204 230 54ms 137ms 1.4s 7.6s 0 transport_latency_assumed last_trade_price g 59,087 77 92ms 252ms 7.6s 25.2s 0 transport_latency_assumed last_trade_price h 59,276 13,448 23ms 62ms 563ms 39.7s 0 transport_latency_assumed market_resolved c 1,241 1,210 5ms 8.1min 12.1min 13.3min 0 transport_latency_assumed market_resolved e 1,233 15 39ms 116ms 487ms 51.7s 0 transport_latency_assumed market_resolved f 1,233 5 49ms 128ms 526ms 51.7s 0 transport_latency_assumed market_resolved g 1,233 not meas. 84ms 246ms 734ms 4.5s 0 transport_latency_assumed market_resolved h 1,233 216 18ms 60ms 272ms 1.0min 0 transport_latency_assumed new_market c 1,929 974 257ms 4.3min 1.9h 6.9h 0 transport_latency_assumed new_market e 1,701 539 186ms 23.9s 51.4s 4.0h 0 transport_latency_assumed new_market f 1,701 428 197ms 22.4s 38.5s 20.0min 0 transport_latency_assumed new_market g 1,701 205 339ms 24.1s 1.0min 2.9h 0 transport_latency_assumed new_market h 1,701 718 150ms 22.8s 43.9s 8.5h 0 transport_latency_assumed price_change c 81,872,063 78,753,758 5ms 11ms 130ms 3.8s 0 transport_latency_assumed price_change e 101,449,893 1,190,872 38ms 48ms 299ms 24.4s 0 transport_latency_assumed price_change f 101,662,995 356,876 48ms 60ms 311ms 7.6s 0 transport_latency_assumed price_change g 101,619,689 36,542 82ms 107ms 730ms 25.0s 0 transport_latency_assumed price_change h 101,655,241 21,366,104 18ms 27ms 255ms 53.6s 0 transport_latency_assumed tick_size_change c 3,372 3,186 5ms 12ms 145ms 517ms 0 transport_latency_assumed tick_size_change e 3,900 22 38ms 49ms 190ms 723ms 0 transport_latency_assumed tick_size_change f 3,900 18 48ms 60ms 302ms 831ms 0 transport_latency_assumed tick_size_change g 3,900 not meas. 81ms 108ms 431ms 1.6s 0 transport_latency_assumed tick_size_change h 3,892 674 18ms 26ms 354ms 2.4s 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/09/2026-09-06T09.parquet sha256sum 2026-09-06T09.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.