Hour audit: 2026-09-10T15
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-10T15 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-10T15:00:00.000290417+00:00 · last event 2026-09-10T15:59:59.999977529+00:00
VOLUME 114,949,144 rows · 1,233,652,120 bytes (1.15 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured g: 113,301,540 · f: 113,294,909 · h: 113,288,428 · e: 113,235,902 · c: 94,553,553 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 74,984 (0.07%) · f: 369,348 (0.32%) · h: 23,657,106 (20.58%) · e: 1,539,229 (1.34%) · c: 89,308,477 (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 114,949,144 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 083c72465e6ecf351957d7bc433b9512dec7a375d256ee05835b2d2cbeb1bc5b
the corpus checksum ledger names this file with the same digest
joined 114,953,216 to merged 114,949,144, minus 4,072 (minus 0.0035%)
boundary drops 4,072 · 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-10T16:59:24Z 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,750,011 122,052,423 0-41 eeb0faf69ac5a20fbf54755584188bd1107c54be3d57ea757f5adcd74c230c48 book 1,713,559 88,054,234 42-48 f3a47e677a6fdd5bd3812b12e9610dee7cf482bcc988b6e4c498e38ea891d4cc last_trade_price 64,291 3,648,932 49-49 aec3b8634293579c39ea9a204c38121ad4f89babf370fb4438529e1a08478621 market_resolved 883 118,238 50-50 12f071674a229f925bb9822caaaf172851d9488ddca1d75ef748dd4a29ccaf30 new_market 1,361 140,407 51-51 9a4ad9bbe2e0acaa532788010d3c66426d966a93cbc6ffec9fed290a6deb8878 price_change 102,415,619 1,018,202,182 52-442 a31f7ea1a93220a71122b5f98ecddf1116862455ddb975645011518fd64135eb tick_size_change 3,420 125,836 443-443 c2a4e0d8107f3d928c8a9bb1d6d701eb411b353ca0c40c1fca536940d6214484 EVENT MIX count share price_change 102,415,619 89.10% best_bid_ask 10,750,011 9.35% book 1,713,559 1.49% last_trade_price 64,291 0.06% tick_size_change 3,420 <0.01% new_market 1,361 <0.01% market_resolved 883 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,750,189 10,750,011 178 2,872 FULL book 1,714,055 1,713,559 496 194,133 FULL last_trade_price 64,291 64,291 0 312 FULL market_resolved 883 883 0 80 FULL new_market 1,361 1,361 0 2 FULL price_change 102,419,017 102,415,619 3,398 2,368 FULL tick_size_change 3,420 3,420 0 140 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,829,485 8,350,121 6ms 14ms 128ms 4.4s 0 transport_latency_assumed best_bid_ask e 10,744,320 143,375 39ms 49ms 223ms 9.0s 0 transport_latency_assumed best_bid_ask f 10,747,797 31,321 47ms 60ms 224ms 5.2s 0 transport_latency_assumed best_bid_ask g 10,746,292 2,944 79ms 100ms 361ms 13.7s 0 transport_latency_assumed best_bid_ask h 10,748,159 2,222,250 18ms 28ms 164ms 24.5s 0 transport_latency_assumed book c 1,660,701 1,645,779 22.0min 1.3d 32.7d 103.7d 0 book_staleness book e 139,665 7,916 43ms 539ms 37.3min 85.1d 0 book_staleness book f 137,775 3,150 50ms 255ms 1.5h 85.2d 0 book_staleness book g 187,259 24,721 101ms 3.3h 8.3d 103.7d 0 book_staleness book h 137,629 31,993 23ms 86ms 59.0min 85.2d 0 book_staleness last_trade_price c 50,778 47,611 11ms 50ms 294ms 5.1s 0 transport_latency_assumed last_trade_price e 63,900 934 53ms 266ms 3.5s 9.1s 0 transport_latency_assumed last_trade_price f 64,128 517 60ms 202ms 1.9s 5.0s 0 transport_latency_assumed last_trade_price g 64,082 162 96ms 310ms 3.9s 12.4s 0 transport_latency_assumed last_trade_price h 64,123 15,067 25ms 83ms 532ms 8.1s 0 transport_latency_assumed market_resolved c 688 598 7ms 5.4min 10.3min 10.3min 0 transport_latency_assumed market_resolved e 712 52 41ms 46.0s 1.0min 1.0min 0 transport_latency_assumed market_resolved f 712 4 49ms 46.2s 1.0min 1.0min 0 transport_latency_assumed market_resolved g 712 74 81ms 377ms 972ms 1.4s 0 transport_latency_assumed market_resolved h 712 155 20ms 46.0s 1.0min 1.0min 0 transport_latency_assumed new_market c 1,027 567 92ms 2.8min 5.3min 40.7d 0 transport_latency_assumed new_market e 900 154 160ms 18.4s 46.3s 58.6s 0 transport_latency_assumed new_market f 900 156 161ms 18.8s 44.5s 1.3min 0 transport_latency_assumed new_market g 902 87 282ms 13.3s 46.5s 40.7d 0 transport_latency_assumed new_market h 902 397 107ms 13.9s 46.8s 40.7d 0 transport_latency_assumed price_change c 84,008,014 79,261,007 6ms 15ms 142ms 7.2s 0 transport_latency_assumed price_change e 102,282,985 1,386,772 40ms 57ms 497ms 9.0s 0 transport_latency_assumed price_change f 102,340,177 334,192 47ms 68ms 334ms 5.3s 0 transport_latency_assumed price_change g 102,298,873 46,996 80ms 116ms 579ms 13.7s 0 transport_latency_assumed price_change h 102,333,483 21,386,652 18ms 31ms 199ms 37.3s 0 transport_latency_assumed tick_size_change c 2,860 2,794 6ms 11ms 42ms 427ms 0 transport_latency_assumed tick_size_change e 3,420 26 40ms 49ms 291ms 647ms 0 transport_latency_assumed tick_size_change f 3,420 8 47ms 66ms 264ms 571ms 0 transport_latency_assumed tick_size_change g 3,420 not meas. 79ms 96ms 239ms 5.7s 0 transport_latency_assumed tick_size_change h 3,420 592 18ms 29ms 162ms 767ms 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-10/15/2026-09-10T15.parquet sha256sum 2026-09-10T15.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.