Hour audit: 2026-09-05T18
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-05T18 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-05T18:00:00.000505149+00:00 · last event 2026-09-05T18:59:59.999981994+00:00
VOLUME 123,291,027 rows · 1,327,527,918 bytes (1.24 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 121,458,184 · h: 121,405,000 · g: 120,797,113 · f: 116,847,454 · c: 101,926,360 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 48,276 (0.04%) · h: 6,918 (0.01%) · g: 120,794,046 (97.97%) · f: 1,028,452 (0.83%) · c: 1,413,335 (1.15%) (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 123,291,027 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 f32c5b1b411d495d4dc2daad1178a80a7bba22fede1da19b26ee4cf11331b9c2
the corpus checksum ledger names this file with the same digest
joined 123,298,452 to merged 123,291,027, minus 7,425 (minus 0.0060%)
boundary drops 7,425 · 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-05T23:12:44Z 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,004,851 116,549,619 0-38 405e567d89ef0cd894ca37539a715b42a3ec49090135263d268235420522e53a book 1,951,785 93,336,494 39-46 fdccc89be74c99ec97f6345d4f1191cdc8d92bd1f41889bbcd6745f75b192cd0 last_trade_price 73,794 4,136,760 47-47 c65739a0703491bd3fffbfd66aa2a0c934b74d5017a0639963ae299c62ed6c84 market_resolved 4,994 612,178 48-48 ed8d336aee9bd4fdc80d3ac80dc45794b98e1a8dab846c5264ccf50a6549a9fb new_market 2,617 239,040 49-49 87d36b7553cfa462650485cdbbfbb9f99be058078df17a974f096ba1f4e97e42 price_change 111,244,358 1,110,943,615 50-474 dac8fea6ac257ec3476f1c90841fdbc59a57eaea734cc13ca7546fa3dd85ef61 tick_size_change 8,628 305,884 475-475 00fb8f43968aa7a428d1b7c5364e76a360e6a8840e8806c5fd2fd15f029503ad EVENT MIX count share price_change 111,244,358 90.23% best_bid_ask 10,004,851 8.11% book 1,951,785 1.58% last_trade_price 73,794 0.06% tick_size_change 8,628 <0.01% market_resolved 4,994 <0.01% new_market 2,617 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,005,057 10,004,851 206 4,273 FULL book 1,955,717 1,951,785 3,932 183,294 FULL last_trade_price 73,795 73,794 1 480 FULL market_resolved 4,994 4,994 0 310 FULL new_market 2,619 2,617 2 7 FULL price_change 111,247,642 111,244,358 3,284 2,136 FULL tick_size_change 8,628 8,628 0 471 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,242,624 449 4ms 11ms 172ms 8.1s 0 transport_latency_assumed best_bid_ask e 10,003,176 3,311 40ms 52ms 268ms 3.0s 0 transport_latency_assumed best_bid_ask f 9,580,310 34,845 47ms 66ms 306ms 3.9s 0 transport_latency_assumed best_bid_ask g 9,965,684 9,965,518 83ms 174ms 1.6s 39.0s 0 transport_latency_assumed best_bid_ask h 10,001,813 728 18ms 50ms 352ms 46.8s 0 transport_latency_assumed book c 1,723,002 1,407,283 3.0min 14.0h 34.3d 98.8d 0 book_staleness book e 153,978 970 42ms 144ms 2.7s 80.2d 0 book_staleness book f 520,342 372,296 59.8s 6.8h 28.4d 98.8d 0 book_staleness book g 169,806 169,666 86ms 29.4s 13.8h 38.1d 0 book_staleness book h 154,966 1,570 23ms 84ms 14.2s 36.4d 0 book_staleness last_trade_price c 60,207 4 9ms 41ms 326ms 5.0s 0 transport_latency_assumed last_trade_price e 73,748 187 46ms 122ms 1.0s 5.0s 0 transport_latency_assumed last_trade_price f 70,791 2,850 54ms 145ms 904ms 5.0s 0 transport_latency_assumed last_trade_price g 70,751 70,750 90ms 347ms 8.4s 29.9s 0 transport_latency_assumed last_trade_price h 73,516 3 24ms 79ms 676ms 46.4s 0 transport_latency_assumed market_resolved c 4,310 1,338 5ms 6.5min 12.5min 13.8min 0 transport_latency_assumed market_resolved e 3,577 not meas. 43ms 151ms 456ms 751ms 0 transport_latency_assumed market_resolved f 3,625 79 51ms 195ms 5.4min 8.6min 0 transport_latency_assumed market_resolved g 3,577 3,577 90ms 287ms 923ms 1.2min 0 transport_latency_assumed market_resolved h 3,577 not meas. 30ms 75ms 267ms 6.3s 0 transport_latency_assumed new_market c 1,681 343 209ms 1.6min 19.4min 55.5min 0 transport_latency_assumed new_market e 1,517 352 215ms 15.2s 35.8s 12.5min 0 transport_latency_assumed new_market f 1,522 312 215ms 13.6s 36.8s 55.6min 0 transport_latency_assumed new_market g 1,517 1,517 370ms 16.6s 34.4s 44.5s 0 transport_latency_assumed new_market h 1,517 93 174ms 14.0s 33.3s 8.2min 0 transport_latency_assumed price_change c 91,887,428 3,918 4ms 12ms 191ms 12.9s 0 transport_latency_assumed price_change e 111,213,560 43,456 40ms 58ms 319ms 3.0s 0 transport_latency_assumed price_change f 106,662,600 618,070 48ms 71ms 353ms 3.9s 0 transport_latency_assumed price_change g 110,577,150 110,574,390 83ms 190ms 1.9s 39.0s 0 transport_latency_assumed price_change h 111,160,983 4,524 18ms 52ms 362ms 47.3s 0 transport_latency_assumed tick_size_change c 7,108 not meas. 4ms 8ms 178ms 916ms 0 transport_latency_assumed tick_size_change e 8,628 not meas. 39ms 45ms 208ms 622ms 0 transport_latency_assumed tick_size_change f 8,264 not meas. 47ms 56ms 231ms 470ms 0 transport_latency_assumed tick_size_change g 8,628 8,628 85ms 229ms 759ms 17.3s 0 transport_latency_assumed tick_size_change h 8,628 not meas. 18ms 46ms 255ms 7.0s 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/18/2026-09-05T18.parquet sha256sum 2026-09-05T18.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.