Hour audit: 2026-09-23T07
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-23T07 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-23T07:00:00.000011553+00:00 · last event 2026-09-23T07:59:59.999924033+00:00
VOLUME 117,131,459 rows · 1,235,164,343 bytes (1.15 GiB) · 7 products, all holding rows
WITNESSES cfhik — 5 machines contributed rows
captured c: 116,482,812 · k: 116,438,168 · i: 116,414,239 · h: 116,339,045 · f: 111,371,647 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 107,328,967 (91.63%) · k: 6,739,994 (5.75%) · i: 928,607 (0.79%) · h: 1,510,142 (1.29%) · f: 623,749 (0.53%) (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,131,459 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 d4aa48fd677b4718779466b330eaa1f50a91bcf11b8941d2447510ca5cf73a46
the corpus checksum ledger names this file with the same digest
joined 117,141,741 to merged 117,131,459, minus 10,282 (minus 0.0088%)
boundary drops 10,282 · 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-23T10:07:27Z 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,316,135 131,687,057 0-43 e0849dd82a2353acc2540a90dd8b4aa1b690ebb2a5bd90bc33b6594e40e7cc3e book 753,179 59,236,812 44-46 c12191fb04ebe100c3d5f435a2b8bb4eb11e6f4d9ce577dfc1a5725108ef034a last_trade_price 54,668 3,084,680 47-47 fc480ae94962da451b6e42bd750cccd96dc83f722452b3df6982d0ae588d80ae market_resolved 630 101,091 48-48 74e0b4bce5e26d677875d5bd9ea399e5a5f68520d818cfe60d1df58775df6982 new_market 1,565 155,002 49-49 55b64ad8bfe393f9c25cfc77695a48a9d4e1cdf861567162cfb4878626c80e5c price_change 105,002,754 1,039,472,186 50-450 e2f940863e7a1401ee51f0e6b4ca3e6e30597be0b8ab69191c7fd04326955561 tick_size_change 2,528 93,427 451-451 2f103108ce537c99130661bbadd046d3e82450480bd6cd2ff5970cb20a4e395e EVENT MIX count share price_change 105,002,754 89.65% best_bid_ask 11,316,135 9.66% book 753,179 0.64% last_trade_price 54,668 0.05% tick_size_change 2,528 <0.01% new_market 1,565 <0.01% market_resolved 630 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,316,273 11,316,135 138 344 FULL book 762,085 753,179 8,906 190,287 FULL last_trade_price 54,668 54,668 0 68 FULL market_resolved 630 630 0 32 FULL new_market 1,565 1,565 0 0 FULL price_change 105,003,992 105,002,754 1,238 125 FULL tick_size_change 2,528 2,528 0 26 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,315,289 10,491,987 5ms 12ms 103ms 6.4s 0 transport_latency_assumed best_bid_ask f 10,771,838 3,150 49ms 63ms 208ms 6.5s 0 transport_latency_assumed best_bid_ask h 11,313,884 129,792 18ms 34ms 161ms 20.4s 0 transport_latency_assumed best_bid_ask i 11,314,018 82,828 21ms 31ms 116ms 7.6s 0 transport_latency_assumed best_bid_ask k 11,314,819 608,378 13ms 21ms 93ms 5.7s 0 transport_latency_assumed book c 135,429 112,794 7ms 8.8min 15.9d 97.9d 0 book_staleness book f 704,160 578,727 4.5min 2.7d 38.9d 116.4d 0 book_staleness book h 123,574 11,875 23ms 2.9s 4.6d 97.9d 0 book_staleness book i 157,882 29,712 36ms 34.6min 17.7d 116.4d 0 book_staleness book k 135,705 20,071 17ms 10.4min 15.9d 116.4d 0 book_staleness last_trade_price c 54,493 48,992 6ms 23ms 210ms 1.9s 0 transport_latency_assumed last_trade_price f 51,874 107 51ms 165ms 1.8s 6.5s 0 transport_latency_assumed last_trade_price h 54,440 969 19ms 69ms 399ms 8.7s 0 transport_latency_assumed last_trade_price i 54,266 436 24ms 111ms 636ms 2.9s 0 transport_latency_assumed last_trade_price k 54,393 4,164 14ms 39ms 205ms 1.2s 0 transport_latency_assumed market_resolved c 593 478 5ms 134ms 58.0s 58.0s 0 transport_latency_assumed market_resolved f 568 33 50ms 324ms 6.1min 6.1min 0 transport_latency_assumed market_resolved h 593 43 20ms 180ms 37.8s 43.4s 0 transport_latency_assumed market_resolved i 593 33 23ms 228ms 37.5s 43.9s 0 transport_latency_assumed market_resolved k 593 43 15ms 143ms 39.2s 45.2s 0 transport_latency_assumed new_market c 992 504 79ms 25.2s 2.7min 4.0min 0 transport_latency_assumed new_market f 1,007 164 172ms 33.0s 4.8min 5.2min 0 transport_latency_assumed new_market h 992 296 114ms 16.6s 2.2min 3.0min 0 transport_latency_assumed new_market i 992 255 104ms 16.0s 2.4min 2.9min 0 transport_latency_assumed new_market k 992 346 82ms 15.1s 2.7min 2.9min 0 transport_latency_assumed price_change c 104,973,488 96,671,960 5ms 15ms 119ms 6.7s 0 transport_latency_assumed price_change f 99,839,776 41,568 49ms 74ms 404ms 10.2s 0 transport_latency_assumed price_change h 104,843,034 1,367,100 18ms 39ms 219ms 20.4s 0 transport_latency_assumed price_change i 104,883,960 815,330 21ms 38ms 208ms 7.6s 0 transport_latency_assumed price_change k 104,929,138 6,106,796 13ms 24ms 120ms 6.0s 0 transport_latency_assumed tick_size_change c 2,528 2,252 5ms 21ms 297ms 454ms 0 transport_latency_assumed tick_size_change f 2,424 not meas. 49ms 70ms 166ms 391ms 0 transport_latency_assumed tick_size_change h 2,528 67 18ms 36ms 84ms 403ms 0 transport_latency_assumed tick_size_change i 2,528 13 21ms 35ms 95ms 306ms 0 transport_latency_assumed tick_size_change k 2,528 196 13ms 24ms 59ms 448ms 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/07/2026-09-23T07.parquet sha256sum 2026-09-23T07.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.