Hour audit: 2026-09-30T10
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-30T10 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-30T10:00:00.000010426+00:00 · last event 2026-09-30T10:59:59.999966550+00:00
VOLUME 114,423,040 rows · 1,206,099,438 bytes (1.12 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured i: 114,231,548 · h: 114,227,094 · k: 114,225,428 · m: 114,087,003 · g: 114,066,140 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 620,158 (0.54%) · h: 1,080,828 (0.94%) · k: 5,946,940 (5.20%) · m: 106,641,598 (93.20%) · g: 133,516 (0.12%) (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 114,423,040 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 dcadcee5edaa042b098163e082211377774a945f36d03850857bd67038c35682
the corpus checksum ledger names this file with the same digest
joined 114,424,975 to merged 114,423,040, minus 1,935 (minus 0.0017%)
boundary drops 1,935 · 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-30T18:16:40Z 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,404,937 120,422,751 0-39 88b0f2ecb62df266c44e4836a0bca2b68e26fc26f493d8f38052053300e1685a book 291,198 29,597,100 40-41 bc96631ac32361c9e5ef5121bead80f7ce7c6e09bd9cb6f332a69abf569d178f last_trade_price 58,485 3,325,725 42-42 08858d78055db5fdba94d985ff96584355ead1c000ec1f31632dc67741c651de market_resolved 844 128,320 43-43 7a38bd8ce1f49c29e1494b97b7bccfc1698fdd302b9609c072811cd1863c6933 new_market 916 94,553 44-44 7ccc23d359718f1a0c8fddd670cb6b1e65007d7b6712ea9d67837c1cbf6d3147 price_change 103,663,172 1,051,096,780 45-440 e16e12482a758c11916e77d1d8021ee25e0dabd7344ea54c5c1a95eb04d59f6b tick_size_change 3,488 128,279 441-441 22e575bc608561dbc8a3e808eb6ba6e8217e8d32e958266eeb53bb1d943454b6 EVENT MIX count share price_change 103,663,172 90.60% best_bid_ask 10,404,937 9.09% book 291,198 0.25% last_trade_price 58,485 0.05% tick_size_change 3,488 <0.01% new_market 916 <0.01% market_resolved 844 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,405,120 10,404,937 183 138 FULL book 291,282 291,198 84 74,693 FULL last_trade_price 58,487 58,485 2 2 FULL market_resolved 844 844 0 0 FULL new_market 916 916 0 0 FULL price_change 103,664,838 103,663,172 1,666 53 FULL tick_size_change 3,488 3,488 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 10,393,189 613 77ms 98ms 402ms 25.7s 0 transport_latency_assumed best_bid_ask h 10,403,787 92,895 18ms 25ms 122ms 49.6s 0 transport_latency_assumed best_bid_ask i 10,403,782 41,042 22ms 30ms 88ms 10.7s 0 transport_latency_assumed best_bid_ask k 10,404,142 537,689 13ms 22ms 87ms 24.0s 0 transport_latency_assumed best_bid_ask m 10,398,099 9,732,698 5ms 12ms 61ms 2.5s 0 transport_latency_assumed book g 246,441 123,905 9.6s 1.3d 38.8d 123.5d 0 book_staleness book h 138,305 21,215 24ms 8.1min 10.8d 105.0d 0 book_staleness book i 125,516 9,399 27ms 105ms 1.4d 105.0d 0 book_staleness book k 123,472 10,753 17ms 85ms 1.1d 105.0d 0 book_staleness book m 134,444 125,926 8ms 47.3s 2.4d 123.5d 0 book_staleness last_trade_price g 57,210 19 90ms 1.1s 8.8s 26.0s 0 transport_latency_assumed last_trade_price h 58,402 674 21ms 79ms 684ms 20.6s 0 transport_latency_assumed last_trade_price i 58,310 839 23ms 42ms 236ms 4.2s 0 transport_latency_assumed last_trade_price k 58,418 3,089 15ms 41ms 321ms 4.9s 0 transport_latency_assumed last_trade_price m 57,838 53,864 6ms 15ms 173ms 2.1s 0 transport_latency_assumed market_resolved g 789 not meas. 82ms 31.3s 56.5s 56.5s 0 transport_latency_assumed market_resolved h 789 3 21ms 27.1s 48.6s 53.8s 0 transport_latency_assumed market_resolved i 789 50 23ms 38.0s 48.8s 48.8s 0 transport_latency_assumed market_resolved k 789 24 16ms 30.9s 52.6s 56.8s 0 transport_latency_assumed market_resolved m 789 767 6ms 22.4s 48.6s 57.4s 0 transport_latency_assumed new_market g 601 31 340ms 21.2s 57.2s 1.5min 0 transport_latency_assumed new_market h 601 131 179ms 18.0s 55.8s 1.7min 0 transport_latency_assumed new_market i 601 169 80ms 18.1s 55.7s 1.5min 0 transport_latency_assumed new_market k 601 180 104ms 14.6s 52.6s 1.5min 0 transport_latency_assumed new_market m 601 405 45ms 16.4s 55.8s 1.6min 0 transport_latency_assumed price_change g 103,364,422 8,948 78ms 133ms 2.1s 26.4s 0 transport_latency_assumed price_change h 103,621,722 965,838 19ms 29ms 227ms 49.7s 0 transport_latency_assumed price_change i 103,639,062 568,622 23ms 31ms 116ms 11.0s 0 transport_latency_assumed price_change k 103,634,518 5,395,054 13ms 24ms 115ms 24.4s 0 transport_latency_assumed price_change m 103,491,744 96,724,710 5ms 12ms 75ms 2.8s 0 transport_latency_assumed tick_size_change g 3,488 not meas. 78ms 101ms 478ms 1.2s 0 transport_latency_assumed tick_size_change h 3,488 72 19ms 39ms 112ms 1.2s 0 transport_latency_assumed tick_size_change i 3,488 37 23ms 35ms 103ms 334ms 0 transport_latency_assumed tick_size_change k 3,488 151 13ms 27ms 134ms 311ms 0 transport_latency_assumed tick_size_change m 3,488 3,228 5ms 15ms 190ms 634ms 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/10/2026-09-30T10.parquet sha256sum 2026-09-30T10.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.