Hour audit: 2026-09-07T17
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-07T17 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-07T17:00:00.000038881+00:00 · last event 2026-09-07T17:59:59.998285796+00:00
VOLUME 105,929,317 rows · 1,088,684,272 bytes (1.01 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 105,886,887 · f: 105,864,617 · g: 105,830,037 · e: 103,968,793 · c: 102,938,276 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 7,728,990 (7.30%) · f: 340,684 (0.32%) · g: 43,765 (0.04%) · e: 627,401 (0.59%) · c: 97,188,477 (91.75%) (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 105,929,317 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 4fb931e24c651977fc1a28d544a7063c3804286d4d836d7db36fb7c06aa502b7
the corpus checksum ledger names this file with the same digest
joined 105,931,190 to merged 105,929,317, minus 1,873 (minus 0.0018%)
boundary drops 1,873 · 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-07T19:35:01Z 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 10,826,508 120,462,286 0-41 6cb91325642a3ef066a066152b638f54fae8691d9073546b93e24c8d86faed14 book 145,347 14,622,131 42-42 467e2dd6a3a043794d15348796fdc194ee5d165e55cd981be1b0a6b346507036 last_trade_price 59,368 3,414,832 43-43 9980a03d1f474d10cef06c69e24fcc29a3d0502e55a02cdd2a1c5988a70f3ddb market_resolved 867 133,675 44-44 a1d6c503485c09b24b4755dc96e4fc6cdab65cba466a48f1975fcf123ff94d89 new_market 4,015 375,507 45-45 9628c1d4a2a14e72584a438adc8041ae90a558c2e901ee82f6146ea1fa94bac9 price_change 94,888,052 948,280,015 46-407 685ea7f01a34a55d18d7600a780aea9025ab2321ad63b91c9c66fbd0593cf98b tick_size_change 5,160 189,529 408-408 7b8c266781cd86b96d54606b8e3f459327bf957e3438b1b68d48ca592a03e303 EVENT MIX count share price_change 94,888,052 89.58% best_bid_ask 10,826,508 10.22% book 145,347 0.14% last_trade_price 59,368 0.06% tick_size_change 5,160 <0.01% new_market 4,015 <0.01% market_resolved 867 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,826,644 10,826,508 136 3,076 FULL book 145,349 145,347 2 7,303 FULL last_trade_price 59,369 59,368 1 187 FULL market_resolved 867 867 0 30 FULL new_market 4,015 4,015 0 0 FULL price_change 94,889,786 94,888,052 1,734 4,558 FULL tick_size_change 5,160 5,160 0 59 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,541,977 9,979,611 5ms 12ms 206ms 14.3s 0 transport_latency_assumed best_bid_ask e 10,632,633 60,616 40ms 51ms 286ms 16.4s 0 transport_latency_assumed best_bid_ask f 10,821,628 33,833 45ms 61ms 321ms 19.1s 0 transport_latency_assumed best_bid_ask g 10,820,078 2,585 85ms 143ms 692ms 25.5s 0 transport_latency_assumed best_bid_ask h 10,823,529 749,863 17ms 27ms 344ms 52.9s 0 transport_latency_assumed book c 122,063 113,149 7ms 41ms 2.7s 19.3s 0 book_staleness book e 120,551 3,162 43ms 217ms 4.0s 82.1d 0 book_staleness book f 126,907 2,750 47ms 283ms 10.0s 82.2d 0 book_staleness book g 138,656 14,369 97ms 8.0s 12.3h 82.3d 0 book_staleness book h 126,900 11,917 22ms 100ms 4.7s 82.1d 0 book_staleness last_trade_price c 57,404 54,042 10ms 51ms 322ms 5.8s 0 transport_latency_assumed last_trade_price e 56,560 430 47ms 171ms 3.1s 11.3s 0 transport_latency_assumed last_trade_price f 59,295 229 52ms 203ms 5.0s 19.1s 0 transport_latency_assumed last_trade_price g 59,117 16 102ms 555ms 8.8s 25.5s 0 transport_latency_assumed last_trade_price h 59,311 4,651 23ms 82ms 620ms 10.5s 0 transport_latency_assumed market_resolved c 806 751 5ms 19ms 1.0min 2.3min 0 transport_latency_assumed market_resolved e 805 42 42ms 261ms 59.7s 1.8min 0 transport_latency_assumed market_resolved f 821 3 46ms 292ms 59.8s 59.8s 0 transport_latency_assumed market_resolved g 820 2 86ms 381ms 980ms 1.7s 0 transport_latency_assumed market_resolved h 821 69 18ms 66ms 322ms 7.2s 0 transport_latency_assumed new_market c 2,350 1,372 120ms 22.7s 1.2min 2.0min 0 transport_latency_assumed new_market e 2,350 699 215ms 23.8s 1.3min 1.9min 0 transport_latency_assumed new_market f 2,350 464 239ms 24.1s 1.3min 1.5min 0 transport_latency_assumed new_market g 2,350 321 384ms 24.0s 1.2min 1.5min 0 transport_latency_assumed new_market h 2,350 1,159 154ms 23.7s 1.3min 2.0min 0 transport_latency_assumed price_change c 92,208,664 87,034,754 5ms 14ms 237ms 14.8s 0 transport_latency_assumed price_change e 93,150,830 562,422 41ms 61ms 384ms 17.8s 0 transport_latency_assumed price_change f 94,848,456 303,396 45ms 71ms 431ms 19.3s 0 transport_latency_assumed price_change g 94,803,856 26,472 85ms 173ms 940ms 25.5s 0 transport_latency_assumed price_change h 94,868,816 6,961,008 17ms 31ms 382ms 56.8s 0 transport_latency_assumed tick_size_change c 5,012 4,798 5ms 15ms 126ms 423ms 0 transport_latency_assumed tick_size_change e 5,064 30 41ms 49ms 155ms 512ms 0 transport_latency_assumed tick_size_change f 5,160 9 45ms 67ms 222ms 443ms 0 transport_latency_assumed tick_size_change g 5,160 not meas. 84ms 119ms 306ms 679ms 0 transport_latency_assumed tick_size_change h 5,160 323 17ms 32ms 840ms 8.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-07/17/2026-09-07T17.parquet sha256sum 2026-09-07T17.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.