Hour audit: 2026-09-29T18
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-29T18 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-29T18:00:00.000270865+00:00 · last event 2026-09-29T18:59:59.999950368+00:00
VOLUME 116,280,484 rows · 1,356,054,560 bytes (1.26 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured k: 114,204,633 · i: 114,176,742 · h: 114,170,838 · g: 112,394,829 · c: 89,700,373 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 29,255,257 (25.16%) · i: 5,842,745 (5.02%) · h: 5,008,788 (4.31%) · g: 98,063 (0.08%) · c: 76,075,631 (65.42%) (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 116,280,484 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 9d196ccf4eefccaa201f5bd07c433d83e79129b6dc8084bde339b60c094011bf
the corpus checksum ledger names this file with the same digest
joined 116,315,799 to merged 116,280,484, minus 35,315 (minus 0.0304%)
boundary drops 35,315 · 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-29T21:14:44Z 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 11,670,187 146,791,257 0-44 fa999a67bb26634e7f8ee2c7d48fd3cfe263dde41f7c42494c8ff11a36712817 book 2,171,229 88,837,025 45-53 7de4d6914a11723052662c0cbd534253c370f15008958fc9e2a1028ae1c4157e last_trade_price 69,336 4,187,330 54-54 5f2d2bce3ea06a698504443ae81e5ed4a3517ef425bfe526b4ef6517912de931 market_resolved 1,236 116,715 55-55 9b352e85001a411d42ea6ec0b7d6583de8069b6b363f37957fa94140a18f7462 new_market 8,422 635,744 56-56 128f3f56e3111cb7155f316f3accc7e63f7aeb520e5e4fefec4b52cfc4450a88 price_change 102,356,430 1,114,029,397 57-447 5e9c94b539d3c91f756d9a9d4ceeb38cadd82dfda536b0bd3e74cb63faefffd1 tick_size_change 3,644 131,498 448-448 9472eb3d246ffe300f4766199a32851718ad8b593d1a3545943af4310584a722 EVENT MIX count share price_change 102,356,430 88.03% best_bid_ask 11,670,187 10.04% book 2,171,229 1.87% last_trade_price 69,336 0.06% new_market 8,422 <0.01% tick_size_change 3,644 <0.01% market_resolved 1,236 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,674,036 11,670,187 3,849 3,395 FULL book 2,171,677 2,171,229 448 226,200 FULL last_trade_price 69,354 69,336 18 2,187 FULL market_resolved 1,236 1,236 0 33 FULL new_market 8,426 8,422 4 14 FULL price_change 102,387,426 102,356,430 30,996 2,428 FULL tick_size_change 3,644 3,644 0 250 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,058,288 7,687,928 6ms 41ms 354ms 38.7s 0 transport_latency_assumed best_bid_ask g 11,644,423 8,579 80ms 268ms 2.1s 44.5s 0 transport_latency_assumed best_bid_ask h 11,665,127 509,310 20ms 117ms 2.5s 2.5min 0 transport_latency_assumed best_bid_ask i 11,669,071 581,342 21ms 54ms 332ms 17.6s 0 transport_latency_assumed best_bid_ask k 11,669,098 2,883,028 14ms 56ms 454ms 1.0min 0 transport_latency_assumed book c 2,102,228 2,052,905 1.3h 2.6d 40.5d 122.9d 0 book_staleness book g 159,104 15,839 208ms 3.6min 3.2d 104.3d 0 book_staleness book h 205,561 44,401 64ms 10.1h 22.3d 122.8d 0 book_staleness book i 151,990 15,711 29ms 1.4s 13.4h 104.3d 0 book_staleness book k 157,826 42,373 25ms 2.7s 1.4d 122.8d 0 book_staleness last_trade_price c 49,852 41,999 7ms 54ms 443ms 15.8s 0 transport_latency_assumed last_trade_price g 64,166 78 161ms 2.3s 17.1s 43.9s 0 transport_latency_assumed last_trade_price h 68,911 3,295 25ms 272ms 2.7s 1.6min 0 transport_latency_assumed last_trade_price i 69,143 3,750 27ms 193ms 2.6s 6.1s 0 transport_latency_assumed last_trade_price k 69,161 20,214 16ms 106ms 685ms 47.1s 0 transport_latency_assumed market_resolved c 1,016 909 2.2min 14.3min 18.7min 19.4min 0 transport_latency_assumed market_resolved g 675 not meas. 111ms 23.1s 52.9s 57.1s 0 transport_latency_assumed market_resolved h 674 20 36ms 28.1s 52.9s 56.7s 0 transport_latency_assumed market_resolved i 675 77 31ms 22.6s 49.3s 49.3s 0 transport_latency_assumed market_resolved k 675 230 22ms 23.8s 51.2s 51.3s 0 transport_latency_assumed new_market c 7,717 5,953 5.0min 16.9min 22.7min 1.5h 0 transport_latency_assumed new_market g 3,889 119 278ms 568ms 2.6min 5.4min 0 transport_latency_assumed new_market h 3,889 510 151ms 381ms 2.4min 5.5min 0 transport_latency_assumed new_market i 3,893 978 109ms 309ms 2.2min 5.3min 0 transport_latency_assumed new_market k 3,889 862 123ms 347ms 2.4min 5.4min 0 transport_latency_assumed price_change c 78,478,628 66,283,532 6ms 44ms 358ms 39.0s 0 transport_latency_assumed price_change g 100,518,928 73,448 83ms 461ms 11.2s 44.6s 0 transport_latency_assumed price_change h 102,223,032 4,451,128 21ms 162ms 3.0s 2.5min 0 transport_latency_assumed price_change i 102,278,326 5,240,751 22ms 72ms 564ms 17.6s 0 transport_latency_assumed price_change k 102,300,340 26,307,571 14ms 64ms 462ms 1.0min 0 transport_latency_assumed tick_size_change c 2,644 2,405 6ms 17ms 246ms 355ms 0 transport_latency_assumed tick_size_change g 3,644 not meas. 80ms 218ms 579ms 7.5s 0 transport_latency_assumed tick_size_change h 3,644 124 21ms 64ms 783ms 4.5s 0 transport_latency_assumed tick_size_change i 3,644 136 21ms 50ms 118ms 1.3s 0 transport_latency_assumed tick_size_change k 3,644 979 14ms 28ms 162ms 2.2s 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/18/2026-09-29T18.parquet sha256sum 2026-09-29T18.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.