Hour audit: 2026-09-16T17
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-16T17 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-16T17:00:00.000015592+00:00 · last event 2026-09-16T17:59:59.999968391+00:00
VOLUME 129,581,704 rows · 1,414,978,661 bytes (1.32 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 128,468,844 · h: 128,454,164 · f: 123,694,887 · g: 123,273,066 · c: 119,611,804 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 1,260,939 (0.97%) · h: 16,138,609 (12.45%) · f: 690,920 (0.53%) · g: 111,611 (0.09%) · c: 111,379,625 (85.95%) (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 129,581,704 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 638e52205df3ccc8db92d6da89b1fd7c7e9c0fa8c418e4713a695befe0a7b518
the corpus checksum ledger names this file with the same digest
joined 129,583,866 to merged 129,581,704, minus 2,162 (minus 0.0017%)
boundary drops 2,162 · 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-16T19:03:02Z 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,437,978 136,477,556 0-43 92a1dba1b4e391b6cd1f77ec2b86b97ec814c045c3839ab358d11c9aa60eeb9a book 1,088,212 76,995,421 44-48 fba0ecb08b3eff916c17681b50ee6ef1bf82810f3b8e45eabdf35f5f5bd3b097 last_trade_price 63,107 3,613,053 49-49 ee7e56329a73ee1e178e9307b44d8f68d124cfb05c0f60a37c6a32af7ee49f52 market_resolved 782 124,575 50-50 b3824640b34da8c92ed92c5d4db8a89b5c83bb27888a0e9f6ef4a9cdb5a72ebc new_market 1,737 173,757 51-51 c3a28f7730f3c883b5a807602e1432ba13c9e3cfdbd84f4a53355643d02b668c price_change 116,985,072 1,195,947,424 52-498 54b9317c2ebd1bc671ee421c889716985e476c482e32e739cf3348c516504b8a tick_size_change 4,816 172,174 499-499 cfa5b295e5e433b58611e75873b4a9b27e8ef7b081c04feed8ae7a617e7b5995 EVENT MIX count share price_change 116,985,072 90.28% best_bid_ask 11,437,978 8.83% book 1,088,212 0.84% last_trade_price 63,107 0.05% tick_size_change 4,816 <0.01% new_market 1,737 <0.01% market_resolved 782 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,438,199 11,437,978 221 1,351 FULL book 1,088,306 1,088,212 94 174,732 FULL last_trade_price 63,114 63,107 7 267 FULL market_resolved 782 782 0 9 FULL new_market 1,737 1,737 0 0 FULL price_change 116,986,912 116,985,072 1,840 371 FULL tick_size_change 4,816 4,816 0 125 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,542,174 9,834,618 6ms 18ms 138ms 3.6s 0 transport_latency_assumed best_bid_ask e 11,434,303 109,829 40ms 57ms 259ms 13.1s 0 transport_latency_assumed best_bid_ask f 10,943,655 41,382 44ms 65ms 276ms 13.1s 0 transport_latency_assumed best_bid_ask g 10,931,960 1,957 80ms 111ms 544ms 36.9s 0 transport_latency_assumed best_bid_ask h 11,432,127 1,450,192 19ms 36ms 194ms 10.4s 0 transport_latency_assumed book c 841,565 792,309 2.5min 1.4d 35.9d 109.8d 0 book_staleness book e 141,279 7,424 44ms 2.7s 3.7h 91.3d 0 book_staleness book f 488,784 180,919 2.1min 12.2h 34.6d 109.8d 0 book_staleness book g 489,188 81,945 2.3min 12.8h 34.6d 109.8d 0 book_staleness book h 143,468 25,615 24ms 562ms 58.4min 91.3d 0 book_staleness last_trade_price c 58,795 54,486 12ms 60ms 319ms 5.0s 0 transport_latency_assumed last_trade_price e 62,775 610 57ms 586ms 6.1s 13.3s 0 transport_latency_assumed last_trade_price f 59,964 353 61ms 460ms 5.2s 12.6s 0 transport_latency_assumed last_trade_price g 58,897 86 102ms 1.2s 12.2s 36.8s 0 transport_latency_assumed last_trade_price h 62,501 7,572 27ms 116ms 627ms 9.7s 0 transport_latency_assumed market_resolved c 706 640 6ms 76ms 5.1min 5.2min 0 transport_latency_assumed market_resolved e 707 24 41ms 196ms 47.3s 57.0s 0 transport_latency_assumed market_resolved f 706 27 46ms 215ms 2.4min 3.3min 0 transport_latency_assumed market_resolved g 701 16 87ms 349ms 3.2min 4.1min 0 transport_latency_assumed market_resolved h 706 75 20ms 75ms 47.6s 56.9s 0 transport_latency_assumed new_market c 1,112 799 84ms 17.6s 1.3min 4.7min 0 transport_latency_assumed new_market e 1,112 159 222ms 21.2s 29.2s 1.4min 0 transport_latency_assumed new_market f 1,112 161 212ms 21.5s 29.7s 1.1min 0 transport_latency_assumed new_market g 1,112 79 365ms 20.3s 32.0s 57.0s 0 transport_latency_assumed new_market h 1,112 539 130ms 20.7s 27.5s 1.3min 0 transport_latency_assumed price_change c 108,162,916 100,692,470 6ms 21ms 156ms 4.3s 0 transport_latency_assumed price_change e 116,823,852 1,142,884 40ms 71ms 882ms 13.3s 0 transport_latency_assumed price_change f 112,196,030 468,078 45ms 78ms 709ms 13.2s 0 transport_latency_assumed price_change g 111,786,612 27,528 81ms 143ms 2.3s 37.0s 0 transport_latency_assumed price_change h 116,809,434 14,654,112 19ms 41ms 263ms 11.8s 0 transport_latency_assumed tick_size_change c 4,536 4,303 5ms 13ms 138ms 392ms 0 transport_latency_assumed tick_size_change e 4,816 9 39ms 46ms 167ms 458ms 0 transport_latency_assumed tick_size_change f 4,636 not meas. 44ms 55ms 174ms 612ms 0 transport_latency_assumed tick_size_change g 4,596 not meas. 79ms 94ms 260ms 641ms 0 transport_latency_assumed tick_size_change h 4,816 504 18ms 28ms 97ms 665ms 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-16/17/2026-09-16T17.parquet sha256sum 2026-09-16T17.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.