Hour audit: 2026-09-24T22
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-24T22 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-24T22:00:00.000800556+00:00 · last event 2026-09-24T22:59:59.999990368+00:00
VOLUME 115,310,457 rows · 1,245,089,942 bytes (1.16 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured k: 113,513,225 · i: 113,496,945 · g: 113,364,191 · h: 108,991,245 · c: 94,836,621 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 24,371,911 (21.14%) · i: 1,855,810 (1.61%) · g: 23,660 (0.02%) · h: 1,942,734 (1.68%) · c: 87,116,342 (75.55%) (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 115,310,457 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 fb1a8fc7151f16975ad34438d98fe68504fd25b008b9384defe7c0d92baf1587
the corpus checksum ledger names this file with the same digest
joined 115,319,669 to merged 115,310,457, minus 9,212 (minus 0.0080%)
boundary drops 9,212 · 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-25T00:10:14Z 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 13,008,168 151,135,579 0-49 6284bc3012d75c4087e6353e730c14c89126086e18df6bbee06040bf4c5537a1 book 1,876,064 83,343,421 50-57 910d7238d758f4c622a0cb3b173641540181680378e4cc93b71efce03c4129b4 last_trade_price 50,548 2,885,817 58-58 989bdd39902b3513a5597bb81047166107a6fc1ed9b929570b9f84a870a3b8d8 market_resolved 1,949 273,082 59-59 7d1111a36c76ccd825f0f00a4845123595173b52783b6215e4dcd42338cbe5ae new_market 1,538 141,612 60-60 6fddc526c4552b2c215e644a840a113873514bd2275b59868c9d7c020e58fc81 price_change 100,369,546 1,005,899,455 61-443 2eb0d0cd5608fc58b5bac77ddf3aed787b0ca536b74934ea95476a7fa3d84629 tick_size_change 2,644 97,905 444-444 aa4ec3011b6bf0b9f862e47a2aa4e3634e6728c54742b2aa65a6715144ac0a74 EVENT MIX count share price_change 100,369,546 87.04% best_bid_ask 13,008,168 11.28% book 1,876,064 1.63% last_trade_price 50,548 0.04% tick_size_change 2,644 <0.01% market_resolved 1,949 <0.01% new_market 1,538 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,008,992 13,008,168 824 2,700 FULL book 1,876,370 1,876,064 306 204,394 FULL last_trade_price 50,552 50,548 4 417 FULL market_resolved 1,949 1,949 0 14 FULL new_market 1,538 1,538 0 0 FULL price_change 100,377,624 100,369,546 8,078 1,012 FULL tick_size_change 2,644 2,644 0 141 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,727,740 9,917,351 5ms 12ms 114ms 4.2s 0 transport_latency_assumed best_bid_ask g 13,004,550 1,145 82ms 106ms 413ms 22.9s 0 transport_latency_assumed best_bid_ask h 12,445,358 175,620 18ms 47ms 275ms 43.7s 0 transport_latency_assumed best_bid_ask i 13,006,808 191,559 20ms 28ms 118ms 4.1s 0 transport_latency_assumed best_bid_ask k 13,006,905 2,722,493 12ms 19ms 106ms 37.8s 0 transport_latency_assumed book c 1,746,360 1,681,264 9.8min 5.2d 43.2d 118.0d 0 book_staleness book g 106,192 2,366 96ms 3.4s 2.0d 99.5d 0 book_staleness book h 517,721 161,628 5.7min 3.1d 33.4d 118.0d 0 book_staleness book i 112,556 6,868 24ms 1.2s 3.3d 99.5d 0 book_staleness book k 107,156 23,938 16ms 99ms 2.0d 99.5d 0 book_staleness last_trade_price c 41,521 37,163 6ms 27ms 240ms 1.8s 0 transport_latency_assumed last_trade_price g 49,801 41 96ms 1.3s 11.0s 22.9s 0 transport_latency_assumed last_trade_price h 48,081 1,156 21ms 94ms 737ms 25.5s 0 transport_latency_assumed last_trade_price i 50,409 933 23ms 112ms 709ms 2.4s 0 transport_latency_assumed last_trade_price k 50,340 11,255 14ms 42ms 260ms 31.9s 0 transport_latency_assumed market_resolved c 1,841 1,546 5ms 4.0min 16.9min 18.7min 0 transport_latency_assumed market_resolved g 1,686 187 84ms 13.5s 46.9s 51.3s 0 transport_latency_assumed market_resolved h 1,684 53 19ms 20.7s 5.3min 5.5min 0 transport_latency_assumed market_resolved i 1,686 11 21ms 255ms 51.7s 55.6s 0 transport_latency_assumed market_resolved k 1,686 152 13ms 15.7s 50.7s 54.7s 0 transport_latency_assumed new_market c 1,084 618 185ms 6.7min 13.5min 15.7min 0 transport_latency_assumed new_market g 880 107 263ms 13.4s 1.7min 2.1min 0 transport_latency_assumed new_market h 880 230 160ms 11.6s 1.7min 2.1min 0 transport_latency_assumed new_market i 880 222 109ms 10.9s 1.7min 1.9min 0 transport_latency_assumed new_market k 880 361 96ms 11.3s 1.7min 2.1min 0 transport_latency_assumed price_change c 82,315,935 75,476,477 5ms 15ms 135ms 4.5s 0 transport_latency_assumed price_change g 100,198,438 19,814 82ms 138ms 1.5s 22.9s 0 transport_latency_assumed price_change h 95,974,973 1,604,008 19ms 52ms 318ms 47.5s 0 transport_latency_assumed price_change i 100,321,962 1,656,182 21ms 34ms 194ms 4.1s 0 transport_latency_assumed price_change k 100,343,614 21,613,065 13ms 23ms 133ms 37.8s 0 transport_latency_assumed tick_size_change c 2,140 1,923 5ms 16ms 69ms 143ms 0 transport_latency_assumed tick_size_change g 2,644 not meas. 82ms 104ms 242ms 483ms 0 transport_latency_assumed tick_size_change h 2,548 39 18ms 40ms 98ms 278ms 0 transport_latency_assumed tick_size_change i 2,644 35 21ms 36ms 90ms 301ms 0 transport_latency_assumed tick_size_change k 2,644 647 13ms 20ms 58ms 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/22/2026-09-24T22.parquet sha256sum 2026-09-24T22.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.