Hour audit: 2026-09-22T23
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-22T23 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-22T23:00:00.001643603+00:00 · last event 2026-09-22T23:59:59.999565354+00:00
VOLUME 123,906,225 rows · 1,353,268,249 bytes (1.26 GiB) · 7 products, all holding rows
WITNESSES cfhik — 5 machines contributed rows
captured i: 121,524,973 · h: 121,355,263 · f: 112,036,904 · c: 102,784,153 · k: 102,252,176 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 2,669,889 (2.15%) · h: 7,641,441 (6.17%) · f: 524,090 (0.42%) · c: 92,283,713 (74.48%) · k: 20,787,092 (16.78%) (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 123,906,225 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 616c35e8684a74878d003744c7a2f7cea512678a5964c322e39de18a3ccdea5f
the corpus checksum ledger names this file with the same digest
joined 123,937,532 to merged 123,906,225, minus 31,307 (minus 0.0253%)
boundary drops 31,307 · 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-23T02:22:34Z 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 12,415,034 142,463,710 0-47 06e608535322913ede347409072d3e5b4741db25158d6d14678fe2a3fffae14f book 2,844,848 116,054,953 48-58 54bd5c65c1af1648e44b69fe5baeb232a8562adaa84bd970c7d96c7efc1f7479 last_trade_price 56,169 3,272,700 59-59 ec7a793415dda51d15455fc8746d936e799e93ddf7183ab0611ce16f25ba51a5 market_resolved 3,098 328,447 60-60 f9dfe5e93636080fc5dce85a5eb6fb4c24333915b46ae7bc261780e4b15c4e74 new_market 2,742 252,417 61-61 05c57bed548fca2dc6e013de7eb3807f0f6bd5f347f7e026fd70a453056b3094 price_change 108,582,014 1,089,399,218 62-476 22993ca9d6d4f21e3299fb406e78b61722014c227b51b7a96c319324c37b474e tick_size_change 2,320 86,575 477-477 4a40655e7ef2ada7aa89cc3259d04e0fd50a7a86e4fe5eec0e4b96aef4580e68 EVENT MIX count share price_change 108,582,014 87.63% best_bid_ask 12,415,034 10.02% book 2,844,848 2.30% last_trade_price 56,169 0.05% market_resolved 3,098 <0.01% new_market 2,742 <0.01% tick_size_change 2,320 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,415,136 12,415,034 102 4,052 FULL book 2,875,006 2,844,848 30,158 87,173 FULL last_trade_price 56,169 56,169 0 539 FULL market_resolved 3,115 3,098 17 657 FULL new_market 2,744 2,742 2 65 FULL price_change 108,583,042 108,582,014 1,028 1,757 FULL tick_size_change 2,320 2,320 0 161 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,325,992 9,403,850 5ms 17ms 186ms 18.1s 0 transport_latency_assumed best_bid_ask f 11,376,138 9,572 49ms 69ms 313ms 11.9s 0 transport_latency_assumed best_bid_ask h 12,409,732 728,207 18ms 36ms 305ms 46.9s 0 transport_latency_assumed best_bid_ask i 12,409,451 244,390 23ms 34ms 152ms 4.0s 0 transport_latency_assumed best_bid_ask k 10,326,768 2,029,015 12ms 22ms 126ms 7.1s 0 transport_latency_assumed book c 1,890,596 1,366,827 12.0min 3.4d 42.2d 116.1d 0 book_staleness book f 1,076,491 411,490 9.4min 3.4d 41.2d 116.1d 0 book_staleness book h 396,847 138,220 2.3min 1.3d 31.4d 116.1d 0 book_staleness book i 552,826 171,165 4.9min 2.1d 37.6d 116.1d 0 book_staleness book k 1,777,695 757,146 10.3min 3.4d 42.2d 116.1d 0 book_staleness last_trade_price c 47,558 41,573 6ms 34ms 350ms 7.5s 0 transport_latency_assumed last_trade_price f 50,807 149 52ms 665ms 6.0s 11.9s 0 transport_latency_assumed last_trade_price h 55,868 4,221 19ms 68ms 814ms 13.6s 0 transport_latency_assumed last_trade_price i 55,757 1,032 25ms 186ms 1.6s 3.6s 0 transport_latency_assumed last_trade_price k 45,084 9,194 14ms 40ms 253ms 2.9s 0 transport_latency_assumed market_resolved c 2,159 1,825 22ms 7.9min 13.1min 13.3min 0 transport_latency_assumed market_resolved f 1,408 141 50ms 1.4min 4.5min 5.7min 0 transport_latency_assumed market_resolved h 1,406 70 18ms 12.6s 54.4s 58.6s 0 transport_latency_assumed market_resolved i 1,406 191 23ms 11.0s 52.6s 56.9s 0 transport_latency_assumed market_resolved k 2,035 871 51ms 12.0min 15.8min 16.9min 0 transport_latency_assumed new_market c 1,746 845 92ms 5.2min 8.5min 9.6min 0 transport_latency_assumed new_market f 1,591 256 183ms 24.7s 7.4min 9.8min 0 transport_latency_assumed new_market h 1,565 450 147ms 20.1s 1.0min 6.5min 0 transport_latency_assumed new_market i 1,565 330 139ms 19.0s 45.2s 4.7min 0 transport_latency_assumed new_market k 1,942 861 167ms 6.7min 11.9min 15.4min 0 transport_latency_assumed price_change c 90,514,098 81,466,984 5ms 21ms 215ms 39.7s 0 transport_latency_assumed price_change f 99,528,365 102,482 49ms 84ms 687ms 11.9s 0 transport_latency_assumed price_change h 108,487,525 6,770,174 18ms 42ms 333ms 47.3s 0 transport_latency_assumed price_change i 108,501,648 2,252,744 23ms 44ms 243ms 4.0s 0 transport_latency_assumed price_change k 90,096,648 17,989,630 13ms 26ms 143ms 8.3s 0 transport_latency_assumed tick_size_change c 2,004 1,809 5ms 18ms 94ms 218ms 0 transport_latency_assumed tick_size_change f 2,104 not meas. 49ms 59ms 130ms 238ms 0 transport_latency_assumed tick_size_change h 2,320 99 18ms 39ms 84ms 129ms 0 transport_latency_assumed tick_size_change i 2,320 37 22ms 33ms 87ms 183ms 0 transport_latency_assumed tick_size_change k 2,004 375 13ms 27ms 71ms 98ms 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-22/23/2026-09-22T23.parquet sha256sum 2026-09-22T23.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.