Hour audit: 2026-09-22T07
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-22T07 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-22T07:00:00.000113161+00:00 · last event 2026-09-22T07:59:59.999983816+00:00
VOLUME 103,930,007 rows · 1,066,102,244 bytes (1016.71 MiB) · 7 products, all holding rows
WITNESSES cefh — 4 machines contributed rows
captured c: 103,585,872 · e: 103,581,109 · h: 103,491,986 · f: 103,370,273 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 99,853,163 (96.08%) · e: 410,773 (0.40%) · h: 3,404,178 (3.28%) · f: 261,893 (0.25%) (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 103,930,007 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 675472483383cca8a305b81f315abb0e34bb80dd85fe58cbf2f6185e4ea2dadd
the corpus checksum ledger names this file with the same digest
joined 103,931,059 to merged 103,930,007, minus 1,052 (minus 0.0010%)
boundary drops 1,052 · 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-22T08:55:18Z 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,808,360 100,928,277 0-33 daf3aba7c673d665afa3ed5ddb6b0ea19c963e53fd18858738224727fee671a9 book 468,154 43,115,283 34-35 00b6da9b587ddb7b62d8a4868d2df8d83af7758cd701d578511c375ac759cc04 last_trade_price 53,606 3,030,413 36-36 69d44dccb81cdf1c8a2567880f2086c505ffa94e95e1f98ed866deb0d720fdce market_resolved 744 123,108 37-37 9f804cf44103ec19528bfb04a6dc1b040ab840008a4e7873d47d733ea5304c0c new_market 899 97,740 38-38 6fd5a3c1af32cd56a6c050eb43a293a6e97cdad3cbc763564f3def68e46fd8b9 price_change 94,595,060 917,509,685 39-399 babe6af36f8bfd630a8678b8a824cf004ffe3d5f1372331227046b7e77d6031b tick_size_change 3,184 115,403 400-400 451a4e6758328578169f10c7d07ae58ad7a509f51e1f5091a7aa2f1a677f86d3 EVENT MIX count share price_change 94,595,060 91.02% best_bid_ask 8,808,360 8.48% book 468,154 0.45% last_trade_price 53,606 0.05% tick_size_change 3,184 <0.01% new_market 899 <0.01% market_resolved 744 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,808,424 8,808,360 64 89 FULL book 468,456 468,154 302 127,925 FULL last_trade_price 53,606 53,606 0 2 FULL market_resolved 744 744 0 0 FULL new_market 899 899 0 0 FULL price_change 94,595,746 94,595,060 686 49 FULL tick_size_change 3,184 3,184 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,807,190 8,519,726 5ms 10ms 81ms 4.9s 0 transport_latency_assumed best_bid_ask e 8,806,216 21,890 43ms 50ms 168ms 18.7s 0 transport_latency_assumed best_bid_ask f 8,806,007 9,859 47ms 58ms 179ms 4.8s 0 transport_latency_assumed best_bid_ask h 8,806,436 256,885 19ms 28ms 115ms 8.5s 0 transport_latency_assumed book c 215,249 193,249 357ms 11.1h 30.7d 115.4d 0 book_staleness book e 232,834 106,029 7.1s 11.4h 30.7d 115.4d 0 book_staleness book f 241,584 114,664 12.1s 11.7h 30.7d 115.4d 0 book_staleness book h 171,356 54,212 36ms 1.4h 28.8d 115.4d 0 book_staleness last_trade_price c 53,362 50,765 6ms 19ms 180ms 2.9s 0 transport_latency_assumed last_trade_price e 53,477 317 44ms 159ms 825ms 4.1s 0 transport_latency_assumed last_trade_price f 53,395 205 49ms 155ms 1.3s 5.2s 0 transport_latency_assumed last_trade_price h 53,241 2,319 20ms 53ms 293ms 8.1s 0 transport_latency_assumed market_resolved c 744 674 5ms 33ms 59.0s 59.7s 0 transport_latency_assumed market_resolved e 744 46 43ms 194ms 50.4s 51.3s 0 transport_latency_assumed market_resolved f 744 not meas. 48ms 216ms 52.4s 53.0s 0 transport_latency_assumed market_resolved h 744 24 20ms 97ms 50.3s 51.9s 0 transport_latency_assumed new_market c 643 448 76ms 14.2s 1.5min 1.7min 0 transport_latency_assumed new_market e 643 110 162ms 17.0s 1.3min 1.6min 0 transport_latency_assumed new_market f 643 118 178ms 20.3s 1.3min 1.5min 0 transport_latency_assumed new_market h 643 223 117ms 17.0s 1.4min 1.6min 0 transport_latency_assumed price_change c 94,505,500 91,085,222 5ms 12ms 98ms 5.9s 0 transport_latency_assumed price_change e 94,484,011 282,377 43ms 61ms 391ms 19.1s 0 transport_latency_assumed price_change f 94,264,716 137,039 48ms 68ms 352ms 9.4s 0 transport_latency_assumed price_change h 94,456,382 3,090,422 19ms 33ms 180ms 8.5s 0 transport_latency_assumed tick_size_change c 3,184 3,079 5ms 10ms 60ms 422ms 0 transport_latency_assumed tick_size_change e 3,184 4 42ms 53ms 119ms 264ms 0 transport_latency_assumed tick_size_change f 3,184 8 48ms 58ms 141ms 254ms 0 transport_latency_assumed tick_size_change h 3,184 93 20ms 30ms 109ms 3.8s 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/07/2026-09-22T07.parquet sha256sum 2026-09-22T07.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.