Hour audit: 2026-09-08T02
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-08T02 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-08T02:00:00.000032907+00:00 · last event 2026-09-08T02:59:59.999978651+00:00
VOLUME 89,462,721 rows · 876,875,480 bytes (836.25 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 89,425,693 · h: 89,392,351 · e: 89,383,186 · f: 89,369,394 · g: 89,359,406 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 86,345,036 (96.52%) · h: 2,858,012 (3.19%) · e: 169,430 (0.19%) · f: 63,367 (0.07%) · g: 26,876 (0.03%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 89,462,721 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 b4df5a97def68aca9ba49efe4b244ec35806aeb3dc1d0b64324dbde2359d37a4
the corpus checksum ledger names this file with the same digest
joined 89,466,449 to merged 89,462,721, minus 3,728 (minus 0.0042%)
boundary drops 3,728 · 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-08T03:53:54Z 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 9,552,687 102,046,571 0-36 073bfba4ede6f99b05270d37b012697b87b6899b698274a2dff96db30b021b39 book 118,619 12,007,672 37-37 35afc95d034aa78c4757e4bea1dfb1f2b792e489121f2045da04592d3db80ffe last_trade_price 47,245 2,615,578 38-38 493a1cd1e4f708578df79ff13636d1a64192395416522fd536d885fb8770ab4f market_resolved 565 93,063 39-39 76541d2cdeb0314d083ccc56b905603c953703b150525060d564721c9a9efac9 new_market 1,201 122,040 40-40 00d98ce162f9b52806fcc9657a8a9678fbc6868e454e8082aa89264b570e28b6 price_change 79,740,188 758,885,102 41-345 03e7e2f819ac2d70b053e77b096d8176663994d94c088071b8c5187ec57cdc61 tick_size_change 2,216 81,814 346-346 5752917b704fafca0f08577f9c2ca8095c9ce2b432c37edf2243f4d8fca683c1 EVENT MIX count share price_change 79,740,188 89.13% best_bid_ask 9,552,687 10.68% book 118,619 0.13% last_trade_price 47,245 0.05% tick_size_change 2,216 <0.01% new_market 1,201 <0.01% market_resolved 565 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,552,975 9,552,687 288 137 FULL book 118,623 118,619 4 9,228 FULL last_trade_price 47,247 47,245 2 0 FULL market_resolved 565 565 0 0 FULL new_market 1,201 1,201 0 0 FULL price_change 79,743,622 79,740,188 3,434 218 FULL tick_size_change 2,216 2,216 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,552,102 9,238,380 5ms 7ms 70ms 3.6s 0 transport_latency_assumed best_bid_ask e 9,551,347 18,000 39ms 45ms 125ms 11.2s 0 transport_latency_assumed best_bid_ask f 9,550,745 6,971 47ms 51ms 152ms 12.4s 0 transport_latency_assumed best_bid_ask g 9,550,268 522 82ms 101ms 330ms 21.8s 0 transport_latency_assumed best_bid_ask h 9,551,865 288,814 13ms 15ms 106ms 53.6s 0 transport_latency_assumed book c 104,632 98,983 6ms 51ms 9.7h 82.7d 0 book_staleness book e 98,612 1,359 41ms 75ms 3.5s 82.5d 0 book_staleness book f 99,078 1,344 48ms 98ms 9.7s 82.6d 0 book_staleness book g 107,419 9,731 90ms 1.2s 15.5h 101.2d 0 book_staleness book h 100,251 7,202 16ms 38ms 42.6min 79.7d 0 book_staleness last_trade_price c 47,168 45,048 10ms 35ms 194ms 5.0s 0 transport_latency_assumed last_trade_price e 47,198 164 45ms 83ms 405ms 11.2s 0 transport_latency_assumed last_trade_price f 47,122 60 52ms 94ms 475ms 12.3s 0 transport_latency_assumed last_trade_price g 47,074 7 95ms 164ms 836ms 22.2s 0 transport_latency_assumed last_trade_price h 47,074 1,966 18ms 46ms 269ms 14.5s 0 transport_latency_assumed market_resolved c 556 539 5ms 9ms 48ms 82ms 0 transport_latency_assumed market_resolved e 556 2 41ms 177ms 55.8s 55.8s 0 transport_latency_assumed market_resolved f 556 10 49ms 187ms 55.6s 55.6s 0 transport_latency_assumed market_resolved g 556 not meas. 85ms 339ms 821ms 1.7s 0 transport_latency_assumed market_resolved h 556 14 13ms 38ms 99ms 146ms 0 transport_latency_assumed new_market c 769 358 162ms 31.6s 53.4s 1.6min 0 transport_latency_assumed new_market e 769 275 184ms 32.0s 50.8s 51.8s 0 transport_latency_assumed new_market f 769 84 219ms 31.8s 51.9s 55.6s 0 transport_latency_assumed new_market g 769 102 337ms 31.3s 45.7s 1.2min 0 transport_latency_assumed new_market h 769 382 136ms 29.5s 45.4s 1.3min 0 transport_latency_assumed price_change c 79,718,250 76,959,600 5ms 8ms 77ms 8.8s 0 transport_latency_assumed price_change e 79,682,488 149,626 40ms 46ms 167ms 11.3s 0 transport_latency_assumed price_change f 79,668,908 54,894 47ms 53ms 197ms 12.4s 0 transport_latency_assumed price_change g 79,651,104 16,514 82ms 103ms 394ms 22.3s 0 transport_latency_assumed price_change h 79,689,620 2,559,554 13ms 17ms 117ms 53.6s 0 transport_latency_assumed tick_size_change c 2,216 2,128 5ms 8ms 211ms 400ms 0 transport_latency_assumed tick_size_change e 2,216 4 40ms 45ms 257ms 645ms 0 transport_latency_assumed tick_size_change f 2,216 4 48ms 68ms 293ms 577ms 0 transport_latency_assumed tick_size_change g 2,216 not meas. 83ms 130ms 509ms 1.0s 0 transport_latency_assumed tick_size_change h 2,216 80 13ms 18ms 284ms 2.7s 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-08/02/2026-09-08T02.parquet sha256sum 2026-09-08T02.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.