Hour audit: 2026-09-18T06
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-18T06 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-18T06:00:00.000003719+00:00 · last event 2026-09-18T06:59:59.999999709+00:00
VOLUME 100,348,070 rows · 1,009,281,102 bytes (962.53 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 100,262,812 · f: 100,241,128 · h: 100,239,216 · g: 100,061,004 · e: 99,451,602 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 94,932,125 (94.60%) · f: 270,763 (0.27%) · h: 4,560,573 (4.54%) · g: 46,961 (0.05%) · e: 537,648 (0.54%) (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 100,348,070 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 6506be441c51289f3257f28d03e3dd5b4b1f29b8ce82c590d2cd30d4b3f9a9b3
the corpus checksum ledger names this file with the same digest
joined 100,349,485 to merged 100,348,070, minus 1,415 (minus 0.0014%)
boundary drops 1,415 · 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-18T07:56:34Z 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 9,175,203 106,560,946 0-35 1228d77599bfea8e92d5beca8e59bf158d0a651cebcfd85be44c725efa08c9e3 book 147,748 14,163,917 36-36 d0471b9541b2c39b9646f697e1497c4836ace36ed741357889b02d3c65b08d46 last_trade_price 52,068 2,972,400 37-37 9598387e2c801252d9ff602453e9f28d43ebb83310bcbb5b010d30f62bdf6b52 market_resolved 501 82,579 38-38 bc07e5f8345bb4eb4812c31a06e2c628f9b917c3a21f82bad8c679407d22204e new_market 3,885 408,757 39-39 bb31fedddac87d96f0f1837c5168fcc27df2708e0dd7dbd48c164c7d96f66f81 price_change 90,966,477 883,863,452 40-387 05e786321851e2d9259df99e0c86a3df6e683abdbfac99cb1518a9d4e67cc444 tick_size_change 2,188 81,870 388-388 c427c76a049a25d62ce9b61fa6c8dca364518e8b86a4fccf996ea81c8a84a491 EVENT MIX count share price_change 90,966,477 90.65% best_bid_ask 9,175,203 9.14% book 147,748 0.15% last_trade_price 52,068 0.05% new_market 3,885 <0.01% tick_size_change 2,188 <0.01% market_resolved 501 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,175,354 9,175,203 151 638 FULL book 147,752 147,748 4 5,308 FULL last_trade_price 52,068 52,068 0 1 FULL market_resolved 501 501 0 15 FULL new_market 3,885 3,885 0 0 FULL price_change 90,967,737 90,966,477 1,260 339 FULL tick_size_change 2,188 2,188 0 4 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,172,142 8,720,868 5ms 12ms 166ms 9.2s 0 transport_latency_assumed best_bid_ask e 9,139,475 46,645 41ms 56ms 387ms 24.6s 0 transport_latency_assumed best_bid_ask f 9,169,638 21,753 47ms 64ms 299ms 13.8s 0 transport_latency_assumed best_bid_ask g 9,167,669 3,393 79ms 111ms 539ms 36.6s 0 transport_latency_assumed best_bid_ask h 9,170,539 382,544 18ms 28ms 346ms 45.2s 0 transport_latency_assumed book c 116,439 106,794 6ms 106ms 25.6min 92.8d 0 book_staleness book e 125,353 19,740 45ms 19.6s 2.6h 2.0d 0 book_staleness book f 115,707 4,303 50ms 728ms 19.6min 111.3d 0 book_staleness book g 115,620 4,555 85ms 1.7s 26.3min 92.8d 0 book_staleness book h 116,325 12,356 21ms 201ms 18.9min 111.3d 0 book_staleness last_trade_price c 51,835 48,514 10ms 53ms 296ms 5.0s 0 transport_latency_assumed last_trade_price e 49,648 315 51ms 329ms 8.7s 24.3s 0 transport_latency_assumed last_trade_price f 51,573 151 58ms 264ms 6.1s 13.8s 0 transport_latency_assumed last_trade_price g 51,106 33 93ms 358ms 14.2s 36.7s 0 transport_latency_assumed last_trade_price h 51,729 3,055 24ms 92ms 490ms 10.6s 0 transport_latency_assumed market_resolved c 489 439 5ms 48ms 53.6s 53.7s 0 transport_latency_assumed market_resolved e 474 8 44ms 583ms 1.2min 1.2min 0 transport_latency_assumed market_resolved f 489 8 58ms 369ms 1.0min 1.0min 0 transport_latency_assumed market_resolved g 489 not meas. 112ms 607ms 1.0min 1.0min 0 transport_latency_assumed market_resolved h 489 46 25ms 128ms 45.6s 45.6s 0 transport_latency_assumed new_market c 2,660 1,504 100ms 35.4s 1.4min 1.8min 0 transport_latency_assumed new_market e 2,660 605 173ms 38.9s 1.5min 2.1min 0 transport_latency_assumed new_market f 2,660 355 211ms 34.7s 1.6min 2.1min 0 transport_latency_assumed new_market g 2,660 218 275ms 32.5s 1.4min 2.1min 0 transport_latency_assumed new_market h 2,660 1,203 138ms 38.4s 1.4min 2.0min 0 transport_latency_assumed price_change c 90,917,059 86,051,967 5ms 15ms 191ms 10.0s 0 transport_latency_assumed price_change e 90,131,820 470,324 42ms 73ms 2.5s 24.7s 0 transport_latency_assumed price_change f 90,898,873 244,188 48ms 78ms 540ms 13.8s 0 transport_latency_assumed price_change g 90,721,272 38,758 80ms 137ms 1.1s 37.2s 0 transport_latency_assumed price_change h 90,895,286 4,161,240 18ms 34ms 390ms 45.2s 0 transport_latency_assumed tick_size_change c 2,188 2,039 5ms 22ms 231ms 304ms 0 transport_latency_assumed tick_size_change e 2,172 11 42ms 112ms 7.9s 12.0s 0 transport_latency_assumed tick_size_change f 2,188 5 47ms 100ms 471ms 663ms 0 transport_latency_assumed tick_size_change g 2,188 4 81ms 193ms 602ms 4.3s 0 transport_latency_assumed tick_size_change h 2,188 129 18ms 40ms 407ms 5.6s 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-18/06/2026-09-18T06.parquet sha256sum 2026-09-18T06.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.