Hour audit: 2026-09-25T14
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: c. 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-25T14 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-25T14:00:00.000012142+00:00 · last event 2026-09-25T14:59:59.999649+00:00
VOLUME 132,141,145 rows · 1,409,900,712 bytes (1.31 GiB) · 7 products, all holding rows
WITNESSES ghik — 4 machines contributed rows
captured i: 121,915,281 · k: 120,971,032 · h: 115,072,561 · g: 21,322,603 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 13,535,545 (10.24%) · k: 105,690,551 (79.98%) · h: 12,692,447 (9.61%) · g: 222,602 (0.17%) (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 132,141,145 rows exactly, so those pairs supplied none
5 expected (cghik), 1 contributed nothing: c
INTEGRITY sha256 a974bb6b266d50928041afd5f9eaae059fa66cd0b5882b6955196d9f5ebdb1c8
the corpus checksum ledger names this file with the same digest
joined 132,143,612 to merged 132,141,145, minus 2,467 (minus 0.0019%)
boundary drops 2,467 · 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-27T05:36:10Z as ghik
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,442,982 139,206,413 0-47 c530d2d71bf231f002fdbc7a7dff6fc7407303202fbd1a7f3f33481a5ec29e77 book 1,668,365 86,204,472 48-54 e33adf112eecb6f397e2f11aafd61fd66e83ff093f3dbe05409015118dfed4a5 last_trade_price 64,765 3,649,490 55-55 7d9f39c1b2e0a1dce97f2f287cc27b6ade3d4cc22af652a1828761e75908e91f market_resolved 1,326 138,795 56-56 70c72270efc7b1de8be6083bf9ad3bc0b9c56196c3006d1a7e8b0c92e2a10755 new_market 950 98,207 57-57 30e24dafb25454db5090bb9995973925420af7a152006e346d1183d2718f77bc price_change 117,960,089 1,179,003,898 58-507 d11b41cb9ec2fae472cb639dcf573a9c433247ec2de3870e4ae82c4c83a3c80f tick_size_change 2,668 98,522 508-508 a30e66d6a4230faed6cdedc8d720240c2a59332d4d5db14a67388f0d1e39f154 EVENT MIX count share price_change 117,960,089 89.27% best_bid_ask 12,442,982 9.42% book 1,668,365 1.26% last_trade_price 64,765 0.05% tick_size_change 2,668 <0.01% market_resolved 1,326 <0.01% new_market 950 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,443,208 12,442,982 226 55,978 PARTIAL book 1,668,379 1,668,365 14 209,988 PARTIAL last_trade_price 64,766 64,765 1 3,767 PARTIAL market_resolved 1,326 1,326 0 813 PARTIAL new_market 950 950 0 626 PARTIAL price_change 117,962,315 117,960,089 2,226 87,584 PARTIAL tick_size_change 2,668 2,668 0 667 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 2,038,146 22,504 81ms 125ms 689ms 21.5s 0 transport_latency_assumed best_bid_ask h 10,811,612 1,023,734 19ms 39ms 148ms 51.5s 0 transport_latency_assumed best_bid_ask i 11,463,324 1,194,064 22ms 34ms 124ms 4.2s 0 transport_latency_assumed best_bid_ask k 11,460,717 10,202,680 13ms 25ms 127ms 11.1s 0 transport_latency_assumed book g 26,700 2,717 110ms 13.9s 6.0d 47.0d 0 book_staleness book h 1,395,172 1,254,567 2.0h 4.0d 41.2d 118.7d 0 book_staleness book i 988,443 181,215 1.4h 3.8d 41.0d 118.7d 0 book_staleness book k 994,785 229,866 1.5h 3.8d 41.0d 118.7d 0 book_staleness last_trade_price g 11,920 87 105ms 4.1s 15.1s 21.1s 0 transport_latency_assumed last_trade_price h 56,669 5,691 21ms 67ms 410ms 42.2s 0 transport_latency_assumed last_trade_price i 59,985 7,160 24ms 69ms 317ms 3.8s 0 transport_latency_assumed last_trade_price k 59,826 51,827 14ms 40ms 197ms 1.6s 0 transport_latency_assumed market_resolved g 101 1 82ms 233ms 52.3s 52.3s 0 transport_latency_assumed market_resolved h 1,094 411 57ms 9.7min 14.6min 15.0min 0 transport_latency_assumed market_resolved i 978 288 42ms 6.0min 10.9min 11.3min 0 transport_latency_assumed market_resolved k 984 626 19ms 9.4min 11.6min 11.7min 0 transport_latency_assumed new_market g 103 10 268ms 642ms 32.1s 32.4s 0 transport_latency_assumed new_market h 680 381 157ms 52.2s 10.0min 1.9h 0 transport_latency_assumed new_market i 644 230 137ms 19.6s 6.4min 1.9h 0 transport_latency_assumed new_market k 645 329 99ms 21.0s 6.9min 6.9min 0 transport_latency_assumed price_change g 19,244,993 197,283 83ms 213ms 9.9s 21.5s 0 transport_latency_assumed price_change h 102,805,066 10,407,470 19ms 44ms 206ms 53.6s 0 transport_latency_assumed price_change i 109,399,491 12,152,397 22ms 40ms 180ms 4.9s 0 transport_latency_assumed price_change k 108,451,531 95,202,939 13ms 29ms 150ms 11.1s 0 transport_latency_assumed tick_size_change g 640 not meas. 78ms 90ms 476ms 509ms 0 transport_latency_assumed tick_size_change h 2,268 193 19ms 36ms 127ms 2.2s 0 transport_latency_assumed tick_size_change i 2,416 191 22ms 35ms 88ms 563ms 0 transport_latency_assumed tick_size_change k 2,544 2,284 12ms 27ms 123ms 253ms 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-25/14/2026-09-25T14.parquet sha256sum 2026-09-25T14.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.