Hour audit: 2026-09-26T19
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.
1 finding
- a machine expected this hour contributed nothing. Of the 5 machines expected to be capturing this hour, 1 contributed no rows: g. The hour is still whole on minutes; it simply rests on 4 machines rather than 5.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-26T19 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-26T19:00:00.000006501+00:00 · last event 2026-09-26T19:59:59.989663810+00:00
VOLUME 139,470,260 rows · 1,548,292,299 bytes (1.44 GiB) · 7 products, all holding rows
WITNESSES chik — 4 machines contributed rows
captured i: 121,035,708 · h: 109,498,646 · k: 103,739,858 · c: 70,375,108 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 13,329,252 (9.56%) · h: 15,871,702 (11.38%) · k: 47,907,917 (34.35%) · c: 62,361,389 (44.71%) (rows of the merged file that came from it; these partition it)
5 expected (cghik), 1 contributed nothing: g
INTEGRITY sha256 619d8c3255c7f445be06c07020bb305e1240f8e02bd6fd91d4658f991f12af31
the corpus checksum ledger names this file with the same digest
joined 139,484,038 to merged 139,470,260, minus 13,778 (minus 0.0099%)
boundary drops 13,778 · 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-27T01:53:14Z as chik
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 7/8 pass, 1 finding
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
FINDING a machine expected this hour contributed nothing
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,714,300 145,722,752 0-48 3e071130ad40b04f842280c7f6815d397c362e4a11fecebfa6dc405c90ff00d7 book 6,094,041 161,657,579 49-72 eed9f29a4ba912f1a544f6ba7b95456c723af7c15dece3c55e4454a561218d13 last_trade_price 55,988 3,198,738 73-73 2a6f099c4afaeb0492ff78e5f75d74a5689cfbf20c5e06daad80eb706e529161 market_resolved 13,769 562,235 74-74 3845f17acd5d9223b44212c9b3627553831d6f6d86adc1fcbf5763619bcda12f new_market 25,598 653,217 75-75 55551f61217fea238d7f581b876cf41770f48bfd5ed5407c7c6adb414497673f price_change 120,557,828 1,234,592,730 76-535 1801d686fc01270810c0ed3805b32a5057527d79f99767710d534d780e80f885 tick_size_change 8,736 321,094 536-536 1493ec16069f798ac0cc6bb74a98ae2af2265987298d731880c33275c88a536a EVENT MIX count share price_change 120,557,828 86.44% best_bid_ask 12,714,300 9.12% book 6,094,041 4.37% last_trade_price 55,988 0.04% new_market 25,598 0.02% market_resolved 13,769 <0.01% tick_size_change 8,736 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,714,337 12,714,300 37 67,408 PARTIAL book 6,107,409 6,094,041 13,368 214,615 PARTIAL last_trade_price 55,988 55,988 0 3,402 PARTIAL market_resolved 13,769 13,769 0 3,055 PARTIAL new_market 25,605 25,598 7 3,355 PARTIAL price_change 120,558,194 120,557,828 366 102,548 PARTIAL tick_size_change 8,736 8,736 0 2,184 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 6,224,063 5,606,254 6ms 18ms 270ms 8.8s 0 transport_latency_assumed best_bid_ask h 10,261,570 1,438,072 19ms 60ms 475ms 1.0min 0 transport_latency_assumed best_bid_ask i 11,444,017 1,214,692 22ms 33ms 213ms 7.8s 0 transport_latency_assumed best_bid_ask k 9,692,809 4,455,282 13ms 21ms 166ms 15.7s 0 transport_latency_assumed book c 4,972,714 3,596,743 1.3h 5.3d 45.2d 119.9d 0 book_staleness book h 2,240,820 552,387 1.1h 5.0d 45.0d 119.9d 0 book_staleness book i 1,473,766 424,550 48.6min 5.0d 42.4d 119.9d 0 book_staleness book k 2,578,819 1,520,361 1.1h 5.0d 45.0d 119.9d 0 book_staleness last_trade_price c 25,061 22,103 7ms 31ms 333ms 3.5s 0 transport_latency_assumed last_trade_price h 43,588 6,663 22ms 74ms 777ms 1.0min 0 transport_latency_assumed last_trade_price i 50,169 7,702 24ms 71ms 469ms 4.1s 0 transport_latency_assumed last_trade_price k 40,189 19,520 14ms 40ms 604ms 4.1s 0 transport_latency_assumed market_resolved c 12,258 10,486 21.7min 1.0h 1.3h 1.4h 0 transport_latency_assumed market_resolved h 3,292 725 37ms 8.8min 16.2min 17.4min 0 transport_latency_assumed market_resolved i 3,165 1,279 27ms 9.3min 14.8min 15.5min 0 transport_latency_assumed market_resolved k 3,276 1,279 17ms 13.6min 25.4min 26.6min 0 transport_latency_assumed new_market c 25,148 18,557 20.2min 49.7min 1.3h 1.6h 0 transport_latency_assumed new_market h 4,149 1,157 16.8s 5.4min 12.7min 13.8min 0 transport_latency_assumed new_market i 4,083 968 287ms 9.0min 10.5min 10.7min 0 transport_latency_assumed new_market k 7,296 4,916 5.6min 17.9min 23.5min 26.7min 0 transport_latency_assumed price_change c 59,111,168 53,103,041 6ms 20ms 300ms 9.6s 0 transport_latency_assumed price_change h 96,937,555 13,871,908 19ms 63ms 602ms 1.0min 0 transport_latency_assumed price_change i 108,052,436 11,679,351 23ms 38ms 277ms 7.8s 0 transport_latency_assumed price_change k 91,410,993 41,903,528 13ms 23ms 213ms 15.7s 0 transport_latency_assumed tick_size_change c 4,696 4,205 6ms 17ms 349ms 1.1s 0 transport_latency_assumed tick_size_change h 7,672 790 19ms 55ms 234ms 4.8s 0 transport_latency_assumed tick_size_change i 8,072 710 22ms 31ms 133ms 356ms 0 transport_latency_assumed tick_size_change k 6,476 3,031 13ms 21ms 152ms 1.3s 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-26/19/2026-09-26T19.parquet sha256sum 2026-09-26T19.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.