Hour audit: 2026-09-25T02
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-25T02 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-25T02:00:00.000013501+00:00 · last event 2026-09-25T02:59:59.999968976+00:00
VOLUME 134,462,351 rows · 1,444,890,350 bytes (1.35 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured g: 126,687,037 · c: 126,625,753 · i: 122,233,740 · h: 106,932,476 · k: 98,147,197 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 118,875 (0.09%) · c: 117,645,345 (87.49%) · i: 1,867,655 (1.39%) · h: 4,219,247 (3.14%) · k: 10,611,229 (7.89%) (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 134,462,351 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 a29dd4111a7f1ec56d5d578120cfb016dc9a4bde12a6f7840d56101d6d609409
the corpus checksum ledger names this file with the same digest
joined 134,464,624 to merged 134,462,351, minus 2,273 (minus 0.0017%)
boundary drops 2,273 · 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-25T04:48:55Z 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 13,960,982 156,512,042 0-53 bb52567dbc51778419d303acc015f27e5cc049e69dcf7f0f233b7ea9900d78f5 book 3,412,788 117,142,393 54-67 f150f06ec61482bea241241b420b4c8e37c35a5585138f7b708487cdce407ba6 last_trade_price 44,876 2,545,195 68-68 8a0d3869a7efe8a385229341fd3b94c2e5a64e5bbcac905bb53fd7cbd4758b09 market_resolved 3,623 230,435 69-69 7b62618e50a79bcc2e08d8dfd822229af3f4452c990abea90b5065100e355d6f new_market 1,062 74,515 70-70 ddd557884718a8b0d7f67576043afd21e25995792bf7d9e43a0f41e5604b98b2 price_change 117,034,716 1,166,698,250 71-517 cb2e01072a14dc01184c45ff8cc4abf84e5bd5db1ccf7dcc555bebfe4aa88024 tick_size_change 4,304 156,291 518-518 aabc4fc7982c84532c239c1f92a9bd547a27a9cc5919cac7b8ff2b5e1c8afbb2 EVENT MIX count share price_change 117,034,716 87.04% best_bid_ask 13,960,982 10.38% book 3,412,788 2.54% last_trade_price 44,876 0.03% tick_size_change 4,304 <0.01% market_resolved 3,623 <0.01% new_market 1,062 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,961,308 13,960,982 326 6,130 FULL book 3,412,882 3,412,788 94 2,498 FULL last_trade_price 44,877 44,876 1 618 FULL market_resolved 3,623 3,623 0 136 FULL new_market 1,062 1,062 0 8 FULL price_change 117,036,568 117,034,716 1,852 3,464 FULL tick_size_change 4,304 4,304 0 430 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 13,463,743 12,625,303 5ms 11ms 89ms 2.2s 0 transport_latency_assumed best_bid_ask g 13,474,082 5,641 81ms 99ms 224ms 8.2s 0 transport_latency_assumed best_bid_ask h 11,150,579 343,417 18ms 34ms 97ms 55.0s 0 transport_latency_assumed best_bid_ask i 12,942,230 171,003 24ms 30ms 93ms 10.3s 0 transport_latency_assumed best_bid_ask k 10,158,577 815,618 12ms 19ms 77ms 8.3s 0 transport_latency_assumed book c 522,326 145,029 4.6min 3.5d 37.0d 118.2d 0 book_staleness book g 504,382 64,757 4.3min 3.4d 37.0d 118.2d 0 book_staleness book h 1,811,658 688,812 10.8min 4.8d 43.5d 118.2d 0 book_staleness book i 931,434 132,254 7.6min 4.2d 43.3d 118.2d 0 book_staleness book k 2,597,275 2,381,936 12.5min 5.3d 44.3d 118.2d 0 book_staleness last_trade_price c 43,125 38,425 6ms 25ms 186ms 1.9s 0 transport_latency_assumed last_trade_price g 43,071 22 84ms 169ms 923ms 8.2s 0 transport_latency_assumed last_trade_price h 37,377 1,826 19ms 51ms 234ms 11.8s 0 transport_latency_assumed last_trade_price i 41,212 851 25ms 45ms 194ms 1.6s 0 transport_latency_assumed last_trade_price k 30,241 3,752 13ms 29ms 163ms 1.6s 0 transport_latency_assumed market_resolved c 1,395 1,002 5ms 6.0min 7.3min 8.2min 0 transport_latency_assumed market_resolved g 1,313 66 88ms 5.1min 6.3min 6.4min 0 transport_latency_assumed market_resolved h 1,289 230 34ms 7.2min 8.3min 9.2min 0 transport_latency_assumed market_resolved i 1,446 50 25ms 5.9min 8.1min 10.7min 0 transport_latency_assumed market_resolved k 2,987 2,275 8.2min 17.3min 26.3min 27.9min 0 transport_latency_assumed new_market c 472 126 100ms 20.1s 7.0min 7.0min 0 transport_latency_assumed new_market g 462 77 289ms 21.8s 6.8min 6.8min 0 transport_latency_assumed new_market h 464 147 145ms 5.1min 8.0min 8.1min 0 transport_latency_assumed new_market i 479 132 84ms 19.6s 6.9min 6.9min 0 transport_latency_assumed new_market k 849 580 3.5min 14.0min 23.8min 23.9min 0 transport_latency_assumed price_change c 112,590,428 104,831,408 5ms 13ms 101ms 3.8s 0 transport_latency_assumed price_change g 112,659,463 48,312 81ms 102ms 280ms 8.3s 0 transport_latency_assumed price_change h 93,927,321 3,184,751 18ms 36ms 112ms 59.0s 0 transport_latency_assumed price_change i 108,312,783 1,563,335 24ms 32ms 108ms 10.6s 0 transport_latency_assumed price_change k 85,354,212 7,406,910 13ms 20ms 87ms 8.3s 0 transport_latency_assumed tick_size_change c 4,264 4,052 5ms 8ms 254ms 598ms 0 transport_latency_assumed tick_size_change g 4,264 not meas. 80ms 95ms 432ms 1.5s 0 transport_latency_assumed tick_size_change h 3,788 64 18ms 29ms 366ms 777ms 0 transport_latency_assumed tick_size_change i 4,156 30 23ms 27ms 206ms 452ms 0 transport_latency_assumed tick_size_change k 3,056 158 12ms 18ms 210ms 370ms 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-25/02/2026-09-25T02.parquet sha256sum 2026-09-25T02.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.