Hour audit: 2026-09-24T01
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-24T01 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-24T01:00:00.000266147+00:00 · last event 2026-09-24T01:59:59.999927022+00:00
VOLUME 126,654,817 rows · 1,366,946,452 bytes (1.27 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured i: 125,246,900 · h: 125,045,121 · c: 120,642,762 · g: 120,132,084 · k: 111,418,537 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 1,605,213 (1.27%) · h: 3,195,068 (2.52%) · c: 110,203,260 (87.01%) · g: 131,746 (0.10%) · k: 11,519,530 (9.10%) (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 126,654,817 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 5ce0811c1cf9233df819cc53580af08b02b9025efa95ad52e3a13602c669d090
the corpus checksum ledger names this file with the same digest
joined 126,657,670 to merged 126,654,817, minus 2,853 (minus 0.0023%)
boundary drops 2,853 · 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-24T07:28:18Z as cghik
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 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,363,046 143,109,523 0-47 920b72280b456d533bb4e709289d1d020086e729e3cb69694cfa2178c23ae71d book 1,634,532 86,815,679 48-54 7a9f94b0705866ac8b5db01927a69e1caa072892eaada87bd9616f898cb4b1ac last_trade_price 64,503 3,537,784 55-55 ab5dc6279e762f6ce43570bfce01b7fa50130ef276f5e772dfaa7d6ff612cc49 market_resolved 2,217 276,588 56-56 36a89e907d8902ee69892504d7251dc3dfea3cb5da34136a2e65df5008016830 new_market 1,097 112,979 57-57 9cc9c6d3566f5bf7460eeecc5eb8c3c45cf54cea0d20d2f7f5c1e49f548b31e6 price_change 112,583,682 1,131,445,302 58-487 20386153848ac6bfc065f856616b0ef2db1b76cf8ab002b9a1a01b15ecb0eef1 tick_size_change 5,740 205,944 488-488 f4be47c9bb0c3b3cb227fdfd00917c51f22e1c4ed6c8064ef5c4a242cab2f648 EVENT MIX count share price_change 112,583,682 88.89% best_bid_ask 12,363,046 9.76% book 1,634,532 1.29% last_trade_price 64,503 0.05% tick_size_change 5,740 <0.01% market_resolved 2,217 <0.01% new_market 1,097 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,363,340 12,363,046 294 1,613 FULL book 1,634,850 1,634,532 318 195,692 FULL last_trade_price 64,504 64,503 1 360 FULL market_resolved 2,217 2,217 0 149 FULL new_market 1,097 1,097 0 38 FULL price_change 112,585,922 112,583,682 2,240 640 FULL tick_size_change 5,740 5,740 0 214 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,872,508 10,939,615 5ms 15ms 104ms 1.9s 0 transport_latency_assumed best_bid_ask g 11,850,776 597 83ms 108ms 354ms 31.6s 0 transport_latency_assumed best_bid_ask h 12,359,537 296,072 18ms 33ms 141ms 41.5s 0 transport_latency_assumed best_bid_ask i 12,359,633 134,003 22ms 34ms 117ms 4.1s 0 transport_latency_assumed best_bid_ask k 10,899,822 992,759 13ms 24ms 97ms 1.8s 0 transport_latency_assumed book c 547,659 292,683 4.3min 2.4d 32.5d 117.1d 0 book_staleness book g 540,405 122,652 4.2min 2.3d 32.5d 117.1d 0 book_staleness book h 140,955 11,057 22ms 322ms 2.2d 98.6d 0 book_staleness book i 294,686 77,962 16.2s 2.1d 32.5d 117.1d 0 book_staleness book k 1,325,888 1,130,178 10.8min 3.7d 42.3d 117.1d 0 book_staleness last_trade_price c 61,495 54,868 6ms 28ms 198ms 1.0s 0 transport_latency_assumed last_trade_price g 60,217 14 88ms 518ms 17.2s 31.6s 0 transport_latency_assumed last_trade_price h 64,072 1,914 19ms 70ms 417ms 9.1s 0 transport_latency_assumed last_trade_price i 64,197 1,189 23ms 68ms 407ms 2.6s 0 transport_latency_assumed last_trade_price k 57,095 6,518 15ms 44ms 209ms 981ms 0 transport_latency_assumed market_resolved c 1,630 1,442 5ms 15.6s 6.9min 7.1min 0 transport_latency_assumed market_resolved g 1,680 318 86ms 3.7min 5.2min 5.2min 0 transport_latency_assumed market_resolved h 1,680 49 18ms 17.4s 45.6s 52.6s 0 transport_latency_assumed market_resolved i 1,680 167 22ms 17.3s 45.6s 52.6s 0 transport_latency_assumed market_resolved k 1,676 241 14ms 4.5min 5.3min 5.7min 0 transport_latency_assumed new_market c 732 523 46ms 22.1s 1.6h 1.6h 0 transport_latency_assumed new_market g 698 53 263ms 11.9s 1.0min 1.3min 0 transport_latency_assumed new_market h 688 117 88ms 13.7s 32.5s 1.7min 0 transport_latency_assumed new_market i 688 153 90ms 12.5s 41.1s 1.8min 0 transport_latency_assumed new_market k 696 251 60ms 22.6s 6.0min 1.9h 0 transport_latency_assumed price_change c 108,153,062 98,908,928 5ms 18ms 118ms 2.3s 0 transport_latency_assumed price_change g 107,672,648 8,112 84ms 119ms 715ms 31.6s 0 transport_latency_assumed price_change h 112,472,449 2,885,776 18ms 37ms 173ms 42.0s 0 transport_latency_assumed price_change i 112,520,276 1,391,606 22ms 38ms 146ms 4.1s 0 transport_latency_assumed price_change k 99,128,372 9,389,260 14ms 27ms 115ms 4.1s 0 transport_latency_assumed tick_size_change c 5,676 5,201 5ms 15ms 121ms 250ms 0 transport_latency_assumed tick_size_change g 5,660 not meas. 83ms 103ms 355ms 3.5s 0 transport_latency_assumed tick_size_change h 5,740 83 18ms 38ms 257ms 4.7s 0 transport_latency_assumed tick_size_change i 5,740 133 22ms 57ms 154ms 258ms 0 transport_latency_assumed tick_size_change k 4,988 323 13ms 26ms 110ms 483ms 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-24/01/2026-09-24T01.parquet sha256sum 2026-09-24T01.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.