Hour audit: 2026-09-05T08
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-05T08 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-05T08:00:00.035308298+00:00 · last event 2026-09-05T08:59:59.999999246+00:00
VOLUME 98,608,717 rows · 949,099,791 bytes (905.13 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 98,562,276 · e: 98,551,983 · h: 98,507,161 · b: 98,506,645 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 21,813 (0.02%) · e: 98,550,780 (99.94%) · h: 19,869 (0.02%) · b: 16,255 (0.02%) (rows of the merged file that came from it; these partition it)
5 product-machine pairs publish no supplied count; the figures above still sum to the file's 98,608,717 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 9ddd0ef8d2a5b79c031b0f0a017a766a75da3b7c0d24dcc9ddc23b720066f9b3
the corpus checksum ledger names this file with the same digest
joined 98,610,528 to merged 98,608,717, minus 1,811 (minus 0.0018%)
boundary drops 1,811 · 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-05T09:53:55Z as bceh
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 8,660,806 95,456,239 0-33 ba63d25f92e6aab96661838ce60eb7b2189f3258963c283c929e9857da152881 book 169,352 17,248,194 34-34 9f2d294e02723184c0bc441cf9dd9aadffc85d82af3ba34fabc48de12a8e7c8e last_trade_price 53,044 3,026,971 35-35 3a8a693a4608f9f41724a9e9ae7662f09d7b967ee1478a477fab0f201c6189a5 market_resolved 415 65,314 36-36 ab60ea0cc1017d333c9ef07aec34fe4f36e2d6ac7a057fd08aaaaaa72963132d new_market 1,116 123,641 37-37 7eb5f139ece66800bb94a31088c29aadf1b0783d54919a44094513094be211f5 price_change 89,721,864 831,974,779 38-380 fda406090cbde2b6f70e6ea38b86d1f3c23ce428519d09066a5e24919aa775e4 tick_size_change 2,120 78,179 381-381 f7942d287347ad834a7a164e7e598b75b83d7c41800585f7244aa1383e4776e5 EVENT MIX count share price_change 89,721,864 90.99% best_bid_ask 8,660,806 8.78% book 169,352 0.17% last_trade_price 53,044 0.05% tick_size_change 2,120 <0.01% new_market 1,116 <0.01% market_resolved 415 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,660,896 8,660,806 90 118 FULL book 169,352 169,352 0 27,678 FULL last_trade_price 53,045 53,044 1 0 FULL market_resolved 415 415 0 0 FULL new_market 1,116 1,116 0 0 FULL price_change 89,723,584 89,721,864 1,720 159 FULL tick_size_change 2,120 2,120 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 8,658,369 26 56ms 67ms 173ms 4.6s 0 transport_latency_assumed best_bid_ask c 8,660,518 676 2ms 4ms 51ms 4.6s 0 transport_latency_assumed best_bid_ask e 8,658,710 8,658,644 40ms 44ms 127ms 2.1s 0 transport_latency_assumed best_bid_ask h 8,659,814 1,460 17ms 20ms 111ms 8.4s 0 transport_latency_assumed book b 125,516 15,672 59ms 30.6s 1.5d 79.9d 0 book_staleness book c 127,187 16,595 4ms 58.4s 2.6d 98.4d 0 book_staleness book e 136,155 136,155 43ms 3.7min 13.5d 98.4d 0 book_staleness book h 109,938 930 20ms 41ms 2.2s 41.5d 0 book_staleness last_trade_price b 53,020 3 62ms 102ms 559ms 4.9s 0 transport_latency_assumed last_trade_price c 53,017 5 7ms 32ms 193ms 4.8s 0 transport_latency_assumed last_trade_price e 53,018 53,017 45ms 80ms 434ms 4.9s 0 transport_latency_assumed last_trade_price h 52,971 19 22ms 51ms 305ms 5.4s 0 transport_latency_assumed market_resolved b 406 not meas. 64ms 287ms 649ms 744ms 0 transport_latency_assumed market_resolved c 406 not meas. 2ms 7ms 145ms 225ms 0 transport_latency_assumed market_resolved e 406 406 42ms 270ms 602ms 671ms 0 transport_latency_assumed market_resolved h 406 9 19ms 137ms 55.0s 55.0s 0 transport_latency_assumed new_market b 818 66 192ms 13.7s 34.0s 1.0min 0 transport_latency_assumed new_market c 818 75 45ms 288ms 31.9s 58.3s 0 transport_latency_assumed new_market e 818 818 144ms 12.7s 34.0s 1.3min 0 transport_latency_assumed new_market h 818 157 121ms 12.4s 42.0s 1.3min 0 transport_latency_assumed price_change b 89,666,396 488 56ms 68ms 257ms 5.6s 0 transport_latency_assumed price_change c 89,718,210 4,462 2ms 5ms 89ms 5.1s 0 transport_latency_assumed price_change e 89,700,756 89,699,620 40ms 45ms 201ms 2.3s 0 transport_latency_assumed price_change h 89,681,094 17,294 17ms 22ms 170ms 8.4s 0 transport_latency_assumed tick_size_change b 2,120 not meas. 56ms 67ms 178ms 308ms 0 transport_latency_assumed tick_size_change c 2,120 not meas. 2ms 4ms 30ms 60ms 0 transport_latency_assumed tick_size_change e 2,120 2,120 40ms 44ms 148ms 229ms 0 transport_latency_assumed tick_size_change h 2,120 not meas. 17ms 20ms 40ms 53ms 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-05/08/2026-09-05T08.parquet sha256sum 2026-09-05T08.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.