Hour audit: 2026-09-22T09
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-22T09 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-22T09:00:00.001477097+00:00 · last event 2026-09-22T09:59:59.999949570+00:00
VOLUME 114,157,354 rows · 1,209,714,171 bytes (1.13 GiB) · 7 products, all holding rows
WITNESSES cefh — 4 machines contributed rows
captured h: 113,353,821 · f: 113,171,200 · e: 113,153,520 · c: 103,668,272 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 14,971,077 (13.11%) · f: 264,470 (0.23%) · e: 843,332 (0.74%) · c: 98,078,475 (85.92%) (rows of the merged file that came from it; these partition it)
4 expected, all 4 contributed
INTEGRITY sha256 9baced72e51bac4fd6d73c1a58f20742c06758eb590201df1980a296a01ff6f5
the corpus checksum ledger names this file with the same digest
joined 114,158,872 to merged 114,157,354, minus 1,518 (minus 0.0013%)
boundary drops 1,518 · 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-22T11:00:03Z as cefh
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,824,190 103,943,402 0-33 9be43b26363ba598c0e6284cea951b587ee900122efa7d7c031ee1485032bbc9 book 871,104 62,152,784 34-37 897cb428f7ebde7d212e0ed1800353aa46e2ad66744265319bcba89aaccd4171 last_trade_price 67,314 3,703,796 38-38 b4543ccf55cca2550257d0d998ada21bf782e0f40fc996dc8ac36a17bdbed4f6 market_resolved 1,035 141,424 39-39 9b4d883004c82f2bb4717ea6cf7863a2de7aa0a0cf0ad56b9d28afc76f682e0a new_market 777 77,726 40-40 a3309e8a0882dcec6b3d610d8babc110cdd0dd8f348b50d0e6f77dc9619f1a3a price_change 104,389,294 1,038,260,546 41-439 c313f6a0b49b87c1285a00b7b60c95cfede0d77ba99e8f20cf015716cbaef4ec tick_size_change 3,640 134,091 440-440 415120beec7be0c24ef4ee0bda2b3c03c97036793f29f628be9703c2952c14f2 EVENT MIX count share price_change 104,389,294 91.44% best_bid_ask 8,824,190 7.73% book 871,104 0.76% last_trade_price 67,314 0.06% tick_size_change 3,640 <0.01% market_resolved 1,035 <0.01% new_market 777 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,824,319 8,824,190 129 856 FULL book 871,156 871,104 52 174,346 FULL last_trade_price 67,339 67,314 25 161 FULL market_resolved 1,035 1,035 0 7 FULL new_market 777 777 0 0 FULL price_change 104,390,606 104,389,294 1,312 283 FULL tick_size_change 3,640 3,640 0 67 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 7,936,607 7,522,372 5ms 14ms 105ms 6.1s 0 transport_latency_assumed best_bid_ask e 8,816,652 65,912 41ms 55ms 262ms 13.7s 0 transport_latency_assumed best_bid_ask f 8,817,216 17,636 48ms 65ms 246ms 16.4s 0 transport_latency_assumed best_bid_ask h 8,820,796 1,218,270 18ms 33ms 125ms 45.2s 0 transport_latency_assumed book c 841,438 824,586 8.0min 2.8d 41.6d 115.5d 0 book_staleness book e 146,156 10,071 46ms 4.4s 2.8d 97.0d 0 book_staleness book f 145,367 8,518 54ms 7.4s 3.6d 96.9d 0 book_staleness book h 150,966 27,929 23ms 6.8s 3.7d 97.0d 0 book_staleness last_trade_price c 61,686 57,897 6ms 23ms 179ms 1.8s 0 transport_latency_assumed last_trade_price e 66,203 375 45ms 1.1s 5.7s 13.7s 0 transport_latency_assumed last_trade_price f 65,728 231 53ms 1.0s 9.9s 16.3s 0 transport_latency_assumed last_trade_price h 66,838 8,811 20ms 65ms 449ms 11.7s 0 transport_latency_assumed market_resolved c 904 815 6ms 4.6min 5.5min 5.7min 0 transport_latency_assumed market_resolved e 865 92 42ms 16.7s 56.9s 56.9s 0 transport_latency_assumed market_resolved f 865 13 49ms 16.8s 57.4s 57.4s 0 transport_latency_assumed market_resolved h 865 115 19ms 18.2s 59.2s 59.3s 0 transport_latency_assumed new_market c 508 345 59ms 21.5s 27.4s 1.6min 0 transport_latency_assumed new_market e 508 126 164ms 21.2s 24.4s 32.5s 0 transport_latency_assumed new_market f 508 109 172ms 17.1s 26.2s 1.4min 0 transport_latency_assumed new_market h 508 197 119ms 12.9s 25.5s 1.8min 0 transport_latency_assumed price_change c 94,823,757 89,669,315 5ms 16ms 118ms 9.4s 0 transport_latency_assumed price_change e 104,119,496 766,726 41ms 72ms 1.4s 13.8s 0 transport_latency_assumed price_change f 104,137,876 237,954 48ms 81ms 1.2s 16.4s 0 transport_latency_assumed price_change h 104,310,208 13,715,299 18ms 38ms 180ms 46.0s 0 transport_latency_assumed tick_size_change c 3,372 3,145 5ms 14ms 237ms 497ms 0 transport_latency_assumed tick_size_change e 3,640 30 41ms 89ms 145ms 266ms 0 transport_latency_assumed tick_size_change f 3,640 9 48ms 54ms 129ms 220ms 0 transport_latency_assumed tick_size_change h 3,640 456 18ms 34ms 83ms 226ms 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-22/09/2026-09-22T09.parquet sha256sum 2026-09-22T09.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.