Hour audit: 2026-09-05T13
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-05T13 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-05T13:00:00.057529468+00:00 · last event 2026-09-05T13:59:59.999980129+00:00
VOLUME 112,524,936 rows · 1,181,161,963 bytes (1.10 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 111,713,713 · h: 111,681,849 · f: 111,607,490 · g: 111,363,620 · c: 102,106,447 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 50,789 (0.05%) · h: 11,501 (0.01%) · f: 328,416 (0.29%) · g: 111,361,373 (98.97%) · c: 772,857 (0.69%) (rows of the merged file that came from it; these partition it)
6 product-machine pairs publish no supplied count; the figures above still sum to the file's 112,524,936 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 2b30bcac09bba55931ed6f80adba2908a43e26bbd396a7eab8fd4d0e30762d3d
the corpus checksum ledger names this file with the same digest
joined 112,527,221 to merged 112,524,936, minus 2,285 (minus 0.0020%)
boundary drops 2,285 · 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-05T19:54:37Z 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,867,731 121,794,495 0-41 4d1b239b593eef4875fa63784dd03ab6e917901e6c9fc5553c97a16cd10b57e4 book 925,559 68,821,128 42-45 ee3ea517acc37af478baed371b7f7110219bf6288109a29f4f114351921b2689 last_trade_price 66,913 3,877,773 46-46 12430601967cc46ad03662ba66d8112faed96bf03c276443e741ac727e84dd4f market_resolved 1,343 212,769 47-47 11e74da6676f0dc367c6706cb95cfd8d76cefa67690f9aaf1e559978c2bd93e2 new_market 2,078 216,061 48-48 d1d7a735134b2b14a9febd241970d22431f11185096b9ea7baf8f90ca230ef28 price_change 100,652,860 984,655,534 49-432 58a15fb01f4eff2dd57a24fef6ba512aa6d4e428805e6017e8a0ddfd707dbb8d tick_size_change 8,452 303,546 433-433 8c5b97ef28c0cfc1ff7469de23298d9aaba66aee7656b97b4cd3c32be6ed2006 EVENT MIX count share price_change 100,652,860 89.45% best_bid_ask 10,867,731 9.66% book 925,559 0.82% last_trade_price 66,913 0.06% tick_size_change 8,452 <0.01% new_market 2,078 <0.01% market_resolved 1,343 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,867,955 10,867,731 224 1,210 FULL book 925,589 925,559 30 187,152 FULL last_trade_price 66,914 66,913 1 197 FULL market_resolved 1,343 1,343 0 74 FULL new_market 2,078 2,078 0 143 FULL price_change 100,654,890 100,652,860 2,030 619 FULL tick_size_change 8,452 8,452 0 98 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,908,332 601 5ms 10ms 110ms 8.5s 0 transport_latency_assumed best_bid_ask e 10,865,726 3,799 38ms 44ms 171ms 4.5s 0 transport_latency_assumed best_bid_ask f 10,858,388 20,960 47ms 63ms 353ms 10.8s 0 transport_latency_assumed best_bid_ask g 10,841,559 10,841,335 82ms 125ms 706ms 26.4s 0 transport_latency_assumed best_bid_ask h 10,865,593 1,036 18ms 24ms 192ms 10.7s 0 transport_latency_assumed book c 898,359 766,928 2.0min 12.2h 33.7d 98.6d 0 book_staleness book e 138,809 1,041 40ms 103ms 2.2s 5.3s 0 book_staleness book f 141,509 5,924 49ms 251ms 7.2min 1.0d 0 book_staleness book g 150,065 150,059 86ms 5.0s 15.9h 35.9d 0 book_staleness book h 139,625 1,607 21ms 50ms 3.4s 34.1d 0 book_staleness last_trade_price c 60,964 6 10ms 39ms 242ms 5.0s 0 transport_latency_assumed last_trade_price e 66,886 321 44ms 87ms 605ms 5.0s 0 transport_latency_assumed last_trade_price f 66,233 1,631 53ms 146ms 5.3s 10.9s 0 transport_latency_assumed last_trade_price g 64,954 64,953 91ms 213ms 6.5s 26.3s 0 transport_latency_assumed last_trade_price h 66,719 2 22ms 57ms 368ms 8.0s 0 transport_latency_assumed market_resolved c 1,259 17 5ms 11ms 2.7min 4.8min 0 transport_latency_assumed market_resolved e 1,325 not meas. 39ms 190ms 508ms 833ms 0 transport_latency_assumed market_resolved f 1,325 9 48ms 134ms 1.6s 10.1s 0 transport_latency_assumed market_resolved g 1,317 1,317 83ms 253ms 2.3s 1.0min 0 transport_latency_assumed market_resolved h 1,325 not meas. 19ms 83ms 302ms 58.3s 0 transport_latency_assumed new_market c 1,230 77 80ms 20.9s 1.4min 2.1min 0 transport_latency_assumed new_market e 1,373 126 157ms 24.7s 1.4min 2.1min 0 transport_latency_assumed new_market f 1,373 350 162ms 20.9s 1.4min 2.1min 0 transport_latency_assumed new_market g 1,373 1,373 277ms 23.0s 1.4min 2.4min 0 transport_latency_assumed new_market h 1,373 152 140ms 30.8s 1.3min 2.1min 0 transport_latency_assumed price_change c 91,228,243 5,228 5ms 11ms 130ms 8.5s 0 transport_latency_assumed price_change e 100,631,142 45,502 38ms 47ms 211ms 4.5s 0 transport_latency_assumed price_change f 100,530,210 299,542 47ms 77ms 502ms 10.9s 0 transport_latency_assumed price_change g 100,295,900 100,293,884 82ms 158ms 971ms 26.4s 0 transport_latency_assumed price_change h 100,598,762 8,704 18ms 27ms 209ms 11.0s 0 transport_latency_assumed tick_size_change c 8,060 not meas. 5ms 8ms 35ms 120ms 0 transport_latency_assumed tick_size_change e 8,452 not meas. 38ms 42ms 90ms 252ms 0 transport_latency_assumed tick_size_change f 8,452 not meas. 48ms 106ms 266ms 804ms 0 transport_latency_assumed tick_size_change g 8,452 8,452 84ms 195ms 365ms 10.4s 0 transport_latency_assumed tick_size_change h 8,452 not meas. 18ms 22ms 62ms 1.9s 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/13/2026-09-05T13.parquet sha256sum 2026-09-05T13.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.