Hour audit: 2026-09-30T09
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-30T09 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-30T09:00:00.000000020+00:00 · last event 2026-09-30T09:59:59.999999918+00:00
VOLUME 115,292,998 rows · 1,245,411,355 bytes (1.16 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured i: 114,863,118 · k: 114,832,953 · h: 114,787,208 · m: 114,669,937 · g: 114,540,539 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 679,746 (0.59%) · k: 5,885,464 (5.10%) · h: 1,465,180 (1.27%) · m: 107,121,066 (92.91%) · g: 141,542 (0.12%) (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,292,998 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 8af8f7face58e79515b55a815d1c1c1bfaa790f5f0f9499034fe0a00db85c060
the corpus checksum ledger names this file with the same digest
joined 115,295,755 to merged 115,292,998, minus 2,757 (minus 0.0024%)
boundary drops 2,757 · 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:46:35Z 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 11,164,644 128,843,010 0-42 ebe7f38a3c2cf28937dfc3cabda2b0f22e8d773e81e70fb723881324d5989d8a book 702,114 62,653,199 43-45 d82255c06d583e476a16c934e77f879d19573e52f9fbf6165257217ba3a91070 last_trade_price 49,085 2,828,200 46-46 74f1f2a4da81b47cbf99354b61fe99d47cde4bb29a2de79da7de79567e7ad3bd market_resolved 837 129,769 47-47 029bb7357ab39c3a4b58dd1428ec47fa1d37ec9d0ac533aad258b992a891657b new_market 808 83,490 48-48 0b0553ff40cbbacefad3687644391f772cfafb5ef5bd6bcb5339de167c058fe6 price_change 103,372,154 1,049,435,219 49-443 9001ed4a2d730d3de764faa3503f8036f3e047b897e6bb2c6172433c2381d062 tick_size_change 3,356 123,997 444-444 a8c5a8d442570d8cc0d91f699fb4db60eee5d51a57ee82cdb45a4ac9578d03ae EVENT MIX count share price_change 103,372,154 89.66% best_bid_ask 11,164,644 9.68% book 702,114 0.61% last_trade_price 49,085 0.04% tick_size_change 3,356 <0.01% market_resolved 837 <0.01% new_market 808 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,164,881 11,164,644 237 163 FULL book 702,744 702,114 630 204,447 FULL last_trade_price 49,086 49,085 1 0 FULL market_resolved 838 837 1 1 FULL new_market 808 808 0 0 FULL price_change 103,374,042 103,372,154 1,888 52 FULL tick_size_change 3,356 3,356 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 11,158,633 684 78ms 101ms 358ms 23.3s 0 transport_latency_assumed best_bid_ask h 11,160,916 132,578 17ms 24ms 123ms 8.2s 0 transport_latency_assumed best_bid_ask i 11,162,037 43,705 22ms 30ms 90ms 4.0s 0 transport_latency_assumed best_bid_ask k 11,162,275 580,359 13ms 22ms 90ms 6.9s 0 transport_latency_assumed best_bid_ask m 11,157,676 10,407,318 5ms 12ms 62ms 3.8s 0 transport_latency_assumed book g 276,897 133,145 2.6min 1.7d 38.8d 123.5d 0 book_staleness book h 275,657 107,280 2.4min 1.7d 38.8d 123.5d 0 book_staleness book i 315,634 149,359 4.8min 1.8d 38.8d 123.5d 0 book_staleness book k 280,412 130,307 2.5min 1.7d 38.8d 123.5d 0 book_staleness book m 239,073 182,023 46.3s 1.4d 38.8d 123.5d 0 book_staleness last_trade_price g 48,047 8 91ms 1.3s 12.0s 23.3s 0 transport_latency_assumed last_trade_price h 48,896 783 19ms 88ms 725ms 4.6s 0 transport_latency_assumed last_trade_price i 48,981 396 24ms 54ms 311ms 1.3s 0 transport_latency_assumed last_trade_price k 48,949 1,943 15ms 48ms 382ms 5.3s 0 transport_latency_assumed last_trade_price m 48,578 45,955 6ms 13ms 121ms 2.5s 0 transport_latency_assumed market_resolved g 818 1 80ms 362ms 52.1s 54.3s 0 transport_latency_assumed market_resolved h 817 3 18ms 72ms 44.6s 48.3s 0 transport_latency_assumed market_resolved i 818 23 23ms 56ms 54.3s 54.3s 0 transport_latency_assumed market_resolved k 818 33 14ms 63ms 47.7s 50.0s 0 transport_latency_assumed market_resolved m 817 777 5ms 41ms 39.6s 42.8s 0 transport_latency_assumed new_market g 531 60 308ms 22.7s 1.1min 1.4min 0 transport_latency_assumed new_market h 531 100 123ms 17.6s 51.6s 58.7s 0 transport_latency_assumed new_market i 531 114 73ms 23.6s 53.4s 1.6min 0 transport_latency_assumed new_market k 531 108 115ms 17.8s 52.9s 1.2min 0 transport_latency_assumed new_market m 531 426 40ms 20.1s 1.1min 1.6min 0 transport_latency_assumed price_change g 103,052,257 7,644 79ms 131ms 2.3s 23.7s 0 transport_latency_assumed price_change h 103,297,035 1,224,392 18ms 28ms 230ms 8.2s 0 transport_latency_assumed price_change i 103,331,761 486,132 23ms 32ms 122ms 4.0s 0 transport_latency_assumed price_change k 103,336,612 5,172,484 13ms 25ms 128ms 7.3s 0 transport_latency_assumed price_change m 103,219,906 96,481,502 5ms 12ms 70ms 3.8s 0 transport_latency_assumed tick_size_change g 3,356 not meas. 79ms 97ms 241ms 1.8s 0 transport_latency_assumed tick_size_change h 3,356 44 18ms 34ms 76ms 282ms 0 transport_latency_assumed tick_size_change i 3,356 17 23ms 32ms 94ms 307ms 0 transport_latency_assumed tick_size_change k 3,356 230 13ms 22ms 115ms 342ms 0 transport_latency_assumed tick_size_change m 3,356 3,065 5ms 14ms 92ms 271ms 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/09/2026-09-30T09.parquet sha256sum 2026-09-30T09.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.