Hour audit: 2026-09-25T11
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-25T11 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-25T11:00:00.000115363+00:00 · last event 2026-09-25T11:59:59.999678490+00:00
VOLUME 120,253,213 rows · 1,256,263,953 bytes (1.17 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured i: 120,208,041 · k: 120,199,813 · h: 120,197,777 · g: 120,052,764 · c: 30,409,166 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 3,005,075 (2.50%) · k: 83,204,994 (69.19%) · h: 6,214,091 (5.17%) · g: 33,560 (0.03%) · c: 27,795,493 (23.11%) (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 120,253,213 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 f45be2597d7affda5dceef4f13c96a681f89d4819ecae163345a5b377a58779c
the corpus checksum ledger names this file with the same digest
joined 120,255,711 to merged 120,253,213, minus 2,498 (minus 0.0021%)
boundary drops 2,498 · 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-26T14:06:26Z as cghik
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 status feed unobserved for this hour. Our incident register was last checked against the venue's feed at 2026-09-23T20:35Z, before this hour ended, so nothing has looked yet. This is a could-not-look and never an all-clear.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 11,591,187 133,419,351 0-44 d7be91485b954f18b7acbc27ef258089fcd91c031d60eeb899f64558c210be52 book 147,468 15,854,412 45-45 a34bed3a63045c3ff29eb0c1dcf97418747c9275693a550dd350eee9199c2453 last_trade_price 56,428 3,220,566 46-46 41ba7d7cbe8faae09fc02e0936c204bb35d1b5daefb351fdb109660d99ed343e market_resolved 676 106,436 47-47 03354e8d2882158209360cc0796f7a6546743206e2fa2c3a3e0fd090b48545a2 new_market 508 53,615 48-48 fdda8e0868940da732a7040d008cb08a9f9f3396bbbd1088d464de024d750442 price_change 108,454,278 1,102,139,275 49-462 bc69900ef73c8f2064ec8a225a1aa50c75d2d5f08c28c72390803dbd009c2377 tick_size_change 2,668 99,952 463-463 00e26f229733a44cde9529579c659cca614e94e984cc9529d970f7fe9b79d943 EVENT MIX count share price_change 108,454,278 90.19% best_bid_ask 11,591,187 9.64% book 147,468 0.12% last_trade_price 56,428 0.05% tick_size_change 2,668 <0.01% market_resolved 676 <0.01% new_market 508 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,591,453 11,591,187 266 13,720 FULL book 147,470 147,468 2 17,162 FULL last_trade_price 56,430 56,428 2 1,982 FULL market_resolved 676 676 0 443 FULL new_market 508 508 0 272 FULL price_change 108,456,506 108,454,278 2,228 12,560 FULL tick_size_change 2,668 2,668 0 416 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 3,013,917 2,762,214 5ms 13ms 107ms 5.0s 0 transport_latency_assumed best_bid_ask g 11,587,901 903 79ms 99ms 293ms 21.8s 0 transport_latency_assumed best_bid_ask h 11,590,532 531,653 18ms 29ms 97ms 20.9s 0 transport_latency_assumed best_bid_ask i 11,590,373 247,285 20ms 27ms 97ms 5.0s 0 transport_latency_assumed best_bid_ask k 11,590,725 8,049,132 12ms 19ms 98ms 7.6s 0 transport_latency_assumed book c 31,587 28,757 7ms 31ms 36.6min 54.0d 0 book_staleness book g 130,414 17,574 92ms 3.5min 9.9d 100.0d 0 book_staleness book h 115,577 8,889 23ms 71ms 28.0min 100.0d 0 book_staleness book i 122,999 16,739 23ms 223ms 3.6d 100.1d 0 book_staleness book k 118,378 75,509 16ms 61ms 17.3h 100.0d 0 book_staleness last_trade_price c 15,266 13,806 6ms 18ms 176ms 1.0s 0 transport_latency_assumed last_trade_price g 55,726 26 89ms 604ms 16.8s 21.8s 0 transport_latency_assumed last_trade_price h 56,331 3,522 20ms 53ms 315ms 20.9s 0 transport_latency_assumed last_trade_price i 56,304 2,017 22ms 62ms 354ms 4.0s 0 transport_latency_assumed last_trade_price k 56,351 37,057 14ms 33ms 197ms 1.5s 0 transport_latency_assumed market_resolved c 205 186 5ms 16ms 58.3s 58.3s 0 transport_latency_assumed market_resolved g 648 not meas. 83ms 41.2s 49.5s 50.4s 0 transport_latency_assumed market_resolved h 648 21 20ms 32.4s 57.7s 57.7s 0 transport_latency_assumed market_resolved i 648 101 21ms 27.8s 51.7s 56.3s 0 transport_latency_assumed market_resolved k 648 368 14ms 39.9s 47.7s 48.7s 0 transport_latency_assumed new_market c 69 47 28ms 264ms 1.3min 1.4min 0 transport_latency_assumed new_market g 341 59 232ms 14.3s 23.3s 1.6min 0 transport_latency_assumed new_market h 341 128 90ms 15.1s 21.3s 1.7min 0 transport_latency_assumed new_market i 341 100 84ms 11.2s 14.1s 18.2s 0 transport_latency_assumed new_market k 341 174 61ms 508ms 18.6s 1.6min 0 transport_latency_assumed price_change c 27,347,118 24,989,530 5ms 15ms 132ms 5.0s 0 transport_latency_assumed price_change g 108,275,066 14,998 79ms 118ms 2.1s 21.8s 0 transport_latency_assumed price_change h 108,431,680 5,669,764 19ms 33ms 152ms 21.0s 0 transport_latency_assumed price_change i 108,434,708 2,738,776 20ms 31ms 175ms 5.0s 0 transport_latency_assumed price_change k 108,430,702 75,041,210 13ms 21ms 134ms 7.6s 0 transport_latency_assumed tick_size_change c 1,004 953 5ms 9ms 37ms 102ms 0 transport_latency_assumed tick_size_change g 2,668 not meas. 78ms 98ms 308ms 2.3s 0 transport_latency_assumed tick_size_change h 2,668 114 19ms 31ms 114ms 5.1s 0 transport_latency_assumed tick_size_change i 2,668 57 20ms 32ms 115ms 231ms 0 transport_latency_assumed tick_size_change k 2,668 1,544 12ms 20ms 109ms 344ms 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-25/11/2026-09-25T11.parquet sha256sum 2026-09-25T11.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.