Hour audit: 2026-09-10T11
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-10T11 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-10T11:00:00.001518674+00:00 · last event 2026-09-10T11:59:59.999996671+00:00
VOLUME 110,826,273 rows · 1,169,887,305 bytes (1.09 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 110,386,004 · f: 110,371,260 · e: 110,365,000 · g: 110,347,524 · c: 105,615,593 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 10,032,360 (9.05%) · f: 187,360 (0.17%) · e: 650,276 (0.59%) · g: 36,862 (0.03%) · c: 99,919,415 (90.16%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 110,826,273 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 b0e950ac92ecf67b4e84a40fa1384db81211bd4131aed81fef69381e11e7d060
the corpus checksum ledger names this file with the same digest
joined 110,830,094 to merged 110,826,273, minus 3,821 (minus 0.0034%)
boundary drops 3,821 · 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-10T12:58:53Z 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,362,512 116,566,208 0-39 81d93f718460dc84924f94aaec07f79366db4db2b1690f50f82778831880c8c2 book 543,151 58,138,769 40-42 334b7eaee99317e1600656e9b4ce753628fa94b3e22647afc201b56d016e6601 last_trade_price 61,675 3,454,574 43-43 4b757507d100fd2d0b07a9d00fcd44c824a36406c095cfdf7ca8e467ff3557b7 market_resolved 850 133,804 44-44 378f501ead089e6baec8bc81173c848c9e0c758c73503e6ed7a822d15cc6b460 new_market 1,183 128,156 45-45 376e34bebef1a7933bdf52747c7021ba26bce5749ebd9c35087b81cdd8935fe9 price_change 99,853,786 990,088,279 46-426 270e2ee4197de2c09c894ae72cc97cb9ad8616a9c6f280dbc338f31cf3b1edb3 tick_size_change 3,116 114,824 427-427 4eb5412416f345697010ce7d37146cfb3f95dce62ff39bb54cfd6c59743f442c EVENT MIX count share price_change 99,853,786 90.10% best_bid_ask 10,362,512 9.35% book 543,151 0.49% last_trade_price 61,675 0.06% tick_size_change 3,116 <0.01% new_market 1,183 <0.01% market_resolved 850 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,362,721 10,362,512 209 1,002 FULL book 543,171 543,151 20 193,422 FULL last_trade_price 61,675 61,675 0 81 FULL market_resolved 850 850 0 16 FULL new_market 1,183 1,183 0 0 FULL price_change 99,857,378 99,853,786 3,592 347 FULL tick_size_change 3,116 3,116 0 44 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,914,196 9,388,227 5ms 13ms 126ms 6.8s 0 transport_latency_assumed best_bid_ask e 10,359,732 58,210 38ms 46ms 181ms 5.2s 0 transport_latency_assumed best_bid_ask f 10,360,262 15,911 47ms 58ms 206ms 5.4s 0 transport_latency_assumed best_bid_ask g 10,359,173 2,599 78ms 102ms 358ms 30.8s 0 transport_latency_assumed best_bid_ask h 10,360,918 897,565 17ms 28ms 161ms 28.8s 0 transport_latency_assumed book c 528,445 517,260 5.1min 22.5h 28.7d 103.5d 0 book_staleness book e 130,968 3,100 41ms 292ms 7.4min 84.9d 0 book_staleness book f 130,766 1,919 50ms 273ms 1.2min 85.0d 0 book_staleness book g 137,595 5,555 87ms 761ms 15.4h 85.0d 0 book_staleness book h 130,468 15,317 21ms 80ms 10.5s 84.9d 0 book_staleness last_trade_price c 58,113 53,954 11ms 53ms 304ms 5.0s 0 transport_latency_assumed last_trade_price e 61,444 509 48ms 221ms 2.1s 5.2s 0 transport_latency_assumed last_trade_price f 61,588 220 58ms 226ms 1.9s 5.5s 0 transport_latency_assumed last_trade_price g 61,464 149 93ms 298ms 3.7s 9.3s 0 transport_latency_assumed last_trade_price h 61,568 6,843 24ms 85ms 494ms 6.1s 0 transport_latency_assumed market_resolved c 820 786 5ms 17ms 5.3min 5.3min 0 transport_latency_assumed market_resolved e 836 4 39ms 119ms 495ms 596ms 0 transport_latency_assumed market_resolved f 836 3 47ms 175ms 460ms 721ms 0 transport_latency_assumed market_resolved g 836 not meas. 84ms 243ms 754ms 1.1s 0 transport_latency_assumed market_resolved h 836 57 18ms 70ms 365ms 1.2s 0 transport_latency_assumed new_market c 832 466 98ms 19.4s 38.9s 4.2min 0 transport_latency_assumed new_market e 832 143 163ms 16.6s 29.5s 52.5s 0 transport_latency_assumed new_market f 832 131 178ms 12.9s 25.2s 53.7s 0 transport_latency_assumed new_market g 832 141 310ms 18.9s 28.4s 59.1s 0 transport_latency_assumed new_market h 832 302 127ms 13.8s 24.3s 1.0min 0 transport_latency_assumed price_change c 95,110,247 89,955,867 5ms 14ms 135ms 7.1s 0 transport_latency_assumed price_change e 99,808,072 588,306 38ms 52ms 305ms 5.2s 0 transport_latency_assumed price_change f 99,813,860 169,176 47ms 65ms 315ms 5.5s 0 transport_latency_assumed price_change g 99,784,508 28,418 79ms 116ms 515ms 30.9s 0 transport_latency_assumed price_change h 99,828,266 9,112,019 17ms 31ms 192ms 29.2s 0 transport_latency_assumed tick_size_change c 2,940 2,855 5ms 9ms 44ms 135ms 0 transport_latency_assumed tick_size_change e 3,116 4 38ms 72ms 121ms 230ms 0 transport_latency_assumed tick_size_change f 3,116 not meas. 46ms 51ms 131ms 222ms 0 transport_latency_assumed tick_size_change g 3,116 not meas. 77ms 91ms 183ms 2.2s 0 transport_latency_assumed tick_size_change h 3,116 257 17ms 28ms 79ms 2.4s 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/11/2026-09-10T11.parquet sha256sum 2026-09-10T11.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.