Hour audit: 2026-09-04T18
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-04T18 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-04T18:00:00.023523588+00:00 · last event 2026-09-04T18:59:59.999972948+00:00
VOLUME 109,890,148 rows · 1,150,390,706 bytes (1.07 GiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 109,446,571 · h: 109,430,147 · e: 109,369,767 · b: 105,319,183 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 18,791 (0.02%) · h: 75,638 (0.07%) · e: 109,368,862 (99.53%) · b: 426,857 (0.39%) (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,890,148 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 d3dedf4139e0d7abd8c2b29b1a9f70c2486a32377b37f7027180140cf45306f3
the corpus checksum ledger names this file with the same digest
joined 109,891,739 to merged 109,890,148, minus 1,591 (minus 0.0014%)
boundary drops 1,591 · 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-04T20:10:43Z 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 11,853,402 130,246,070 0-45 fe876910e91bce55eff5323a1ee763603176c04cdc9087f4d8a722b40619baf8 book 564,781 57,799,795 46-48 1f17c44cba0513234009c040753c15e72dbdef15f9fe80dcedf75e593f4f92fc last_trade_price 66,212 3,722,538 49-49 f2ea7ba78efd48ce95f4724acf24c4c21e7d8ac836917da1e6f868f227f95fd7 market_resolved 947 153,596 50-50 a390be6e8604327a95050fca5cdeefbae123d48131a1adbd3c92a3651d93f9e8 new_market 3,142 330,790 51-51 4fa30a4f1960f7f84c587dfcfb929f60b85f02e1d484462756e00332d2455c77 price_change 97,394,388 956,622,099 52-423 a144a47a41a17f8d127d62a49f3446e7fc4b49387544257cad2bf007198cda1d tick_size_change 7,276 263,366 424-424 9f9592e61e3d033e633d423a3a6e3d6fdb3d120f9a3a429437dee3b81429d05a EVENT MIX count share price_change 97,394,388 88.63% best_bid_ask 11,853,402 10.79% book 564,781 0.51% last_trade_price 66,212 0.06% tick_size_change 7,276 <0.01% new_market 3,142 <0.01% market_resolved 947 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,853,531 11,853,402 129 948 FULL book 565,247 564,781 466 189,823 FULL last_trade_price 66,214 66,212 2 119 FULL market_resolved 947 947 0 3 FULL new_market 3,142 3,142 0 0 FULL price_change 97,395,382 97,394,388 994 456 FULL tick_size_change 7,276 7,276 0 50 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 11,375,059 226 50ms 70ms 341ms 12.5s 0 transport_latency_assumed best_bid_ask c 11,852,348 1,269 5ms 9ms 139ms 6.2s 0 transport_latency_assumed best_bid_ask e 11,847,683 11,847,583 40ms 60ms 372ms 19.7s 0 transport_latency_assumed best_bid_ask h 11,851,164 4,324 19ms 29ms 327ms 46.5s 0 transport_latency_assumed book b 547,328 410,143 1.5min 12.0h 28.8d 97.8d 0 book_staleness book c 148,596 9,913 7ms 132ms 4.7h 97.9d 0 book_staleness book e 141,396 141,382 43ms 258ms 13.1min 8.0d 0 book_staleness book h 140,838 3,343 23ms 83ms 7.4s 79.2d 0 book_staleness last_trade_price b 62,515 7 61ms 187ms 1.9s 12.4s 0 transport_latency_assumed last_trade_price c 66,186 4 10ms 40ms 300ms 5.0s 0 transport_latency_assumed last_trade_price e 65,883 65,882 47ms 175ms 2.4s 19.7s 0 transport_latency_assumed last_trade_price h 66,172 319 24ms 71ms 685ms 45.1s 0 transport_latency_assumed market_resolved b 917 14 52ms 390ms 4.5min 4.5min 0 transport_latency_assumed market_resolved c 920 13 5ms 13ms 59.8s 59.8s 0 transport_latency_assumed market_resolved e 920 920 40ms 204ms 50.2s 51.8s 0 transport_latency_assumed market_resolved h 920 not meas. 19ms 131ms 46.5s 48.7s 0 transport_latency_assumed new_market b 2,177 115 229ms 11.3s 29.7s 4.6min 0 transport_latency_assumed new_market c 2,177 336 85ms 19.1s 34.4s 1.2min 0 transport_latency_assumed new_market e 2,177 2,177 198ms 14.9s 36.2s 2.1min 0 transport_latency_assumed new_market h 2,177 514 144ms 13.6s 32.4s 2.0min 0 transport_latency_assumed price_change b 93,324,111 16,352 51ms 81ms 431ms 12.6s 0 transport_latency_assumed price_change c 97,369,068 7,256 5ms 10ms 164ms 6.9s 0 transport_latency_assumed price_change e 97,304,432 97,303,642 40ms 76ms 526ms 19.7s 0 transport_latency_assumed price_change h 97,361,600 67,138 19ms 33ms 364ms 46.7s 0 transport_latency_assumed tick_size_change b 7,076 not meas. 50ms 63ms 138ms 308ms 0 transport_latency_assumed tick_size_change c 7,276 not meas. 5ms 8ms 31ms 261ms 0 transport_latency_assumed tick_size_change e 7,276 7,276 40ms 105ms 181ms 3.9s 0 transport_latency_assumed tick_size_change h 7,276 not meas. 19ms 26ms 96ms 1.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-04/18/2026-09-04T18.parquet sha256sum 2026-09-04T18.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.