Hour audit: 2026-09-15T17
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-15T17 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-15T17:00:00.000072873+00:00 · last event 2026-09-15T17:59:59.998839391+00:00
VOLUME 121,029,830 rows · 1,344,650,131 bytes (1.25 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 118,885,433 · e: 118,852,317 · f: 118,838,988 · g: 114,074,377 · c: 96,461,644 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 27,227,504 (22.50%) · e: 1,273,690 (1.05%) · f: 838,680 (0.69%) · g: 291,007 (0.24%) · c: 91,398,949 (75.52%) (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 121,029,830 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 2db65cb68429ae759434210082a1521da718ea3734ab8b7aabfa27a3ceca7f92
the corpus checksum ledger names this file with the same digest
joined 121,051,773 to merged 121,029,830, minus 21,943 (minus 0.0181%)
boundary drops 21,943 · 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-15T19:00:25Z 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,310,302 144,187,599 0-46 abf29b1f4f384ef1cd1a84d43d51db02371b4f086ee97753be45db94262876de book 2,166,324 98,469,677 47-55 83999839cbacc6d9e67fea65ec82f0fa350bf0ce6e4e5ce2d73cee168945130c last_trade_price 59,231 3,454,421 56-56 4b8c5ec58f7a8ee5918b98d375ffcf544d048563c96429ffbbaace5b53129f37 market_resolved 1,049 107,393 57-57 203e85d569f162de6bfe64678969bea03cae745a3b5c8f4af8c3c0db97236a1a new_market 1,308 128,981 58-58 df6d720a910c37e0c4131481983dc6bb25f25e1e83bbea7027864045659b1dcb price_change 106,487,312 1,096,765,083 59-465 d283a765fb6fa96549d30db8836d03a097ebedf2273a02293f42296d21eba914 tick_size_change 4,304 159,415 466-466 8b772793b23dccb4a06f9d096e2b789cf1078afc6d3a34b8018fc50f18b90b36 EVENT MIX count share price_change 106,487,312 87.98% best_bid_ask 12,310,302 10.17% book 2,166,324 1.79% last_trade_price 59,231 0.05% tick_size_change 4,304 <0.01% new_market 1,308 <0.01% market_resolved 1,049 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,310,831 12,310,302 529 3,741 FULL book 2,183,744 2,166,324 17,420 172,592 FULL last_trade_price 59,232 59,231 1 507 FULL market_resolved 1,049 1,049 0 50 FULL new_market 1,309 1,308 1 3 FULL price_change 106,491,304 106,487,312 3,992 1,944 FULL tick_size_change 4,304 4,304 0 200 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,799,462 9,333,884 6ms 13ms 111ms 4.5s 0 transport_latency_assumed best_bid_ask e 12,307,361 119,822 41ms 51ms 195ms 18.8s 0 transport_latency_assumed best_bid_ask f 12,307,869 67,032 43ms 53ms 192ms 13.3s 0 transport_latency_assumed best_bid_ask g 11,836,347 2,351 84ms 149ms 481ms 28.1s 0 transport_latency_assumed best_bid_ask h 12,308,350 2,787,213 19ms 28ms 119ms 46.0s 0 transport_latency_assumed book c 1,969,803 1,887,590 5.7min 3.0d 38.0d 108.8d 0 book_staleness book e 126,221 4,614 44ms 248ms 14.9min 90.3d 0 book_staleness book f 129,028 5,145 46ms 392ms 24.5min 108.8d 0 book_staleness book g 504,033 237,513 1.4min 13.0h 34.1d 108.8d 0 book_staleness book h 127,228 31,462 23ms 77ms 17.9min 90.3d 0 book_staleness last_trade_price c 46,757 44,255 11ms 48ms 238ms 5.0s 0 transport_latency_assumed last_trade_price e 58,756 797 50ms 168ms 2.1s 18.7s 0 transport_latency_assumed last_trade_price f 58,918 491 52ms 173ms 3.5s 13.3s 0 transport_latency_assumed last_trade_price g 55,475 42 105ms 1.1s 11.4s 20.2s 0 transport_latency_assumed last_trade_price h 58,962 13,646 25ms 74ms 401ms 9.7s 0 transport_latency_assumed market_resolved c 853 844 166ms 9.6min 15.6min 15.9min 0 transport_latency_assumed market_resolved e 602 6 43ms 196ms 42.7s 45.8s 0 transport_latency_assumed market_resolved f 602 6 45ms 187ms 49.2s 52.2s 0 transport_latency_assumed market_resolved g 585 7 90ms 342ms 1.0min 5.6min 0 transport_latency_assumed market_resolved h 602 186 20ms 94ms 40.8s 43.1s 0 transport_latency_assumed new_market c 895 583 97ms 2.1min 11.8min 51.9min 0 transport_latency_assumed new_market e 809 166 163ms 16.8s 25.3s 1.1min 0 transport_latency_assumed new_market f 809 145 171ms 17.4s 1.3min 1.4min 0 transport_latency_assumed new_market g 821 78 282ms 808ms 5.8min 5.8min 0 transport_latency_assumed new_market h 809 336 112ms 17.8s 1.3min 1.4min 0 transport_latency_assumed price_change c 84,640,226 80,128,284 6ms 15ms 165ms 5.3s 0 transport_latency_assumed price_change e 106,354,264 1,148,230 42ms 63ms 437ms 19.0s 0 transport_latency_assumed price_change f 106,337,458 765,840 43ms 64ms 391ms 13.3s 0 transport_latency_assumed price_change g 101,672,956 51,016 85ms 174ms 2.1s 28.5s 0 transport_latency_assumed price_change h 106,385,178 24,393,942 19ms 33ms 212ms 46.5s 0 transport_latency_assumed tick_size_change c 3,648 3,509 6ms 16ms 65ms 165ms 0 transport_latency_assumed tick_size_change e 4,304 55 42ms 56ms 193ms 619ms 0 transport_latency_assumed tick_size_change f 4,304 21 43ms 54ms 186ms 491ms 0 transport_latency_assumed tick_size_change g 4,160 not meas. 85ms 159ms 514ms 4.1s 0 transport_latency_assumed tick_size_change h 4,304 719 19ms 35ms 96ms 5.0s 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/17/2026-09-15T17.parquet sha256sum 2026-09-15T17.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.