Hour audit: 2026-09-12T14
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-12T14 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-12T14:00:00.000041072+00:00 · last event 2026-09-12T14:59:59.999997175+00:00
VOLUME 141,083,724 rows · 1,572,747,248 bytes (1.46 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 135,889,967 · e: 125,209,126 · g: 124,465,442 · f: 124,204,479 · c: 64,976,028 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 73,294,786 (51.95%) · e: 3,993,194 (2.83%) · g: 201,581 (0.14%) · f: 1,433,319 (1.02%) · c: 62,160,844 (44.06%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 4fbdbc2d8ed68bf739b267b5f6c7e69eadcde02addc6c1dcf55efe673b98f316
the corpus checksum ledger names this file with the same digest
joined 141,103,466 to merged 141,083,724, minus 19,742 (minus 0.0140%)
boundary drops 19,742 · 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-12T16:02:15Z as cefgh
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 12,578,091 142,308,164 0-47 b6c8e45abecc4d37fdc5a1462286cd5295b3caf92b924ad528a826b7f603be8b book 5,644,341 162,193,670 48-69 e4151dedaace8c459ce57d7452733673c5cc2584200bb3f52ed5edcd5f7af6f1 last_trade_price 65,350 3,873,770 70-70 2f912f5399613e3ed18176bd0fa2b503a0c8e29951f44c12fa0d7d1c305f316f market_resolved 18,097 668,519 71-71 2faf42915dd749a9ea303aa17df76aedca2195599a152040d225660704c09592 new_market 26,417 578,846 72-72 c9b52c481efe2a637753ffd46b2da76b4ae9591d7c1e0050e5b6fc0a3d217bca price_change 122,740,456 1,261,114,466 73-541 cc558d6f77df001ab8212693d35ad58432c78d958f30645070af964d4d691631 tick_size_change 10,972 406,508 542-542 a92cd2466705ecbf0f8aa97addb1cb73b6598b6ef5c75ef4d122d1cdb21926e7 EVENT MIX count share price_change 122,740,456 87.00% best_bid_ask 12,578,091 8.92% book 5,644,341 4.00% last_trade_price 65,350 0.05% new_market 26,417 0.02% market_resolved 18,097 0.01% tick_size_change 10,972 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,578,457 12,578,091 366 18,120 FULL book 5,658,114 5,644,341 13,773 31,065 FULL last_trade_price 65,351 65,350 1 1,932 FULL market_resolved 18,097 18,097 0 2,437 FULL new_market 26,523 26,417 106 1,485 FULL price_change 122,745,952 122,740,456 5,496 13,023 FULL tick_size_change 10,972 10,972 0 1,342 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 5,604,759 5,383,655 6ms 13ms 90ms 5.9s 0 transport_latency_assumed best_bid_ask e 11,560,966 342,886 41ms 49ms 248ms 12.1s 0 transport_latency_assumed best_bid_ask f 11,462,121 94,977 48ms 56ms 259ms 11.9s 0 transport_latency_assumed best_bid_ask g 11,489,860 7,860 78ms 99ms 532ms 35.3s 0 transport_latency_assumed best_bid_ask h 12,574,732 6,748,713 18ms 33ms 326ms 1.0min 0 transport_latency_assumed book c 5,081,405 4,780,046 15.2min 20.8h 31.8d 105.7d 0 book_staleness book e 1,053,611 211,155 7.3min 20.5h 31.0d 105.7d 0 book_staleness book f 1,098,565 365,130 7.6min 20.5h 31.0d 105.7d 0 book_staleness book g 973,560 103,904 7.3min 20.6h 30.8d 105.7d 0 book_staleness book h 530,422 184,106 2.5min 15.6h 21.1d 105.7d 0 book_staleness last_trade_price c 28,248 26,883 11ms 46ms 223ms 4.9s 0 transport_latency_assumed last_trade_price e 60,074 1,916 49ms 120ms 1.2s 11.6s 0 transport_latency_assumed last_trade_price f 59,640 536 55ms 136ms 1.3s 11.5s 0 transport_latency_assumed last_trade_price g 59,564 115 92ms 235ms 3.8s 35.2s 0 transport_latency_assumed last_trade_price h 65,272 35,900 24ms 74ms 582ms 1.0min 0 transport_latency_assumed market_resolved c 17,263 16,938 59.4min 2.3h 2.8h 2.9h 0 transport_latency_assumed market_resolved e 1,645 257 47ms 8.2min 15.6min 15.7min 0 transport_latency_assumed market_resolved f 1,448 170 51ms 4.6min 9.1min 10.5min 0 transport_latency_assumed market_resolved g 1,515 1 88ms 5.4min 9.8min 11.3min 0 transport_latency_assumed market_resolved h 1,390 731 19ms 61ms 57.8s 1.0min 0 transport_latency_assumed new_market c 26,387 25,144 52.8min 2.0h 2.5h 2.9h 0 transport_latency_assumed new_market e 1,673 325 226ms 4.5min 8.8min 12.4min 0 transport_latency_assumed new_market f 1,662 362 238ms 4.3min 6.6min 44.8min 0 transport_latency_assumed new_market g 1,738 167 406ms 4.9min 7.3min 44.9min 0 transport_latency_assumed new_market h 1,511 419 181ms 21.1s 1.5min 1.9min 0 transport_latency_assumed price_change c 54,212,150 51,922,652 6ms 14ms 110ms 6.5s 0 transport_latency_assumed price_change e 112,520,457 3,436,422 42ms 53ms 313ms 12.1s 0 transport_latency_assumed price_change f 111,570,823 972,116 48ms 61ms 327ms 14.0s 0 transport_latency_assumed price_change g 111,928,945 89,530 78ms 108ms 671ms 35.3s 0 transport_latency_assumed price_change h 122,705,668 66,319,736 18ms 36ms 361ms 1.0min 0 transport_latency_assumed tick_size_change c 5,816 5,526 6ms 12ms 60ms 426ms 0 transport_latency_assumed tick_size_change e 10,700 233 41ms 45ms 93ms 381ms 0 transport_latency_assumed tick_size_change f 10,220 28 47ms 51ms 122ms 611ms 0 transport_latency_assumed tick_size_change g 10,260 4 77ms 91ms 325ms 4.9s 0 transport_latency_assumed tick_size_change h 10,972 5,181 18ms 23ms 107ms 32.8s 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-12/14/2026-09-12T14.parquet sha256sum 2026-09-12T14.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.