Hour audit: 2026-09-12T20
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-12T20 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-12T20:00:00.000916921+00:00 · last event 2026-09-12T20:59:59.999928268+00:00
VOLUME 136,785,164 rows · 1,544,283,293 bytes (1.44 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 131,217,638 · e: 125,408,989 · g: 120,360,904 · f: 115,661,547 · c: 55,660,101 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 73,692,509 (53.87%) · e: 6,890,634 (5.04%) · g: 512,932 (0.37%) · f: 2,958,996 (2.16%) · c: 52,730,093 (38.55%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 e1adce79d11274e6b9c3e73466418e998947619cf00a4006bc3d291e6350393f
the corpus checksum ledger names this file with the same digest
joined 136,822,153 to merged 136,785,164, minus 36,989 (minus 0.0270%)
boundary drops 36,989 · 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-12T22:01:44Z 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 13,206,469 152,957,344 0-50 a3245395a914549b363274a8716ceb6fc08efc9efeb1507f812e0a3348e31ea0 book 5,663,892 150,884,068 51-72 b3c800f48d315699f3794daf5b365e98e6aaf131ee8696c17189a45f8fd387ef last_trade_price 79,992 4,416,962 73-73 7e9441d36a0722d163b6c728904fb9caaef94197c35690cac66a70ad8d00c597 market_resolved 22,073 1,890,355 74-74 8ea01da2481aaaca42b13740a602241e5ab8a2b0ce2a348359b4b41f60945f96 new_market 42,106 1,843,469 75-75 16d6ba2b8ca91401857e197fc5649fa3b58132c1ca96f81cfa503d140d014055 price_change 117,760,744 1,230,368,554 76-525 e9b9ae33f677ebff8455d9291eb47893edbd418e2b524139ffca3c7acc67b9b9 tick_size_change 9,888 366,750 526-526 6438971c8da43a46aa6732b3b13aed90b96190a405f1f4a3eb8e70fd631cf971 EVENT MIX count share price_change 117,760,744 86.09% best_bid_ask 13,206,469 9.65% book 5,663,892 4.14% last_trade_price 79,992 0.06% new_market 42,106 0.03% market_resolved 22,073 0.02% tick_size_change 9,888 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,208,163 13,206,469 1,694 21,051 FULL book 5,676,516 5,663,892 12,624 191,870 FULL last_trade_price 80,011 79,992 19 1,760 FULL market_resolved 22,073 22,073 0 8,240 FULL new_market 42,274 42,106 168 5,380 FULL price_change 117,783,228 117,760,744 22,484 18,698 FULL tick_size_change 9,888 9,888 0 1,669 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 5,058,022 4,797,065 6ms 17ms 244ms 5.3s 0 transport_latency_assumed best_bid_ask e 12,579,252 687,799 40ms 79ms 489ms 27.0s 0 transport_latency_assumed best_bid_ask f 11,513,956 248,249 46ms 86ms 489ms 19.4s 0 transport_latency_assumed best_bid_ask g 12,049,124 26,233 79ms 228ms 1.1s 45.1s 0 transport_latency_assumed best_bid_ask h 13,203,414 7,447,123 19ms 66ms 2.0s 1.4min 0 transport_latency_assumed book c 5,102,735 4,805,711 25.9min 1.1d 34.9d 105.9d 0 book_staleness book e 564,341 116,370 1.8min 17.1h 21.3d 105.9d 0 book_staleness book f 1,335,530 416,434 9.6min 1.1d 32.1d 105.9d 0 book_staleness book g 966,762 224,860 6.8min 1.1d 31.2d 105.9d 0 book_staleness book h 185,495 100,517 25ms 1.1s 2.5h 87.4d 0 book_staleness last_trade_price c 29,645 28,141 12ms 45ms 262ms 4.8s 0 transport_latency_assumed last_trade_price e 74,345 3,523 54ms 515ms 12.8s 27.0s 0 transport_latency_assumed last_trade_price f 68,678 1,613 61ms 572ms 7.4s 18.5s 0 transport_latency_assumed last_trade_price g 68,898 374 106ms 2.5s 15.5s 45.4s 0 transport_latency_assumed last_trade_price h 79,633 46,341 27ms 189ms 2.9s 1.0min 0 transport_latency_assumed market_resolved c 19,148 17,963 59.1min 2.2h 2.6h 2.6h 0 transport_latency_assumed market_resolved e 4,294 325 113ms 352ms 5.5min 5.8min 0 transport_latency_assumed market_resolved f 4,597 702 123ms 5.6min 10.3min 11.0min 0 transport_latency_assumed market_resolved g 5,122 655 222ms 8.2min 13.2min 14.0min 0 transport_latency_assumed market_resolved h 4,322 2,428 40ms 109ms 765ms 33.7s 0 transport_latency_assumed new_market c 41,460 37,728 30.3min 3.3h 4.7h 5.1h 0 transport_latency_assumed new_market e 4,929 1,306 274ms 4.1min 6.5min 305.1d 0 transport_latency_assumed new_market f 5,733 998 315ms 5.9min 7.6min 305.0d 0 transport_latency_assumed new_market g 5,784 732 504ms 7.5min 9.7min 305.0d 0 transport_latency_assumed new_market h 4,821 1,342 219ms 3.0min 6.7min 305.0d 0 transport_latency_assumed price_change c 45,405,319 43,039,924 6ms 18ms 252ms 5.3s 0 transport_latency_assumed price_change e 112,172,316 6,080,885 41ms 99ms 627ms 27.0s 0 transport_latency_assumed price_change f 102,724,361 2,290,805 46ms 102ms 595ms 19.7s 0 transport_latency_assumed price_change g 107,256,174 260,062 79ms 282ms 2.6s 45.4s 0 transport_latency_assumed price_change h 117,730,065 66,089,068 19ms 72ms 2.1s 1.6min 0 transport_latency_assumed tick_size_change c 3,772 3,561 6ms 20ms 222ms 340ms 0 transport_latency_assumed tick_size_change e 9,512 426 40ms 90ms 571ms 762ms 0 transport_latency_assumed tick_size_change f 8,692 195 46ms 90ms 529ms 781ms 0 transport_latency_assumed tick_size_change g 9,040 16 78ms 169ms 771ms 1.3s 0 transport_latency_assumed tick_size_change h 9,888 5,690 19ms 56ms 777ms 8.4s 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/20/2026-09-12T20.parquet sha256sum 2026-09-12T20.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.