Hour audit: 2026-09-18T14
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-18T14 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-18T14:00:00.004527669+00:00 · last event 2026-09-18T14:59:59.999977822+00:00
VOLUME 138,653,490 rows · 1,578,412,607 bytes (1.47 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 134,956,008 · e: 129,086,313 · g: 127,833,546 · f: 112,528,235 · c: 95,985,019 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 42,814,779 (30.88%) · e: 3,898,520 (2.81%) · g: 333,582 (0.24%) · f: 1,782,763 (1.29%) · c: 89,823,846 (64.78%) (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 138,653,490 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 f5062428b6b39d0594e36a4ceecb90ed8a87a1e08072beac239555e7c8bfdfab
the corpus checksum ledger names this file with the same digest
joined 138,655,990 to merged 138,653,490, minus 2,500 (minus 0.0018%)
boundary drops 2,500 · 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-18T16:09:05Z 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 14,599,637 174,031,275 0-55 19a3750331a1aefb7318b39f65c27997a0716dbe233e278f213a6349724f6d16 book 3,705,144 149,071,655 56-70 3b4b2a6d27e39b5c660cdc49e12132fbe6eb429d600de6d5b5e7d040964c479d last_trade_price 78,037 4,610,537 71-71 2d3aa393981a464abf622d2fcbfe9fd48702c0e4265cb074a436a1e7d39ab2c9 market_resolved 1,233 135,067 72-72 e3f223144cef692a6555bb2e7c52d8a2d8758819bcc4f945204437e4743b7a42 new_market 3,707 350,135 73-73 5eaee2c28d4c8ae84bedade2f655da2598244e405835d99048bd3f175de40514 price_change 120,260,756 1,248,457,928 74-532 1bcabbfd6c19ae4b622630f91156daa1a18ecec1148d77e2df2537e64e523280 tick_size_change 4,976 181,500 533-533 853dad9c03f4734b3ee9e1858159fe87f253ffcc4a3e267adc21b34aaa949f8b EVENT MIX count share price_change 120,260,756 86.73% best_bid_ask 14,599,637 10.53% book 3,705,144 2.67% last_trade_price 78,037 0.06% tick_size_change 4,976 <0.01% new_market 3,707 <0.01% market_resolved 1,233 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 14,599,891 14,599,637 254 12,464 FULL book 3,705,354 3,705,144 210 195,071 FULL last_trade_price 78,039 78,037 2 1,788 FULL market_resolved 1,233 1,233 0 157 FULL new_market 3,707 3,707 0 0 FULL price_change 120,262,790 120,260,756 2,034 7,109 FULL tick_size_change 4,976 4,976 0 563 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,016,756 9,398,409 6ms 18ms 153ms 2.1s 0 transport_latency_assumed best_bid_ask e 13,952,955 393,146 41ms 64ms 329ms 24.0s 0 transport_latency_assumed best_bid_ask f 12,062,106 91,261 48ms 70ms 339ms 18.6s 0 transport_latency_assumed best_bid_ask g 13,951,920 16,706 82ms 128ms 675ms 40.5s 0 transport_latency_assumed best_bid_ask h 14,595,040 4,700,115 19ms 44ms 382ms 34.7s 0 transport_latency_assumed book c 2,906,448 2,651,280 3.9min 19.1h 37.8d 111.7d 0 book_staleness book e 566,454 118,946 1.1min 4.5h 27.0d 111.7d 0 book_staleness book f 1,726,595 729,226 3.1min 13.1h 37.8d 111.7d 0 book_staleness book g 568,338 152,942 1.0min 5.9h 27.0d 111.7d 0 book_staleness book h 170,177 52,750 26ms 256ms 14.0min 93.1d 0 book_staleness last_trade_price c 54,029 50,836 12ms 54ms 292ms 5.0s 0 transport_latency_assumed last_trade_price e 72,799 2,205 68ms 2.9s 10.5s 23.7s 0 transport_latency_assumed last_trade_price f 62,795 852 72ms 1.9s 11.7s 17.8s 0 transport_latency_assumed last_trade_price g 69,177 163 110ms 2.9s 19.0s 40.5s 0 transport_latency_assumed last_trade_price h 77,702 23,981 29ms 160ms 1.3s 13.5s 0 transport_latency_assumed market_resolved c 953 815 11ms 11.2min 18.8min 18.8min 0 transport_latency_assumed market_resolved e 803 34 43ms 399ms 4.8min 5.6min 0 transport_latency_assumed market_resolved f 830 103 51ms 8.7min 13.5min 13.8min 0 transport_latency_assumed market_resolved g 798 13 85ms 340ms 3.9min 4.6min 0 transport_latency_assumed market_resolved h 799 268 21ms 85ms 1.0min 1.0min 0 transport_latency_assumed new_market c 2,819 2,014 93ms 3.3min 6.9min 13.3min 0 transport_latency_assumed new_market e 2,285 468 206ms 46.5s 4.9min 5.1min 0 transport_latency_assumed new_market f 2,291 277 227ms 3.9min 5.8min 10.1min 0 transport_latency_assumed new_market g 2,220 230 283ms 20.9s 44.9s 1.5min 0 transport_latency_assumed new_market h 2,220 718 140ms 26.9s 47.0s 1.8min 0 transport_latency_assumed price_change c 83,000,662 77,717,202 6ms 21ms 180ms 3.6s 0 transport_latency_assumed price_change e 114,486,161 3,383,623 42ms 106ms 5.3s 24.0s 0 transport_latency_assumed price_change f 98,669,614 961,026 49ms 106ms 4.2s 18.6s 0 transport_latency_assumed price_change g 113,236,277 163,528 83ms 222ms 8.7s 40.5s 0 transport_latency_assumed price_change h 120,105,094 38,035,377 20ms 54ms 602ms 1.2min 0 transport_latency_assumed tick_size_change c 3,352 3,290 6ms 11ms 28ms 103ms 0 transport_latency_assumed tick_size_change e 4,856 98 41ms 54ms 211ms 680ms 0 transport_latency_assumed tick_size_change f 4,004 18 48ms 62ms 228ms 504ms 0 transport_latency_assumed tick_size_change g 4,816 not meas. 81ms 107ms 308ms 865ms 0 transport_latency_assumed tick_size_change h 4,976 1,570 19ms 37ms 154ms 1.1s 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-18/14/2026-09-18T14.parquet sha256sum 2026-09-18T14.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.