Hour audit: 2026-09-24T02
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-24T02 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-24T02:00:00.000111494+00:00 · last event 2026-09-24T02:59:59.999992580+00:00
VOLUME 122,974,497 rows · 1,308,169,287 bytes (1.22 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured i: 122,026,092 · c: 122,007,309 · h: 121,969,376 · g: 116,676,896 · k: 112,545,017 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 1,498,789 (1.22%) · c: 112,079,677 (91.14%) · h: 2,077,424 (1.69%) · g: 119,740 (0.10%) · k: 7,198,867 (5.85%) (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 122,974,497 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 ec5bdb287ebd7f3fee8e98bb8e8d5dee75bfb97c50aa6b6068ad14fbe6419f41
the corpus checksum ledger names this file with the same digest
joined 122,981,566 to merged 122,974,497, minus 7,069 (minus 0.0057%)
boundary drops 7,069 · 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:55:42Z 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,673,873 145,153,607 0-48 a29427fc1da6f5ea6db5e84b85e23cbd8545064b9745354df0af451bbdc62b6b book 1,026,105 66,828,552 49-52 393e160dbe4a7bbe707b9cfd867877dcb4ce98ea11c1a05fc67fdffd1059c6f6 last_trade_price 47,934 2,760,074 53-53 b7d0158ade5480918f99cb231e253be1b5b010505a26dab478ea89becdcaf4fa market_resolved 3,474 452,555 54-54 b75ee5b9fede4cbc62f19a80bcd97299b74f8179b96c46a312133632bc0d7a49 new_market 1,689 175,611 55-55 3eec106d35ac5af82e9164b74cbb49e914520e87f1d1881c120782d669b629ba price_change 109,212,474 1,091,081,271 56-472 d3db274dff1a65634ec94d263aa6eb986f0058b71c782ef8ab7edfaee6d7cd9a tick_size_change 8,948 319,423 473-473 629495b537feb44c67cb45fed59da1c902b5e8382dd6d583cfd6c73a08c36fc7 EVENT MIX count share price_change 109,212,474 88.81% best_bid_ask 12,673,873 10.31% book 1,026,105 0.83% last_trade_price 47,934 0.04% tick_size_change 8,948 <0.01% market_resolved 3,474 <0.01% new_market 1,689 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,674,078 12,673,873 205 1,249 FULL book 1,030,991 1,026,105 4,886 194,421 FULL last_trade_price 47,934 47,934 0 165 FULL market_resolved 3,474 3,474 0 43 FULL new_market 1,689 1,689 0 2 FULL price_change 109,214,452 109,212,474 1,978 537 FULL tick_size_change 8,948 8,948 0 50 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 12,671,907 11,712,981 5ms 13ms 135ms 7.3s 0 transport_latency_assumed best_bid_ask g 12,062,655 643 83ms 106ms 470ms 24.8s 0 transport_latency_assumed best_bid_ask h 12,671,604 199,982 18ms 30ms 204ms 49.5s 0 transport_latency_assumed best_bid_ask i 12,669,928 142,914 21ms 30ms 115ms 8.2s 0 transport_latency_assumed best_bid_ask k 11,626,824 617,353 13ms 21ms 115ms 10.6s 0 transport_latency_assumed book c 123,323 97,631 7ms 14.3min 16.7d 117.2d 0 book_staleness book g 493,383 111,432 4.2min 2.8d 38.3d 117.2d 0 book_staleness book h 103,583 7,300 21ms 154ms 1.3d 98.6d 0 book_staleness book i 133,734 25,987 26ms 26.5min 18.5d 117.2d 0 book_staleness book k 881,080 783,755 8.6min 3.6d 42.3d 117.2d 0 book_staleness last_trade_price c 47,667 42,673 5ms 24ms 217ms 3.0s 0 transport_latency_assumed last_trade_price g 46,091 10 86ms 206ms 2.0s 24.6s 0 transport_latency_assumed last_trade_price h 47,715 1,199 19ms 54ms 377ms 49.5s 0 transport_latency_assumed last_trade_price i 47,798 660 23ms 58ms 377ms 2.8s 0 transport_latency_assumed last_trade_price k 43,523 3,392 13ms 35ms 208ms 1.2s 0 transport_latency_assumed market_resolved c 2,770 2,363 5ms 147ms 53.6s 56.4s 0 transport_latency_assumed market_resolved g 2,774 161 86ms 2.5min 5.4min 5.6min 0 transport_latency_assumed market_resolved h 2,774 363 18ms 23.5s 52.1s 57.1s 0 transport_latency_assumed market_resolved i 2,774 18 22ms 23.5s 52.2s 1.3min 0 transport_latency_assumed market_resolved k 2,817 569 13ms 3.5min 5.4min 5.5min 0 transport_latency_assumed new_market c 1,134 585 82ms 22.3s 1.4min 1.7min 0 transport_latency_assumed new_market g 1,134 110 312ms 48.7s 1.4min 4.3min 0 transport_latency_assumed new_market h 1,134 334 156ms 28.6s 1.5min 1.7min 0 transport_latency_assumed new_market i 1,134 414 119ms 47.6s 1.5min 1.7min 0 transport_latency_assumed new_market k 1,132 246 107ms 56.1s 4.3min 4.3min 0 transport_latency_assumed price_change c 109,151,564 100,214,970 5ms 15ms 147ms 7.3s 0 transport_latency_assumed price_change g 104,062,071 7,384 83ms 113ms 621ms 24.9s 0 transport_latency_assumed price_change h 109,133,618 1,868,173 18ms 34ms 232ms 49.6s 0 transport_latency_assumed price_change i 109,161,776 1,328,759 21ms 33ms 142ms 8.3s 0 transport_latency_assumed price_change k 99,980,805 5,793,188 13ms 24ms 129ms 11.7s 0 transport_latency_assumed tick_size_change c 8,944 8,474 5ms 9ms 44ms 162ms 0 transport_latency_assumed tick_size_change g 8,788 not meas. 82ms 99ms 222ms 381ms 0 transport_latency_assumed tick_size_change h 8,948 73 18ms 35ms 73ms 6.3s 0 transport_latency_assumed tick_size_change i 8,948 37 22ms 45ms 189ms 1.7s 0 transport_latency_assumed tick_size_change k 8,836 364 13ms 21ms 56ms 99ms 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/02/2026-09-24T02.parquet sha256sum 2026-09-24T02.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.