Hour audit: 2026-09-17T15
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-17T15 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-17T15:00:00.000013775+00:00 · last event 2026-09-17T15:59:59.999999278+00:00
VOLUME 112,409,293 rows · 1,189,172,222 bytes (1.11 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 112,057,036 · h: 111,905,796 · f: 111,809,046 · g: 111,369,394 · e: 111,113,847 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 105,902,441 (94.21%) · h: 5,405,630 (4.81%) · f: 366,999 (0.33%) · g: 123,110 (0.11%) · e: 611,113 (0.54%) (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 112,409,293 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 6ff289d5e6f99a5e1b2a497dccbe557509f069b7df3f398cddd3cee123a4e60f
the corpus checksum ledger names this file with the same digest
joined 112,411,913 to merged 112,409,293, minus 2,620 (minus 0.0023%)
boundary drops 2,620 · 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-17T17:36:18Z 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,046,352 128,421,779 0-42 0eb1ce6150b2dced02d74065a762cca2bf2c47a163ef1f1ad633d91c8d57befa book 603,594 54,803,929 43-45 ae5b3bcc21712209018ca2cdc32e38ec1b570aa7b9aaf371f4745cb6776e131a last_trade_price 60,640 3,615,742 46-46 ad54888b491ecafbfe67c84ab64004ff7044cb3d9ecc62f132166a7a641a481e market_resolved 642 103,826 47-47 2628398ec64d74f52566c0a78ae47f1057dcae43cf18123dec0d78a63f9cd9cf new_market 1,323 142,861 48-48 c85577c16bee75ff1f5d9bbc82ff53f044af1822597e69a910ad44d50df2b34c price_change 100,692,266 1,000,637,772 49-433 e3f9d4ebd7eeb30517bfc65b6a833deee10e7f85fb1fee404a01b9c67cc98a50 tick_size_change 4,476 163,477 434-434 b261fbb86f9c07157f41991ce1fcd99a5b8c4387e7289e91a6898f707aa8eac3 EVENT MIX count share price_change 100,692,266 89.58% best_bid_ask 11,046,352 9.83% book 603,594 0.54% last_trade_price 60,640 0.05% tick_size_change 4,476 <0.01% new_market 1,323 <0.01% market_resolved 642 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,046,604 11,046,352 252 207 FULL book 603,919 603,594 325 138,569 FULL last_trade_price 60,643 60,640 3 1 FULL market_resolved 642 642 0 0 FULL new_market 1,323 1,323 0 0 FULL price_change 100,694,306 100,692,266 2,040 62 FULL tick_size_change 4,476 4,476 0 2 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,044,655 10,508,652 5ms 13ms 102ms 3.3s 0 transport_latency_assumed best_bid_ask e 11,021,124 41,252 40ms 51ms 263ms 31.0s 0 transport_latency_assumed best_bid_ask f 11,041,998 17,657 46ms 60ms 235ms 22.9s 0 transport_latency_assumed best_bid_ask g 11,036,605 1,992 78ms 103ms 399ms 24.6s 0 transport_latency_assumed best_bid_ask h 11,040,317 476,799 19ms 31ms 150ms 7.0s 0 transport_latency_assumed book c 291,854 258,439 13.7s 33.9min 26.1d 110.7d 0 book_staleness book e 191,695 54,764 124ms 20.7min 18.8d 110.7d 0 book_staleness book f 216,035 76,455 350ms 22.4min 26.0d 110.7d 0 book_staleness book g 208,457 68,521 442ms 22.0min 26.1d 110.7d 0 book_staleness book h 286,827 145,415 12.0s 32.4min 26.1d 110.7d 0 book_staleness last_trade_price c 60,512 57,290 11ms 51ms 259ms 5.0s 0 transport_latency_assumed last_trade_price e 58,915 247 57ms 650ms 8.3s 30.8s 0 transport_latency_assumed last_trade_price f 60,080 152 64ms 676ms 7.6s 23.0s 0 transport_latency_assumed last_trade_price g 58,489 29 100ms 922ms 9.4s 24.7s 0 transport_latency_assumed last_trade_price h 60,145 2,922 26ms 100ms 584ms 6.2s 0 transport_latency_assumed market_resolved c 637 594 6ms 35ms 52.1s 58.4s 0 transport_latency_assumed market_resolved e 637 3 42ms 358ms 52.2s 58.5s 0 transport_latency_assumed market_resolved f 637 1 49ms 344ms 54.6s 1.0min 0 transport_latency_assumed market_resolved g 637 5 88ms 434ms 1.0min 1.0min 0 transport_latency_assumed market_resolved h 637 39 20ms 101ms 52.7s 59.4s 0 transport_latency_assumed new_market c 940 571 69ms 12.9s 1.4min 2.2min 0 transport_latency_assumed new_market e 940 165 170ms 20.9s 1.9min 2.3min 0 transport_latency_assumed new_market f 940 126 174ms 27.8s 2.0min 2.8min 0 transport_latency_assumed new_market g 940 43 273ms 13.5s 2.0min 2.8min 0 transport_latency_assumed new_market h 940 418 76ms 11.3s 2.0min 2.8min 0 transport_latency_assumed price_change c 100,653,962 95,072,664 6ms 17ms 171ms 3.4s 0 transport_latency_assumed price_change e 99,836,060 514,682 41ms 77ms 3.0s 31.0s 0 transport_latency_assumed price_change f 100,484,880 272,596 47ms 85ms 1.9s 22.9s 0 transport_latency_assumed price_change g 100,059,798 52,520 79ms 148ms 3.6s 25.3s 0 transport_latency_assumed price_change h 100,512,454 4,779,804 19ms 39ms 307ms 7.8s 0 transport_latency_assumed tick_size_change c 4,476 4,231 6ms 17ms 182ms 291ms 0 transport_latency_assumed tick_size_change e 4,476 not meas. 40ms 60ms 473ms 22.7s 0 transport_latency_assumed tick_size_change f 4,476 12 46ms 66ms 392ms 8.8s 0 transport_latency_assumed tick_size_change g 4,468 not meas. 78ms 101ms 707ms 1.1s 0 transport_latency_assumed tick_size_change h 4,476 233 19ms 32ms 197ms 368ms 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/15/2026-09-17T15.parquet sha256sum 2026-09-17T15.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.