Hour audit: 2026-09-09T18
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-09T18 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-09T18:00:00.000413973+00:00 · last event 2026-09-09T18:59:59.999384710+00:00
VOLUME 111,564,029 rows · 1,226,737,799 bytes (1.14 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 109,559,569 · f: 109,506,986 · e: 109,474,122 · g: 109,368,776 · c: 88,193,287 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 26,835,907 (24.05%) · f: 565,823 (0.51%) · e: 1,378,664 (1.24%) · g: 52,623 (0.05%) · c: 82,731,012 (74.16%) (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 111,564,029 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 75d2d7074d563f61324ce43ad6c481ac244f7fe2da9178b8210a19f792bc2382
the corpus checksum ledger names this file with the same digest
joined 111,566,842 to merged 111,564,029, minus 2,813 (minus 0.0025%)
boundary drops 2,813 · 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-09T20:02:31Z 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,848,686 124,085,183 0-41 7fcdd489e931e133e4c672435ad6470d97b3baf0b721d54271c1ef3679d8a77d book 2,182,194 94,568,994 42-50 2c1234c52187a53bedb0cfe7481b329bfeace4c61fce508e67f574dff722a34e last_trade_price 74,320 4,392,037 51-51 38085a4bcd46ba7756b607a7fa65326430295a306cc13bfdfcd785d85a6a9575 market_resolved 1,430 187,088 52-52 b60dcd6280ab506f8d909922ea0bae901ab5991d6e67f2d42f9faf95b9e12e58 new_market 3,155 297,146 53-53 cd4d0d0bd37cb1d0cbb93c5d4c04f8a7b27083b3be3e7981711e955446b5123e price_change 98,450,924 1,001,813,148 54-429 effd5d5c82a5e3272db058933a1b5228e050c24a45da2334d60e5cf3c0f2798d tick_size_change 3,320 122,704 430-430 85601fc82eef8d5139d771f60ca81e14cba5033c27f3a078114aebf2a7806e15 EVENT MIX count share price_change 98,450,924 88.25% best_bid_ask 10,848,686 9.72% book 2,182,194 1.96% last_trade_price 74,320 0.07% tick_size_change 3,320 <0.01% new_market 3,155 <0.01% market_resolved 1,430 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,848,928 10,848,686 242 2,874 FULL book 2,182,626 2,182,194 432 192,685 FULL last_trade_price 74,321 74,320 1 539 FULL market_resolved 1,430 1,430 0 50 FULL new_market 3,155 3,155 0 0 FULL price_change 98,453,062 98,450,924 2,138 1,766 FULL tick_size_change 3,320 3,320 0 134 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,547,957 8,023,115 6ms 16ms 252ms 11.3s 0 transport_latency_assumed best_bid_ask e 10,844,625 133,645 41ms 55ms 312ms 16.8s 0 transport_latency_assumed best_bid_ask f 10,844,764 52,174 45ms 64ms 334ms 16.0s 0 transport_latency_assumed best_bid_ask g 10,840,862 4,125 84ms 139ms 703ms 47.0s 0 transport_latency_assumed best_bid_ask h 10,844,650 2,635,627 18ms 32ms 357ms 54.5s 0 transport_latency_assumed book c 2,126,965 2,094,887 28.4min 21.8h 32.0d 102.9d 0 book_staleness book e 161,693 6,640 44ms 482ms 6.8h 102.8d 0 book_staleness book f 159,326 3,686 48ms 355ms 1.7h 84.4d 0 book_staleness book g 170,566 7,288 94ms 9.1s 22.9h 102.9d 0 book_staleness book h 214,352 69,693 33ms 3.1h 6.8d 102.9d 0 book_staleness last_trade_price c 59,171 55,335 11ms 55ms 335ms 8.0s 0 transport_latency_assumed last_trade_price e 74,039 894 56ms 244ms 2.2s 16.8s 0 transport_latency_assumed last_trade_price f 74,211 585 61ms 238ms 3.4s 16.0s 0 transport_latency_assumed last_trade_price g 73,377 69 102ms 438ms 8.6s 47.0s 0 transport_latency_assumed last_trade_price h 74,084 17,437 25ms 103ms 656ms 37.3s 0 transport_latency_assumed market_resolved c 1,253 1,207 6ms 5.7min 8.6min 11.0min 0 transport_latency_assumed market_resolved e 1,147 6 42ms 201ms 50.9s 53.6s 0 transport_latency_assumed market_resolved f 1,147 2 47ms 208ms 57.2s 59.8s 0 transport_latency_assumed market_resolved g 1,147 6 89ms 375ms 1.1s 1.8s 0 transport_latency_assumed market_resolved h 1,147 209 19ms 85ms 49.9s 1.0min 0 transport_latency_assumed new_market c 2,029 1,160 125ms 4.8min 5.5min 6.4min 0 transport_latency_assumed new_market e 1,916 527 180ms 18.0s 50.1s 1.7min 0 transport_latency_assumed new_market f 1,916 471 170ms 15.0s 39.7s 1.5min 0 transport_latency_assumed new_market g 1,916 255 292ms 16.7s 50.9s 1.6min 0 transport_latency_assumed new_market h 1,916 742 135ms 16.3s 47.9s 1.7min 0 transport_latency_assumed price_change c 77,453,128 72,552,656 6ms 18ms 275ms 11.3s 0 transport_latency_assumed price_change e 98,387,382 1,236,899 41ms 69ms 481ms 16.9s 0 transport_latency_assumed price_change f 98,422,302 508,902 45ms 79ms 498ms 16.1s 0 transport_latency_assumed price_change g 98,277,588 40,880 85ms 168ms 1.3s 47.0s 0 transport_latency_assumed price_change h 98,420,100 24,111,587 18ms 37ms 390ms 54.5s 0 transport_latency_assumed tick_size_change c 2,784 2,652 6ms 16ms 153ms 629ms 0 transport_latency_assumed tick_size_change e 3,320 53 40ms 48ms 146ms 311ms 0 transport_latency_assumed tick_size_change f 3,320 3 45ms 56ms 206ms 488ms 0 transport_latency_assumed tick_size_change g 3,320 not meas. 81ms 112ms 395ms 2.5s 0 transport_latency_assumed tick_size_change h 3,320 612 18ms 28ms 113ms 3.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-09/18/2026-09-09T18.parquet sha256sum 2026-09-09T18.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.