Hour audit: 2026-09-23T08
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-23T08 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-23T08:00:00.000285796+00:00 · last event 2026-09-23T08:59:59.999943037+00:00
VOLUME 117,551,304 rows · 1,249,779,699 bytes (1.16 GiB) · 7 products, all holding rows
WITNESSES cfhik — 5 machines contributed rows
captured c: 116,539,447 · i: 116,497,792 · h: 116,356,143 · f: 111,890,754 · k: 107,674,567 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 107,554,081 (91.50%) · i: 1,216,032 (1.03%) · h: 1,889,261 (1.61%) · f: 216,340 (0.18%) · k: 6,675,590 (5.68%) (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 117,551,304 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 b057584c8c2ad2d7727102de25d9303e91127aa065573d7c8a4381dcd0deb579
the corpus checksum ledger names this file with the same digest
joined 117,557,620 to merged 117,551,304, minus 6,316 (minus 0.0054%)
boundary drops 6,316 · 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-23T11:07:50Z as cfhik
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 our incident register was checked against the venue's own status feed at 2026-09-23T20:35Z and names no event in this hour. That is a statement about what they published, not a check that every message they sent reached us.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 11,304,756 131,652,667 0-43 167142138e474f3a6bdce388e0970b72c9c3bab773e8fb7d0820c6ba0fc7c93e book 1,079,315 71,299,698 44-48 1918f7880d2cb29008b2fb9429ff4876dd5db45b368ed1e38b686d6afb7b8dde last_trade_price 55,357 3,141,063 49-49 cfc0284b1ed0cb345eca06d4c30173dd9a1bce93f81a96a0d95bf7ecd92bbf05 market_resolved 784 115,094 50-50 054fcfcc7645edb6e5b02d27b46cfb0d58da5d055f4bfde269cdcfb4cdfc4cf5 new_market 1,510 161,572 51-51 a3bd7bfbc67644251a7d5891ec8432dd623332ff5722827bf06d72cee691b6df price_change 105,106,798 1,041,967,288 52-452 46c5da422ecd399d6c7b81473dee6366efededf4346d9bb164e6422116db8a4c tick_size_change 2,784 102,707 453-453 71d2490807ac823e7c40b5113508ee19cda2291a7446c09c20b84d6ffea88fd2 EVENT MIX count share price_change 105,106,798 89.41% best_bid_ask 11,304,756 9.62% book 1,079,315 0.92% last_trade_price 55,357 0.05% tick_size_change 2,784 <0.01% new_market 1,510 <0.01% market_resolved 784 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,304,930 11,304,756 174 1,089 FULL book 1,084,305 1,079,315 4,990 190,308 FULL last_trade_price 55,357 55,357 0 194 FULL market_resolved 784 784 0 118 FULL new_market 1,510 1,510 0 0 FULL price_change 105,107,950 105,106,798 1,152 218 FULL tick_size_change 2,784 2,784 0 105 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,303,845 10,493,924 5ms 13ms 112ms 6.5s 0 transport_latency_assumed best_bid_ask f 10,824,206 3,771 49ms 63ms 245ms 17.3s 0 transport_latency_assumed best_bid_ask h 11,303,419 163,434 19ms 30ms 185ms 46.2s 0 transport_latency_assumed best_bid_ask i 11,303,384 111,448 20ms 29ms 130ms 7.7s 0 transport_latency_assumed best_bid_ask k 10,423,494 532,179 14ms 21ms 105ms 11.8s 0 transport_latency_assumed book c 119,371 104,199 7ms 91ms 1.5d 97.9d 0 book_staleness book f 536,138 166,759 6.3min 2.5d 38.6d 116.4d 0 book_staleness book h 122,270 9,704 23ms 587ms 2.6d 97.9d 0 book_staleness book i 119,530 5,414 24ms 459ms 1.5d 97.9d 0 book_staleness book k 908,920 793,239 7.6min 3.5d 41.7d 116.4d 0 book_staleness last_trade_price c 55,155 49,812 6ms 25ms 207ms 2.9s 0 transport_latency_assumed last_trade_price f 53,535 50 52ms 341ms 8.5s 17.1s 0 transport_latency_assumed last_trade_price h 55,214 1,366 20ms 80ms 548ms 27.1s 0 transport_latency_assumed last_trade_price i 55,138 446 24ms 139ms 735ms 4.9s 0 transport_latency_assumed last_trade_price k 49,283 3,683 15ms 39ms 218ms 1.1s 0 transport_latency_assumed market_resolved c 713 625 5ms 44ms 59.5s 59.5s 0 transport_latency_assumed market_resolved f 686 1 51ms 275ms 59.7s 4.8min 0 transport_latency_assumed market_resolved h 713 14 20ms 485ms 59.8s 59.8s 0 transport_latency_assumed market_resolved i 713 77 22ms 297ms 59.0s 59.1s 0 transport_latency_assumed market_resolved k 632 67 15ms 18.0s 4.9min 5.4min 0 transport_latency_assumed new_market c 1,041 440 82ms 14.4s 1.4min 1.7min 0 transport_latency_assumed new_market f 1,041 89 177ms 12.1s 1.5min 3.8min 0 transport_latency_assumed new_market h 1,041 300 127ms 12.6s 1.5min 1.7min 0 transport_latency_assumed new_market i 1,041 340 111ms 22.9s 1.5min 1.7min 0 transport_latency_assumed new_market k 1,041 341 87ms 16.3s 1.5min 1.7min 0 transport_latency_assumed price_change c 105,056,538 96,902,469 5ms 15ms 136ms 6.9s 0 transport_latency_assumed price_change f 100,472,520 45,670 49ms 78ms 751ms 17.6s 0 transport_latency_assumed price_change h 104,870,702 1,714,396 19ms 36ms 298ms 52.5s 0 transport_latency_assumed price_change i 105,015,202 1,098,282 21ms 37ms 280ms 7.7s 0 transport_latency_assumed price_change k 96,288,677 5,345,981 14ms 24ms 137ms 12.0s 0 transport_latency_assumed tick_size_change c 2,784 2,612 5ms 11ms 55ms 169ms 0 transport_latency_assumed tick_size_change f 2,628 not meas. 49ms 55ms 120ms 255ms 0 transport_latency_assumed tick_size_change h 2,784 47 19ms 35ms 83ms 274ms 0 transport_latency_assumed tick_size_change i 2,784 25 21ms 40ms 82ms 353ms 0 transport_latency_assumed tick_size_change k 2,520 100 14ms 23ms 57ms 191ms 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-23/08/2026-09-23T08.parquet sha256sum 2026-09-23T08.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.