Hour audit: 2026-09-08T16
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-08T16 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-08T16:00:00.000008291+00:00 · last event 2026-09-08T16:59:59.997689285+00:00
VOLUME 103,986,349 rows · 1,131,582,224 bytes (1.05 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 102,803,509 · h: 102,799,082 · e: 102,700,078 · g: 102,597,730 · c: 90,678,820 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 758,702 (0.73%) · h: 17,599,098 (16.92%) · e: 1,234,569 (1.19%) · g: 70,479 (0.07%) · c: 84,323,501 (81.09%) (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 103,986,349 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 81a3d80c86fcae3d3ecdacd89aaf9d5c9ff682ba4eda8591b3df7f4ce10a6bd8
the corpus checksum ledger names this file with the same digest
joined 103,989,288 to merged 103,986,349, minus 2,939 (minus 0.0028%)
boundary drops 2,939 · 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-08T17:57:08Z 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,345,171 116,592,001 0-39 758db907256477bc8c6d625aae34551992375e71429e719dd2076754750997d4 book 1,272,624 74,726,139 40-44 061fa50b407f1c919e7f4ff4301fe7f13c6509a238c1aacbdb8b6638e958b930 last_trade_price 73,762 4,177,347 45-45 9fd8e41cbdbb1ee27d7efa651d35c5fca3c75e865b8cfef9eb490e83e3587092 market_resolved 1,883 225,889 46-46 8900c017b6ed370de43d2c717a966c98d5cf9a23fb4964ac7a9fb01e7e34fab4 new_market 7,583 655,103 47-47 82e28d95eefe9d6f4adbd477b3937ce6a9e8bc317af1dde66f7af2050b02c33a price_change 92,281,182 933,865,677 48-400 48848b670524e356532f206a4311d549d94ecbd68cb2cff15d6f28fef2c57d03 tick_size_change 4,144 154,134 401-401 f1dbadc8b2ce855871701e1d596ea8e7582ec6749dcc8a9caf4dbe8fffd63af6 EVENT MIX count share price_change 92,281,182 88.74% best_bid_ask 10,345,171 9.95% book 1,272,624 1.22% last_trade_price 73,762 0.07% new_market 7,583 <0.01% tick_size_change 4,144 <0.01% market_resolved 1,883 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,345,386 10,345,171 215 1,809 FULL book 1,272,684 1,272,624 60 178,381 FULL last_trade_price 73,762 73,762 0 267 FULL market_resolved 1,883 1,883 0 77 FULL new_market 7,583 7,583 0 0 FULL price_change 92,283,846 92,281,182 2,664 1,219 FULL tick_size_change 4,144 4,144 0 201 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,996,823 8,358,276 5ms 18ms 248ms 7.0s 0 transport_latency_assumed best_bid_ask e 10,339,827 122,794 41ms 62ms 339ms 18.8s 0 transport_latency_assumed best_bid_ask f 10,340,291 68,474 44ms 69ms 351ms 19.7s 0 transport_latency_assumed best_bid_ask g 10,332,256 4,837 88ms 178ms 737ms 40.1s 0 transport_latency_assumed best_bid_ask h 10,341,828 1,790,790 18ms 34ms 408ms 48.3s 0 transport_latency_assumed book c 1,242,332 1,225,764 19.4min 1.0d 31.0d 101.7d 0 book_staleness book e 161,450 6,196 45ms 1.5s 52.8min 83.2d 0 book_staleness book f 159,740 4,391 48ms 616ms 16.6s 83.2d 0 book_staleness book g 173,617 11,465 100ms 13.2s 1.2d 83.3d 0 book_staleness book h 159,777 24,808 24ms 230ms 8.1s 83.2d 0 book_staleness last_trade_price c 65,555 60,987 11ms 57ms 346ms 5.1s 0 transport_latency_assumed last_trade_price e 73,405 1,097 51ms 395ms 8.1s 18.8s 0 transport_latency_assumed last_trade_price f 73,544 601 54ms 293ms 5.6s 19.8s 0 transport_latency_assumed last_trade_price g 72,445 71 105ms 548ms 12.3s 40.5s 0 transport_latency_assumed last_trade_price h 73,457 11,006 24ms 128ms 714ms 10.6s 0 transport_latency_assumed market_resolved c 1,711 1,651 7ms 9.7min 14.1min 14.9min 0 transport_latency_assumed market_resolved e 1,366 30 43ms 255ms 1.0min 1.0min 0 transport_latency_assumed market_resolved f 1,366 3 46ms 265ms 1.0min 1.0min 0 transport_latency_assumed market_resolved g 1,366 not meas. 94ms 414ms 1.0s 4.8s 0 transport_latency_assumed market_resolved h 1,366 199 18ms 92ms 285ms 5.1s 0 transport_latency_assumed new_market c 5,089 3,146 252ms 6.6min 12.7min 12.9min 0 transport_latency_assumed new_market e 4,066 969 193ms 1.2min 3.0min 3.2min 0 transport_latency_assumed new_market f 4,066 788 209ms 55.7s 3.0min 3.2min 0 transport_latency_assumed new_market g 4,066 657 339ms 59.1s 2.2min 3.0min 0 transport_latency_assumed new_market h 4,066 2,023 136ms 1.1min 3.0min 3.2min 0 transport_latency_assumed price_change c 80,363,970 74,670,592 5ms 21ms 258ms 7.1s 0 transport_latency_assumed price_change e 92,115,820 1,103,446 42ms 87ms 951ms 18.8s 0 transport_latency_assumed price_change f 92,220,358 684,430 45ms 93ms 793ms 19.8s 0 transport_latency_assumed price_change g 92,009,836 53,448 89ms 230ms 2.2s 40.5s 0 transport_latency_assumed price_change h 92,214,444 15,769,266 18ms 42ms 475ms 49.2s 0 transport_latency_assumed tick_size_change c 3,340 3,085 5ms 21ms 156ms 260ms 0 transport_latency_assumed tick_size_change e 4,144 37 41ms 65ms 281ms 779ms 0 transport_latency_assumed tick_size_change f 4,144 15 44ms 81ms 243ms 498ms 0 transport_latency_assumed tick_size_change g 4,144 1 86ms 187ms 590ms 7.6s 0 transport_latency_assumed tick_size_change h 4,144 1,006 17ms 34ms 439ms 2.8s 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/16/2026-09-08T16.parquet sha256sum 2026-09-08T16.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.