Hour audit: 2026-09-08T11
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-08T11 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-08T11:00:00.000005211+00:00 · last event 2026-09-08T11:59:59.999984560+00:00
VOLUME 99,456,324 rows · 1,005,561,393 bytes (958.98 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 99,428,752 · h: 99,428,746 · e: 99,413,079 · f: 99,391,637 · g: 99,375,551 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 94,566,746 (95.08%) · h: 4,270,838 (4.29%) · e: 395,303 (0.40%) · f: 190,118 (0.19%) · g: 33,319 (0.03%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 99,456,324 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 4cde7d05bc64acac046f9eb6d113ba1c14eeb569d844329ab3586437eda0002f
the corpus checksum ledger names this file with the same digest
joined 99,460,274 to merged 99,456,324, minus 3,950 (minus 0.0040%)
boundary drops 3,950 · 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-08T12:56:29Z 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 9,747,971 107,503,923 0-37 d063cc2e48a4ee2eb4d23df0758ace92976dfcfa30ecbc83ef095ec689a7fee7 book 146,636 15,030,830 38-38 a4e34b67ddd3eddbf0483ecaadaa0f64065ed9e7eda0140cd0bac6d229e20bef last_trade_price 61,554 3,455,771 39-39 180d0739ff7549af28668804da8beaf2f729c188ce75c0e9be878fa12ffac86a market_resolved 1,058 163,807 40-40 d05271a7ae0718e326215ec8c4a9904229a96ddbddab3f49e244fb2dae685465 new_market 2,551 257,960 41-41 e3aea86b2c4a1b0560e7055d284cf171cd25b675a09d55eacde6ee6508a10f44 price_change 89,492,734 877,876,100 42-383 e254b0600867b367fa0afc4475346e0d507c677757a82c473cf80f677bccb573 tick_size_change 3,820 137,159 384-384 e703a64fb8e08345d7c91a7b177b768a0c96ffc57758d6ab699d01f6f3464120 EVENT MIX count share price_change 89,492,734 89.98% best_bid_ask 9,747,971 9.80% book 146,636 0.15% last_trade_price 61,554 0.06% tick_size_change 3,820 <0.01% new_market 2,551 <0.01% market_resolved 1,058 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,748,169 9,747,971 198 178 FULL book 146,636 146,636 0 7,793 FULL last_trade_price 61,556 61,554 2 0 FULL market_resolved 1,058 1,058 0 0 FULL new_market 2,551 2,551 0 0 FULL price_change 89,496,484 89,492,734 3,750 82 FULL tick_size_change 3,820 3,820 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,747,265 9,284,280 5ms 11ms 144ms 7.8s 0 transport_latency_assumed best_bid_ask e 9,746,170 37,137 40ms 48ms 216ms 8.3s 0 transport_latency_assumed best_bid_ask f 9,745,753 17,438 47ms 56ms 230ms 6.6s 0 transport_latency_assumed best_bid_ask g 9,744,858 2,021 81ms 101ms 457ms 26.7s 0 transport_latency_assumed best_bid_ask h 9,747,120 407,095 17ms 24ms 214ms 9.0s 0 transport_latency_assumed book c 129,824 121,146 7ms 32ms 3.1s 83.0d 0 book_staleness book e 130,395 2,957 43ms 308ms 7.8s 101.6d 0 book_staleness book f 130,742 2,805 49ms 239ms 1.6min 83.0d 0 book_staleness book g 141,234 13,217 84ms 3.3s 23.3h 83.1d 0 book_staleness book h 129,272 6,511 21ms 97ms 2.7s 8.7s 0 book_staleness last_trade_price c 61,436 58,069 10ms 43ms 240ms 5.4s 0 transport_latency_assumed last_trade_price e 61,473 404 47ms 208ms 4.6s 8.3s 0 transport_latency_assumed last_trade_price f 61,387 196 53ms 169ms 3.0s 6.6s 0 transport_latency_assumed last_trade_price g 61,384 96 91ms 226ms 5.2s 26.7s 0 transport_latency_assumed last_trade_price h 61,527 2,789 23ms 88ms 455ms 8.8s 0 transport_latency_assumed market_resolved c 1,010 902 5ms 42ms 1.0min 1.0min 0 transport_latency_assumed market_resolved e 1,010 82 42ms 351ms 59.0s 59.1s 0 transport_latency_assumed market_resolved f 1,010 2 47ms 326ms 59.1s 59.2s 0 transport_latency_assumed market_resolved g 1,010 not meas. 85ms 385ms 59.1s 59.3s 0 transport_latency_assumed market_resolved h 1,010 72 17ms 99ms 56.7s 56.9s 0 transport_latency_assumed new_market c 1,685 993 101ms 32.8s 58.4s 1.5min 0 transport_latency_assumed new_market e 1,685 313 185ms 32.9s 57.4s 1.5min 0 transport_latency_assumed new_market f 1,685 315 186ms 30.5s 56.9s 1.5min 0 transport_latency_assumed new_market g 1,685 225 313ms 32.8s 55.8s 1.3min 0 transport_latency_assumed new_market h 1,685 705 134ms 29.7s 1.0min 1.5min 0 transport_latency_assumed price_change c 89,483,712 85,097,940 5ms 13ms 157ms 7.8s 0 transport_latency_assumed price_change e 89,468,526 354,376 41ms 56ms 362ms 8.3s 0 transport_latency_assumed price_change f 89,447,240 169,340 47ms 64ms 342ms 6.6s 0 transport_latency_assumed price_change g 89,421,560 17,760 81ms 119ms 634ms 26.7s 0 transport_latency_assumed price_change h 89,484,312 3,853,318 17ms 28ms 253ms 9.1s 0 transport_latency_assumed tick_size_change c 3,820 3,416 5ms 28ms 235ms 381ms 0 transport_latency_assumed tick_size_change e 3,820 34 41ms 77ms 259ms 565ms 0 transport_latency_assumed tick_size_change f 3,820 22 47ms 90ms 283ms 452ms 0 transport_latency_assumed tick_size_change g 3,820 not meas. 83ms 203ms 696ms 987ms 0 transport_latency_assumed tick_size_change h 3,820 348 17ms 34ms 325ms 1.1s 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/11/2026-09-08T11.parquet sha256sum 2026-09-08T11.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.