Hour audit: 2026-09-12T13
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-12T13 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-12T13:00:00.000011340+00:00 · last event 2026-09-12T13:59:59.999972679+00:00
VOLUME 128,686,423 rows · 1,409,780,534 bytes (1.31 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 123,445,753 · e: 123,429,926 · g: 118,221,805 · f: 118,216,629 · c: 60,617,280 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 66,911,395 (52.00%) · e: 3,009,360 (2.34%) · g: 97,225 (0.08%) · f: 610,838 (0.47%) · c: 58,057,605 (45.12%) (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 128,686,423 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 08b6fd1550eff15eb4f6611a04e3785d9d9aba6dcd84746150b5a9b13b3693bd
the corpus checksum ledger names this file with the same digest
joined 128,702,609 to merged 128,686,423, minus 16,186 (minus 0.0126%)
boundary drops 16,186 · 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-12T15:00:34Z 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 11,683,914 131,730,125 0-44 e96e275e6451b23d9573fbb3606918cbba997377451ed595b31c9adde17ef8c7 book 5,348,040 151,911,706 45-65 a7ea72b123ab0f58b0c05afd285a17f9a3a17f47abaf412a660bd5caa79d3545 last_trade_price 74,368 4,295,358 66-66 5f61bb7d9c25a62dc9963968821f446a8688cd0e1371e52e6d04ea4c29e74e90 market_resolved 16,226 448,420 67-67 0e32a3b4464ba5c887fffef0583c03dfad3def1859bfbc5deb25742ef82a7d52 new_market 13,047 291,495 68-68 183084388b4456f5086ae6f3e6c17a18f99832acbac72ec53e55984732664802 price_change 111,544,360 1,119,400,000 69-494 1a2884305b922f83f0016cccecc399cf99efeca2a1a3e842005b42f4eb002fc3 tick_size_change 6,468 238,677 495-495 97be1d138d2fcf6cb0fb48e2a63b089a38fbc695c1234eae32f85f051f4961c9 EVENT MIX count share price_change 111,544,360 86.68% best_bid_ask 11,683,914 9.08% book 5,348,040 4.16% last_trade_price 74,368 0.06% market_resolved 16,226 0.01% new_market 13,047 0.01% tick_size_change 6,468 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,684,154 11,683,914 240 15,816 FULL book 5,361,565 5,348,040 13,525 202,956 FULL last_trade_price 74,369 74,368 1 1,864 FULL market_resolved 16,226 16,226 0 965 FULL new_market 13,107 13,047 60 855 FULL price_change 111,546,720 111,544,360 2,360 14,387 FULL tick_size_change 6,468 6,468 0 786 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 5,348,483 5,121,013 5ms 13ms 85ms 3.3s 0 transport_latency_assumed best_bid_ask e 11,681,951 268,290 39ms 44ms 151ms 2.8s 0 transport_latency_assumed best_bid_ask f 11,191,862 36,061 48ms 55ms 187ms 2.5s 0 transport_latency_assumed best_bid_ask g 11,153,203 3,974 77ms 95ms 328ms 14.9s 0 transport_latency_assumed best_bid_ask h 11,682,803 6,254,576 18ms 25ms 142ms 19.5s 0 transport_latency_assumed book c 5,147,026 5,059,372 13.1min 19.8h 31.8d 105.7d 0 book_staleness book e 158,767 8,078 41ms 116ms 1.1min 105.6d 0 book_staleness book f 564,613 155,390 2.1min 15.2h 21.0d 105.6d 0 book_staleness book g 585,805 42,820 2.8min 15.5h 21.0d 105.6d 0 book_staleness book h 158,131 82,380 21ms 51ms 2.5s 41.1d 0 book_staleness last_trade_price c 33,223 31,483 11ms 43ms 214ms 5.0s 0 transport_latency_assumed last_trade_price e 74,085 2,316 46ms 110ms 529ms 5.0s 0 transport_latency_assumed last_trade_price f 70,266 506 54ms 126ms 1.0s 5.0s 0 transport_latency_assumed last_trade_price g 70,948 56 91ms 264ms 2.9s 6.2s 0 transport_latency_assumed last_trade_price h 74,214 40,007 24ms 63ms 317ms 10.9s 0 transport_latency_assumed market_resolved c 15,418 15,291 40.3min 1.5h 1.9h 2.0h 0 transport_latency_assumed market_resolved e 1,523 118 40ms 187ms 1.0min 1.0min 0 transport_latency_assumed market_resolved f 1,520 25 48ms 128ms 5.1min 5.6min 0 transport_latency_assumed market_resolved g 1,539 3 85ms 299ms 8.3min 8.4min 0 transport_latency_assumed market_resolved h 1,523 789 19ms 51ms 143ms 1.1min 0 transport_latency_assumed new_market c 12,758 12,303 41.0min 1.3h 1.7h 1.9h 0 transport_latency_assumed new_market e 756 183 172ms 18.9s 26.5s 1.8min 0 transport_latency_assumed new_market f 758 102 198ms 17.6s 35.0s 6.3min 0 transport_latency_assumed new_market g 792 150 338ms 20.9s 1.6h 1.6h 0 transport_latency_assumed new_market h 756 309 148ms 16.3s 26.1s 1.1min 0 transport_latency_assumed price_change c 50,056,940 47,815,002 5ms 13ms 105ms 4.9s 0 transport_latency_assumed price_change e 111,506,376 2,730,202 39ms 47ms 216ms 4.9s 0 transport_latency_assumed price_change f 106,381,354 418,722 48ms 58ms 259ms 4.9s 0 transport_latency_assumed price_change g 106,403,286 50,222 77ms 99ms 479ms 14.9s 0 transport_latency_assumed price_change h 111,521,858 60,530,212 18ms 28ms 189ms 19.6s 0 transport_latency_assumed tick_size_change c 3,432 3,141 6ms 22ms 96ms 518ms 0 transport_latency_assumed tick_size_change e 6,468 173 39ms 46ms 158ms 394ms 0 transport_latency_assumed tick_size_change f 6,256 32 48ms 61ms 497ms 805ms 0 transport_latency_assumed tick_size_change g 6,232 not meas. 77ms 94ms 186ms 690ms 0 transport_latency_assumed tick_size_change h 6,468 3,122 18ms 30ms 134ms 382ms 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/13/2026-09-12T13.parquet sha256sum 2026-09-12T13.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.