Hour audit: 2026-09-07T07
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-07T07 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-07T07:00:00.000019771+00:00 · last event 2026-09-07T07:59:59.999999839+00:00
VOLUME 93,825,568 rows · 917,201,191 bytes (874.71 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured g: 93,680,289 · f: 93,676,355 · c: 93,652,961 · e: 93,628,147 · h: 93,486,752 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 56,335 (0.06%) · f: 135,549 (0.14%) · c: 90,410,082 (96.36%) · e: 313,721 (0.33%) · h: 2,909,881 (3.10%) (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 93,825,568 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 fb77e61b5ea3bc70238462298df0db04014bac1c304921087bf8b61b05ad7eca
the corpus checksum ledger names this file with the same digest
joined 93,827,089 to merged 93,825,568, minus 1,521 (minus 0.0016%)
boundary drops 1,521 · 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-07T08:55:21Z 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,795,174 105,079,284 0-37 7b979065d7d6b8a40efc13674d8d118485a7ad33abb033707a643aadb032566a book 130,375 12,656,218 38-38 c4165e112ac1a744489b7c2c5893b997624403978b40c516e3fb0ba14790cdb2 last_trade_price 54,942 3,050,264 39-39 3b4bd60ba7274a80b5c64de113359ad80c889ec18b455c198442a71e3fd11900 market_resolved 660 108,017 40-40 11fadb1828a6847839f056f537d3f1b9187158607cfb9edaf9aa102b0bba7a61 new_market 1,675 172,031 41-41 ca8744bd4e27ffcedeb641aab850a1c1fdd06eb02c04fab2d699a2c124ae4ddb price_change 83,840,842 794,995,074 42-361 204203955f6ae5bdf741d7e08b0a8598db615f17785f834b9bda7a2f316f1993 tick_size_change 1,900 69,960 362-362 7a60a4f6d728cdbb90f3cb2a22151a587188d82ff142da14c1b53fd1b23058cc EVENT MIX count share price_change 83,840,842 89.36% best_bid_ask 9,795,174 10.44% book 130,375 0.14% last_trade_price 54,942 0.06% tick_size_change 1,900 <0.01% new_market 1,675 <0.01% market_resolved 660 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,795,302 9,795,174 128 283 FULL book 130,379 130,375 4 6,671 FULL last_trade_price 54,943 54,942 1 0 FULL market_resolved 660 660 0 0 FULL new_market 1,675 1,675 0 0 FULL price_change 83,842,230 83,840,842 1,388 797 FULL tick_size_change 1,900 1,900 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,793,882 9,463,490 5ms 9ms 108ms 5.3s 0 transport_latency_assumed best_bid_ask e 9,792,298 28,695 41ms 46ms 169ms 2.0s 0 transport_latency_assumed best_bid_ask f 9,792,351 12,857 49ms 55ms 180ms 3.0s 0 transport_latency_assumed best_bid_ask g 9,791,596 1,848 80ms 97ms 345ms 12.1s 0 transport_latency_assumed best_bid_ask h 9,793,523 288,284 17ms 21ms 143ms 15.9s 0 transport_latency_assumed book c 115,337 108,554 7ms 21ms 3.1s 81.8d 0 book_staleness book e 117,400 4,242 43ms 174ms 2.1h 81.9d 0 book_staleness book f 115,936 2,207 53ms 163ms 34.0s 100.4d 0 book_staleness book g 122,108 8,491 89ms 597ms 12.6h 81.9d 0 book_staleness book h 115,194 6,881 20ms 45ms 2.5s 81.8d 0 book_staleness last_trade_price c 54,794 52,340 10ms 40ms 215ms 5.0s 0 transport_latency_assumed last_trade_price e 54,810 137 47ms 131ms 1.0s 5.0s 0 transport_latency_assumed last_trade_price f 54,848 109 57ms 139ms 1.1s 5.0s 0 transport_latency_assumed last_trade_price g 54,803 48 95ms 236ms 3.4s 12.2s 0 transport_latency_assumed last_trade_price h 54,840 2,308 22ms 55ms 296ms 6.7s 0 transport_latency_assumed market_resolved c 660 643 5ms 11ms 76ms 1.3s 0 transport_latency_assumed market_resolved e 660 2 42ms 192ms 453ms 861ms 0 transport_latency_assumed market_resolved f 660 2 51ms 201ms 445ms 1.0s 0 transport_latency_assumed market_resolved g 660 not meas. 86ms 362ms 900ms 1.1s 0 transport_latency_assumed market_resolved h 660 13 18ms 77ms 255ms 3.8s 0 transport_latency_assumed new_market c 1,106 597 106ms 15.4s 26.2s 2.1h 0 transport_latency_assumed new_market e 1,106 330 157ms 14.1s 36.6s 4.6h 0 transport_latency_assumed new_market f 1,106 134 198ms 15.4s 26.4s 49.2min 0 transport_latency_assumed new_market g 1,106 138 268ms 14.2s 23.6s 7.1min 0 transport_latency_assumed new_market h 1,106 476 134ms 17.3s 25.4s 1.1h 0 transport_latency_assumed price_change c 83,685,282 80,782,589 5ms 10ms 113ms 6.5s 0 transport_latency_assumed price_change e 83,659,973 280,311 41ms 49ms 218ms 2.1s 0 transport_latency_assumed price_change f 83,709,554 120,236 50ms 59ms 222ms 3.0s 0 transport_latency_assumed price_change g 83,708,116 45,810 81ms 100ms 425ms 12.2s 0 transport_latency_assumed price_change h 83,519,529 2,611,896 17ms 23ms 150ms 15.9s 0 transport_latency_assumed tick_size_change c 1,900 1,869 5ms 8ms 41ms 407ms 0 transport_latency_assumed tick_size_change e 1,900 4 41ms 45ms 110ms 162ms 0 transport_latency_assumed tick_size_change f 1,900 4 50ms 59ms 156ms 232ms 0 transport_latency_assumed tick_size_change g 1,900 not meas. 81ms 94ms 287ms 386ms 0 transport_latency_assumed tick_size_change h 1,900 23 17ms 20ms 73ms 1.6s 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/07/2026-09-07T07.parquet sha256sum 2026-09-07T07.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.