Hour audit: 2026-09-18T20
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-18T20 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-18T20:00:00.000005642+00:00 · last event 2026-09-18T20:59:59.999445440+00:00
VOLUME 111,795,235 rows · 1,231,235,285 bytes (1.15 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 110,673,834 · h: 110,464,344 · g: 109,929,273 · f: 106,322,860 · c: 101,304,649 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 1,845,645 (1.65%) · h: 13,886,723 (12.42%) · g: 61,918 (0.06%) · f: 874,827 (0.78%) · c: 95,126,122 (85.09%) (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,795,235 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 d4ae640746d8b1b39b83b3022ce0c579ad3f42d3a6b9676442cc81eee7ebe94c
the corpus checksum ledger names this file with the same digest
joined 111,806,798 to merged 111,795,235, minus 11,563 (minus 0.0103%)
boundary drops 11,563 · 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-19T00:22:45Z 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,907,970 147,045,566 0-49 91270bb4420f5e122c85632f309a375efbf8e7eaf80e31aa5ca976c6ee280f92 book 1,346,309 80,906,109 50-55 b439a69815e294ffad70c34273771f781c645eae075301dfa8bb8968b7ca070d last_trade_price 60,230 3,523,036 56-56 903078764e302d66dccead7231839997988c21b7fc328fba20470cf0d7ebcfae market_resolved 2,371 360,486 57-57 9fcca6cdedf19d24279760cb163c870dbafb4e7937ad4341a920d213919e5147 new_market 3,911 356,081 58-58 e596b22ad56109cad79012a896efb35cd1723cb0d50d19dd4cc7a1a62d3498cf price_change 97,467,656 997,524,923 59-430 b579ea145949e76f0db31d012f2cc8acebde64d1caf324e6c7492b2d8162cb29 tick_size_change 6,788 245,284 431-431 72e58dc54fb8d5199e0791589421015bfc3e498cac2253e36beeb8dcb8fd2a6a EVENT MIX count share price_change 97,467,656 87.18% best_bid_ask 12,907,970 11.55% book 1,346,309 1.20% last_trade_price 60,230 0.05% tick_size_change 6,788 <0.01% new_market 3,911 <0.01% market_resolved 2,371 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,908,249 12,907,970 279 2,151 FULL book 1,355,531 1,346,309 9,222 211,113 FULL last_trade_price 60,232 60,230 2 335 FULL market_resolved 2,371 2,371 0 14 FULL new_market 3,911 3,911 0 0 FULL price_change 97,469,716 97,467,656 2,060 1,413 FULL tick_size_change 6,788 6,788 0 190 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,762,770 11,097,072 5ms 15ms 202ms 24.9s 0 transport_latency_assumed best_bid_ask e 12,902,046 196,831 41ms 61ms 358ms 18.3s 0 transport_latency_assumed best_bid_ask f 12,349,153 57,606 47ms 65ms 358ms 29.0s 0 transport_latency_assumed best_bid_ask g 12,899,552 6,291 81ms 134ms 760ms 37.1s 0 transport_latency_assumed best_bid_ask h 12,905,917 1,550,170 18ms 37ms 467ms 48.7s 0 transport_latency_assumed book c 1,054,045 810,060 11.1min 4.8h 34.4d 111.9d 0 book_staleness book e 467,534 174,186 4.1min 4.8h 27.3d 111.9d 0 book_staleness book f 749,567 335,646 8.2min 4.7h 34.1d 111.9d 0 book_staleness book g 137,597 6,458 94ms 11.3s 5.1h 93.4d 0 book_staleness book h 132,839 19,959 23ms 271ms 4.9h 93.4d 0 book_staleness last_trade_price c 54,108 50,776 11ms 57ms 394ms 5.0s 0 transport_latency_assumed last_trade_price e 59,494 839 62ms 716ms 6.9s 18.4s 0 transport_latency_assumed last_trade_price f 57,424 307 67ms 708ms 7.5s 29.2s 0 transport_latency_assumed last_trade_price g 58,396 51 105ms 1.4s 16.8s 37.1s 0 transport_latency_assumed last_trade_price h 60,001 8,257 26ms 132ms 917ms 43.9s 0 transport_latency_assumed market_resolved c 2,254 2,095 5ms 46ms 10.5min 12.8min 0 transport_latency_assumed market_resolved e 2,218 66 82ms 208ms 58.7s 1.0min 0 transport_latency_assumed market_resolved f 2,205 30 72ms 207ms 51.7s 1.6min 0 transport_latency_assumed market_resolved g 2,218 27 103ms 353ms 1.2s 1.1min 0 transport_latency_assumed market_resolved h 2,218 153 32ms 88ms 59.0s 1.0min 0 transport_latency_assumed new_market c 3,071 1,933 188ms 7.7min 8.8min 9.5min 0 transport_latency_assumed new_market e 2,186 423 219ms 27.2s 2.1min 3.2min 0 transport_latency_assumed new_market f 2,218 465 235ms 2.4min 5.2min 6.6min 0 transport_latency_assumed new_market g 2,186 324 365ms 29.4s 2.0min 2.5min 0 transport_latency_assumed new_market h 2,186 766 178ms 27.5s 1.8min 3.2min 0 transport_latency_assumed price_change c 88,422,201 83,158,280 5ms 18ms 220ms 34.4s 0 transport_latency_assumed price_change e 97,233,568 1,473,248 41ms 100ms 2.3s 18.4s 0 transport_latency_assumed price_change f 93,155,689 480,737 47ms 103ms 2.6s 29.2s 0 transport_latency_assumed price_change g 96,822,536 48,767 82ms 233ms 6.1s 37.4s 0 transport_latency_assumed price_change h 97,354,395 12,306,624 18ms 45ms 559ms 48.8s 0 transport_latency_assumed tick_size_change c 6,200 5,906 6ms 14ms 182ms 333ms 0 transport_latency_assumed tick_size_change e 6,788 52 41ms 52ms 291ms 773ms 0 transport_latency_assumed tick_size_change f 6,604 36 47ms 64ms 308ms 623ms 0 transport_latency_assumed tick_size_change g 6,788 not meas. 81ms 121ms 669ms 27.4s 0 transport_latency_assumed tick_size_change h 6,788 794 18ms 35ms 528ms 3.5s 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/20/2026-09-18T20.parquet sha256sum 2026-09-18T20.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.