Hour audit: 2026-09-30T17
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-30T17 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-30T17:00:00.000041465+00:00 · last event 2026-09-30T17:59:59.999903017+00:00
VOLUME 116,651,296 rows · 1,249,414,667 bytes (1.16 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured h: 116,613,949 · k: 116,610,460 · i: 116,580,696 · m: 116,573,008 · g: 116,447,283 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 3,872,622 (3.32%) · k: 13,664,034 (11.71%) · i: 3,428,892 (2.94%) · m: 95,648,164 (81.99%) · g: 37,584 (0.03%) (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 116,651,296 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 84cf07f8238822a3c2f03b41c02506716d4dcf3f4523a71808682f1bec96506d
the corpus checksum ledger names this file with the same digest
joined 116,653,805 to merged 116,651,296, minus 2,509 (minus 0.0022%)
boundary drops 2,509 · 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-30T22:36:39Z 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,797,726 127,798,683 0-41 488675ffaf9f1390c9c1efa362772a2f08b75c9e84ef21d84ef06f01e700cba0 book 132,388 14,938,892 42-42 d07d644ac8b9e07050dbd815bad63c7a7c6a1d0381f702feebaad57ccc494c2a last_trade_price 59,132 3,375,766 43-43 7f9c9a820591fb18246d099116c5a3d7f2db7b432ee671ecbff26ec7b3ffa3a1 market_resolved 927 141,101 44-44 45462b7c836a20cfb4868be8ec830979deceda0577f4f05b22907c69d7f41c42 new_market 1,487 139,816 45-45 afa49fb617d1d21ed68a47ec2c789ed583f04eef7768a9f212c7434b796aa705 price_change 105,656,364 1,101,567,600 46-449 f8e813dab81ff94a77a9f8f7e35ca5aad226506046b8a8c57222b0ab4e9830d4 tick_size_change 3,272 120,502 450-450 2bfa84a903be2d8e2bbeb87d1bd18e3afc1989e8dedab0807128e12e2ed734c1 EVENT MIX count share price_change 105,656,364 90.57% best_bid_ask 10,797,726 9.26% book 132,388 0.11% last_trade_price 59,132 0.05% tick_size_change 3,272 <0.01% new_market 1,487 <0.01% market_resolved 927 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,797,957 10,797,726 231 112 FULL book 132,398 132,388 10 5,071 FULL last_trade_price 59,132 59,132 0 0 FULL market_resolved 927 927 0 0 FULL new_market 1,487 1,487 0 0 FULL price_change 105,658,632 105,656,364 2,268 106 FULL tick_size_change 3,272 3,272 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 10,792,269 2,922 79ms 103ms 338ms 19.1s 0 transport_latency_assumed best_bid_ask h 10,797,048 312,407 19ms 45ms 210ms 1.2min 0 transport_latency_assumed best_bid_ask i 10,797,062 275,835 20ms 51ms 140ms 15.1s 0 transport_latency_assumed best_bid_ask k 10,797,158 1,156,432 15ms 37ms 164ms 39.7s 0 transport_latency_assumed best_bid_ask m 10,796,147 9,050,130 5ms 23ms 101ms 2.8s 0 transport_latency_assumed book g 122,588 5,146 85ms 541ms 17.1h 105.3d 0 book_staleness book h 121,577 5,943 23ms 75ms 2.8min 116.1d 0 book_staleness book i 120,582 5,263 24ms 81ms 2.8s 105.1d 0 book_staleness book k 121,812 14,892 22ms 74ms 27.5min 105.3d 0 book_staleness book m 122,246 101,144 7ms 42ms 31.8min 19.6d 0 book_staleness last_trade_price g 58,121 32 84ms 261ms 8.6s 19.0s 0 transport_latency_assumed last_trade_price h 59,111 2,165 21ms 60ms 461ms 44.1s 0 transport_latency_assumed last_trade_price i 59,114 1,444 24ms 72ms 487ms 3.3s 0 transport_latency_assumed last_trade_price k 59,109 7,272 18ms 57ms 258ms 15.5s 0 transport_latency_assumed last_trade_price m 59,058 48,219 6ms 31ms 171ms 1.3s 0 transport_latency_assumed market_resolved g 880 not meas. 82ms 376ms 56.1s 56.1s 0 transport_latency_assumed market_resolved h 880 15 22ms 38.9s 47.9s 48.4s 0 transport_latency_assumed market_resolved i 880 11 24ms 37.5s 46.8s 47.1s 0 transport_latency_assumed market_resolved k 880 119 17ms 58ms 54.7s 57.4s 0 transport_latency_assumed market_resolved m 880 782 6ms 33.8s 43.0s 43.5s 0 transport_latency_assumed new_market g 873 88 475ms 32.1s 44.6s 1.1min 0 transport_latency_assumed new_market h 873 198 184ms 18.6s 33.8s 1.6min 0 transport_latency_assumed new_market i 873 397 173ms 32.0s 37.5s 1.7min 0 transport_latency_assumed new_market k 873 198 196ms 31.5s 37.3s 1.6min 0 transport_latency_assumed new_market m 873 606 86ms 27.5s 48.2s 1.7min 0 transport_latency_assumed price_change g 105,469,280 29,396 79ms 121ms 1.1s 19.2s 0 transport_latency_assumed price_change h 105,631,188 3,551,828 20ms 47ms 250ms 1.2min 0 transport_latency_assumed price_change i 105,598,913 3,145,894 20ms 53ms 187ms 21.0s 0 transport_latency_assumed price_change k 105,627,356 12,484,836 16ms 40ms 179ms 39.8s 0 transport_latency_assumed price_change m 105,590,532 86,444,410 6ms 25ms 115ms 2.8s 0 transport_latency_assumed tick_size_change g 3,272 not meas. 78ms 94ms 390ms 1.0s 0 transport_latency_assumed tick_size_change h 3,272 66 20ms 46ms 277ms 7.2s 0 transport_latency_assumed tick_size_change i 3,272 48 20ms 49ms 117ms 3.2s 0 transport_latency_assumed tick_size_change k 3,272 285 15ms 32ms 171ms 7.9s 0 transport_latency_assumed tick_size_change m 3,272 2,873 5ms 18ms 48ms 220ms 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/17/2026-09-30T17.parquet sha256sum 2026-09-30T17.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.