Hour audit: 2026-09-07T08
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-07T08 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-07T08:00:00.000041880+00:00 · last event 2026-09-07T08:59:59.999347513+00:00
VOLUME 95,100,777 rows · 946,751,941 bytes (902.89 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 94,948,712 · c: 94,939,100 · g: 94,935,252 · e: 94,899,126 · h: 94,806,467 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 202,939 (0.21%) · c: 91,085,723 (95.78%) · g: 41,042 (0.04%) · e: 348,725 (0.37%) · h: 3,422,348 (3.60%) (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 95,100,777 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 27468d8439875cd124949ca15cbdcca3a9c611f6ffb9664365856cfcee86f479
the corpus checksum ledger names this file with the same digest
joined 95,103,454 to merged 95,100,777, minus 2,677 (minus 0.0028%)
boundary drops 2,677 · 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-07T09:55:12Z 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,133,516 108,309,626 0-38 b17551c23610115ca5bcd6ada5f3bd7b8a47ec6be0e721d06d69d13c3db2afd1 book 170,205 17,640,656 39-39 41aac56b809325d7cba6b4b0042b936443bf9a91d0a02176b07da5e74005bcee last_trade_price 51,871 2,917,339 40-40 9849a66cd52254ef2d5576dd39dfb1352cc1dbb331166bb33071e0924ad43992 market_resolved 553 90,714 41-41 1711c35de7ee0a5e77ccfdf5cd13cd5aead40efb4648fe2d4545a3f1f780b9cd new_market 2,680 267,313 42-42 50080c80d1a9eb66924e9e0439ffa0f88cab3264e55d3c93255788b2d18c124c price_change 84,740,448 816,385,958 43-366 a7021d7a6e66c3ea5c9345d1fa8713d245eeaf7fd899fdcc57d37085067a5491 tick_size_change 1,504 55,091 367-367 73b6d3e7a6e5faaaa214b6ffe5a9b4ce25ed20ff1d629feec99910039f39a816 EVENT MIX count share price_change 84,740,448 89.11% best_bid_ask 10,133,516 10.66% book 170,205 0.18% last_trade_price 51,871 0.05% new_market 2,680 <0.01% tick_size_change 1,504 <0.01% market_resolved 553 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,133,766 10,133,516 250 449 FULL book 170,215 170,205 10 27,283 FULL last_trade_price 51,874 51,871 3 0 FULL market_resolved 553 553 0 0 FULL new_market 2,680 2,680 0 0 FULL price_change 84,742,862 84,740,448 2,414 852 FULL tick_size_change 1,504 1,504 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,132,003 9,735,689 5ms 10ms 140ms 3.6s 0 transport_latency_assumed best_bid_ask e 10,130,190 30,334 40ms 46ms 240ms 9.0s 0 transport_latency_assumed best_bid_ask f 10,130,366 19,295 44ms 52ms 238ms 7.9s 0 transport_latency_assumed best_bid_ask g 10,128,700 1,508 81ms 100ms 534ms 24.3s 0 transport_latency_assumed best_bid_ask h 10,131,000 346,690 17ms 22ms 245ms 53.7s 0 transport_latency_assumed book c 129,528 121,455 7ms 1.7min 5.4d 81.9d 0 book_staleness book e 114,086 5,894 43ms 426ms 7.8h 81.9d 0 book_staleness book f 123,707 14,762 48ms 15.4s 1.8d 100.4d 0 book_staleness book g 127,838 18,972 92ms 1.4min 5.4d 100.4d 0 book_staleness book h 112,062 9,122 21ms 101ms 1.6h 81.9d 0 book_staleness last_trade_price c 51,755 48,916 10ms 44ms 235ms 5.0s 0 transport_latency_assumed last_trade_price e 51,790 214 47ms 176ms 2.3s 9.2s 0 transport_latency_assumed last_trade_price f 51,855 154 51ms 172ms 2.0s 8.0s 0 transport_latency_assumed last_trade_price g 51,506 15 95ms 281ms 3.7s 24.3s 0 transport_latency_assumed last_trade_price h 51,765 2,572 23ms 67ms 413ms 20.7s 0 transport_latency_assumed market_resolved c 541 520 5ms 15ms 346ms 57.9s 0 transport_latency_assumed market_resolved e 541 14 42ms 372ms 46.7s 1.0min 0 transport_latency_assumed market_resolved f 541 3 48ms 367ms 46.7s 1.0min 0 transport_latency_assumed market_resolved g 541 1 88ms 553ms 1.0s 1.6s 0 transport_latency_assumed market_resolved h 541 15 19ms 127ms 47.1s 50.9s 0 transport_latency_assumed new_market c 1,708 1,016 106ms 20.4s 49.5s 21.7min 0 transport_latency_assumed new_market e 1,708 335 186ms 26.2s 49.7s 5.0h 0 transport_latency_assumed new_market f 1,708 431 222ms 28.4s 53.7s 1.9h 0 transport_latency_assumed new_market g 1,708 293 279ms 22.3s 49.5s 2.4h 0 transport_latency_assumed new_market h 1,708 605 152ms 23.6s 49.3s 1.8h 0 transport_latency_assumed price_change c 84,622,061 81,176,681 5ms 11ms 150ms 4.2s 0 transport_latency_assumed price_change e 84,599,307 311,930 40ms 52ms 306ms 9.3s 0 transport_latency_assumed price_change f 84,639,031 168,290 45ms 57ms 303ms 8.0s 0 transport_latency_assumed price_change g 84,623,455 20,253 81ms 112ms 660ms 24.3s 0 transport_latency_assumed price_change h 84,507,887 3,063,294 17ms 24ms 247ms 55.4s 0 transport_latency_assumed tick_size_change c 1,504 1,446 5ms 7ms 125ms 238ms 0 transport_latency_assumed tick_size_change e 1,504 4 40ms 43ms 126ms 176ms 0 transport_latency_assumed tick_size_change f 1,504 4 45ms 50ms 109ms 142ms 0 transport_latency_assumed tick_size_change g 1,504 not meas. 80ms 97ms 237ms 672ms 0 transport_latency_assumed tick_size_change h 1,504 50 17ms 23ms 79ms 190ms 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/08/2026-09-07T08.parquet sha256sum 2026-09-07T08.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.