Hour audit: 2026-09-06T14
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-06T14 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-06T14:00:00.064261986+00:00 · last event 2026-09-06T14:59:59.999984953+00:00
VOLUME 127,964,091 rows · 1,402,892,855 bytes (1.31 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 125,679,150 · e: 125,541,139 · g: 120,891,667 · f: 120,852,118 · c: 102,991,479 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 25,305,691 (19.78%) · e: 3,014,991 (2.36%) · g: 212,006 (0.17%) · f: 1,264,919 (0.99%) · c: 98,166,484 (76.71%) (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 127,964,091 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 54ecbb9a192d6c503d86c53e0e660bbe0962f3341806e8a9e2ade029c6fb58b4
the corpus checksum ledger names this file with the same digest
joined 127,972,200 to merged 127,964,091, minus 8,109 (minus 0.0063%)
boundary drops 8,109 · 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-06T23:03:09Z 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,338,676 141,233,313 0-47 c7c32da1be8c8c815279af6d12a0429a41fd29fb6cb661de3f0e127ad9c82aec book 2,200,246 97,462,939 48-56 6610e3d108148de7ccb72a14cb8ac2ed514c46ab0c4c952bfa84b8fd9c3d6b5f last_trade_price 78,246 4,465,200 57-57 ae796d4af7347200195514aa0c173c3b8bd6abcbe8c479350fd27b0b93be0cde market_resolved 2,175 284,074 58-58 f37a42b21db7c7fb50c225162670d0df4be9b3c7cb98c6188a8606522a47c843 new_market 5,049 474,878 59-59 031b05f96d48d8a1a36a1415c9175a4ad4c5f79f700c0ba2efd5a8dc213f2876 price_change 113,331,899 1,157,232,465 60-492 dbbc31ef2510b84e444e1204592c5f8e33421dedce534f72141563da267954b8 tick_size_change 7,800 282,934 493-493 fcbb9f953de39d03fca41f9806e85c1ebaa38b6f544527581c55cccea3800e2f EVENT MIX count share price_change 113,331,899 88.57% best_bid_ask 12,338,676 9.64% book 2,200,246 1.72% last_trade_price 78,246 0.06% tick_size_change 7,800 <0.01% new_market 5,049 <0.01% market_resolved 2,175 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,339,401 12,338,676 725 3,242 FULL book 2,202,414 2,200,246 2,168 171,731 FULL last_trade_price 78,250 78,246 4 471 FULL market_resolved 2,175 2,175 0 179 FULL new_market 5,049 5,049 0 97 FULL price_change 113,337,111 113,331,899 5,212 1,893 FULL tick_size_change 7,800 7,800 0 437 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,921,170 9,507,666 5ms 13ms 143ms 6.4s 0 transport_latency_assumed best_bid_ask e 12,336,461 283,069 40ms 58ms 313ms 5.3s 0 transport_latency_assumed best_bid_ask f 11,806,024 92,852 48ms 70ms 329ms 5.9s 0 transport_latency_assumed best_bid_ask g 11,827,436 7,217 83ms 146ms 710ms 45.7s 0 transport_latency_assumed best_bid_ask h 12,337,274 2,447,872 19ms 42ms 483ms 1.1min 0 transport_latency_assumed book c 1,897,361 1,876,222 3.6min 21.2h 35.1d 99.7d 0 book_staleness book e 164,848 6,274 43ms 186ms 3.2s 23.7h 0 book_staleness book f 508,426 162,407 45.5s 15.5h 29.1d 99.7d 0 book_staleness book g 515,988 122,518 47.7s 15.6h 29.2d 99.7d 0 book_staleness book h 165,464 32,825 24ms 93ms 3.7s 81.1d 0 book_staleness last_trade_price c 63,104 60,017 10ms 44ms 259ms 5.0s 0 transport_latency_assumed last_trade_price e 78,152 1,647 47ms 143ms 1.4s 5.4s 0 transport_latency_assumed last_trade_price f 74,167 600 55ms 156ms 1.1s 5.9s 0 transport_latency_assumed last_trade_price g 73,786 35 94ms 373ms 6.6s 45.4s 0 transport_latency_assumed last_trade_price h 78,212 15,947 25ms 78ms 758ms 23.4s 0 transport_latency_assumed market_resolved c 1,874 1,816 5ms 5.2min 8.6min 9.9min 0 transport_latency_assumed market_resolved e 1,727 58 41ms 129ms 58.4s 1.0min 0 transport_latency_assumed market_resolved f 1,620 6 49ms 155ms 58.4s 1.0min 0 transport_latency_assumed market_resolved g 1,631 9 85ms 245ms 1.0s 2.3min 0 transport_latency_assumed market_resolved h 1,727 286 20ms 65ms 267ms 5.2s 0 transport_latency_assumed new_market c 3,333 2,330 73ms 5.0min 23.4min 11.5h 0 transport_latency_assumed new_market e 2,968 806 178ms 39.4s 2.8min 1.6h 0 transport_latency_assumed new_market f 2,968 499 211ms 48.4s 3.4min 1.3h 0 transport_latency_assumed new_market g 2,964 358 321ms 44.3s 2.9min 4.0h 0 transport_latency_assumed new_market h 2,969 1,056 157ms 49.1s 2.8min 7.7h 0 transport_latency_assumed price_change c 91,098,265 86,712,304 5ms 16ms 206ms 7.4s 0 transport_latency_assumed price_change e 112,949,183 2,722,958 41ms 76ms 394ms 5.5s 0 transport_latency_assumed price_change f 108,451,297 1,008,513 49ms 88ms 399ms 5.9s 0 transport_latency_assumed price_change g 108,462,362 81,869 85ms 185ms 938ms 45.8s 0 transport_latency_assumed price_change h 113,085,704 22,806,255 19ms 50ms 527ms 1.7min 0 transport_latency_assumed tick_size_change c 6,372 6,129 5ms 13ms 85ms 253ms 0 transport_latency_assumed tick_size_change e 7,800 179 40ms 49ms 258ms 683ms 0 transport_latency_assumed tick_size_change f 7,616 42 48ms 64ms 313ms 486ms 0 transport_latency_assumed tick_size_change g 7,500 not meas. 81ms 111ms 552ms 20.7s 0 transport_latency_assumed tick_size_change h 7,800 1,450 19ms 41ms 365ms 2.5s 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-06/14/2026-09-06T14.parquet sha256sum 2026-09-06T14.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.