Hour audit: 2026-09-23T16
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-23T16 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-23T16:00:00.000140932+00:00 · last event 2026-09-23T16:59:59.999922799+00:00
VOLUME 126,530,948 rows · 1,369,504,877 bytes (1.28 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured h: 125,438,013 · i: 124,769,315 · g: 124,481,357 · c: 119,202,459 · k: 116,392,333 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 4,436,800 (3.51%) · i: 2,272,447 (1.80%) · g: 50,234 (0.04%) · c: 107,810,879 (85.21%) · k: 11,960,588 (9.45%) (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 126,530,948 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 9421d70a3932c1906eb4688dd5ee17954a3f7db107b4866a83ec002ec8e997f1
the corpus checksum ledger names this file with the same digest
joined 126,534,143 to merged 126,530,948, minus 3,195 (minus 0.0025%)
boundary drops 3,195 · 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-24T03:17:52Z as cghik
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,533,634 136,894,692 0-43 38a905e60c56c5fe1c0ba244e32c9ccc162b7487fa39dc2ee7dcdee7cc8da228 book 1,090,592 72,145,496 44-48 f8b8fdde89ada8b9381a51f3f5f3f316202a3e1901592839f88d2d09cb74cef3 last_trade_price 62,732 3,621,671 49-49 c9ef4798697f25a355ba55b3b41c6db6fc9ff4b2ea2b91e9289234f2a99edf35 market_resolved 1,575 214,503 50-50 505384e4d88cfddebc95be63ce4e004e50b3d80eca80fbc52435df4ed9b0f08c new_market 2,295 241,812 51-51 f11d91005f24da055b371d7ed2ec19fb22abd817102a2aaa656c4b6a63e0f963 price_change 113,837,180 1,154,837,805 52-486 226a2733388a677d0939d430353f594b6d13f5ff686b42dcd5de0f88e68a2204 tick_size_change 2,940 108,926 487-487 64d0d7f251d7b64a8e404ce54baa4af53d80ecb5735b364da557be1a69ccf645 EVENT MIX count share price_change 113,837,180 89.97% best_bid_ask 11,533,634 9.12% book 1,090,592 0.86% last_trade_price 62,732 0.05% tick_size_change 2,940 <0.01% new_market 2,295 <0.01% market_resolved 1,575 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,533,954 11,533,634 320 2,109 FULL book 1,090,966 1,090,592 374 190,611 FULL last_trade_price 62,733 62,732 1 203 FULL market_resolved 1,575 1,575 0 41 FULL new_market 2,295 2,295 0 0 FULL price_change 113,839,680 113,837,180 2,500 1,200 FULL tick_size_change 2,940 2,940 0 82 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,961,490 10,004,592 5ms 16ms 169ms 6.7s 0 transport_latency_assumed best_bid_ask g 11,516,050 984 80ms 128ms 1.0s 38.9s 0 transport_latency_assumed best_bid_ask h 11,527,331 357,986 19ms 38ms 288ms 27.7s 0 transport_latency_assumed best_bid_ask i 11,445,126 185,908 22ms 34ms 164ms 5.3s 0 transport_latency_assumed best_bid_ask k 10,695,515 984,164 13ms 22ms 117ms 7.0s 0 transport_latency_assumed book c 569,239 223,007 3.8min 2.8d 38.9d 116.8d 0 book_staleness book g 161,349 23,667 219ms 22.8min 17.7d 116.8d 0 book_staleness book h 145,704 15,250 26ms 40.4s 5.0d 98.3d 0 book_staleness book i 190,365 30,657 60ms 2.5h 18.1d 116.8d 0 book_staleness book k 913,190 798,011 6.2min 3.2d 41.9d 116.8d 0 book_staleness last_trade_price c 58,278 52,233 6ms 25ms 239ms 2.0s 0 transport_latency_assumed last_trade_price g 58,875 120 105ms 3.5s 13.4s 39.0s 0 transport_latency_assumed last_trade_price h 62,343 2,727 21ms 108ms 722ms 9.2s 0 transport_latency_assumed last_trade_price i 62,384 1,073 27ms 206ms 1.3s 5.3s 0 transport_latency_assumed last_trade_price k 56,521 6,579 14ms 39ms 190ms 2.9s 0 transport_latency_assumed market_resolved c 1,287 995 6ms 44.9s 5.8min 5.9min 0 transport_latency_assumed market_resolved g 1,301 1 189ms 45.2s 1.0min 1.1min 0 transport_latency_assumed market_resolved h 1,301 324 37ms 42.5s 57.3s 1.0min 0 transport_latency_assumed market_resolved i 1,300 39 28ms 38.4s 59.3s 2.2min 0 transport_latency_assumed market_resolved k 1,285 216 18ms 56.5s 4.8min 5.1min 0 transport_latency_assumed new_market c 1,576 821 85ms 14.0s 5.2min 5.3min 0 transport_latency_assumed new_market g 1,556 130 347ms 16.5s 52.9s 1.4min 0 transport_latency_assumed new_market h 1,556 281 140ms 14.5s 53.0s 1.5min 0 transport_latency_assumed new_market i 1,556 428 139ms 14.5s 1.1min 1.5min 0 transport_latency_assumed new_market k 1,580 635 101ms 31.6s 4.5min 4.5min 0 transport_latency_assumed price_change c 107,607,789 97,526,670 5ms 18ms 186ms 6.8s 0 transport_latency_assumed price_change g 112,739,286 25,332 81ms 224ms 6.5s 39.0s 0 transport_latency_assumed price_change h 113,696,838 4,060,152 19ms 46ms 350ms 31.2s 0 transport_latency_assumed price_change i 113,065,656 2,054,297 23ms 46ms 313ms 7.0s 0 transport_latency_assumed price_change k 104,721,550 10,170,729 13ms 26ms 133ms 7.1s 0 transport_latency_assumed tick_size_change c 2,800 2,561 5ms 15ms 98ms 225ms 0 transport_latency_assumed tick_size_change g 2,940 not meas. 79ms 114ms 396ms 2.2s 0 transport_latency_assumed tick_size_change h 2,940 80 19ms 39ms 325ms 2.4s 0 transport_latency_assumed tick_size_change i 2,928 45 22ms 30ms 85ms 170ms 0 transport_latency_assumed tick_size_change k 2,692 254 13ms 21ms 73ms 185ms 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-23/16/2026-09-23T16.parquet sha256sum 2026-09-23T16.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.