Hour audit: 2026-09-29T16
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-29T16 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-29T16:00:00.000025826+00:00 · last event 2026-09-29T16:59:59.999996264+00:00
VOLUME 113,056,831 rows · 1,325,734,673 bytes (1.23 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured h: 111,200,542 · i: 111,011,074 · g: 109,108,114 · k: 101,027,168 · c: 96,843,050 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 4,590,974 (4.06%) · i: 5,935,485 (5.25%) · g: 92,948 (0.08%) · k: 21,935,596 (19.40%) · c: 80,501,828 (71.20%) (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 113,056,831 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 c8f7fd7ba06f10c63c7c63e652bf0282697bef37f242b7e85e886c9edbbd792d
the corpus checksum ledger names this file with the same digest
joined 113,058,491 to merged 113,056,831, minus 1,660 (minus 0.0015%)
boundary drops 1,660 · 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-29T19:12:15Z 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,947,761 127,394,653 0-37 f1cf0984f1565fede4ad7edf0af8db88c604366625a9190265437f6a74c4173c book 1,890,946 93,866,676 38-45 656bb1d8a99f2736d66d48faa24299edf2c26b455c3f90d92feb6283e7faa676 last_trade_price 64,998 3,786,503 46-46 748aa5e6712cab69a65438ae3afd6dd8a33d800ce7368e2232f598e4ab9e61d3 market_resolved 1,534 171,041 47-47 8a0e7db58979cfc44a541b90c5b86d3211e3fbeb7d1c1a227c1fa7345192eaa2 new_market 8,432 829,690 48-48 03e0193f1f5066204a574e669a18454de1f329007661a6f555a2edd403f2cd69 price_change 101,139,416 1,098,259,727 49-434 f4ff6d66455d8411fdff42152f06bbf73d30647d9487bef088f28febe37e1dfe tick_size_change 3,744 139,635 435-435 903b23130a90648db66e9337f9eea16d70a07784e65e6963a63db14f843b046a EVENT MIX count share price_change 101,139,416 89.46% best_bid_ask 9,947,761 8.80% book 1,890,946 1.67% last_trade_price 64,998 0.06% new_market 8,432 <0.01% tick_size_change 3,744 <0.01% market_resolved 1,534 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,947,897 9,947,761 136 2,706 FULL book 1,891,018 1,890,946 72 224,817 FULL last_trade_price 64,998 64,998 0 455 FULL market_resolved 1,534 1,534 0 46 FULL new_market 8,432 8,432 0 22 FULL price_change 101,140,868 101,139,416 1,452 2,338 FULL tick_size_change 3,744 3,744 0 177 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,590,242 7,178,502 6ms 48ms 329ms 8.6s 0 transport_latency_assumed best_bid_ask g 9,914,952 6,642 82ms 270ms 3.5s 40.9s 0 transport_latency_assumed best_bid_ask h 9,939,283 398,452 21ms 139ms 3.2s 1.9min 0 transport_latency_assumed best_bid_ask i 9,926,147 493,527 21ms 55ms 352ms 29.1s 0 transport_latency_assumed best_bid_ask k 8,931,847 1,870,638 13ms 48ms 317ms 13.1s 0 transport_latency_assumed book c 1,545,027 1,438,532 1.7h 2.5d 38.2d 122.8d 0 book_staleness book g 160,576 19,777 273ms 1.7h 20.3d 115.0d 0 book_staleness book h 215,526 33,900 126ms 15.0h 24.1d 104.3d 0 book_staleness book i 190,481 30,601 55ms 8.4h 22.2d 122.8d 0 book_staleness book k 1,101,163 368,136 1.3h 2.5d 38.1d 122.8d 0 book_staleness last_trade_price c 54,318 45,110 7ms 59ms 406ms 2.7s 0 transport_latency_assumed last_trade_price g 58,911 47 170ms 4.1s 20.7s 38.9s 0 transport_latency_assumed last_trade_price h 64,669 2,674 25ms 261ms 4.4s 1.6min 0 transport_latency_assumed last_trade_price i 64,695 3,270 23ms 190ms 1.6s 7.5s 0 transport_latency_assumed last_trade_price k 58,426 13,897 15ms 82ms 353ms 6.0s 0 transport_latency_assumed market_resolved c 1,187 1,086 14ms 8.9min 12.4min 12.5min 0 transport_latency_assumed market_resolved g 1,012 14 91ms 458ms 2.7s 55.7s 0 transport_latency_assumed market_resolved h 1,012 68 30ms 417ms 53.5s 1.2min 0 transport_latency_assumed market_resolved i 1,011 75 23ms 154ms 56.6s 57.3s 0 transport_latency_assumed market_resolved k 998 291 18ms 54.4s 5.9min 6.0min 0 transport_latency_assumed new_market c 6,931 3,946 124ms 9.3min 11.5min 12.9min 0 transport_latency_assumed new_market g 5,255 225 243ms 817ms 2.6min 3.8min 0 transport_latency_assumed new_market h 5,255 723 141ms 439ms 2.5min 3.8min 0 transport_latency_assumed new_market i 5,255 2,024 70ms 329ms 2.7min 4.0min 0 transport_latency_assumed new_market k 5,363 1,514 103ms 47.8s 13.5min 16.0min 0 transport_latency_assumed price_change c 86,642,029 71,831,888 6ms 51ms 358ms 10.6s 0 transport_latency_assumed price_change g 98,963,664 66,243 85ms 562ms 13.9s 41.0s 0 transport_latency_assumed price_change h 100,971,053 4,155,044 22ms 183ms 3.6s 2.2min 0 transport_latency_assumed price_change i 100,819,749 5,405,825 22ms 72ms 666ms 29.2s 0 transport_latency_assumed price_change k 90,925,907 19,680,416 14ms 57ms 335ms 13.2s 0 transport_latency_assumed tick_size_change c 3,316 2,764 7ms 30ms 189ms 253ms 0 transport_latency_assumed tick_size_change g 3,744 not meas. 81ms 212ms 548ms 876ms 0 transport_latency_assumed tick_size_change h 3,744 113 22ms 55ms 2.0s 17.3s 0 transport_latency_assumed tick_size_change i 3,736 163 22ms 45ms 158ms 397ms 0 transport_latency_assumed tick_size_change k 3,464 704 14ms 28ms 267ms 703ms 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-29/16/2026-09-29T16.parquet sha256sum 2026-09-29T16.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.