Hour audit: 2026-09-27T18
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-27T18 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-27T18:00:00.000009504+00:00 · last event 2026-09-27T18:59:59.999970067+00:00
VOLUME 135,995,069 rows · 1,602,532,620 bytes (1.49 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured h: 132,112,593 · k: 126,659,122 · i: 126,632,284 · g: 120,415,319 · c: 81,392,951 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 11,341,762 (8.34%) · k: 49,565,361 (36.45%) · i: 3,857,542 (2.84%) · g: 289,349 (0.21%) · c: 70,941,055 (52.16%) (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 135,995,069 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 8b98c2ad45863973fe33866b493dd4bf16b995d6a9130576f937dea12e93b9d9
the corpus checksum ledger names this file with the same digest
joined 136,047,337 to merged 135,995,069, minus 52,268 (minus 0.0384%)
boundary drops 52,268 · 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-27T20:50:42Z 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 status feed unobserved for this hour. Our incident register was last checked against the venue's feed at 2026-09-23T20:35Z, before this hour ended, so nothing has looked yet. This is a could-not-look and never an all-clear.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 14,096,612 167,714,091 0-53 b5e1cbff95eed327e9d571c146f6f900368fb20c78d0be96a729067864f809c1 book 3,933,604 118,588,183 54-69 df7bf99bc07e9b4ec54f0c3633cf74f26becb1dd5e51dfa6ca91ad8992ef817f last_trade_price 81,473 4,580,407 70-70 495a5e988eac5563efad89449a7aa34697e83c0100efe924b450ab22576fb9dd market_resolved 7,514 454,162 71-71 357b0ea45603869ed2f1e111fc814c339f15a30e3a9b36e93dfd4a0e9be52118 new_market 23,030 892,256 72-72 162f8bbd3a35f70408028e4b0bb5f325840a5b2e6aecb9185966b022a2d85b4c price_change 117,847,072 1,308,546,908 73-522 034e2c08b40cf62f08fe2669cc5e1b40c8c4ace7f127eac3e36f9d3a50ec1354 tick_size_change 5,764 209,740 523-523 dd12cc1e3fcf9e304587bc8fb33c8f18cd84f04ea55f9a9bcca6f1f59c0850bc EVENT MIX count share price_change 117,847,072 86.66% best_bid_ask 14,096,612 10.37% book 3,933,604 2.89% last_trade_price 81,473 0.06% new_market 23,030 0.02% market_resolved 7,514 <0.01% tick_size_change 5,764 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 14,097,302 14,096,612 690 10,114 FULL book 3,979,338 3,933,604 45,734 208,620 FULL last_trade_price 81,478 81,473 5 1,237 FULL market_resolved 7,520 7,514 6 838 FULL new_market 23,121 23,030 91 3,177 FULL price_change 117,852,814 117,847,072 5,742 12,925 FULL tick_size_change 5,764 5,764 0 696 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,237,045 7,209,706 6ms 18ms 168ms 6.4s 0 transport_latency_assumed best_bid_ask g 12,724,048 1,880 81ms 131ms 557ms 34.2s 0 transport_latency_assumed best_bid_ask h 14,095,672 1,220,714 18ms 29ms 252ms 1.4min 0 transport_latency_assumed best_bid_ask i 13,479,241 362,337 21ms 28ms 113ms 3.8s 0 transport_latency_assumed best_bid_ask k 13,436,941 5,301,975 13ms 23ms 147ms 12.3s 0 transport_latency_assumed book c 3,601,720 3,106,343 39.2min 4.8d 46.0d 120.9d 0 book_staleness book g 1,009,644 270,116 9.8min 2.9d 36.2d 120.8d 0 book_staleness book h 167,890 14,439 23ms 104ms 3.4s 102.3d 0 book_staleness book i 627,088 328,275 3.8min 18.6h 36.2d 120.8d 0 book_staleness book k 602,187 214,431 4.0min 16.4h 36.2d 120.8d 0 book_staleness last_trade_price c 48,382 42,093 7ms 27ms 227ms 1.5s 0 transport_latency_assumed last_trade_price g 72,743 54 92ms 1.2s 16.8s 34.2s 0 transport_latency_assumed last_trade_price h 81,353 7,003 20ms 77ms 676ms 8.2s 0 transport_latency_assumed last_trade_price i 77,500 1,878 22ms 96ms 832ms 2.4s 0 transport_latency_assumed last_trade_price k 77,697 30,445 14ms 41ms 296ms 3.7s 0 transport_latency_assumed market_resolved c 6,789 6,137 19.3min 1.1h 1.5h 1.6h 0 transport_latency_assumed market_resolved g 1,815 82 82ms 42.6s 11.2min 12.6min 0 transport_latency_assumed market_resolved h 1,784 311 19ms 17.3s 48.9s 49.0s 0 transport_latency_assumed market_resolved i 1,845 188 22ms 41.1s 7.6min 7.6min 0 transport_latency_assumed market_resolved k 2,010 796 15ms 5.8min 10.8min 10.8min 0 transport_latency_assumed new_market c 22,670 21,136 33.5min 1.2h 1.4h 1.6h 0 transport_latency_assumed new_market g 2,039 197 282ms 3.3min 15.8min 16.3min 0 transport_latency_assumed new_market h 1,900 302 113ms 387ms 2.8min 4.4min 0 transport_latency_assumed new_market i 2,227 904 106ms 7.6min 8.6min 8.9min 0 transport_latency_assumed new_market k 1,932 491 95ms 354ms 7.5min 9.0min 0 transport_latency_assumed price_change c 69,472,693 60,552,285 6ms 20ms 182ms 6.5s 0 transport_latency_assumed price_change g 106,599,878 17,020 81ms 170ms 1.7s 34.2s 0 transport_latency_assumed price_change h 117,758,230 10,098,615 19ms 34ms 297ms 1.4min 0 transport_latency_assumed price_change i 112,439,219 3,163,759 21ms 33ms 173ms 3.8s 0 transport_latency_assumed price_change k 112,532,771 44,015,393 13ms 26ms 161ms 12.3s 0 transport_latency_assumed tick_size_change c 3,652 3,355 6ms 12ms 45ms 231ms 0 transport_latency_assumed tick_size_change g 5,152 not meas. 80ms 101ms 357ms 690ms 0 transport_latency_assumed tick_size_change h 5,764 378 18ms 25ms 129ms 1.1s 0 transport_latency_assumed tick_size_change i 5,164 201 21ms 30ms 93ms 427ms 0 transport_latency_assumed tick_size_change k 5,584 1,830 13ms 22ms 97ms 327ms 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-27/18/2026-09-27T18.parquet sha256sum 2026-09-27T18.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.