Hour audit: 2026-09-23T03
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-23T03 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-23T03:00:00.000381471+00:00 · last event 2026-09-23T03:59:59.999988568+00:00
VOLUME 110,548,036 rows · 1,133,285,685 bytes (1.06 GiB) · 7 products, all holding rows
WITNESSES cfhik — 5 machines contributed rows
captured c: 110,378,807 · k: 110,352,560 · f: 110,340,764 · h: 110,339,535 · i: 110,315,499 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 102,908,459 (93.09%) · k: 5,484,825 (4.96%) · f: 92,508 (0.08%) · h: 1,352,589 (1.22%) · i: 709,655 (0.64%) (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 110,548,036 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 47a67e944a382b8421df37b41a4c719669f60b8ae22f8b36a1e01925f50ce8b2
the corpus checksum ledger names this file with the same digest
joined 110,549,103 to merged 110,548,036, minus 1,067 (minus 0.0010%)
boundary drops 1,067 · 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-23T04:58:21Z as cfhik
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 our incident register was checked against the venue's own status feed at 2026-09-23T20:35Z and names no event in this hour. That is a statement about what they published, not a check that every message they sent reached us.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,399,447 128,438,438 0-43 5fe618fcd696c4912e6af45902d141bda19bffdf9dc49dc0e53c8c990c189df4 book 291,450 28,339,524 44-45 51724883d4fb747542e69a05b88a22a3a14fccf90703560b042c1e47047089e6 last_trade_price 44,366 2,532,004 46-46 2cdb042e078218c9ab8683ad177da9cb21e7be004fe93419910c40f5e11334fd market_resolved 1,443 219,306 47-47 e27220eef69f19f3446de663dcf222e2ec30006d37c2d4302f2c149132d6c875 new_market 872 91,980 48-48 4195fb88cd3d7f48fc6d6934135c4e21df60e2931fdd1e46e781e88c5f33c08e price_change 98,804,886 972,200,851 49-425 83e84f9ca29efc51a81cc7daccf0271d04bd4513fd65140eb9bba26e661e961c tick_size_change 5,572 203,596 426-426 0324ee6a55a5de9259f14c3ba5cbccc8d27dd3fa14afd60d3dbbe4cf8125c511 EVENT MIX count share price_change 98,804,886 89.38% best_bid_ask 11,399,447 10.31% book 291,450 0.26% last_trade_price 44,366 0.04% tick_size_change 5,572 <0.01% market_resolved 1,443 <0.01% new_market 872 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,399,580 11,399,447 133 95 FULL book 291,476 291,450 26 82,101 FULL last_trade_price 44,366 44,366 0 0 FULL market_resolved 1,443 1,443 0 0 FULL new_market 872 872 0 0 FULL price_change 98,805,794 98,804,886 908 75 FULL tick_size_change 5,572 5,572 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,398,645 10,717,952 5ms 10ms 74ms 1.9s 0 transport_latency_assumed best_bid_ask f 11,397,343 2,961 48ms 56ms 144ms 1.6s 0 transport_latency_assumed best_bid_ask h 11,397,655 111,284 18ms 31ms 104ms 7.3s 0 transport_latency_assumed best_bid_ask i 11,398,038 62,117 22ms 27ms 85ms 4.0s 0 transport_latency_assumed best_bid_ask k 11,398,095 505,133 12ms 18ms 74ms 5.0s 0 transport_latency_assumed book c 152,661 138,490 14ms 7.9h 28.3d 116.2d 0 book_staleness book f 139,121 44,551 55ms 5.2h 24.2d 116.2d 0 book_staleness book h 139,460 46,169 30ms 5.6h 23.5d 116.2d 0 book_staleness book i 104,962 13,836 24ms 2.8min 12.8d 97.7d 0 book_staleness book k 136,676 48,404 18ms 5.2h 20.4d 116.2d 0 book_staleness last_trade_price c 44,193 40,067 6ms 19ms 183ms 809ms 0 transport_latency_assumed last_trade_price f 44,134 69 49ms 93ms 340ms 1.5s 0 transport_latency_assumed last_trade_price h 44,178 830 19ms 48ms 243ms 5.4s 0 transport_latency_assumed last_trade_price i 44,103 356 23ms 46ms 247ms 1.5s 0 transport_latency_assumed last_trade_price k 44,149 3,044 13ms 27ms 162ms 696ms 0 transport_latency_assumed market_resolved c 1,356 1,206 5ms 28ms 54.4s 58.0s 0 transport_latency_assumed market_resolved f 1,356 1 48ms 304ms 58.8s 1.0min 0 transport_latency_assumed market_resolved h 1,356 14 18ms 23.7s 57.1s 1.0min 0 transport_latency_assumed market_resolved i 1,356 185 22ms 26.4s 59.9s 1.0min 0 transport_latency_assumed market_resolved k 1,356 37 13ms 63ms 56.9s 1.0min 0 transport_latency_assumed new_market c 592 359 49ms 46.2s 1.5min 2.1min 0 transport_latency_assumed new_market f 592 66 129ms 43.3s 1.6min 2.3min 0 transport_latency_assumed new_market h 592 154 117ms 37.7s 1.5min 2.4min 0 transport_latency_assumed new_market i 592 181 87ms 44.6s 1.4min 3.1min 0 transport_latency_assumed new_market k 592 112 87ms 46.8s 1.5min 2.4min 0 transport_latency_assumed price_change c 98,775,788 92,005,066 5ms 12ms 93ms 2.3s 0 transport_latency_assumed price_change f 98,752,646 44,860 48ms 60ms 178ms 2.0s 0 transport_latency_assumed price_change h 98,750,722 1,194,102 18ms 34ms 129ms 8.7s 0 transport_latency_assumed price_change i 98,760,876 632,972 22ms 31ms 114ms 7.9s 0 transport_latency_assumed price_change k 98,766,120 4,927,886 13ms 20ms 92ms 5.7s 0 transport_latency_assumed tick_size_change c 5,572 5,319 5ms 9ms 38ms 218ms 0 transport_latency_assumed tick_size_change f 5,572 not meas. 48ms 58ms 122ms 218ms 0 transport_latency_assumed tick_size_change h 5,572 36 18ms 40ms 99ms 457ms 0 transport_latency_assumed tick_size_change i 5,572 8 23ms 48ms 158ms 295ms 0 transport_latency_assumed tick_size_change k 5,572 209 13ms 18ms 50ms 453ms 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-23/03/2026-09-23T03.parquet sha256sum 2026-09-23T03.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.