Hour audit: 2026-09-30T22
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-30T22 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-30T22:00:00.000006723+00:00 · last event 2026-09-30T22:59:59.999921568+00:00
VOLUME 95,075,232 rows · 1,043,132,241 bytes (994.81 MiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured i: 94,440,413 · m: 94,326,823 · h: 94,315,720 · k: 94,287,523 · g: 94,282,086 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 3,307,510 (3.48%) · m: 77,781,526 (81.81%) · h: 2,684,366 (2.82%) · k: 11,061,344 (11.63%) · g: 240,486 (0.25%) (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 95,075,232 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 b05d200b2a421008809c1cb7f4c4d12f9bd5338c37927fb83d2abe349301f062
the corpus checksum ledger names this file with the same digest
joined 95,077,454 to merged 95,075,232, minus 2,222 (minus 0.0023%)
boundary drops 2,222 · 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-10-01T00:49:11Z 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 9,209,965 109,403,278 0-35 c9fcfe95bfc41a304ded13917663bcb416097e08f6b3d0bb3acea0213835743f book 1,246,393 86,428,752 36-40 c7b14fc3640ac5016f24e683b43b7f5e34b0ce3ff21d82e2f29774794662434b last_trade_price 42,301 2,468,679 41-41 b6f397c4e331b9d33873b66c36cd145bef267398b73505b595ad66978e2d3a5f market_resolved 957 143,733 42-42 bfe9574701e1a8f99ca27e2112621cc593031ea35e58c618a1f7710b582e313c new_market 1,570 157,856 43-43 b9ddb8b02b303a948c3b211a1b39aa4775e547c5a7b0433cc4d32d26b49b9542 price_change 84,572,082 843,368,725 44-366 81596c617f5b595ca62e07e7a09589434a7e91a97293596bf8499b80d600ddf9 tick_size_change 1,964 73,263 367-367 aa34fc16c807ff209b54201e5a1bcc8cc770201ec5eca0388d6a6074dcc78c71 EVENT MIX count share price_change 84,572,082 88.95% best_bid_ask 9,209,965 9.69% book 1,246,393 1.31% last_trade_price 42,301 0.04% tick_size_change 1,964 <0.01% new_market 1,570 <0.01% market_resolved 957 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,210,139 9,209,965 174 108 FULL book 1,246,403 1,246,393 10 143,185 FULL last_trade_price 42,301 42,301 0 2 FULL market_resolved 957 957 0 0 FULL new_market 1,570 1,570 0 0 FULL price_change 84,574,120 84,572,082 2,038 105 FULL tick_size_change 1,964 1,964 0 2 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,205,648 2,850 80ms 98ms 317ms 13.3s 0 transport_latency_assumed best_bid_ask h 9,206,998 234,274 20ms 46ms 234ms 51.7s 0 transport_latency_assumed best_bid_ask i 9,206,907 280,619 20ms 57ms 160ms 50.3s 0 transport_latency_assumed best_bid_ask k 9,207,583 1,005,571 14ms 34ms 151ms 55.8s 0 transport_latency_assumed best_bid_ask m 9,208,155 7,686,651 5ms 21ms 97ms 1.8s 0 transport_latency_assumed book g 517,261 207,762 36.6min 2.5d 39.4d 124.0d 0 book_staleness book h 528,900 245,874 45.6min 2.7d 39.4d 124.0d 0 book_staleness book i 654,041 280,790 54.6min 3.0d 39.4d 124.0d 0 book_staleness book k 490,329 212,270 34.3min 2.5d 39.4d 124.0d 0 book_staleness book m 530,728 299,697 38.8min 2.8d 39.4d 124.0d 0 book_staleness last_trade_price g 42,278 37 86ms 204ms 4.0s 13.4s 0 transport_latency_assumed last_trade_price h 42,269 1,452 24ms 63ms 353ms 41.2s 0 transport_latency_assumed last_trade_price i 42,284 2,395 33ms 109ms 1.2s 6.5s 0 transport_latency_assumed last_trade_price k 42,278 5,695 17ms 47ms 228ms 8.0s 0 transport_latency_assumed last_trade_price m 42,277 32,722 7ms 33ms 158ms 1.2s 0 transport_latency_assumed market_resolved g 883 1 86ms 18.7s 53.9s 58.2s 0 transport_latency_assumed market_resolved h 883 24 30ms 22.0s 55.2s 2.1min 0 transport_latency_assumed market_resolved i 883 15 42ms 19.0s 54.0s 57.6s 0 transport_latency_assumed market_resolved k 883 136 18ms 115ms 49.4s 49.5s 0 transport_latency_assumed market_resolved m 883 781 7ms 17.5s 52.5s 57.6s 0 transport_latency_assumed new_market g 1,018 138 355ms 19.9s 35.2s 350.1d 0 transport_latency_assumed new_market h 1,018 143 204ms 20.8s 35.9s 350.1d 0 transport_latency_assumed new_market i 1,018 334 128ms 20.9s 34.6s 350.1d 0 transport_latency_assumed new_market k 1,018 198 224ms 23.8s 33.3s 350.1d 0 transport_latency_assumed new_market m 1,018 757 60ms 19.7s 30.4s 350.1d 0 transport_latency_assumed price_change g 84,513,042 29,698 81ms 105ms 540ms 13.4s 0 transport_latency_assumed price_change h 84,533,688 2,202,532 20ms 49ms 261ms 58.9s 0 transport_latency_assumed price_change i 84,533,316 2,743,294 22ms 61ms 250ms 1.6min 0 transport_latency_assumed price_change k 84,543,468 9,837,254 14ms 36ms 165ms 55.8s 0 transport_latency_assumed price_change m 84,541,798 69,759,304 5ms 23ms 106ms 2.2s 0 transport_latency_assumed tick_size_change g 1,956 not meas. 81ms 98ms 451ms 803ms 0 transport_latency_assumed tick_size_change h 1,964 67 20ms 48ms 333ms 361ms 0 transport_latency_assumed tick_size_change i 1,964 63 25ms 61ms 243ms 420ms 0 transport_latency_assumed tick_size_change k 1,964 220 15ms 40ms 358ms 519ms 0 transport_latency_assumed tick_size_change m 1,964 1,614 5ms 23ms 97ms 217ms 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/22/2026-09-30T22.parquet sha256sum 2026-09-30T22.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.