Hour audit: 2026-09-11T07
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-11T07 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-11T07:00:00.000912522+00:00 · last event 2026-09-11T07:59:59.998935078+00:00
VOLUME 99,753,136 rows · 1,022,527,381 bytes (975.16 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured g: 99,609,089 · c: 99,292,268 · h: 99,269,433 · f: 99,258,382 · e: 99,221,550 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 427,714 (0.43%) · c: 95,689,721 (95.93%) · h: 3,128,365 (3.14%) · f: 149,592 (0.15%) · e: 357,744 (0.36%) (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 99,753,136 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 6589455440e6ba9b5f0ca809d8343733eb7d159d8252177c2bc6fb1efe994556
the corpus checksum ledger names this file with the same digest
joined 99,758,839 to merged 99,753,136, minus 5,703 (minus 0.0057%)
boundary drops 5,703 · 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-11T08:56:43Z 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,675,694 100,569,459 0-33 052071900a382b3c232df226926957956d5fdd4f11d6766777a06ec7b268562a book 569,899 54,761,747 34-36 e1f5c657e95b534aff644b864f180ba932baddf1c796a21ecaf1878954f75e89 last_trade_price 44,364 2,591,428 37-37 6fca5bdfd55a9525ee757be5189df56d38128a5226f2969e74803bd22fe48cac market_resolved 544 89,845 38-38 a4503a734cc1831bb5edba88ece961dd70adf2088f2b04186cff98717dd6bf4c new_market 781 79,988 39-39 61e9e6922ae093d8511119ea5207bca1e41fc88e95ae226edbd0c4d9add9dbd0 price_change 90,460,306 863,235,143 40-385 8cdaa33291aba2cd0393e7fa4cc350ec91059ba4fee231ea60b9cc06e86fd1a3 tick_size_change 1,548 57,143 386-386 99f645e91a17d5743e789b3e42f2903916cac9c7659369bcb1be62735db88135 EVENT MIX count share price_change 90,460,306 90.68% best_bid_ask 8,675,694 8.70% book 569,899 0.57% last_trade_price 44,364 0.04% tick_size_change 1,548 <0.01% new_market 781 <0.01% market_resolved 544 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,676,059 8,675,694 365 118 FULL book 570,415 569,899 516 175,851 FULL last_trade_price 44,366 44,364 2 1 FULL market_resolved 544 544 0 0 FULL new_market 783 781 2 2 FULL price_change 90,465,124 90,460,306 4,818 117 FULL tick_size_change 1,548 1,548 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,675,098 8,390,148 5ms 9ms 95ms 8.0s 0 transport_latency_assumed best_bid_ask e 8,672,141 24,825 38ms 43ms 146ms 5.7s 0 transport_latency_assumed best_bid_ask f 8,674,119 7,725 44ms 50ms 159ms 5.8s 0 transport_latency_assumed best_bid_ask g 8,670,866 1,912 77ms 116ms 350ms 12.9s 0 transport_latency_assumed best_bid_ask h 8,674,906 251,084 17ms 22ms 123ms 26.9s 0 transport_latency_assumed book c 127,415 116,524 8ms 1.2h 5.7d 104.4d 0 book_staleness book e 118,763 24,236 43ms 22.0min 4.9d 104.4d 0 book_staleness book f 111,088 16,179 48ms 6.8min 3.9d 86.3d 0 book_staleness book g 511,334 389,829 6.0min 22.3h 26.9d 104.4d 0 book_staleness book h 115,073 23,131 22ms 14.9min 3.9d 85.9d 0 book_staleness last_trade_price c 44,253 42,164 10ms 43ms 244ms 5.7s 0 transport_latency_assumed last_trade_price e 44,043 168 46ms 131ms 818ms 5.7s 0 transport_latency_assumed last_trade_price f 44,272 71 52ms 124ms 769ms 4.9s 0 transport_latency_assumed last_trade_price g 44,148 43 91ms 253ms 2.2s 13.1s 0 transport_latency_assumed last_trade_price h 44,291 1,918 23ms 62ms 271ms 10.6s 0 transport_latency_assumed market_resolved c 538 516 5ms 11ms 16.7s 54.8s 0 transport_latency_assumed market_resolved e 538 not meas. 40ms 145ms 16.6s 54.4s 0 transport_latency_assumed market_resolved f 538 not meas. 47ms 192ms 16.8s 54.7s 0 transport_latency_assumed market_resolved g 538 6 85ms 288ms 563ms 894ms 0 transport_latency_assumed market_resolved h 538 22 18ms 61ms 16.4s 54.3s 0 transport_latency_assumed new_market c 510 261 105ms 13.2s 21.7s 1.3min 0 transport_latency_assumed new_market e 511 110 178ms 541ms 20.5s 1.0min 0 transport_latency_assumed new_market f 512 85 198ms 17.9s 22.5s 58.1s 0 transport_latency_assumed new_market g 511 56 312ms 13.3s 22.8s 1.0min 0 transport_latency_assumed new_market h 510 269 164ms 17.5s 21.2s 1.2min 0 transport_latency_assumed price_change c 90,442,906 87,138,652 5ms 10ms 168ms 9.6s 0 transport_latency_assumed price_change e 90,384,006 308,398 39ms 45ms 259ms 5.7s 0 transport_latency_assumed price_change f 90,426,305 125,532 45ms 52ms 271ms 5.9s 0 transport_latency_assumed price_change g 90,380,144 35,868 77ms 126ms 525ms 13.2s 0 transport_latency_assumed price_change h 90,432,567 2,851,856 17ms 24ms 227ms 27.1s 0 transport_latency_assumed tick_size_change c 1,548 1,456 5ms 11ms 216ms 574ms 0 transport_latency_assumed tick_size_change e 1,548 7 39ms 46ms 152ms 202ms 0 transport_latency_assumed tick_size_change f 1,548 not meas. 44ms 49ms 243ms 465ms 0 transport_latency_assumed tick_size_change g 1,548 not meas. 76ms 119ms 274ms 768ms 0 transport_latency_assumed tick_size_change h 1,548 85 17ms 23ms 45ms 2.2s 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-11/07/2026-09-11T07.parquet sha256sum 2026-09-11T07.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.