Hour audit: 2026-09-28T22
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-28T22 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-28T22:00:00.000004348+00:00 · last event 2026-09-28T22:59:59.999987773+00:00
VOLUME 90,905,071 rows · 953,191,568 bytes (909.03 MiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured c: 90,824,921 · k: 90,815,807 · i: 90,813,423 · h: 90,798,744 · g: 90,175,788 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 81,229,637 (89.36%) · k: 5,748,703 (6.32%) · i: 1,390,903 (1.53%) · h: 2,497,033 (2.75%) · g: 38,795 (0.04%) (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 90,905,071 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 25eb3c58b1816b5558ed9284c183b6e5d03e6189e7962b9412520b6941a034ed
the corpus checksum ledger names this file with the same digest
joined 90,906,951 to merged 90,905,071, minus 1,880 (minus 0.0021%)
boundary drops 1,880 · 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-29T01:04:02Z as cghik
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 status feed unobserved for this hour. Our incident register was last checked against the venue's feed at 2026-09-23T20:35Z, before this hour ended, so nothing has looked yet. This is a could-not-look and never an all-clear.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,957,557 115,479,374 0-37 46a140b9e5781c13e0e72aa05ccf44cdaec41d7c6a6f02060b3def416dc12f37 book 136,554 13,426,325 38-38 7bc8c1152fe728da47dabd24f1f831de5647630f66c037017c49ddb5f95fa60f last_trade_price 48,224 2,788,946 39-39 a7dd490e5b2f817de905038dbdcb01a499caa2459d66fe9876f9d5aaf0220e22 market_resolved 3,226 478,222 40-40 416f503427cd1efd6c50efe87e56dc37f2a1b0616cba38cd41631aa290cbb2b8 new_market 6,514 640,633 41-41 7a07fa942c336aee161fd8eab66a41a98c8e7bef49d750da920d7531f981d127 price_change 80,749,948 819,228,846 42-350 37ce212966a1969c5b9728dbbd018afe738386f70277da3ece9e139c18426e9c tick_size_change 3,048 111,213 351-351 0e6270e36ec51f83c0663a5c0a123d98ed1f251666cbed0c2d0e37ab0702b534 EVENT MIX count share price_change 80,749,948 88.83% best_bid_ask 9,957,557 10.95% book 136,554 0.15% last_trade_price 48,224 0.05% new_market 6,514 <0.01% market_resolved 3,226 <0.01% tick_size_change 3,048 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,957,752 9,957,557 195 1,273 FULL book 136,557 136,554 3 9,598 FULL last_trade_price 48,224 48,224 0 0 FULL market_resolved 3,226 3,226 0 0 FULL new_market 6,514 6,514 0 0 FULL price_change 80,751,630 80,749,948 1,682 634 FULL tick_size_change 3,048 3,048 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,953,601 8,971,902 5ms 18ms 227ms 16.4s 0 transport_latency_assumed best_bid_ask g 9,943,249 3,068 81ms 172ms 793ms 43.6s 0 transport_latency_assumed best_bid_ask h 9,952,662 256,925 18ms 33ms 451ms 58.9s 0 transport_latency_assumed best_bid_ask i 9,952,120 145,352 29ms 41ms 266ms 13.2s 0 transport_latency_assumed best_bid_ask k 9,952,304 580,310 12ms 27ms 276ms 41.1s 0 transport_latency_assumed book c 111,509 94,701 8ms 1.8s 1.5d 103.5d 0 book_staleness book g 107,433 9,526 127ms 8.5s 1.8d 103.5d 0 book_staleness book h 109,401 10,699 24ms 922ms 1.1d 103.5d 0 book_staleness book i 108,411 6,483 33ms 603ms 13.9h 122.0d 0 book_staleness book k 111,259 15,145 18ms 1.4s 1.5d 103.4d 0 book_staleness last_trade_price c 48,009 42,100 6ms 43ms 316ms 11.7s 0 transport_latency_assumed last_trade_price g 45,570 14 120ms 2.4s 16.2s 43.0s 0 transport_latency_assumed last_trade_price h 47,959 1,523 20ms 105ms 809ms 52.5s 0 transport_latency_assumed last_trade_price i 48,042 757 31ms 159ms 945ms 7.2s 0 transport_latency_assumed last_trade_price k 47,976 3,830 14ms 74ms 366ms 11.8s 0 transport_latency_assumed market_resolved c 3,039 2,506 5ms 273ms 51.7s 52.6s 0 transport_latency_assumed market_resolved g 3,039 5 83ms 720ms 53.5s 55.0s 0 transport_latency_assumed market_resolved h 3,039 91 19ms 412ms 48.7s 56.4s 0 transport_latency_assumed market_resolved i 3,039 496 31ms 20.3s 54.2s 57.2s 0 transport_latency_assumed market_resolved k 3,039 128 13ms 437ms 49.5s 55.7s 0 transport_latency_assumed new_market c 4,089 1,918 103ms 50.6s 1.8min 2.6min 0 transport_latency_assumed new_market g 4,089 506 279ms 53.9s 1.7min 19.8d 0 transport_latency_assumed new_market h 4,089 1,686 118ms 46.7s 1.5min 2.8min 0 transport_latency_assumed new_market i 4,089 1,053 118ms 48.7s 1.8min 19.8d 0 transport_latency_assumed new_market k 4,089 1,351 146ms 44.9s 1.5min 19.8d 0 transport_latency_assumed price_change c 80,701,626 72,113,868 5ms 23ms 245ms 17.5s 0 transport_latency_assumed price_change g 80,069,360 25,676 82ms 259ms 6.3s 43.6s 0 transport_latency_assumed price_change h 80,678,546 2,226,008 18ms 42ms 533ms 59.8s 0 transport_latency_assumed price_change i 80,694,674 1,236,702 29ms 55ms 407ms 14.3s 0 transport_latency_assumed price_change k 80,694,092 5,147,694 12ms 34ms 296ms 41.4s 0 transport_latency_assumed tick_size_change c 3,048 2,642 5ms 21ms 290ms 375ms 0 transport_latency_assumed tick_size_change g 3,048 not meas. 81ms 124ms 406ms 9.4s 0 transport_latency_assumed tick_size_change h 3,048 101 18ms 32ms 91ms 2.8s 0 transport_latency_assumed tick_size_change i 3,048 60 29ms 44ms 129ms 582ms 0 transport_latency_assumed tick_size_change k 3,048 245 12ms 25ms 78ms 289ms 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-28/22/2026-09-28T22.parquet sha256sum 2026-09-28T22.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.