Hour audit: 2026-09-03T14
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-03T14 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-03T14:00:00.003930573+00:00 · last event 2026-09-03T14:59:59.999991387+00:00
VOLUME 109,024,340 rows · 1,143,593,318 bytes (1.07 GiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured h: 107,357,647 · e: 106,100,131 · b: 98,600,536 · c: 76,767,593 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 2,537,201 (2.33%) · e: 106,098,876 (97.32%) · b: 137,481 (0.13%) · c: 250,782 (0.23%) (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 109,024,340 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 aeda1ba9d75a28e4c82e8440e8d5ffdb5988dd17f8f8c6b2a4804defd13a7886
the corpus checksum ledger names this file with the same digest
joined 109,025,913 to merged 109,024,340, minus 1,573 (minus 0.0014%)
boundary drops 1,573 · 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-03T16:39:05Z as bceh
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,395,916 120,705,525 0-39 9a18a0cdef2decddf34a192b3cc1f0daa6b84a513819e030d93ab0bf2efc8c05 book 1,027,463 78,806,247 40-43 cd4eec45af22ab075a7abf171372b947c5fad83a08c79ff5a538421af3c0062f last_trade_price 86,335 4,768,117 44-44 9fe40983d765e79b9ce038bfff2d73da2e0a2b05c98328cd193e61910ccaf871 market_resolved 1,527 210,409 45-45 60b06e02864a01c3434a9b3ffbe86cc3f5f54f40d5fc38f3f7e43f345f355fe5 new_market 2,231 218,290 46-46 b47efb1f80f41feedcf236da40b704a10cda21f209805621ac22431267c364e4 price_change 97,507,476 937,525,155 47-418 28034a8ef1058984e3665d79a2109aa8ab90c12355d13e12671a14d1f8e99ee3 tick_size_change 3,392 121,264 419-419 2f5ee4e952f5ae7626021b2624a37e78f93fb73f4003fe2ab856875f4b3c520f EVENT MIX count share price_change 97,507,476 89.44% best_bid_ask 10,395,916 9.54% book 1,027,463 0.94% last_trade_price 86,335 0.08% tick_size_change 3,392 <0.01% new_market 2,231 <0.01% market_resolved 1,527 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,396,018 10,395,916 102 7,184 FULL book 1,027,479 1,027,463 16 119,477 FULL last_trade_price 86,336 86,335 1 704 FULL market_resolved 1,527 1,527 0 30 FULL new_market 2,231 2,231 0 0 FULL price_change 97,508,930 97,507,476 1,454 20,452 FULL tick_size_change 3,392 3,392 0 305 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 10,377,475 200 49ms 76ms 533ms 26.8s 0 transport_latency_assumed best_bid_ask c 7,404,191 714 12ms 19ms 98ms 3.0s 0 transport_latency_assumed best_bid_ask e 10,371,321 10,371,237 41ms 80ms 827ms 25.5s 0 transport_latency_assumed best_bid_ask h 10,392,500 23,765 18ms 27ms 163ms 11.0s 0 transport_latency_assumed book b 443,332 121,551 28.9s 1.7h 26.0d 96.7d 0 book_staleness book c 546,497 223,335 1.6min 2.6h 29.8d 96.7d 0 book_staleness book e 466,414 466,404 35.0s 1.9h 30.9d 96.7d 0 book_staleness book h 486,092 216,173 34.1s 1.8h 26.0d 96.7d 0 book_staleness last_trade_price b 82,140 12 81ms 4.0s 14.2s 26.8s 0 transport_latency_assumed last_trade_price c 61,947 15 19ms 44ms 204ms 5.0s 0 transport_latency_assumed last_trade_price e 81,641 81,640 72ms 3.7s 12.6s 25.6s 0 transport_latency_assumed last_trade_price h 86,270 4,668 27ms 121ms 675ms 5.8s 0 transport_latency_assumed market_resolved b 1,290 not meas. 53ms 286ms 737ms 1.0s 0 transport_latency_assumed market_resolved c 1,260 236 11ms 12.5min 18.5min 20.0min 0 transport_latency_assumed market_resolved e 1,290 1,290 43ms 274ms 777ms 1.0min 0 transport_latency_assumed market_resolved h 1,290 1 20ms 87ms 276ms 5.5s 0 transport_latency_assumed new_market b 1,405 126 208ms 18.4s 1.2min 25.8min 0 transport_latency_assumed new_market c 1,406 352 163ms 9.8min 16.0min 28.4min 0 transport_latency_assumed new_market e 1,405 1,405 197ms 17.2s 1.4min 14.7min 0 transport_latency_assumed new_market h 1,405 348 101ms 15.4s 1.2min 12.1min 0 transport_latency_assumed price_change b 87,691,502 15,592 49ms 121ms 6.1s 26.8s 0 transport_latency_assumed price_change c 68,750,120 26,130 12ms 20ms 122ms 3.7s 0 transport_latency_assumed price_change e 95,174,668 95,173,508 42ms 136ms 5.3s 25.5s 0 transport_latency_assumed price_change h 96,386,698 2,292,246 19ms 32ms 226ms 11.3s 0 transport_latency_assumed tick_size_change b 3,392 not meas. 49ms 99ms 416ms 631ms 0 transport_latency_assumed tick_size_change c 2,172 not meas. 12ms 20ms 244ms 1.1s 0 transport_latency_assumed tick_size_change e 3,392 3,392 41ms 111ms 1.0s 9.9s 0 transport_latency_assumed tick_size_change h 3,392 not meas. 19ms 34ms 209ms 795ms 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-03/14/2026-09-03T14.parquet sha256sum 2026-09-03T14.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.