Hour audit: 2026-09-15T06
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-15T06 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-15T06:00:00.000002258+00:00 · last event 2026-09-15T06:59:59.999622857+00:00
VOLUME 106,092,428 rows · 1,083,298,120 bytes (1.01 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 105,639,431 · e: 105,622,062 · f: 105,581,671 · g: 105,545,946 · c: 102,210,975 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 7,802,271 (7.35%) · e: 474,281 (0.45%) · f: 216,771 (0.20%) · g: 57,895 (0.05%) · c: 97,541,210 (91.94%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 106,092,428 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 2d9bf15ec5d93e6d111405857d005eba93c3be413b402a1740dd6c09fc6c1c06
the corpus checksum ledger names this file with the same digest
joined 106,096,093 to merged 106,092,428, minus 3,665 (minus 0.0035%)
boundary drops 3,665 · 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-15T07:57:39Z 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,989,346 130,410,881 0-45 31537835a390044d743f11574a2ba4e8ada23479fca91da40629ab2bf45efe71 book 491,163 51,460,737 46-47 215d0dc2bf0493e90399d2bd9ea5542222469d28b87ed9f54e5fe0e7f7067323 last_trade_price 42,976 2,487,270 48-48 c1fb0a9e0a32c657805575ad0a7964e29b7a8c1a64e8fe39f0e20fb44f395ec1 market_resolved 1,223 189,922 49-49 47d27dce6623e298b1777613e43cb43e572930bc6e65eda15936a9ddfe65ef66 new_market 2,482 257,728 50-50 4ae2b5babb41c97d3d3cc02a219d5ccafefa43df55ed01915b250a3fb8c4f2a0 price_change 93,563,210 897,210,654 51-407 2048abaa2913cba752f1edaf7f1ccecfb5ec46bbdeb77a86e6ca8c720498c60f tick_size_change 2,028 74,773 408-408 039ab31ec5a05c9210fcc97ecf22a416d4b4059e0cf627f6b5613ecb594d0a13 EVENT MIX count share price_change 93,563,210 88.19% best_bid_ask 11,989,346 11.30% book 491,163 0.46% last_trade_price 42,976 0.04% new_market 2,482 <0.01% tick_size_change 2,028 <0.01% market_resolved 1,223 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,989,610 11,989,346 264 807 FULL book 491,187 491,163 24 169,057 FULL last_trade_price 42,977 42,976 1 62 FULL market_resolved 1,223 1,223 0 23 FULL new_market 2,482 2,482 0 0 FULL price_change 93,566,586 93,563,210 3,376 476 FULL tick_size_change 2,028 2,028 0 14 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,547,204 11,052,397 5ms 10ms 171ms 11.0s 0 transport_latency_assumed best_bid_ask e 11,987,264 49,194 40ms 46ms 234ms 19.7s 0 transport_latency_assumed best_bid_ask f 11,987,238 21,799 49ms 55ms 267ms 11.9s 0 transport_latency_assumed best_bid_ask g 11,984,568 2,279 81ms 101ms 559ms 22.7s 0 transport_latency_assumed best_bid_ask h 11,988,284 863,677 17ms 23ms 266ms 54.4s 0 transport_latency_assumed book c 454,951 429,664 5.3min 1.6d 34.5d 108.3d 0 book_staleness book e 109,455 17,183 44ms 5.4min 7.8d 89.8d 0 book_staleness book f 96,204 4,127 51ms 521ms 8.8h 89.8d 0 book_staleness book g 132,800 31,324 102ms 1.3h 15.6d 89.8d 0 book_staleness book h 94,095 8,865 21ms 133ms 25.2min 89.8d 0 book_staleness last_trade_price c 41,657 39,603 10ms 47ms 293ms 5.0s 0 transport_latency_assumed last_trade_price e 42,738 297 48ms 131ms 1.2s 19.7s 0 transport_latency_assumed last_trade_price f 42,700 121 56ms 150ms 1.7s 11.9s 0 transport_latency_assumed last_trade_price g 42,755 23 93ms 281ms 3.3s 22.2s 0 transport_latency_assumed last_trade_price h 42,899 2,932 23ms 81ms 428ms 48.6s 0 transport_latency_assumed market_resolved c 1,159 1,102 5ms 19ms 4.7min 5.2min 0 transport_latency_assumed market_resolved e 1,168 3 104ms 202ms 49.5s 56.9s 0 transport_latency_assumed market_resolved f 1,168 17 97ms 192ms 652ms 59.3s 0 transport_latency_assumed market_resolved g 1,166 not meas. 154ms 376ms 48.5s 57.4s 0 transport_latency_assumed market_resolved h 1,170 101 34ms 79ms 48.1s 56.9s 0 transport_latency_assumed new_market c 1,701 899 215ms 4.2min 4.3min 4.4min 0 transport_latency_assumed new_market e 1,701 412 286ms 4.2min 4.4min 4.4min 0 transport_latency_assumed new_market f 1,701 323 316ms 4.2min 4.4min 4.4min 0 transport_latency_assumed new_market g 1,701 217 470ms 4.2min 4.4min 4.5min 0 transport_latency_assumed new_market h 1,701 631 333ms 4.2min 4.4min 4.4min 0 transport_latency_assumed price_change c 90,162,331 86,015,655 5ms 12ms 187ms 11.5s 0 transport_latency_assumed price_change e 93,477,708 407,180 41ms 51ms 343ms 19.8s 0 transport_latency_assumed price_change f 93,450,632 190,380 49ms 62ms 379ms 12.3s 0 transport_latency_assumed price_change g 93,380,928 24,052 82ms 113ms 740ms 22.8s 0 transport_latency_assumed price_change h 93,509,254 6,925,943 18ms 27ms 303ms 54.4s 0 transport_latency_assumed tick_size_change c 1,972 1,890 5ms 11ms 63ms 937ms 0 transport_latency_assumed tick_size_change e 2,028 12 41ms 50ms 126ms 267ms 0 transport_latency_assumed tick_size_change f 2,028 4 49ms 64ms 140ms 483ms 0 transport_latency_assumed tick_size_change g 2,028 not meas. 82ms 101ms 320ms 492ms 0 transport_latency_assumed tick_size_change h 2,028 122 18ms 33ms 105ms 6.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-15/06/2026-09-15T06.parquet sha256sum 2026-09-15T06.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.