Hour audit: 2026-09-30T12
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-30T12 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-30T12:00:00.000084169+00:00 · last event 2026-09-30T12:59:59.999537514+00:00
VOLUME 119,585,709 rows · 1,293,165,633 bytes (1.20 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured i: 119,267,745 · h: 119,070,951 · k: 119,064,767 · m: 118,998,753 · g: 118,664,988 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 864,506 (0.72%) · h: 1,424,326 (1.19%) · k: 6,015,666 (5.03%) · m: 111,237,397 (93.02%) · g: 43,814 (0.04%) (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 119,585,709 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 9e46d772695272f1bad25bbb7115e0ff7716a62b4c15079e073bddc05ceb30b5
the corpus checksum ledger names this file with the same digest
joined 119,586,734 to merged 119,585,709, minus 1,025 (minus 0.0009%)
boundary drops 1,025 · 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-30T19:20:49Z 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,875,057 128,404,738 0-41 ba46d4707f8ffa979cca4ff9158e107e698cd1ed828ec58486c6520f8e75e50b book 642,448 64,305,982 42-44 b383886dbdb1321ecf8c3c67a4ed806264eb0644e51d5e018936c46c743cdb47 last_trade_price 66,277 3,739,650 45-45 0b8686ee75b398bef5c1598d5b7acd0e51a9d8c64f08d01a7cd4ea7eb5607777 market_resolved 894 136,245 46-46 eb4ded487ea63054a84a741a1c4f62631e9f5dfa127870ae592335e90791709a new_market 1,123 114,455 47-47 ce27e781195aaa0eb931b4ebbcb34398fdbdd7d237a6e6216ecf3d6efb4966f1 price_change 107,996,034 1,094,961,898 48-459 3e64460cf9a693ff8fb412bfa2d1131e2d2ef066860b9b5e725450420129abe4 tick_size_change 3,876 140,776 460-460 721cef222d3ac3674006548b6d6cc0c319347bfa246f8fa2ac1ebe5c0955223d EVENT MIX count share price_change 107,996,034 90.31% best_bid_ask 10,875,057 9.09% book 642,448 0.54% last_trade_price 66,277 0.06% tick_size_change 3,876 <0.01% new_market 1,123 <0.01% market_resolved 894 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,875,124 10,875,057 67 110 FULL book 642,506 642,448 58 226,896 FULL last_trade_price 66,277 66,277 0 1 FULL market_resolved 894 894 0 0 FULL new_market 1,123 1,123 0 0 FULL price_change 107,996,934 107,996,034 900 130 FULL tick_size_change 3,876 3,876 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 10,868,791 1,708 77ms 96ms 431ms 24.3s 0 transport_latency_assumed best_bid_ask h 10,874,185 114,111 17ms 24ms 145ms 42.0s 0 transport_latency_assumed best_bid_ask i 10,848,950 27,147 25ms 33ms 99ms 27.6s 0 transport_latency_assumed best_bid_ask k 10,874,492 484,536 13ms 22ms 109ms 23.0s 0 transport_latency_assumed best_bid_ask m 10,871,525 10,247,555 5ms 11ms 61ms 8.8s 0 transport_latency_assumed book g 152,446 21,246 90ms 4.3min 10.9d 123.6d 0 book_staleness book h 138,562 6,691 21ms 79ms 8.1h 105.1d 0 book_staleness book i 623,059 469,959 8.3min 2.1d 39.0d 123.6d 0 book_staleness book k 139,284 13,580 17ms 56ms 19.5h 105.0d 0 book_staleness book m 142,181 130,972 7ms 35ms 21.6h 42.4d 0 book_staleness last_trade_price g 64,796 19 84ms 597ms 7.0s 24.4s 0 transport_latency_assumed last_trade_price h 66,259 987 19ms 45ms 339ms 21.8s 0 transport_latency_assumed last_trade_price i 66,097 456 25ms 40ms 199ms 6.5s 0 transport_latency_assumed last_trade_price k 66,258 4,659 15ms 31ms 208ms 16.7s 0 transport_latency_assumed last_trade_price m 66,088 60,156 6ms 16ms 104ms 2.4s 0 transport_latency_assumed market_resolved g 835 49 79ms 337ms 53.2s 56.3s 0 transport_latency_assumed market_resolved h 835 6 19ms 39.6s 49.5s 52.5s 0 transport_latency_assumed market_resolved i 835 2 25ms 35.4s 52.2s 55.0s 0 transport_latency_assumed market_resolved k 835 35 15ms 44.8s 56.2s 56.3s 0 transport_latency_assumed market_resolved m 835 802 5ms 34.8s 44.3s 47.3s 0 transport_latency_assumed new_market g 742 140 318ms 18.4s 1.0min 1.8min 0 transport_latency_assumed new_market h 742 97 155ms 14.1s 33.9s 1.6min 0 transport_latency_assumed new_market i 742 206 79ms 13.3s 35.6s 1.6min 0 transport_latency_assumed new_market k 742 132 109ms 16.3s 44.3s 1.6min 0 transport_latency_assumed new_market m 742 548 59ms 19.6s 34.4s 1.4min 0 transport_latency_assumed price_change g 107,573,502 20,652 78ms 119ms 2.0s 24.5s 0 transport_latency_assumed price_change h 107,986,492 1,302,408 18ms 26ms 212ms 42.2s 0 transport_latency_assumed price_change i 107,724,186 366,730 25ms 34ms 125ms 27.6s 0 transport_latency_assumed price_change k 107,979,280 5,512,566 14ms 23ms 127ms 24.0s 0 transport_latency_assumed price_change m 107,913,506 100,793,678 5ms 12ms 74ms 8.8s 0 transport_latency_assumed tick_size_change g 3,876 not meas. 78ms 92ms 219ms 736ms 0 transport_latency_assumed tick_size_change h 3,876 26 18ms 30ms 48ms 1.9s 0 transport_latency_assumed tick_size_change i 3,876 6 25ms 32ms 58ms 154ms 0 transport_latency_assumed tick_size_change k 3,876 158 14ms 21ms 52ms 280ms 0 transport_latency_assumed tick_size_change m 3,876 3,686 5ms 11ms 26ms 49ms 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/12/2026-09-30T12.parquet sha256sum 2026-09-30T12.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.