Hour audit: 2026-09-24T05
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-24T05 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-24T05:00:00.000032769+00:00 · last event 2026-09-24T05:59:59.999912963+00:00
VOLUME 112,769,137 rows · 1,134,567,949 bytes (1.06 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured i: 112,723,596 · c: 112,719,866 · k: 112,711,018 · h: 112,681,142 · g: 112,672,972 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 592,450 (0.53%) · c: 105,367,340 (93.44%) · k: 5,540,434 (4.91%) · h: 1,255,842 (1.11%) · g: 13,071 (0.01%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 b403b5fb1aa9945b013bccd7c6c86603402abacc68bee876fc05f896ff0361d8
the corpus checksum ledger names this file with the same digest
joined 112,771,417 to merged 112,769,137, minus 2,280 (minus 0.0020%)
boundary drops 2,280 · 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-24T09:15:50Z 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,906,288 144,634,270 0-49 1f1c1bd4f9567a28fc5f4d1c373cb87f83a619969ca5466fc6747b2a2d42c343 book 129,573 13,831,155 50-50 33d7ca35ee666c2a67ee73f6fc2b27b493fee5b672bab3e00182f5253535fcb9 last_trade_price 46,927 2,652,724 51-51 2a2fd5b9e361fc1dfbe901988cf64e39eb90fce542f89a5a88ceecbaef5449ca market_resolved 1,324 215,653 52-52 66422a28768684041beffb1239feada77c27f6ca0045a9e4d147dbadfcbad296 new_market 813 83,304 53-53 2e7602889f44ad00dfce8a8ce2dafbd8f697c80dff8e5cec300b9bbc9027d736 price_change 99,680,456 971,727,857 54-434 ac60015291a33c818c14ea76432831fd348327510f59ad3ea6dedd22b86807ca tick_size_change 3,756 136,600 435-435 229ad7e5a481278d2352352afc99d163f722366579416d785a639162847ae002 EVENT MIX count share price_change 99,680,456 88.39% best_bid_ask 12,906,288 11.44% book 129,573 0.11% last_trade_price 46,927 0.04% tick_size_change 3,756 <0.01% market_resolved 1,324 <0.01% new_market 813 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,906,562 12,906,288 274 102 FULL book 129,577 129,573 4 14,315 FULL last_trade_price 46,927 46,927 0 0 FULL market_resolved 1,378 1,324 54 55 FULL new_market 813 813 0 0 FULL price_change 99,682,404 99,680,456 1,948 305 FULL tick_size_change 3,756 3,756 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 12,905,578 12,163,733 4ms 9ms 72ms 3.1s 0 transport_latency_assumed best_bid_ask g 12,904,180 314 79ms 97ms 240ms 19.0s 0 transport_latency_assumed best_bid_ask h 12,905,199 118,112 18ms 26ms 104ms 27.9s 0 transport_latency_assumed best_bid_ask i 12,905,525 59,352 21ms 28ms 88ms 5.1s 0 transport_latency_assumed best_bid_ask k 12,905,359 564,777 12ms 17ms 73ms 8.9s 0 transport_latency_assumed book c 104,134 94,139 6ms 285ms 4.6d 98.8d 0 book_staleness book g 104,193 9,378 82ms 3.2s 4.7d 98.8d 0 book_staleness book h 101,728 8,955 21ms 133ms 2.4d 117.3d 0 book_staleness book i 98,528 4,708 24ms 107ms 18.7h 98.7d 0 book_staleness book k 100,266 12,393 15ms 65ms 2.3d 98.8d 0 book_staleness last_trade_price c 46,764 42,328 5ms 18ms 152ms 2.7s 0 transport_latency_assumed last_trade_price g 46,647 3 80ms 225ms 2.5s 19.0s 0 transport_latency_assumed last_trade_price h 46,798 829 19ms 47ms 230ms 8.6s 0 transport_latency_assumed last_trade_price i 46,902 287 23ms 62ms 351ms 2.6s 0 transport_latency_assumed last_trade_price k 46,746 3,480 13ms 25ms 159ms 1.6s 0 transport_latency_assumed market_resolved c 1,289 1,131 5ms 34ms 48.9s 55.5s 0 transport_latency_assumed market_resolved g 1,343 1 81ms 27.5s 52.2s 56.1s 0 transport_latency_assumed market_resolved h 1,290 108 18ms 119ms 46.8s 46.8s 0 transport_latency_assumed market_resolved i 1,290 5 22ms 151ms 46.9s 47.0s 0 transport_latency_assumed market_resolved k 1,343 79 13ms 85ms 55.2s 56.7s 0 transport_latency_assumed new_market c 540 239 70ms 12.5s 56.7s 1.6min 0 transport_latency_assumed new_market g 540 31 166ms 14.6s 38.1s 1.7min 0 transport_latency_assumed new_market h 540 176 72ms 257ms 34.8s 1.6min 0 transport_latency_assumed new_market i 540 162 82ms 15.4s 36.2s 46.4s 0 transport_latency_assumed new_market k 540 205 65ms 12.4s 32.1s 1.2min 0 transport_latency_assumed price_change c 99,657,805 93,062,136 4ms 11ms 86ms 3.6s 0 transport_latency_assumed price_change g 99,612,313 3,340 79ms 102ms 369ms 19.0s 0 transport_latency_assumed price_change h 99,621,831 1,127,647 18ms 30ms 125ms 29.9s 0 transport_latency_assumed price_change i 99,667,055 527,917 22ms 31ms 119ms 7.9s 0 transport_latency_assumed price_change k 99,653,008 4,959,416 12ms 19ms 88ms 9.0s 0 transport_latency_assumed tick_size_change c 3,756 3,634 4ms 7ms 50ms 240ms 0 transport_latency_assumed tick_size_change g 3,756 4 79ms 97ms 170ms 328ms 0 transport_latency_assumed tick_size_change h 3,756 15 18ms 21ms 59ms 254ms 0 transport_latency_assumed tick_size_change i 3,756 19 21ms 26ms 68ms 265ms 0 transport_latency_assumed tick_size_change k 3,756 84 12ms 16ms 68ms 344ms 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/05/2026-09-24T05.parquet sha256sum 2026-09-24T05.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.