Hour audit: 2026-09-05T17
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-05T17 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-05T17:00:00.053701756+00:00 · last event 2026-09-05T17:59:59.999998229+00:00
VOLUME 132,243,342 rows · 1,435,636,581 bytes (1.34 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 129,554,744 · h: 129,525,612 · g: 129,060,929 · f: 123,970,866 · c: 94,960,916 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 64,339 (0.05%) · h: 8,567 (0.01%) · g: 129,038,914 (97.58%) · f: 869,739 (0.66%) · c: 2,261,783 (1.71%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 132,243,342 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 8668f81ba8577a254caf8120a2a9240964b8eea1c546363bdd00563dda1e0dad
the corpus checksum ledger names this file with the same digest
joined 132,266,144 to merged 132,243,342, minus 22,802 (minus 0.0172%)
boundary drops 22,802 · 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-05T22:43:20Z 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 11,886,197 138,068,949 0-45 e53e7642078f6156273e7cb705031085c97505c0b1ff083641d7db29ae6a6d3f book 2,812,547 112,776,706 46-56 237a9e740109a7f21b84f87957f67abce6bbdc1ba54dd2c3f3db2465af0fe77f last_trade_price 76,626 4,313,224 57-57 8e7ecc911e1e60ad37bc091a203275708bf3c6e9d13d131fbde22d3636e3c1e3 market_resolved 4,917 534,266 58-58 cfeb171917dfb4a8eac9badbaabe70b67f406a8d5881910cb1735347307a86b1 new_market 2,455 199,956 59-59 77a7bc239bbfa6f85eb6ad246be156efaaae13a4a95e4e5a477a4423126ff341 price_change 117,443,704 1,177,618,279 60-508 568cd53165b5af5421673bbd32dc7aff4e76834db227737249927f70da1b5b5f tick_size_change 16,896 620,800 509-509 19372a5594c8e7bb9b54f7e8fddfd311205196fdc4ee260139df2b75eb4d03ee EVENT MIX count share price_change 117,443,704 88.81% best_bid_ask 11,886,197 8.99% book 2,812,547 2.13% last_trade_price 76,626 0.06% tick_size_change 16,896 0.01% market_resolved 4,917 <0.01% new_market 2,455 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,888,023 11,886,197 1,826 5,132 FULL book 2,812,891 2,812,547 344 185,045 FULL last_trade_price 76,702 76,626 76 846 FULL market_resolved 4,917 4,917 0 348 FULL new_market 2,455 2,455 0 11 FULL price_change 117,464,248 117,443,704 20,544 2,389 FULL tick_size_change 16,908 16,896 12 1,750 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,331,103 404 4ms 11ms 137ms 5.6s 0 transport_latency_assumed best_bid_ask e 11,884,072 3,592 41ms 52ms 196ms 18.7s 0 transport_latency_assumed best_bid_ask f 11,316,279 23,111 47ms 64ms 277ms 13.8s 0 transport_latency_assumed best_bid_ask g 11,859,841 11,858,065 84ms 145ms 892ms 21.1s 0 transport_latency_assumed best_bid_ask h 11,884,576 1,025 18ms 37ms 206ms 47.8s 0 transport_latency_assumed book c 2,658,578 2,254,992 3.7min 14.4h 34.2d 98.8d 0 book_staleness book e 160,027 1,264 43ms 126ms 2.4s 34.2d 0 book_staleness book f 530,607 380,995 58.1s 7.1h 28.3d 98.8d 0 book_staleness book g 174,245 174,097 88ms 11.5s 11.3h 80.3d 0 book_staleness book h 160,065 1,199 22ms 71ms 2.7s 2.5d 0 book_staleness last_trade_price c 54,549 5 10ms 42ms 260ms 5.0s 0 transport_latency_assumed last_trade_price e 76,565 298 47ms 115ms 1.2s 5.2s 0 transport_latency_assumed last_trade_price f 71,788 2,396 54ms 156ms 2.4s 13.8s 0 transport_latency_assumed last_trade_price g 73,991 73,918 91ms 350ms 7.3s 20.7s 0 transport_latency_assumed last_trade_price h 76,440 9 24ms 69ms 461ms 44.6s 0 transport_latency_assumed market_resolved c 3,972 1,526 6ms 10.1min 17.1min 18.0min 0 transport_latency_assumed market_resolved e 3,232 not meas. 42ms 122ms 766ms 1.0min 0 transport_latency_assumed market_resolved f 3,263 146 49ms 190ms 5.0min 5.7min 0 transport_latency_assumed market_resolved g 3,231 3,231 86ms 310ms 32.9s 1.5min 0 transport_latency_assumed market_resolved h 3,232 14 19ms 66ms 29.2s 1.0min 0 transport_latency_assumed new_market c 1,991 726 255ms 9.7min 17.1min 37.0min 0 transport_latency_assumed new_market e 1,246 195 148ms 12.7s 35.2s 20.5min 0 transport_latency_assumed new_market f 1,255 230 159ms 15.4s 1.6min 1.6h 0 transport_latency_assumed new_market g 1,246 1,246 271ms 11.2s 45.9s 25.9min 0 transport_latency_assumed new_market h 1,246 58 120ms 11.8s 40.7s 25.9min 0 transport_latency_assumed price_change c 83,900,723 4,130 4ms 12ms 148ms 6.1s 0 transport_latency_assumed price_change e 117,412,706 58,990 41ms 58ms 245ms 21.2s 0 transport_latency_assumed price_change f 112,032,890 462,853 47ms 71ms 344ms 13.9s 0 transport_latency_assumed price_change g 116,931,475 116,911,469 84ms 175ms 1.3s 21.2s 0 transport_latency_assumed price_change h 117,383,157 6,262 18ms 39ms 228ms 47.8s 0 transport_latency_assumed tick_size_change c 10,000 not meas. 4ms 8ms 57ms 246ms 0 transport_latency_assumed tick_size_change e 16,896 not meas. 41ms 48ms 151ms 623ms 0 transport_latency_assumed tick_size_change f 14,784 8 50ms 188ms 312ms 408ms 0 transport_latency_assumed tick_size_change g 16,900 16,888 108ms 400ms 763ms 10.3s 0 transport_latency_assumed tick_size_change h 16,896 not meas. 18ms 36ms 84ms 2.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/17/2026-09-05T17.parquet sha256sum 2026-09-05T17.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.