Hour audit: 2026-09-23T19
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-23T19 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-23T19:00:00.000164897+00:00 · last event 2026-09-23T19:59:59.999990366+00:00
VOLUME 123,436,325 rows · 1,393,513,489 bytes (1.30 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured h: 120,211,395 · i: 116,080,555 · k: 115,776,811 · g: 114,817,957 · c: 85,821,396 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 7,197,585 (5.83%) · i: 3,683,031 (2.98%) · k: 37,195,165 (30.13%) · g: 266,723 (0.22%) · c: 75,093,821 (60.84%) (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 123,436,325 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 fcd6966312a60bb2ac3e5989de48996f36696789fd2bde18469ae33d6ce61f91
the corpus checksum ledger names this file with the same digest
joined 123,445,636 to merged 123,436,325, minus 9,311 (minus 0.0075%)
boundary drops 9,311 · 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-24T04:44:45Z 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 10,365,328 130,444,455 0-39 690184c5244eb48f5b4cc05dcd98e4c44446656eb298f4aeee4a626edf5c1e69 book 3,017,640 112,259,972 40-51 4a66b4a6fb96aedb724e5907654288f3f24aaee914a9195d901607feaf5c7f3c last_trade_price 60,659 3,418,155 52-52 6166887507aed9d78cda3d7ec3419148487718184b67b1a4474b3a23b2bc2a08 market_resolved 1,298 139,419 53-53 524cd3068eca8351bc08add252f21b23fd31a37311ee60acadcd52d4f397df8e new_market 6,426 534,480 54-54 e228df35df66cdfda1d50a3fe0d8412ef6c6545936b26baf0bb2a6417dc46952 price_change 109,981,598 1,145,187,001 55-474 2b204fa17dcc96a5982c93e90b6c362b2b32cfcf2224e22383c9796968572245 tick_size_change 3,376 124,521 475-475 730ddbb063589a784f20a167af131f338174a374c0f8cb2a7dfd825925912531 EVENT MIX count share price_change 109,981,598 89.10% best_bid_ask 10,365,328 8.40% book 3,017,640 2.44% last_trade_price 60,659 0.05% new_market 6,426 <0.01% tick_size_change 3,376 <0.01% market_resolved 1,298 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,365,543 10,365,328 215 5,816 FULL book 3,024,800 3,017,640 7,160 188,707 FULL last_trade_price 60,659 60,659 0 598 FULL market_resolved 1,298 1,298 0 133 FULL new_market 6,426 6,426 0 112 FULL price_change 109,983,534 109,981,598 1,936 2,257 FULL tick_size_change 3,376 3,376 0 343 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 7,089,235 6,238,945 6ms 22ms 213ms 11.3s 0 transport_latency_assumed best_bid_ask g 9,944,924 11,732 81ms 187ms 1.3s 43.2s 0 transport_latency_assumed best_bid_ask h 10,352,080 629,607 18ms 51ms 685ms 53.0s 0 transport_latency_assumed best_bid_ask i 9,944,160 300,895 22ms 42ms 221ms 4.5s 0 transport_latency_assumed best_bid_ask k 9,908,508 3,184,149 13ms 27ms 190ms 12.0s 0 transport_latency_assumed book c 2,741,868 2,643,678 6.3min 4.2d 43.0d 116.9d 0 book_staleness book g 525,669 123,085 2.9min 2.2d 33.1d 116.9d 0 book_staleness book h 142,458 21,212 36ms 17.4s 1.9d 115.3d 0 book_staleness book i 517,068 114,337 2.4min 2.1d 32.2d 116.9d 0 book_staleness book k 525,508 115,328 2.6min 2.1d 32.3d 116.9d 0 book_staleness last_trade_price c 41,950 36,076 7ms 41ms 297ms 1.7s 0 transport_latency_assumed last_trade_price g 53,930 172 112ms 3.5s 17.7s 43.2s 0 transport_latency_assumed last_trade_price h 59,757 2,895 22ms 352ms 2.8s 20.5s 0 transport_latency_assumed last_trade_price i 58,590 1,737 29ms 413ms 2.1s 4.5s 0 transport_latency_assumed last_trade_price k 57,932 19,779 14ms 58ms 294ms 8.5s 0 transport_latency_assumed market_resolved c 882 711 16ms 10.9min 14.4min 14.4min 0 transport_latency_assumed market_resolved g 818 81 85ms 2.7min 3.7min 4.1min 0 transport_latency_assumed market_resolved h 827 123 19ms 253ms 1.0min 1.0min 0 transport_latency_assumed market_resolved i 827 72 23ms 46.9s 4.7min 4.7min 0 transport_latency_assumed market_resolved k 816 311 13ms 67ms 4.7min 5.3min 0 transport_latency_assumed new_market c 4,978 3,145 307ms 6.9min 11.2min 17.0min 0 transport_latency_assumed new_market g 3,149 405 363ms 25.2s 4.1min 315.0d 0 transport_latency_assumed new_market h 3,241 976 158ms 17.6s 1.3min 2.7min 0 transport_latency_assumed new_market i 3,223 742 145ms 30.6s 4.2min 5.4min 0 transport_latency_assumed new_market k 3,283 1,158 118ms 1.2min 4.5min 4.7min 0 transport_latency_assumed price_change c 75,940,359 66,169,403 6ms 27ms 237ms 11.3s 0 transport_latency_assumed price_change g 104,286,199 131,248 82ms 290ms 8.1s 43.3s 0 transport_latency_assumed price_change h 109,649,656 6,542,552 19ms 71ms 904ms 53.7s 0 transport_latency_assumed price_change i 105,553,455 3,265,206 22ms 57ms 441ms 8.2s 0 transport_latency_assumed price_change k 105,277,476 33,873,189 13ms 32ms 215ms 13.3s 0 transport_latency_assumed tick_size_change c 2,124 1,863 6ms 19ms 93ms 255ms 0 transport_latency_assumed tick_size_change g 3,268 not meas. 80ms 112ms 453ms 2.1s 0 transport_latency_assumed tick_size_change h 3,376 220 18ms 35ms 243ms 2.2s 0 transport_latency_assumed tick_size_change i 3,232 42 22ms 32ms 85ms 725ms 0 transport_latency_assumed tick_size_change k 3,288 1,251 13ms 22ms 77ms 721ms 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/19/2026-09-23T19.parquet sha256sum 2026-09-23T19.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.