Hour audit: 2026-09-17T20
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-17T20 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-17T20:00:00.000071733+00:00 · last event 2026-09-17T20:59:59.999985959+00:00
VOLUME 119,691,752 rows · 1,302,844,356 bytes (1.21 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 118,157,283 · h: 117,266,693 · g: 117,200,034 · c: 108,827,693 · f: 108,164,638 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 1,772,845 (1.48%) · h: 14,997,626 (12.53%) · g: 135,479 (0.11%) · c: 101,505,907 (84.81%) · f: 1,279,895 (1.07%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 df1a253b095904452ffcd30dc218f9a4383c11c23fe5c0836e5fa6b913c8a91a
the corpus checksum ledger names this file with the same digest
joined 119,695,637 to merged 119,691,752, minus 3,885 (minus 0.0032%)
boundary drops 3,885 · 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-17T22:07:19Z 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,233,395 130,931,872 0-42 36882de71bce8a4f3d9af45fdaf93052afda0065eaeb484213e41a21c79e8f07 book 1,358,244 85,007,047 43-48 4ab420af24b20cb22f529b80e731cde69ca0ff2e656b760174b075b12184b52d last_trade_price 53,517 3,071,798 49-49 81df4212eeb05fe02750d897fb10053eee9b2a58ea30d2755d60247ffbc4c107 market_resolved 1,602 208,047 50-50 d68fba08b599d22763c92c6d5d22f250584c0641b00bf11ff81c238c745cd88e new_market 4,399 437,185 51-51 708c6ae8f559a8f93dd771fb966f1f2a07a61539edc4011fb2cc64b438f24504 price_change 107,036,019 1,081,656,658 52-460 a9b378afe4273de928a7f5c5dd4a3c3de6760948356e7aac862d067512487224 tick_size_change 4,576 169,036 461-461 11356b701721bbf341c5203b875c7347bc81d4a0599ede9916b5bfba7b0bd489 EVENT MIX count share price_change 107,036,019 89.43% best_bid_ask 11,233,395 9.39% book 1,358,244 1.13% last_trade_price 53,517 0.04% tick_size_change 4,576 <0.01% new_market 4,399 <0.01% market_resolved 1,602 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,233,634 11,233,395 239 3,173 FULL book 1,359,166 1,358,244 922 181,615 FULL last_trade_price 53,517 53,517 0 376 FULL market_resolved 1,602 1,602 0 278 FULL new_market 4,399 4,399 0 29 FULL price_change 107,038,743 107,036,019 2,724 3,058 FULL tick_size_change 4,576 4,576 0 122 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,311,254 9,684,971 5ms 15ms 227ms 4.5s 0 transport_latency_assumed best_bid_ask e 11,218,194 151,411 40ms 57ms 355ms 20.5s 0 transport_latency_assumed best_bid_ask f 10,216,652 45,955 47ms 67ms 380ms 18.0s 0 transport_latency_assumed best_bid_ask g 11,125,273 5,447 82ms 125ms 736ms 34.8s 0 transport_latency_assumed best_bid_ask h 11,119,039 1,345,611 18ms 33ms 466ms 59.7s 0 transport_latency_assumed book c 886,139 401,546 3.3min 17.9h 37.1d 110.9d 0 book_staleness book e 233,681 76,553 3.7s 30.7min 26.3d 110.9d 0 book_staleness book f 896,853 734,068 3.1min 15.8h 37.1d 110.9d 0 book_staleness book g 204,779 58,866 1.0s 24.7min 26.3d 110.9d 0 book_staleness book h 224,785 87,211 1.6s 27.8min 26.3d 110.9d 0 book_staleness last_trade_price c 48,872 45,435 12ms 61ms 338ms 5.0s 0 transport_latency_assumed last_trade_price e 52,282 732 55ms 366ms 5.1s 20.2s 0 transport_latency_assumed last_trade_price f 48,677 373 63ms 422ms 6.7s 18.0s 0 transport_latency_assumed last_trade_price g 52,136 41 103ms 645ms 10.0s 34.9s 0 transport_latency_assumed last_trade_price h 51,958 6,936 25ms 103ms 662ms 52.5s 0 transport_latency_assumed market_resolved c 1,260 1,190 6ms 4.4min 5.4min 5.6min 0 transport_latency_assumed market_resolved e 1,262 24 42ms 194ms 30.7s 1.0min 0 transport_latency_assumed market_resolved f 1,155 148 52ms 6.0min 10.5min 12.5min 0 transport_latency_assumed market_resolved g 1,252 5 88ms 292ms 1.1s 2.3min 0 transport_latency_assumed market_resolved h 1,255 235 21ms 64ms 352ms 1.0min 0 transport_latency_assumed new_market c 2,723 1,586 104ms 48.1s 1.8min 6.1min 0 transport_latency_assumed new_market e 2,719 521 187ms 45.1s 1.8min 2.2min 0 transport_latency_assumed new_market f 2,832 614 225ms 1.2min 7.7min 12.6min 0 transport_latency_assumed new_market g 2,719 449 362ms 52.4s 1.9min 3.4min 0 transport_latency_assumed new_market h 2,719 1,229 150ms 46.0s 1.8min 2.1min 0 transport_latency_assumed price_change c 97,573,097 91,367,251 6ms 18ms 242ms 7.4s 0 transport_latency_assumed price_change e 106,644,569 1,543,532 40ms 74ms 602ms 20.5s 0 transport_latency_assumed price_change f 96,994,149 498,710 47ms 86ms 723ms 18.0s 0 transport_latency_assumed price_change g 105,809,339 70,666 82ms 166ms 1.5s 34.9s 0 transport_latency_assumed price_change h 105,862,381 13,555,860 18ms 38ms 525ms 1.3min 0 transport_latency_assumed tick_size_change c 4,348 3,928 6ms 28ms 258ms 811ms 0 transport_latency_assumed tick_size_change e 4,576 72 40ms 89ms 376ms 826ms 0 transport_latency_assumed tick_size_change f 4,320 27 47ms 80ms 336ms 780ms 0 transport_latency_assumed tick_size_change g 4,536 5 82ms 162ms 751ms 1.7s 0 transport_latency_assumed tick_size_change h 4,556 544 18ms 51ms 346ms 6.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/20/2026-09-17T20.parquet sha256sum 2026-09-17T20.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.