Hour audit: 2026-09-08T08
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-08T08 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-08T08:00:00.000116436+00:00 · last event 2026-09-08T08:59:59.999898379+00:00
VOLUME 93,780,124 rows · 966,008,245 bytes (921.26 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 93,473,395 · c: 93,450,019 · e: 93,427,523 · f: 93,422,221 · g: 93,234,596 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 3,239,853 (3.45%) · c: 90,105,499 (96.08%) · e: 257,656 (0.27%) · f: 163,997 (0.17%) · g: 13,119 (0.01%) (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,780,124 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 5eb92ed574b5f989efe429132c5512636990a95931235e50c88a6e1b2db28d3a
the corpus checksum ledger names this file with the same digest
joined 93,783,782 to merged 93,780,124, minus 3,658 (minus 0.0039%)
boundary drops 3,658 · 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-08T09:55: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 8,415,394 91,690,769 0-32 af95a8345dd4fa462f1f1b0301b9e7162d03d241b519c2325dcbdd9d29577d03 book 596,760 57,135,920 33-35 5bbef364f685e7a65818b6e99113d8bfb254214df5191e1854e7346f08bebfb5 last_trade_price 66,823 3,647,034 36-36 d8fcda7c9637e4af608027c0be2ab8a5c73e2255805bfb514d97fbdff16c9f23 market_resolved 671 102,723 37-37 4f793b62ba7d79be12fece456142186c52e9500246b4853c724d85ad8e6acd5f new_market 776 88,714 38-38 68742e3e219f1d8f4aa05739cc7c0d5f22f44e29932d8fd5a00a7bd929cfd6fb price_change 84,697,272 812,180,116 39-362 83b66a87272f76f0d2065b8bb4703df31ba825c0f135d310196f1be507ed5ecb tick_size_change 2,428 88,621 363-363 a99735e62ebdfdf4b59a4c257242081f950d60666e3d892be60d18e311ff3d98 EVENT MIX count share price_change 84,697,272 90.31% best_bid_ask 8,415,394 8.97% book 596,760 0.64% last_trade_price 66,823 0.07% tick_size_change 2,428 <0.01% new_market 776 <0.01% market_resolved 671 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,415,598 8,415,394 204 173 FULL book 598,128 596,760 1,368 155,732 FULL last_trade_price 66,823 66,823 0 1 FULL market_resolved 671 671 0 0 FULL new_market 776 776 0 0 FULL price_change 84,699,358 84,697,272 2,086 210 FULL tick_size_change 2,428 2,428 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,414,278 8,130,145 5ms 9ms 70ms 3.2s 0 transport_latency_assumed best_bid_ask e 8,412,994 12,937 39ms 43ms 130ms 2.9s 0 transport_latency_assumed best_bid_ask f 8,412,664 4,573 48ms 53ms 145ms 5.0s 0 transport_latency_assumed best_bid_ask g 8,412,726 359 79ms 98ms 263ms 9.5s 0 transport_latency_assumed best_bid_ask h 8,413,315 267,380 17ms 21ms 84ms 34.8s 0 transport_latency_assumed book c 289,143 244,515 4.2s 9.0h 16.8d 101.4d 0 book_staleness book e 279,061 102,007 1.3s 8.5h 16.8d 101.4d 0 book_staleness book f 285,788 108,309 3.6s 8.5h 16.8d 101.4d 0 book_staleness book g 151,193 8,502 84ms 873ms 19.2h 101.4d 0 book_staleness book h 316,451 133,427 18.3s 10.0h 16.8d 101.4d 0 book_staleness last_trade_price c 66,739 63,692 10ms 36ms 176ms 5.0s 0 transport_latency_assumed last_trade_price e 66,773 190 45ms 98ms 726ms 5.0s 0 transport_latency_assumed last_trade_price f 66,732 114 54ms 123ms 1.7s 5.0s 0 transport_latency_assumed last_trade_price g 66,708 13 89ms 169ms 1.5s 8.3s 0 transport_latency_assumed last_trade_price h 66,742 2,814 22ms 53ms 241ms 5.3s 0 transport_latency_assumed market_resolved c 631 570 5ms 22ms 57.6s 59.3s 0 transport_latency_assumed market_resolved e 631 65 41ms 27.4s 1.0min 1.0min 0 transport_latency_assumed market_resolved f 631 1 49ms 27.4s 1.0min 1.0min 0 transport_latency_assumed market_resolved g 631 1 85ms 331ms 52.5s 1.4min 0 transport_latency_assumed market_resolved h 631 34 17ms 74ms 57.7s 1.1min 0 transport_latency_assumed new_market c 570 285 63ms 435ms 31.1s 1.5min 0 transport_latency_assumed new_market e 570 89 135ms 18.7s 37.7s 1.3min 0 transport_latency_assumed new_market f 570 82 124ms 13.8s 51.4s 57.4s 0 transport_latency_assumed new_market g 570 54 215ms 16.9s 32.2s 56.1s 0 transport_latency_assumed new_market h 570 266 61ms 15.7s 51.6s 1.0min 0 transport_latency_assumed price_change c 84,676,230 81,663,886 5ms 10ms 76ms 4.3s 0 transport_latency_assumed price_change e 84,665,066 142,366 39ms 46ms 173ms 4.3s 0 transport_latency_assumed price_change f 84,653,408 50,918 48ms 56ms 206ms 5.0s 0 transport_latency_assumed price_change g 84,600,340 4,190 80ms 100ms 347ms 10.7s 0 transport_latency_assumed price_change h 84,673,258 2,835,912 17ms 23ms 99ms 34.9s 0 transport_latency_assumed tick_size_change c 2,428 2,406 5ms 7ms 18ms 67ms 0 transport_latency_assumed tick_size_change e 2,428 2 39ms 42ms 77ms 127ms 0 transport_latency_assumed tick_size_change f 2,428 not meas. 47ms 51ms 108ms 138ms 0 transport_latency_assumed tick_size_change g 2,428 not meas. 79ms 97ms 201ms 251ms 0 transport_latency_assumed tick_size_change h 2,428 20 17ms 21ms 41ms 99ms 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/08/2026-09-08T08.parquet sha256sum 2026-09-08T08.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.