Hour audit: 2026-09-24T12
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-24T12 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-24T12:00:00.000001376+00:00 · last event 2026-09-24T12:59:59.999936842+00:00
VOLUME 123,432,597 rows · 1,330,548,751 bytes (1.24 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured h: 122,785,134 · i: 122,782,257 · g: 122,570,767 · c: 118,176,214 · k: 118,027,239 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 2,196,971 (1.78%) · i: 867,276 (0.70%) · g: 26,370 (0.02%) · c: 107,864,043 (87.39%) · k: 12,477,937 (10.11%) (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 123,432,597 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 08b614ae28785c1d9e66553c4e5ddf111b760ce54a63da2e291089ace58093ca
the corpus checksum ledger names this file with the same digest
joined 123,434,789 to merged 123,432,597, minus 2,192 (minus 0.0018%)
boundary drops 2,192 · 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-24T14:53:18Z 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 12,755,723 148,122,688 0-48 f2e5d3fce28ce1760e79f453a57648a2f6d143f170ddcabfb7235bbc55f508c9 book 722,385 62,467,319 49-51 eefd74d498d6339b8ca1a0bda0789f1ec1b2435388ddc1423d7b6233dd3ba36c last_trade_price 57,814 3,329,811 52-52 85ef3bfb28335b2801de97255450bde9de247e1ff1335ff087a603cdf421cccb market_resolved 1,094 155,867 53-53 723d9abda127aa7e2b85177835f58837b5ad8e8e6b325ded9552bf04f8473267 new_market 1,037 112,655 54-54 8295c491fca7a852939f07cf91d2eaa1cf375ecd93683c6ae2b451e06cc30718 price_change 109,890,968 1,114,826,027 55-474 b596d6f77d0a5495d78ddd6dfd463eaba17ae26fe46cc6869970d9024c19fdce tick_size_change 3,576 130,284 475-475 f5874a539874b096f35b40b02aba45b248faa6b4099169132f462984eeab87a2 EVENT MIX count share price_change 109,890,968 89.03% best_bid_ask 12,755,723 10.33% book 722,385 0.59% last_trade_price 57,814 0.05% tick_size_change 3,576 <0.01% market_resolved 1,094 <0.01% new_market 1,037 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,755,941 12,755,723 218 774 FULL book 722,391 722,385 6 193,422 FULL last_trade_price 57,814 57,814 0 165 FULL market_resolved 1,094 1,094 0 46 FULL new_market 1,037 1,037 0 10 FULL price_change 109,892,936 109,890,968 1,968 138 FULL tick_size_change 3,576 3,576 0 96 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 12,256,391 11,263,613 5ms 13ms 109ms 5.9s 0 transport_latency_assumed best_bid_ask g 12,748,075 753 80ms 105ms 387ms 23.2s 0 transport_latency_assumed best_bid_ask h 12,753,562 209,147 18ms 34ms 152ms 23.9s 0 transport_latency_assumed best_bid_ask i 12,752,847 80,422 22ms 32ms 125ms 9.4s 0 transport_latency_assumed best_bid_ask k 12,260,638 1,201,788 13ms 19ms 84ms 4.9s 0 transport_latency_assumed book c 525,501 508,746 5.0min 2.9d 36.4d 117.6d 0 book_staleness book g 143,489 18,186 105ms 11.7min 17.1d 99.1d 0 book_staleness book h 126,617 9,469 23ms 379ms 2.7d 99.1d 0 book_staleness book i 154,846 23,858 32ms 23.1min 17.1d 117.6d 0 book_staleness book k 513,672 162,126 9.0min 2.8d 35.3d 117.6d 0 book_staleness last_trade_price c 54,878 48,827 6ms 28ms 242ms 1.2s 0 transport_latency_assumed last_trade_price g 56,257 29 92ms 1.0s 11.0s 23.0s 0 transport_latency_assumed last_trade_price h 57,657 1,198 19ms 86ms 607ms 9.1s 0 transport_latency_assumed last_trade_price i 57,422 460 25ms 124ms 993ms 4.1s 0 transport_latency_assumed last_trade_price k 54,679 7,300 14ms 35ms 226ms 1.0s 0 transport_latency_assumed market_resolved c 971 834 5ms 33.3s 5.4min 6.1min 0 transport_latency_assumed market_resolved g 963 not meas. 82ms 386ms 48.3s 49.3s 0 transport_latency_assumed market_resolved h 963 145 19ms 27.7s 55.6s 55.6s 0 transport_latency_assumed market_resolved i 963 26 23ms 160ms 49.8s 51.3s 0 transport_latency_assumed market_resolved k 929 89 13ms 37.8s 4.6min 5.6min 0 transport_latency_assumed new_market c 725 366 87ms 18.4s 1.4min 5.0min 0 transport_latency_assumed new_market g 719 110 301ms 20.6s 39.9s 1.6min 0 transport_latency_assumed new_market h 719 114 132ms 17.5s 38.7s 60.0s 0 transport_latency_assumed new_market i 719 178 113ms 20.3s 58.9s 1.7min 0 transport_latency_assumed new_market k 741 269 84ms 32.8s 55.1min 1.3h 0 transport_latency_assumed price_change c 105,334,356 96,038,624 5ms 16ms 128ms 6.0s 0 transport_latency_assumed price_change g 109,617,688 7,292 81ms 138ms 1.8s 23.2s 0 transport_latency_assumed price_change h 109,842,040 1,976,816 18ms 40ms 212ms 24.1s 0 transport_latency_assumed price_change i 109,811,884 762,284 22ms 40ms 204ms 9.6s 0 transport_latency_assumed price_change k 105,193,204 11,105,952 13ms 22ms 101ms 5.2s 0 transport_latency_assumed tick_size_change c 3,392 3,033 5ms 19ms 197ms 328ms 0 transport_latency_assumed tick_size_change g 3,576 not meas. 81ms 124ms 361ms 1.0s 0 transport_latency_assumed tick_size_change h 3,576 82 18ms 40ms 136ms 3.0s 0 transport_latency_assumed tick_size_change i 3,576 48 22ms 39ms 130ms 262ms 0 transport_latency_assumed tick_size_change k 3,376 413 13ms 21ms 84ms 159ms 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-24/12/2026-09-24T12.parquet sha256sum 2026-09-24T12.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.