Hour audit: 2026-09-07T00
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-07T00 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-07T00:00:00.000212160+00:00 · last event 2026-09-07T00:59:59.999997402+00:00
VOLUME 121,013,937 rows · 1,278,009,209 bytes (1.19 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured g: 119,751,719 · e: 119,619,943 · h: 119,505,962 · f: 115,444,427 · c: 106,493,606 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 72,787 (0.06%) · e: 2,829,901 (2.34%) · h: 14,630,417 (12.09%) · f: 754,010 (0.62%) · c: 102,726,822 (84.89%) (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 121,013,937 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 f09d691df14fba5115d0f777272b6addf07758729c5ab7031f8bad8af3c9fb0a
the corpus checksum ledger names this file with the same digest
joined 121,016,710 to merged 121,013,937, minus 2,773 (minus 0.0023%)
boundary drops 2,773 · 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-07T03:36: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,849,499 141,855,495 0-49 29e6351e552e4efface3536499cd7bab51a8dff23c89e5a67ba9c2657d43e1e3 book 1,332,148 74,523,744 50-55 9fdcbb26e60bb0b6865feed97a6902d0c56b6d76f3679d65f4b3e355a771469f last_trade_price 59,383 3,317,247 56-56 8cfa75aa71c2f97662570d67196db5aa14c8cf9e265c397d3f726f3e002a65e7 market_resolved 1,878 241,994 57-57 b82c3210ef8a79157c37ef59e1d05ceb329d757b378ea8dadc03ca4571db879b new_market 1,945 167,962 58-58 d5b18a2a3a1af85a4011969baa8faa1df5569e8f555de2b7b5a5edf4eba8305b price_change 106,765,792 1,056,402,368 59-466 4941dc66c2681d61f896d926f15fc748d539bef70d38b7caa9538bb7876d9eef tick_size_change 3,292 120,958 467-467 9085665067a3100ba0c238733d341a74649eed72d050679fb2db081f2cd76624 EVENT MIX count share price_change 106,765,792 88.23% best_bid_ask 12,849,499 10.62% book 1,332,148 1.10% last_trade_price 59,383 0.05% tick_size_change 3,292 <0.01% new_market 1,945 <0.01% market_resolved 1,878 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,849,768 12,849,499 269 1,868 FULL book 1,332,576 1,332,148 428 169,952 FULL last_trade_price 59,383 59,383 0 291 FULL market_resolved 1,878 1,878 0 156 FULL new_market 1,945 1,945 0 18 FULL price_change 106,767,868 106,765,792 2,076 1,496 FULL tick_size_change 3,292 3,292 0 117 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,380,905 10,994,832 4ms 9ms 72ms 2.1s 0 transport_latency_assumed best_bid_ask e 12,847,048 294,027 39ms 47ms 180ms 7.7s 0 transport_latency_assumed best_bid_ask f 12,358,233 52,764 49ms 61ms 224ms 5.0s 0 transport_latency_assumed best_bid_ask g 12,845,397 6,634 83ms 103ms 372ms 12.7s 0 transport_latency_assumed best_bid_ask h 12,838,833 1,501,242 17ms 36ms 181ms 45.9s 0 transport_latency_assumed book c 1,146,921 1,134,158 4.9min 1.0d 35.5d 100.1d 0 book_staleness book e 124,064 6,105 41ms 156ms 1.7s 26.3d 0 book_staleness book f 466,650 161,780 1.4min 15.4h 33.3d 100.1d 0 book_staleness book g 134,882 7,576 90ms 1.5s 21.2h 81.6d 0 book_staleness book h 129,437 22,529 22ms 210ms 2.8h 81.5d 0 book_staleness last_trade_price c 51,121 48,717 10ms 41ms 235ms 4.9s 0 transport_latency_assumed last_trade_price e 59,340 2,121 46ms 139ms 1.1s 7.7s 0 transport_latency_assumed last_trade_price f 57,752 743 54ms 131ms 1.0s 5.0s 0 transport_latency_assumed last_trade_price g 59,180 72 94ms 211ms 2.5s 12.7s 0 transport_latency_assumed last_trade_price h 58,456 7,730 23ms 100ms 640ms 43.1s 0 transport_latency_assumed market_resolved c 1,574 1,526 5ms 4.5min 11.0min 11.2min 0 transport_latency_assumed market_resolved e 1,491 64 42ms 184ms 733ms 56.2s 0 transport_latency_assumed market_resolved f 1,404 37 52ms 220ms 3.4min 4.5min 0 transport_latency_assumed market_resolved g 1,491 5 90ms 261ms 1.0s 1.5s 0 transport_latency_assumed market_resolved h 1,491 246 24ms 77ms 426ms 59.7s 0 transport_latency_assumed new_market c 1,276 842 101ms 6.6min 1.4h 4.4h 0 transport_latency_assumed new_market e 1,038 237 179ms 18.4s 25.6s 4.3h 0 transport_latency_assumed new_market f 1,056 242 184ms 20.3s 1.0d 2.1d 0 transport_latency_assumed new_market g 1,038 188 276ms 19.5s 25.9s 4.1h 0 transport_latency_assumed new_market h 1,038 436 151ms 19.9s 24.6s 4.0h 0 transport_latency_assumed price_change c 93,908,837 90,543,851 5ms 11ms 82ms 2.7s 0 transport_latency_assumed price_change e 106,583,670 2,527,285 39ms 52ms 231ms 7.7s 0 transport_latency_assumed price_change f 102,556,188 538,435 49ms 67ms 260ms 5.0s 0 transport_latency_assumed price_change g 106,706,439 58,312 84ms 112ms 461ms 12.7s 0 transport_latency_assumed price_change h 106,473,415 13,097,909 18ms 39ms 211ms 50.6s 0 transport_latency_assumed tick_size_change c 2,972 2,896 5ms 10ms 56ms 139ms 0 transport_latency_assumed tick_size_change e 3,292 62 39ms 46ms 97ms 585ms 0 transport_latency_assumed tick_size_change f 3,144 9 49ms 56ms 167ms 354ms 0 transport_latency_assumed tick_size_change g 3,292 not meas. 81ms 96ms 218ms 763ms 0 transport_latency_assumed tick_size_change h 3,292 325 18ms 30ms 79ms 488ms 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-07/00/2026-09-07T00.parquet sha256sum 2026-09-07T00.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.