Hour audit: 2026-09-18T17
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-18T17 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-18T17:00:00.000065390+00:00 · last event 2026-09-18T17:59:59.999998053+00:00
VOLUME 107,558,473 rows · 1,220,393,102 bytes (1.14 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 106,398,175 · e: 106,300,955 · f: 106,155,561 · g: 105,502,614 · c: 98,429,517 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 15,843,654 (14.73%) · e: 1,611,536 (1.50%) · f: 998,743 (0.93%) · g: 183,938 (0.17%) · c: 88,920,602 (82.67%) (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 107,558,473 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 18d47f6fdcc59653def536e6c556f45068bae310e28b2340052d93f682ebf8d4
the corpus checksum ledger names this file with the same digest
joined 107,561,365 to merged 107,558,473, minus 2,892 (minus 0.0027%)
boundary drops 2,892 · 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-18T21:17:15Z 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,574,383 139,416,546 0-44 1f26e2fe0a89fc1891958571d4bf83937aee8f0eefb9b91c27901d533112e14f book 1,205,131 78,542,123 45-49 d9898708e8c479ba6a6c84a6984e23f28b23a181f13e28ea90e9844afbb3a8f0 last_trade_price 62,221 3,703,381 50-50 44333aaf03c68fe3112766b076e7c50a9e95e150673cf2bdb57adc1e6e2a8439 market_resolved 837 131,248 51-51 13e3939ab38b58be30c859da57f6d13d4124203d2bf800897a2d27717f135781 new_market 9,875 1,013,557 52-52 266a58b74433782fe7fc2680452c4d4c2183cc7e0086be902646b39c54745761 price_change 94,699,854 996,131,956 53-414 c908672562cf1c5a91438523d2ac41facc6aac6ec95e5067416704ee86addc6c tick_size_change 6,172 227,504 415-415 987a016a9c6c8d0075ff0439b51b73c607616f057750ece0d9487ca8fa456b5a EVENT MIX count share price_change 94,699,854 88.04% best_bid_ask 11,574,383 10.76% book 1,205,131 1.12% last_trade_price 62,221 0.06% new_market 9,875 <0.01% tick_size_change 6,172 <0.01% market_resolved 837 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,574,697 11,574,383 314 2,857 FULL book 1,205,327 1,205,131 196 198,666 FULL last_trade_price 62,221 62,221 0 232 FULL market_resolved 837 837 0 26 FULL new_market 9,875 9,875 0 221 FULL price_change 94,702,236 94,699,854 2,382 3,921 FULL tick_size_change 6,172 6,172 0 138 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,616,788 9,596,098 6ms 33ms 308ms 17.8s 0 transport_latency_assumed best_bid_ask e 11,563,503 170,071 44ms 97ms 414ms 21.4s 0 transport_latency_assumed best_bid_ask f 11,560,918 101,232 47ms 104ms 430ms 31.5s 0 transport_latency_assumed best_bid_ask g 11,552,086 10,717 83ms 249ms 1.1s 35.6s 0 transport_latency_assumed best_bid_ask h 11,568,630 1,696,265 19ms 50ms 762ms 1.2min 0 transport_latency_assumed book c 1,046,321 956,953 7.9min 2.5h 36.9d 111.8d 0 book_staleness book e 265,545 81,875 3.0s 1.7h 27.1d 111.8d 0 book_staleness book f 252,830 72,833 2.2s 1.7h 27.1d 111.8d 0 book_staleness book g 244,935 60,954 3.5s 1.7h 27.1d 111.8d 0 book_staleness book h 151,968 32,516 29ms 2.6s 1.9h 93.2d 0 book_staleness last_trade_price c 55,799 50,849 11ms 76ms 436ms 5.0s 0 transport_latency_assumed last_trade_price e 61,322 651 90ms 1.2s 10.1s 21.0s 0 transport_latency_assumed last_trade_price f 60,809 448 91ms 1.1s 11.7s 31.5s 0 transport_latency_assumed last_trade_price g 58,698 118 163ms 4.0s 20.6s 35.6s 0 transport_latency_assumed last_trade_price h 61,983 10,155 27ms 152ms 1.1s 10.4s 0 transport_latency_assumed market_resolved c 793 719 6ms 139ms 6.3min 6.3min 0 transport_latency_assumed market_resolved e 795 8 48ms 301ms 915ms 47.7s 0 transport_latency_assumed market_resolved f 795 9 52ms 289ms 918ms 49.2s 0 transport_latency_assumed market_resolved g 795 not meas. 91ms 528ms 1.6s 56.4s 0 transport_latency_assumed market_resolved h 795 101 22ms 114ms 2.0s 40.2s 0 transport_latency_assumed new_market c 6,481 3,723 102ms 2.3min 34.7min 36.9min 0 transport_latency_assumed new_market e 6,282 1,517 161ms 1.5min 6.6min 10.0min 0 transport_latency_assumed new_market f 6,283 1,039 182ms 1.4min 6.6min 10.2min 0 transport_latency_assumed new_market g 6,282 695 273ms 1.2min 6.4min 9.7min 0 transport_latency_assumed new_market h 6,284 2,901 124ms 1.6min 7.5min 10.2min 0 transport_latency_assumed price_change c 86,697,711 78,307,256 6ms 38ms 333ms 17.8s 0 transport_latency_assumed price_change e 94,397,336 1,357,332 45ms 162ms 2.8s 21.5s 0 transport_latency_assumed price_change f 94,267,754 823,157 48ms 169ms 2.7s 31.6s 0 transport_latency_assumed price_change g 93,633,650 111,454 85ms 408ms 9.0s 36.0s 0 transport_latency_assumed price_change h 94,602,343 14,100,655 19ms 64ms 836ms 1.7min 0 transport_latency_assumed tick_size_change c 5,624 5,004 6ms 27ms 173ms 1.3s 0 transport_latency_assumed tick_size_change e 6,172 82 44ms 76ms 265ms 544ms 0 transport_latency_assumed tick_size_change f 6,172 25 47ms 73ms 213ms 377ms 0 transport_latency_assumed tick_size_change g 6,168 not meas. 81ms 198ms 527ms 5.2s 0 transport_latency_assumed tick_size_change h 6,172 1,061 19ms 41ms 651ms 6.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-18/17/2026-09-18T17.parquet sha256sum 2026-09-18T17.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.