Hour audit: 2026-09-12T19
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-12T19 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-12T19:00:00.000522747+00:00 · last event 2026-09-12T19:59:59.999304341+00:00
VOLUME 137,031,122 rows · 1,524,393,863 bytes (1.42 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 131,635,061 · e: 131,595,413 · g: 120,868,516 · f: 120,771,733 · c: 52,559,264 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 80,536,674 (58.77%) · e: 4,900,673 (3.58%) · g: 304,605 (0.22%) · f: 1,477,471 (1.08%) · c: 49,811,699 (36.35%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 ff2c2e7db48a56f27a40aa70df0305607bac09206a14c05441d3b184c15cc78d
the corpus checksum ledger names this file with the same digest
joined 137,061,992 to merged 137,031,122, minus 30,870 (minus 0.0225%)
boundary drops 30,870 · 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-12T21:01:41Z 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 12,892,427 149,400,376 0-49 dcfa4d3d36411e56d86eaaf7bc93800fb37f08aeea78b39eb47499c1274a5c13 book 5,511,408 144,346,633 50-71 bb73ccf880a25721cf7ad96f381ee9d2afb15d8b3f95f66d295273c019a497e5 last_trade_price 78,309 4,434,115 72-72 cf23041eef3ff7623b37914c228e428714c2455c62b214b6158eaa68e40dfacc market_resolved 4,188 550,556 73-73 b306fb55438b8fe456c2c6f9b516994c91f3633f5bb8b53952422a589ed850c6 new_market 31,712 697,373 74-74 9e794255a845630b223bfe26b92088eb6b8ea8080f943b71eac194b3df2cdf9d price_change 118,502,002 1,222,994,576 75-527 43c5d6a92ef7bd3c9913e4f6cd9453ce0f724de73b5c8b2f95fee921ac5e52fe tick_size_change 11,076 408,937 528-528 76f6a92a2ebe84af13dacfecbded40334c405238c39ea5a44d4cbf66e9721f17 EVENT MIX count share price_change 118,502,002 86.48% best_bid_ask 12,892,427 9.41% book 5,511,408 4.02% last_trade_price 78,309 0.06% new_market 31,712 0.02% tick_size_change 11,076 <0.01% market_resolved 4,188 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,892,668 12,892,427 241 22,614 FULL book 5,539,923 5,511,408 28,515 196,153 FULL last_trade_price 78,311 78,309 2 1,869 FULL market_resolved 4,192 4,188 4 1,963 FULL new_market 31,736 31,712 24 2,021 FULL price_change 118,504,086 118,502,002 2,084 22,006 FULL tick_size_change 11,076 11,076 0 1,699 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 4,740,822 4,491,546 6ms 16ms 153ms 6.6s 0 transport_latency_assumed best_bid_ask e 12,888,066 471,772 42ms 53ms 295ms 16.1s 0 transport_latency_assumed best_bid_ask f 11,771,363 112,739 47ms 60ms 305ms 11.0s 0 transport_latency_assumed best_bid_ask g 11,780,288 11,231 78ms 109ms 610ms 35.0s 0 transport_latency_assumed best_bid_ask h 12,890,145 7,805,139 19ms 37ms 366ms 50.6s 0 transport_latency_assumed book c 5,207,283 5,000,419 18.0min 1.1d 34.3d 105.9d 0 book_staleness book e 168,393 9,614 45ms 368ms 8.6s 87.3d 0 book_staleness book f 948,285 229,624 6.5min 1.0d 31.0d 105.9d 0 book_staleness book g 963,375 171,146 6.7min 1.1d 31.0d 105.9d 0 book_staleness book h 169,887 100,605 23ms 84ms 3.1s 87.4d 0 book_staleness last_trade_price c 27,427 25,780 12ms 48ms 280ms 4.9s 0 transport_latency_assumed last_trade_price e 77,400 2,830 52ms 273ms 4.5s 16.2s 0 transport_latency_assumed last_trade_price f 70,997 1,234 57ms 236ms 3.6s 11.1s 0 transport_latency_assumed last_trade_price g 69,733 129 97ms 1.4s 11.5s 35.0s 0 transport_latency_assumed last_trade_price h 78,163 48,336 25ms 86ms 742ms 10.3s 0 transport_latency_assumed market_resolved c 1,430 1,375 6ms 17ms 298ms 3.2s 0 transport_latency_assumed market_resolved e 3,356 133 45ms 163ms 469ms 54.7s 0 transport_latency_assumed market_resolved f 3,733 735 90ms 10.1min 13.4min 13.8min 0 transport_latency_assumed market_resolved g 3,765 30 139ms 10.5min 13.8min 14.3min 0 transport_latency_assumed market_resolved h 3,356 1,915 32ms 69ms 772ms 47.0s 0 transport_latency_assumed new_market c 31,340 30,031 51.2min 1.7h 2.0h 2.1h 0 transport_latency_assumed new_market e 1,569 347 207ms 20.7s 30.5s 50.4min 0 transport_latency_assumed new_market f 1,777 471 277ms 4.7min 12.1min 1.1h 0 transport_latency_assumed new_market g 1,807 337 473ms 9.4min 32.9min 1.1h 0 transport_latency_assumed new_market h 1,569 526 178ms 20.3s 36.1s 37.1min 0 transport_latency_assumed price_change c 42,546,674 40,258,420 7ms 16ms 169ms 8.3s 0 transport_latency_assumed price_change e 118,445,553 4,415,688 42ms 58ms 369ms 16.2s 0 transport_latency_assumed price_change f 107,965,054 1,132,561 47ms 66ms 376ms 11.1s 0 transport_latency_assumed price_change g 108,039,072 121,725 78ms 125ms 811ms 35.0s 0 transport_latency_assumed price_change h 118,480,865 72,573,608 19ms 40ms 399ms 50.7s 0 transport_latency_assumed tick_size_change c 4,288 4,128 7ms 15ms 47ms 216ms 0 transport_latency_assumed tick_size_change e 11,076 289 42ms 50ms 351ms 632ms 0 transport_latency_assumed tick_size_change f 10,524 107 47ms 81ms 348ms 672ms 0 transport_latency_assumed tick_size_change g 10,476 7 78ms 100ms 640ms 1.9s 0 transport_latency_assumed tick_size_change h 11,076 6,545 19ms 32ms 303ms 4.9s 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-12/19/2026-09-12T19.parquet sha256sum 2026-09-12T19.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.