Hour audit: 2026-09-08T21
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-08T21 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-08T21:00:00.000032499+00:00 · last event 2026-09-08T21:59:59.999975087+00:00
VOLUME 86,386,524 rows · 868,344,516 bytes (828.12 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 86,183,419 · f: 86,138,089 · g: 86,101,849 · h: 86,059,125 · e: 86,038,922 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 83,155,991 (96.26%) · f: 145,984 (0.17%) · g: 86,729 (0.10%) · h: 2,771,712 (3.21%) · e: 226,108 (0.26%) (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 86,386,524 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 b17f3a44a8b9b9556d9ee449823864fd42e63692fbce5edb909d28dfccc2791d
the corpus checksum ledger names this file with the same digest
joined 86,388,833 to merged 86,386,524, minus 2,309 (minus 0.0027%)
boundary drops 2,309 · 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-08T22:53:18Z 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 8,152,062 89,751,828 0-31 1d669efcdbb3d6d7e23db858a2097f51b8b4530a9074ea434b81b8218e03f03b book 383,460 38,947,579 32-33 2bf2712bb299a7edd5bdaea300808d43fcb5b3610ec018774dd77cedad0319d7 last_trade_price 56,784 3,183,865 34-34 8a92e6f87e3c42c92e6b6e54ef34c03267a4a6a00ec071027fa065cfb65de89a market_resolved 1,119 177,483 35-35 bd60fbd9875985db528ae7e76c77f53bfacb1775ac5fc9a8bea5757853455dbf new_market 975 103,538 36-36 32516e0765077270dafd87b3ae7520145e6c5775faa1af0e59c500859ef40b85 price_change 77,789,196 735,085,349 37-333 451aa3004fa0f34461bfa9c7d6b5fa89217143c5459e99b27cccffb823ea7670 tick_size_change 2,928 105,901 334-334 a8758b01e1c19beac5d1a973d6ae1361a994fe8d253ebb0e83f55ee7fc1aa32d EVENT MIX count share price_change 77,789,196 90.05% best_bid_ask 8,152,062 9.44% book 383,460 0.44% last_trade_price 56,784 0.07% tick_size_change 2,928 <0.01% market_resolved 1,119 <0.01% new_market 975 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,152,188 8,152,062 126 135 FULL book 383,476 383,460 16 112,908 FULL last_trade_price 56,785 56,784 1 0 FULL market_resolved 1,119 1,119 0 0 FULL new_market 975 975 0 0 FULL price_change 77,791,362 77,789,196 2,166 348 FULL tick_size_change 2,928 2,928 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,151,416 7,872,080 5ms 9ms 83ms 12.9s 0 transport_latency_assumed best_bid_ask e 8,148,817 17,134 40ms 46ms 190ms 11.5s 0 transport_latency_assumed best_bid_ask f 8,149,962 7,252 46ms 53ms 190ms 7.8s 0 transport_latency_assumed best_bid_ask g 8,147,430 590 86ms 103ms 353ms 17.7s 0 transport_latency_assumed best_bid_ask h 8,150,332 255,006 17ms 22ms 114ms 8.8s 0 transport_latency_assumed book c 196,993 176,844 12ms 7.1h 17.3d 102.0d 0 book_staleness book e 172,101 40,166 74ms 3.3h 6.9d 102.0d 0 book_staleness book f 188,677 62,524 124ms 6.1h 15.3d 102.0d 0 book_staleness book g 203,623 74,439 434ms 8.1h 17.2d 102.0d 0 book_staleness book h 148,339 29,487 23ms 43.3min 1.5d 102.0d 0 book_staleness last_trade_price c 56,743 54,354 10ms 40ms 189ms 5.0s 0 transport_latency_assumed last_trade_price e 56,371 150 48ms 349ms 4.7s 11.5s 0 transport_latency_assumed last_trade_price f 56,683 116 54ms 298ms 4.3s 7.8s 0 transport_latency_assumed last_trade_price g 56,286 19 102ms 660ms 12.1s 17.8s 0 transport_latency_assumed last_trade_price h 56,511 2,145 23ms 85ms 608ms 7.6s 0 transport_latency_assumed market_resolved c 1,097 1,077 5ms 11ms 67ms 200ms 0 transport_latency_assumed market_resolved e 1,097 15 44ms 203ms 59.9s 1.0min 0 transport_latency_assumed market_resolved f 1,097 9 52ms 230ms 59.8s 1.0min 0 transport_latency_assumed market_resolved g 1,097 not meas. 97ms 399ms 1.0s 59.3s 0 transport_latency_assumed market_resolved h 1,097 18 19ms 90ms 186ms 58.4s 0 transport_latency_assumed new_market c 673 430 65ms 20.7s 1.5min 2.7min 0 transport_latency_assumed new_market e 673 128 126ms 13.6s 1.2min 2.1min 0 transport_latency_assumed new_market f 673 86 136ms 14.7s 1.7min 2.1min 0 transport_latency_assumed new_market g 673 46 233ms 18.8s 1.2min 2.1min 0 transport_latency_assumed new_market h 673 285 64ms 14.7s 1.9min 4.6min 0 transport_latency_assumed price_change c 77,773,569 75,048,316 5ms 10ms 94ms 13.7s 0 transport_latency_assumed price_change e 77,656,935 168,515 40ms 52ms 379ms 11.5s 0 transport_latency_assumed price_change f 77,738,069 75,997 46ms 59ms 347ms 7.8s 0 transport_latency_assumed price_change g 77,689,812 11,635 87ms 113ms 684ms 17.7s 0 transport_latency_assumed price_change h 77,699,245 2,484,733 17ms 24ms 157ms 8.8s 0 transport_latency_assumed tick_size_change c 2,928 2,890 5ms 7ms 19ms 47ms 0 transport_latency_assumed tick_size_change e 2,928 not meas. 40ms 56ms 116ms 266ms 0 transport_latency_assumed tick_size_change f 2,928 not meas. 46ms 49ms 68ms 130ms 0 transport_latency_assumed tick_size_change g 2,928 not meas. 85ms 98ms 196ms 1.0s 0 transport_latency_assumed tick_size_change h 2,928 38 17ms 24ms 49ms 208ms 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-08/21/2026-09-08T21.parquet sha256sum 2026-09-08T21.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.