Hour audit: 2026-09-17T19
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-17T19 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-17T19:00:00.000530999+00:00 · last event 2026-09-17T19:59:59.999979607+00:00
VOLUME 126,427,980 rows · 1,425,224,476 bytes (1.33 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 123,931,371 · h: 123,393,181 · f: 114,128,924 · g: 113,382,941 · c: 110,786,437 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 4,022,627 (3.18%) · h: 19,892,314 (15.73%) · f: 1,434,572 (1.13%) · g: 815,105 (0.64%) · c: 100,263,362 (79.30%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 37a2eb9a156d7be1bdc20acb835f6bd19f547ec62ef856fb90ad50081a129463
the corpus checksum ledger names this file with the same digest
joined 126,441,584 to merged 126,427,980, minus 13,604 (minus 0.0108%)
boundary drops 13,604 · 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-17T21:39:28Z 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 11,516,447 139,031,288 0-43 fac98260b769f8fbcc6e62d9beae52a0c9b47f147928583c18f229c10c49a621 book 1,905,778 101,495,755 44-51 0d9ba3fb0ed25bee01eb0da1b60cee37f24cef97536789ce53baca894c6578c2 last_trade_price 60,548 3,572,599 52-52 eba34fb4eeb3b96fee38013cae9fb9899236c08d8b68a464812cb13b1f18cff8 market_resolved 2,118 314,504 53-53 49ce8ccafea97698bea682b4e80b75b015459a1c7ecb7e4e7319a9929478b06b new_market 14,797 1,391,991 54-54 ffb2d55465293880599a7a0137ec717c5be15e4cccb206f0b2bccb544b9beab4 price_change 112,922,824 1,177,778,660 55-485 7d8d299d48cbe9d454544eb85485fa16f86864adfb7f76f66ab376704030c94c tick_size_change 5,468 203,395 486-486 986b9165974e45861ffd7c23404593c817eeb1c8e85e16927d1f40ba45bdd29d EVENT MIX count share price_change 112,922,824 89.32% best_bid_ask 11,516,447 9.11% book 1,905,778 1.51% last_trade_price 60,548 0.05% new_market 14,797 0.01% tick_size_change 5,468 <0.01% market_resolved 2,118 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,516,904 11,516,447 457 6,552 FULL book 1,915,038 1,905,778 9,260 147,201 FULL last_trade_price 60,551 60,548 3 445 FULL market_resolved 2,118 2,118 0 97 FULL new_market 14,803 14,797 6 414 FULL price_change 112,926,702 112,922,824 3,878 4,207 FULL tick_size_change 5,468 5,468 0 215 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,152,103 9,250,595 6ms 38ms 306ms 8.4s 0 transport_latency_assumed best_bid_ask e 11,479,269 385,260 43ms 150ms 562ms 48.7s 0 transport_latency_assumed best_bid_ask f 10,531,375 96,493 47ms 131ms 515ms 30.8s 0 transport_latency_assumed best_bid_ask g 10,491,225 34,526 84ms 302ms 1.4s 36.1s 0 transport_latency_assumed best_bid_ask h 11,348,151 1,749,573 19ms 90ms 1.1s 51.8s 0 transport_latency_assumed book c 1,284,610 838,339 3.5min 1.8d 37.0d 110.9d 0 book_staleness book e 285,226 106,159 6.9s 26.6min 26.2d 110.9d 0 book_staleness book f 948,916 409,652 2.7min 1.1d 37.0d 110.9d 0 book_staleness book g 960,452 401,509 2.8min 1.1d 37.0d 110.9d 0 book_staleness book h 338,098 150,119 17.2s 38.5min 26.2d 110.9d 0 book_staleness last_trade_price c 52,444 47,234 13ms 104ms 486ms 5.0s 0 transport_latency_assumed last_trade_price e 57,410 1,231 83ms 1.0s 14.6s 48.2s 0 transport_latency_assumed last_trade_price f 52,579 487 80ms 699ms 11.8s 30.8s 0 transport_latency_assumed last_trade_price g 50,976 285 121ms 1.4s 17.3s 35.5s 0 transport_latency_assumed last_trade_price h 60,260 11,311 33ms 257ms 2.4s 32.2s 0 transport_latency_assumed market_resolved c 1,901 1,732 6ms 65ms 7.5min 8.2min 0 transport_latency_assumed market_resolved e 1,922 31 100ms 269ms 698ms 7.9s 0 transport_latency_assumed market_resolved f 1,881 32 105ms 303ms 7.5min 9.5min 0 transport_latency_assumed market_resolved g 1,973 153 178ms 803ms 9.1min 9.9min 0 transport_latency_assumed market_resolved h 1,916 170 35ms 116ms 778ms 2.1min 0 transport_latency_assumed new_market c 9,416 6,029 134ms 4.5min 29.5min 30.8min 0 transport_latency_assumed new_market e 8,684 2,148 212ms 1.5min 4.0min 30.1min 0 transport_latency_assumed new_market f 9,762 1,343 263ms 4.7min 40.9min 42.2min 0 transport_latency_assumed new_market g 10,377 1,692 410ms 6.7min 9.4min 30.1min 0 transport_latency_assumed new_market h 8,690 3,585 169ms 1.4min 3.9min 34.5min 0 transport_latency_assumed price_change c 99,281,063 90,114,903 6ms 46ms 330ms 8.6s 0 transport_latency_assumed price_change e 112,093,400 3,527,674 43ms 211ms 3.6s 48.7s 0 transport_latency_assumed price_change f 102,579,195 926,476 47ms 184ms 2.0s 30.8s 0 transport_latency_assumed price_change g 101,862,914 376,936 86ms 387ms 5.6s 36.3s 0 transport_latency_assumed price_change h 111,630,650 17,976,835 19ms 112ms 1.3s 1.5min 0 transport_latency_assumed tick_size_change c 4,900 4,530 6ms 36ms 268ms 589ms 0 transport_latency_assumed tick_size_change e 5,460 124 43ms 159ms 829ms 6.5s 0 transport_latency_assumed tick_size_change f 5,216 89 47ms 154ms 462ms 734ms 0 transport_latency_assumed tick_size_change g 5,024 4 83ms 263ms 803ms 2.0s 0 transport_latency_assumed tick_size_change h 5,416 721 19ms 73ms 541ms 5.8s 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-17/19/2026-09-17T19.parquet sha256sum 2026-09-17T19.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.