Hour audit: 2026-09-06T10
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-06T10 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-06T10:00:00.076704951+00:00 · last event 2026-09-06T10:59:59.999988426+00:00
VOLUME 121,909,317 rows · 1,283,148,421 bytes (1.20 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 120,084,104 · g: 120,082,341 · f: 120,079,002 · e: 119,960,409 · c: 97,918,659 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 24,466,133 (20.07%) · g: 36,268 (0.03%) · f: 316,291 (0.26%) · e: 2,378,958 (1.95%) · c: 94,711,667 (77.69%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 121,909,317 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 85fee1d4292c001b70e3d6c6acb820070108793c5370fb50c1ef4ae9bf9b9a0d
the corpus checksum ledger names this file with the same digest
joined 121,909,487 to merged 121,909,317, minus 170 (minus 0.0001%)
boundary drops 170 · 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-06T21:13:58Z 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 12,244,678 135,503,652 0-46 95ea2bf0de9155908f62b63427b5e0be6d1a35e36d7a474f7a05ee9a7b37cfc1 book 1,881,397 80,657,788 47-54 df8c3c4b0650d4d6e87257fb91fce6328b37a3da84dd7a4d2a2f86a205a55c0b last_trade_price 57,436 3,324,231 55-55 02ee73a8a22672e27f34a0978d6fe76290dddb6f4a69b3cdd53f49d43d58dadd market_resolved 1,308 160,346 56-56 3eadd76d81212af2216d93abc56fe1ffe434f4fd755ffca7c17686b0e0e46803 new_market 1,426 133,393 57-57 2c4df2f7d5e9b2c7d764d3571b84cec4de0a44ba92c6081e1eed32149e05952f price_change 107,718,472 1,061,815,248 58-468 f1531a454c3c68edb98705bafec4f38c7877a83162e4e94d2dea1275c6c771f8 tick_size_change 4,600 167,730 469-469 90f1a393d2ecd94110940d6e86204c3242dffe8d32c97b5475ea7f99d46b5f33 EVENT MIX count share price_change 107,718,472 88.36% best_bid_ask 12,244,678 10.04% book 1,881,397 1.54% last_trade_price 57,436 0.05% tick_size_change 4,600 <0.01% new_market 1,426 <0.01% market_resolved 1,308 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,244,688 12,244,678 10 2,296 FULL book 1,881,413 1,881,397 16 171,979 FULL last_trade_price 57,436 57,436 0 376 FULL market_resolved 1,308 1,308 0 92 FULL new_market 1,426 1,426 0 1 FULL price_change 107,718,616 107,718,472 144 1,515 FULL tick_size_change 4,600 4,600 0 167 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,702,314 9,397,955 5ms 9ms 78ms 2.1s 0 transport_latency_assumed best_bid_ask e 12,242,706 250,676 39ms 45ms 143ms 6.0s 0 transport_latency_assumed best_bid_ask f 12,242,990 29,749 48ms 55ms 172ms 4.7s 0 transport_latency_assumed best_bid_ask g 12,241,770 2,427 80ms 97ms 314ms 19.3s 0 transport_latency_assumed best_bid_ask h 12,243,456 2,563,871 18ms 28ms 115ms 39.4s 0 transport_latency_assumed book c 1,851,853 1,845,292 6.5min 20.3h 34.9d 99.5d 0 book_staleness book e 120,146 5,244 41ms 107ms 53.5s 80.9d 0 book_staleness book f 119,447 1,709 50ms 117ms 2.2s 80.9d 0 book_staleness book g 127,035 5,016 82ms 388ms 14.4h 81.0d 0 book_staleness book h 118,953 24,136 22ms 56ms 769ms 32.7d 0 book_staleness last_trade_price c 45,959 43,983 10ms 40ms 293ms 5.0s 0 transport_latency_assumed last_trade_price e 57,307 1,186 45ms 89ms 682ms 5.6s 0 transport_latency_assumed last_trade_price f 57,397 143 54ms 103ms 665ms 5.0s 0 transport_latency_assumed last_trade_price g 57,398 12 89ms 163ms 1.4s 19.3s 0 transport_latency_assumed last_trade_price h 57,402 12,112 23ms 60ms 400ms 6.5s 0 transport_latency_assumed market_resolved c 1,043 1,030 6ms 8.1min 13.9min 14.0min 0 transport_latency_assumed market_resolved e 976 26 40ms 176ms 512ms 1.0min 0 transport_latency_assumed market_resolved f 976 3 48ms 169ms 441ms 1.0min 0 transport_latency_assumed market_resolved g 973 1 85ms 255ms 729ms 1.3s 0 transport_latency_assumed market_resolved h 976 248 18ms 74ms 280ms 1.5s 0 transport_latency_assumed new_market c 1,014 657 120ms 4.0min 3.4h 5.7h 0 transport_latency_assumed new_market e 838 128 138ms 17.5s 50.3s 5.6h 0 transport_latency_assumed new_market f 838 220 166ms 25.2s 48.8s 1.6h 0 transport_latency_assumed new_market g 838 116 275ms 20.4s 50.0s 4.2h 0 transport_latency_assumed new_market h 838 305 94ms 11.5s 52.5s 4.3h 0 transport_latency_assumed price_change c 86,312,544 83,419,051 5ms 10ms 93ms 3.6s 0 transport_latency_assumed price_change e 107,533,836 2,121,621 40ms 47ms 183ms 6.0s 0 transport_latency_assumed price_change f 107,652,754 284,455 48ms 58ms 205ms 5.2s 0 transport_latency_assumed price_change g 107,649,727 28,696 80ms 100ms 393ms 19.4s 0 transport_latency_assumed price_change h 107,657,879 21,864,649 18ms 30ms 134ms 39.5s 0 transport_latency_assumed tick_size_change c 3,932 3,699 5ms 14ms 214ms 406ms 0 transport_latency_assumed tick_size_change e 4,600 77 39ms 50ms 167ms 362ms 0 transport_latency_assumed tick_size_change f 4,600 12 48ms 60ms 120ms 295ms 0 transport_latency_assumed tick_size_change g 4,600 not meas. 80ms 99ms 355ms 910ms 0 transport_latency_assumed tick_size_change h 4,600 812 18ms 27ms 93ms 939ms 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/10/2026-09-06T10.parquet sha256sum 2026-09-06T10.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.