Hour audit: 2026-09-24T19
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-24T19 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-24T19:00:00.000004573+00:00 · last event 2026-09-24T19:59:59.999983003+00:00
VOLUME 136,377,418 rows · 1,543,933,460 bytes (1.44 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured g: 127,964,965 · i: 124,223,135 · h: 117,508,346 · k: 102,369,865 · c: 94,455,766 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 171,117 (0.13%) · i: 7,046,121 (5.17%) · h: 11,907,257 (8.73%) · k: 35,091,546 (25.73%) · c: 82,161,377 (60.25%) (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 136,377,418 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 8d2d9931c8dc9be5ac0997f192239f35eedbc8bad491babe7aadd446951f7fc8
the corpus checksum ledger names this file with the same digest
joined 136,385,462 to merged 136,377,418, minus 8,044 (minus 0.0059%)
boundary drops 8,044 · 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-24T21:55:47Z 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,471,822 160,028,190 0-51 27b76f7bd8f50f71e2d0915be82fdad2b4dcbb12e2dc236a9305f356ab9c56d8 book 4,176,767 142,264,304 52-67 54975fb157f4b15d5c3ae29c59aa0e135fc96ac0c50b8ed1159cdc61fbe3c99f last_trade_price 60,315 3,503,841 68-68 b408d64afa8a4def43aba40e1573d295a4ce25048cd693430f9c51d9ce777473 market_resolved 1,982 170,450 69-69 b5a187aa795b4e173892e4008cd1faa2c6a8df92ddec2439a9c4b478a47febc6 new_market 7,579 445,443 70-70 ca066b1af2a3c356a6f8d5db60e1644e7523228548573560d3afc7c90ccbe3db price_change 118,654,481 1,235,806,560 71-523 ee71796e4ea59afcf5452e9add62ba5243933d56e7806c33cba730db02e94f8e tick_size_change 4,472 165,145 524-524 aa2a45c03623fe9d91bb71f1aa10d150de5e03b62c6efeca4956e753e4a3108f EVENT MIX count share price_change 118,654,481 87.00% best_bid_ask 13,471,822 9.88% book 4,176,767 3.06% last_trade_price 60,315 0.04% new_market 7,579 <0.01% tick_size_change 4,472 <0.01% market_resolved 1,982 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,472,131 13,471,822 309 8,140 FULL book 4,181,973 4,176,767 5,206 2,125 FULL last_trade_price 60,316 60,315 1 1,145 FULL market_resolved 1,982 1,982 0 76 FULL new_market 7,579 7,579 0 0 FULL price_change 118,657,009 118,654,481 2,528 3,624 FULL tick_size_change 4,472 4,472 0 723 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,431,389 8,313,452 6ms 23ms 234ms 3.6s 0 transport_latency_assumed best_bid_ask g 13,062,439 6,463 82ms 139ms 894ms 53.3s 0 transport_latency_assumed best_bid_ask h 11,829,250 1,117,081 19ms 51ms 351ms 1.1min 0 transport_latency_assumed best_bid_ask i 12,570,352 674,527 20ms 36ms 177ms 4.8s 0 transport_latency_assumed best_bid_ask k 10,229,217 3,360,299 13ms 24ms 165ms 13.2s 0 transport_latency_assumed book c 2,882,907 1,847,658 8.6min 5.2d 44.0d 117.9d 0 book_staleness book g 680,930 95,481 4.4min 3.7d 40.2d 117.9d 0 book_staleness book h 1,425,702 482,053 6.8min 4.8d 43.2d 117.9d 0 book_staleness book i 939,086 209,862 5.9min 4.0d 43.0d 117.9d 0 book_staleness book k 2,434,258 1,541,713 7.2min 5.2d 44.0d 117.9d 0 book_staleness last_trade_price c 39,627 34,188 7ms 40ms 357ms 2.1s 0 transport_latency_assumed last_trade_price g 56,099 45 98ms 2.2s 12.1s 53.1s 0 transport_latency_assumed last_trade_price h 53,189 5,999 22ms 111ms 742ms 31.8s 0 transport_latency_assumed last_trade_price i 56,225 3,530 24ms 171ms 1.1s 4.8s 0 transport_latency_assumed last_trade_price k 45,593 16,553 14ms 57ms 362ms 2.3s 0 transport_latency_assumed market_resolved c 1,220 991 33ms 10.3min 15.3min 16.5min 0 transport_latency_assumed market_resolved g 985 2 84ms 23.2s 4.6min 6.3min 0 transport_latency_assumed market_resolved h 1,056 220 22ms 7.8min 11.0min 13.6min 0 transport_latency_assumed market_resolved i 1,069 202 22ms 1.2min 8.4min 11.0min 0 transport_latency_assumed market_resolved k 1,201 567 39ms 12.2min 21.5min 23.1min 0 transport_latency_assumed new_market c 4,810 2,877 1.4min 7.3min 12.2min 19.0min 0 transport_latency_assumed new_market g 2,683 158 397ms 4.1min 5.0min 5.2min 0 transport_latency_assumed new_market h 3,970 898 467ms 8.3min 9.6min 9.7min 0 transport_latency_assumed new_market i 3,717 1,062 302ms 6.0min 7.1min 7.2min 0 transport_latency_assumed new_market k 5,725 2,584 3.2min 11.6min 13.7min 18.8min 0 transport_latency_assumed price_change c 82,092,485 71,959,112 6ms 26ms 255ms 5.2s 0 transport_latency_assumed price_change g 114,157,449 68,968 83ms 207ms 4.6s 53.4s 0 transport_latency_assumed price_change h 104,190,971 10,300,699 19ms 56ms 417ms 1.1min 0 transport_latency_assumed price_change i 110,648,414 6,156,684 21ms 46ms 301ms 4.8s 0 transport_latency_assumed price_change k 89,651,339 30,169,018 13ms 28ms 197ms 13.2s 0 transport_latency_assumed tick_size_change c 3,328 3,099 6ms 12ms 87ms 254ms 0 transport_latency_assumed tick_size_change g 4,380 not meas. 82ms 100ms 788ms 1.1s 0 transport_latency_assumed tick_size_change h 4,208 307 19ms 43ms 219ms 576ms 0 transport_latency_assumed tick_size_change i 4,272 254 20ms 28ms 176ms 390ms 0 transport_latency_assumed tick_size_change k 2,532 812 13ms 20ms 122ms 643ms 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/19/2026-09-24T19.parquet sha256sum 2026-09-24T19.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.