Hour audit: 2026-09-30T08
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-30T08 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-30T08:00:00.000065552+00:00 · last event 2026-09-30T08:59:59.999959578+00:00
VOLUME 108,494,181 rows · 1,187,029,465 bytes (1.11 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured i: 107,777,656 · k: 107,758,998 · h: 107,510,566 · m: 107,472,334 · g: 107,286,041 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 1,060,218 (0.98%) · k: 6,664,347 (6.14%) · h: 1,490,916 (1.37%) · m: 99,019,420 (91.27%) · g: 259,280 (0.24%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 108,494,181 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 92a30ad5a13a918cb342d4ac0672fc3ca5bf6df579167dde58d02c3630909b08
the corpus checksum ledger names this file with the same digest
joined 108,501,277 to merged 108,494,181, minus 7,096 (minus 0.0065%)
boundary drops 7,096 · 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-30T17:18:22Z as ghikm
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 10,616,598 124,659,515 0-40 73f5c489596d90281c84b225a22da80d98912c00e60a277d9cdf1a7bf5a83cd3 book 1,099,194 81,146,529 41-45 edf309ee550ab45951ff523c21881c67477659ea57a17824a7aeb138152e427f last_trade_price 63,267 3,522,563 46-46 07f677506e915d0554ba0bb5c6bb5e0164008f2c6f60f096a5d48bd8d2532914 market_resolved 557 89,290 47-47 1b2994dc90fc178e655808af2f0eabe59b9be13a88a850dfe82ca08d337bd540 new_market 959 95,274 48-48 658adfde846839966937ec9e09db80c7e8e0184fb8a1260fdac40d8925928054 price_change 96,710,366 976,159,652 49-417 34f5a35b5b6a223163774ef2c09be45bf454705e48668c63aaa7bacfde92db69 tick_size_change 3,240 118,686 418-418 91c17a5ac4232e133be0c070774d4e6e283bddbb1ec56f76ae63dbf1d0b0de61 EVENT MIX count share price_change 96,710,366 89.14% best_bid_ask 10,616,598 9.79% book 1,099,194 1.01% last_trade_price 63,267 0.06% tick_size_change 3,240 <0.01% new_market 959 <0.01% market_resolved 557 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,616,845 10,616,598 247 105 FULL book 1,103,904 1,099,194 4,710 210,116 FULL last_trade_price 63,268 63,267 1 6 FULL market_resolved 557 557 0 1 FULL new_market 959 959 0 0 FULL price_change 96,712,504 96,710,366 2,138 75 FULL tick_size_change 3,240 3,240 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 10,592,934 349 79ms 101ms 560ms 24.0s 0 transport_latency_assumed best_bid_ask h 10,603,922 129,793 17ms 26ms 348ms 51.3s 0 transport_latency_assumed best_bid_ask i 10,613,704 56,164 22ms 30ms 98ms 9.3s 0 transport_latency_assumed best_bid_ask k 10,614,168 605,599 13ms 23ms 94ms 25.9s 0 transport_latency_assumed best_bid_ask m 10,598,959 9,824,693 5ms 12ms 76ms 12.7s 0 transport_latency_assumed book g 565,215 254,908 21.9min 2.1d 38.8d 123.4d 0 book_staleness book h 433,204 179,269 5.8min 1.9d 38.8d 123.4d 0 book_staleness book i 432,648 178,041 5.1min 1.9d 38.8d 123.4d 0 book_staleness book k 425,178 184,305 4.5min 1.8d 38.8d 123.4d 0 book_staleness book m 436,283 302,671 4.6min 1.9d 38.8d 123.4d 0 book_staleness last_trade_price g 56,199 12 107ms 5.2s 13.4s 24.0s 0 transport_latency_assumed last_trade_price h 61,877 608 21ms 653ms 2.6s 46.9s 0 transport_latency_assumed last_trade_price i 63,048 1,911 24ms 56ms 281ms 2.0s 0 transport_latency_assumed last_trade_price k 63,058 4,769 15ms 57ms 334ms 11.1s 0 transport_latency_assumed last_trade_price m 61,997 55,967 6ms 21ms 216ms 9.2s 0 transport_latency_assumed market_resolved g 542 not meas. 82ms 324ms 38.5s 57.2s 0 transport_latency_assumed market_resolved h 543 10 18ms 82ms 40.4s 52.6s 0 transport_latency_assumed market_resolved i 542 7 23ms 60ms 43.5s 49.9s 0 transport_latency_assumed market_resolved k 542 23 15ms 47ms 40.8s 54.3s 0 transport_latency_assumed market_resolved m 543 517 5ms 25ms 56.5s 56.5s 0 transport_latency_assumed new_market g 614 57 347ms 19.1s 40.0s 1.6min 0 transport_latency_assumed new_market h 614 106 176ms 15.6s 48.2s 1.7min 0 transport_latency_assumed new_market i 614 181 109ms 16.5s 48.5s 1.4min 0 transport_latency_assumed new_market k 614 157 125ms 20.8s 40.3s 1.7min 0 transport_latency_assumed new_market m 614 458 73ms 30.6s 33.6s 1.8min 0 transport_latency_assumed price_change g 96,067,297 3,954 79ms 149ms 4.4s 24.0s 0 transport_latency_assumed price_change h 96,407,166 1,181,076 18ms 34ms 894ms 53.3s 0 transport_latency_assumed price_change i 96,663,860 823,906 23ms 32ms 133ms 9.4s 0 transport_latency_assumed price_change k 96,652,198 5,869,366 13ms 25ms 133ms 26.0s 0 transport_latency_assumed price_change m 96,370,698 88,832,064 5ms 14ms 107ms 13.7s 0 transport_latency_assumed tick_size_change g 3,240 not meas. 78ms 95ms 299ms 2.8s 0 transport_latency_assumed tick_size_change h 3,240 54 18ms 37ms 145ms 23.0s 0 transport_latency_assumed tick_size_change i 3,240 8 22ms 30ms 74ms 283ms 0 transport_latency_assumed tick_size_change k 3,240 128 13ms 23ms 94ms 17.1s 0 transport_latency_assumed tick_size_change m 3,240 3,050 5ms 11ms 42ms 362ms 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-30/08/2026-09-30T08.parquet sha256sum 2026-09-30T08.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.