Hour audit: 2026-09-20T09
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-20T09 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-20T09:00:00.000014496+00:00 · last event 2026-09-20T09:59:59.999870536+00:00
VOLUME 104,173,456 rows · 1,066,729,673 bytes (1017.31 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 104,090,313 · h: 104,087,074 · f: 104,059,477 · e: 104,036,147 · g: 103,980,447 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 99,647,467 (95.66%) · h: 3,838,972 (3.69%) · f: 221,776 (0.21%) · e: 416,790 (0.40%) · g: 48,451 (0.05%) (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 104,173,456 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 455c5eabfccdad0c9b5ab7ce2e5333eb1cc5545a775974d89f81d44b7937c2fd
the corpus checksum ledger names this file with the same digest
joined 104,175,654 to merged 104,173,456, minus 2,198 (minus 0.0021%)
boundary drops 2,198 · 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-20T11:35:13Z 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,174,238 126,971,316 0-42 bcb98aeaec4c71094469af99fbf91e83410599cf9a5ad7f4d67e5a705ceaa63e book 164,831 17,751,293 43-43 0c42449ff256717cb69fce0bf94ef42ba3958f09601db770beddd71f4c714682 last_trade_price 54,655 3,192,588 44-44 ead928bc22d5fa5b730fbfedd1090835b41884a34da1df490377d7bfa3ba5237 market_resolved 974 154,852 45-45 a2dc03248e0b19bf189222ae308973ab734ec7738ba06d1ff7628d97b3b8db93 new_market 2,336 242,517 46-46 d9114b18848d96cdc6303cfc0fd3591d490560e1f1c8c5d6b4dffaef09d5be3b price_change 92,771,662 917,057,648 47-400 896fd7f98c1d1c533cefe72bfdf285e7a7fd91d336da3f2e99d18333911c1907 tick_size_change 4,760 173,884 401-401 14bf44bb2c8af3f4e666dc2086d6f916bc4ba5ec3cc635823f20f073abf8a73b EVENT MIX count share price_change 92,771,662 89.05% best_bid_ask 11,174,238 10.73% book 164,831 0.16% last_trade_price 54,655 0.05% tick_size_change 4,760 <0.01% new_market 2,336 <0.01% market_resolved 974 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,174,515 11,174,238 277 497 FULL book 164,893 164,831 62 21,839 FULL last_trade_price 54,656 54,655 1 0 FULL market_resolved 974 974 0 0 FULL new_market 2,336 2,336 0 0 FULL price_change 92,773,520 92,771,662 1,858 232 FULL tick_size_change 4,760 4,760 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,171,840 10,741,455 5ms 10ms 148ms 4.0s 0 transport_latency_assumed best_bid_ask e 11,170,848 38,319 40ms 47ms 243ms 20.5s 0 transport_latency_assumed best_bid_ask f 11,170,150 18,062 46ms 56ms 281ms 20.6s 0 transport_latency_assumed best_bid_ask g 11,169,544 2,505 76ms 94ms 528ms 53.5s 0 transport_latency_assumed best_bid_ask h 11,171,119 373,897 18ms 27ms 286ms 52.2s 0 transport_latency_assumed book c 115,077 107,701 7ms 47ms 14.8min 94.8d 0 book_staleness book e 125,025 12,934 43ms 8.4s 2.7d 113.5d 0 book_staleness book f 122,213 10,421 50ms 2.4s 1.7d 111.9d 0 book_staleness book g 122,299 10,433 82ms 4.9s 1.7d 105.7d 0 book_staleness book h 129,550 23,342 22ms 51.8s 11.0d 113.5d 0 book_staleness last_trade_price c 54,490 51,631 5ms 17ms 224ms 2.1s 0 transport_latency_assumed last_trade_price e 54,494 222 42ms 144ms 4.3s 20.5s 0 transport_latency_assumed last_trade_price f 54,312 129 49ms 156ms 4.7s 20.6s 0 transport_latency_assumed last_trade_price g 54,356 24 80ms 291ms 13.8s 53.5s 0 transport_latency_assumed last_trade_price h 54,577 2,649 19ms 47ms 409ms 38.5s 0 transport_latency_assumed market_resolved c 974 930 5ms 13ms 237ms 973ms 0 transport_latency_assumed market_resolved e 974 2 41ms 155ms 502ms 753ms 0 transport_latency_assumed market_resolved f 974 1 47ms 138ms 501ms 772ms 0 transport_latency_assumed market_resolved g 974 1 78ms 226ms 740ms 1.1s 0 transport_latency_assumed market_resolved h 974 40 18ms 65ms 406ms 40.0s 0 transport_latency_assumed new_market c 1,600 1,015 100ms 18.3s 37.5s 7.2h 0 transport_latency_assumed new_market e 1,600 249 203ms 18.9s 54.5s 4.1h 0 transport_latency_assumed new_market f 1,600 277 211ms 18.6s 53.7s 1.9h 0 transport_latency_assumed new_market g 1,600 96 280ms 583ms 21.6s 7.2h 0 transport_latency_assumed new_market h 1,600 699 165ms 21.9s 52.1s 7.2h 0 transport_latency_assumed price_change c 92,741,572 88,740,112 5ms 11ms 182ms 4.0s 0 transport_latency_assumed price_change e 92,678,446 365,052 40ms 55ms 429ms 20.6s 0 transport_latency_assumed price_change f 92,705,468 192,886 47ms 66ms 481ms 20.7s 0 transport_latency_assumed price_change g 92,626,914 35,392 76ms 114ms 1.1s 53.5s 0 transport_latency_assumed price_change h 92,724,494 3,438,220 18ms 32ms 354ms 52.8s 0 transport_latency_assumed tick_size_change c 4,760 4,623 5ms 8ms 50ms 115ms 0 transport_latency_assumed tick_size_change e 4,760 12 40ms 45ms 96ms 250ms 0 transport_latency_assumed tick_size_change f 4,760 not meas. 47ms 55ms 144ms 410ms 0 transport_latency_assumed tick_size_change g 4,760 not meas. 76ms 87ms 127ms 1.1s 0 transport_latency_assumed tick_size_change h 4,760 125 18ms 24ms 72ms 39.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-20/09/2026-09-20T09.parquet sha256sum 2026-09-20T09.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.