Hour audit: 2026-09-16T04
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-16T04 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-16T04:00:00.003172646+00:00 · last event 2026-09-16T04:59:59.999961742+00:00
VOLUME 108,108,509 rows · 1,110,658,453 bytes (1.03 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 107,697,669 · h: 107,642,962 · f: 107,600,510 · e: 107,567,269 · g: 107,394,717 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 102,886,801 (95.17%) · h: 3,940,298 (3.64%) · f: 374,969 (0.35%) · e: 834,321 (0.77%) · g: 72,120 (0.07%) (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 108,108,509 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 e414b05f43f7b55087cc09f23fa7ff016f68370432279860164a17fabd72a62e
the corpus checksum ledger names this file with the same digest
joined 108,111,373 to merged 108,108,509, minus 2,864 (minus 0.0026%)
boundary drops 2,864 · 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-16T05:57:59Z 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,970,446 134,215,008 0-45 461e11ea9b08ae9d58aefb915e3908d55a3136700622f541d15eee5a0abbdc34 book 613,656 53,078,019 46-48 a7f00376a6066668bbde1be0ae3e13167fcbbe2d4e69da839af34e35dcc381cd last_trade_price 41,191 2,367,400 49-49 a7c8dd87bf93ac3d54504101c436c9b58995641fdf6b730503029fde9119a71a market_resolved 1,043 170,741 50-50 6708b6cd39c65226b3519c39f84c71aac9d5c3e1677c1fa242cdc7cd0c615fd6 new_market 3,605 359,294 51-51 4802fcd1913549248655ad710280a0313249453b74a59403259d5bac998764d8 price_change 95,475,204 919,112,087 52-416 6a1b26942753edb0f7ae3e9a15691117eb8a8818c621e0d8944310e5e1551162 tick_size_change 3,364 123,477 417-417 2d34b76a1bf6f4296a13cdff1e65810b344b5f226f73f5f4ee2ff8ee8a56ef8c EVENT MIX count share price_change 95,475,204 88.31% best_bid_ask 11,970,446 11.07% book 613,656 0.57% last_trade_price 41,191 0.04% new_market 3,605 <0.01% tick_size_change 3,364 <0.01% market_resolved 1,043 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,970,746 11,970,446 300 254 FULL book 614,256 613,656 600 147,747 FULL last_trade_price 41,191 41,191 0 0 FULL market_resolved 1,043 1,043 0 0 FULL new_market 3,605 3,605 0 0 FULL price_change 95,477,168 95,475,204 1,964 117 FULL tick_size_change 3,364 3,364 0 1 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,968,633 11,460,486 4ms 9ms 188ms 6.0s 0 transport_latency_assumed best_bid_ask e 11,964,713 76,519 38ms 47ms 279ms 59.8s 0 transport_latency_assumed best_bid_ask f 11,966,437 29,692 47ms 60ms 296ms 35.1s 0 transport_latency_assumed best_bid_ask g 11,962,645 3,331 80ms 136ms 578ms 17.7s 0 transport_latency_assumed best_bid_ask h 11,966,626 400,418 17ms 30ms 387ms 21.6s 0 transport_latency_assumed book c 233,835 201,897 33.5s 2.3h 24.6d 109.3d 0 book_staleness book e 238,865 123,094 37.0s 1.7h 24.7d 109.3d 0 book_staleness book f 227,367 110,756 29.2s 1.7h 24.6d 109.3d 0 book_staleness book g 151,850 45,726 328ms 23.0min 24.6d 109.3d 0 book_staleness book h 243,548 132,183 40.6s 2.5h 24.7d 109.3d 0 book_staleness last_trade_price c 41,045 38,640 10ms 55ms 313ms 5.0s 0 transport_latency_assumed last_trade_price e 40,821 490 46ms 166ms 1.9s 20.4s 0 transport_latency_assumed last_trade_price f 40,918 131 57ms 183ms 1.4s 5.2s 0 transport_latency_assumed last_trade_price g 40,704 29 97ms 354ms 6.4s 17.7s 0 transport_latency_assumed last_trade_price h 40,878 1,901 24ms 90ms 518ms 9.2s 0 transport_latency_assumed market_resolved c 1,040 990 5ms 16ms 24.5s 48.4s 0 transport_latency_assumed market_resolved e 1,040 7 43ms 184ms 808ms 58.3s 0 transport_latency_assumed market_resolved f 1,040 2 60ms 196ms 650ms 58.3s 0 transport_latency_assumed market_resolved g 1,040 1 103ms 356ms 31.5s 59.8s 0 transport_latency_assumed market_resolved h 1,040 43 27ms 72ms 1.6s 56.1s 0 transport_latency_assumed new_market c 2,320 1,320 110ms 21.5s 1.3min 2.9min 0 transport_latency_assumed new_market e 2,320 448 204ms 22.9s 1.2min 1.7min 0 transport_latency_assumed new_market f 2,320 417 186ms 22.6s 1.2min 1.7min 0 transport_latency_assumed new_market g 2,320 355 348ms 24.0s 1.3min 1.7min 0 transport_latency_assumed new_market h 2,320 1,065 153ms 22.4s 1.3min 1.7min 0 transport_latency_assumed price_change c 95,447,432 91,180,314 5ms 11ms 195ms 6.0s 0 transport_latency_assumed price_change e 95,316,146 633,734 38ms 58ms 435ms 1.0min 0 transport_latency_assumed price_change f 95,359,064 233,966 47ms 70ms 435ms 35.2s 0 transport_latency_assumed price_change g 95,232,798 22,678 82ms 160ms 933ms 17.8s 0 transport_latency_assumed price_change h 95,385,186 3,404,512 17ms 36ms 393ms 21.6s 0 transport_latency_assumed tick_size_change c 3,364 3,154 5ms 17ms 239ms 494ms 0 transport_latency_assumed tick_size_change e 3,364 29 38ms 57ms 342ms 608ms 0 transport_latency_assumed tick_size_change f 3,364 5 47ms 60ms 241ms 660ms 0 transport_latency_assumed tick_size_change g 3,360 not meas. 83ms 190ms 560ms 1.7s 0 transport_latency_assumed tick_size_change h 3,364 176 18ms 29ms 282ms 2.7s 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-16/04/2026-09-16T04.parquet sha256sum 2026-09-16T04.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.