Hour audit: 2026-09-06T08
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-06T08 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-06T08:00:00.065649021+00:00 · last event 2026-09-06T08:59:59.999974581+00:00
VOLUME 107,861,235 rows · 1,082,713,254 bytes (1.01 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 107,522,188 · h: 107,250,332 · g: 107,232,042 · e: 107,098,963 · c: 103,306,475 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 346,529 (0.32%) · h: 9,620 (0.01%) · g: 107,230,004 (99.41%) · e: 12,193 (0.01%) · c: 262,889 (0.24%) (rows of the merged file that came from it; these partition it)
5 product-machine pairs publish no supplied count; the figures above still sum to the file's 107,861,235 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 4a5a13ad941a64d5c37c5670fe7b6bb430a19336a2bbe3a0cdfd12f23f01aac2
the corpus checksum ledger names this file with the same digest
joined 107,863,313 to merged 107,861,235, minus 2,078 (minus 0.0019%)
boundary drops 2,078 · 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-06T10:26:59Z 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 10,769,228 114,835,425 0-41 9d43c0c5d6cfb4142006550dd8ec24b82f1321236763b305fd1716f912a5b82a book 676,232 56,950,758 42-44 e03a5b87d54a2f28aefe6df34d0924f47b6052e4a2602356019612d4526b0933 last_trade_price 54,297 3,084,345 45-45 faba4d55205100d0e60809faa3d5c47af75c0369f7d6e75803e28e8ed5450a2f market_resolved 1,198 181,889 46-46 3da31f36bb1382e69aa4275f80694a514894885b9348c7a74002bcabdd61d80d new_market 3,105 291,104 47-47 6b8cfeff16365e2bea57dff2381a67296973ac8118778200a513429ffe5e176e price_change 96,354,863 906,054,831 48-415 ea9c91b33a833ce04f36873e4c2f4134bd7efd9ea161c8c6a33bb4df48174d68 tick_size_change 2,312 85,571 416-416 d3e6fcda5b0e1d072b6e964821524222633e2b980a287a9f1d9db0bbd7075e8e EVENT MIX count share price_change 96,354,863 89.33% best_bid_ask 10,769,228 9.98% book 676,232 0.63% last_trade_price 54,297 0.05% new_market 3,105 <0.01% tick_size_change 2,312 <0.01% market_resolved 1,198 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,769,473 10,769,228 245 938 FULL book 676,272 676,232 40 170,786 FULL last_trade_price 54,298 54,297 1 64 FULL market_resolved 1,198 1,198 0 65 FULL new_market 3,105 3,105 0 0 FULL price_change 96,356,655 96,354,863 1,792 525 FULL tick_size_change 2,312 2,312 0 30 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,332,382 946 4ms 10ms 137ms 7.3s 0 transport_latency_assumed best_bid_ask e 10,762,122 793 38ms 43ms 233ms 16.7s 0 transport_latency_assumed best_bid_ask f 10,762,446 2,535 48ms 55ms 253ms 7.3s 0 transport_latency_assumed best_bid_ask g 10,764,477 10,764,232 80ms 99ms 537ms 19.9s 0 transport_latency_assumed best_bid_ask h 10,766,516 722 17ms 24ms 266ms 56.4s 0 transport_latency_assumed book c 461,863 251,086 1.8min 14.9h 34.7d 99.4d 0 book_staleness book e 122,059 6,509 40ms 572ms 12.0h 80.9d 0 book_staleness book f 409,735 294,291 1.3min 14.8h 32.6d 99.4d 0 book_staleness book g 123,661 123,661 89ms 2.3s 16.0h 99.4d 0 book_staleness book h 114,829 685 21ms 65ms 3.2s 42.5d 0 book_staleness last_trade_price c 52,017 1 9ms 39ms 278ms 5.0s 0 transport_latency_assumed last_trade_price e 54,006 9 44ms 117ms 1.4s 16.7s 0 transport_latency_assumed last_trade_price f 54,220 114 54ms 112ms 1.2s 7.3s 0 transport_latency_assumed last_trade_price g 54,169 54,168 92ms 199ms 6.0s 19.9s 0 transport_latency_assumed last_trade_price h 54,268 5 22ms 62ms 582ms 54.7s 0 transport_latency_assumed market_resolved c 1,103 25 5ms 12ms 5.1min 5.1min 0 transport_latency_assumed market_resolved e 1,144 12 39ms 187ms 1.0min 1.0min 0 transport_latency_assumed market_resolved f 1,147 14 49ms 178ms 56.0s 1.1min 0 transport_latency_assumed market_resolved g 1,147 1,147 85ms 240ms 755ms 59.5s 0 transport_latency_assumed market_resolved h 1,147 not meas. 18ms 64ms 242ms 49.7s 0 transport_latency_assumed new_market c 1,921 137 175ms 3.9min 4.3min 3.1h 0 transport_latency_assumed new_market e 1,887 306 197ms 25.0s 1.4min 1.9h 0 transport_latency_assumed new_market f 1,887 663 186ms 29.6s 1.3min 4.2h 0 transport_latency_assumed new_market g 1,887 1,887 347ms 31.0s 1.3min 8.1h 0 transport_latency_assumed new_market h 1,887 112 157ms 26.6s 1.4min 4.5h 0 transport_latency_assumed price_change c 92,454,997 10,694 5ms 10ms 156ms 8.2s 0 transport_latency_assumed price_change e 96,155,433 4,564 38ms 47ms 297ms 16.7s 0 transport_latency_assumed price_change f 96,290,441 48,912 48ms 59ms 303ms 7.4s 0 transport_latency_assumed price_change g 96,284,389 96,282,597 81ms 106ms 690ms 19.9s 0 transport_latency_assumed price_change h 96,309,373 8,096 18ms 26ms 294ms 56.4s 0 transport_latency_assumed tick_size_change c 2,192 not meas. 5ms 15ms 550ms 563ms 0 transport_latency_assumed tick_size_change e 2,312 not meas. 38ms 56ms 545ms 825ms 0 transport_latency_assumed tick_size_change f 2,312 not meas. 48ms 65ms 584ms 686ms 0 transport_latency_assumed tick_size_change g 2,312 2,312 80ms 101ms 1.1s 1.7s 0 transport_latency_assumed tick_size_change h 2,312 not meas. 17ms 36ms 738ms 3.5s 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/08/2026-09-06T08.parquet sha256sum 2026-09-06T08.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.