Hour audit: 2026-09-25T01
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-25T01 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-25T01:00:00.000377606+00:00 · last event 2026-09-25T01:59:59.999921692+00:00
VOLUME 136,864,955 rows · 1,483,244,367 bytes (1.38 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured g: 128,660,910 · h: 128,058,999 · c: 123,663,822 · i: 123,303,083 · k: 107,472,397 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 74,891 (0.05%) · h: 4,228,369 (3.09%) · c: 114,463,426 (83.63%) · i: 2,556,052 (1.87%) · k: 15,542,217 (11.36%) (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 136,864,955 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 9a16720225a8885434fee353dbf12218ef0143aaf08ef972470c76c9ac56e6e6
the corpus checksum ledger names this file with the same digest
joined 136,866,305 to merged 136,864,955, minus 1,350 (minus 0.0010%)
boundary drops 1,350 · 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-25T03:49:35Z 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 14,695,125 166,308,229 0-56 c462be6d1cdc9f25fb36ed9d9503f497ee0005f7a028f872803321a841b0d527 book 2,708,853 104,102,746 57-67 e27b90bb764583aac649834704e81dcc9942750b397445dcf6fc44b280154cf9 last_trade_price 49,074 2,759,612 68-68 97f57e82d47986848d469bc5acc7d2ac0cb015909373be0ae04963176694b8e6 market_resolved 2,026 211,022 69-69 181d98d83c1ee9417b99e262d8e859b9ffa74646865f010d3e92abc47d46bc8b new_market 647 60,089 70-70 87aa68b7b4bc51a1c44d1b7e067504fb78b7e0a1a0d0fba33f88f3ad3de829c0 price_change 119,403,506 1,208,041,729 71-526 ae000917981db3ae5e3b34e93a99229861970b7eb3d61b78d2aa7920e3ea64e4 tick_size_change 5,724 203,831 527-527 2503f525a3460c06e1aba02980d1edaa22fb8659b00f12ada371d7a1f78b436f EVENT MIX count share price_change 119,403,506 87.24% best_bid_ask 14,695,125 10.74% book 2,708,853 1.98% last_trade_price 49,074 0.04% tick_size_change 5,724 <0.01% market_resolved 2,026 <0.01% new_market 647 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 14,695,250 14,695,125 125 4,007 FULL book 2,708,897 2,708,853 44 2,487 FULL last_trade_price 49,074 49,074 0 500 FULL market_resolved 2,027 2,026 1 97 FULL new_market 647 647 0 37 FULL price_change 119,404,686 119,403,506 1,180 1,911 FULL tick_size_change 5,724 5,724 0 428 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 13,417,719 12,534,254 5ms 12ms 86ms 3.6s 0 transport_latency_assumed best_bid_ask g 14,094,012 3,961 82ms 102ms 233ms 9.2s 0 transport_latency_assumed best_bid_ask h 14,013,990 425,967 18ms 44ms 101ms 7.4s 0 transport_latency_assumed best_bid_ask i 13,453,301 232,219 21ms 27ms 91ms 4.1s 0 transport_latency_assumed best_bid_ask k 11,644,101 1,498,724 13ms 20ms 76ms 1.6s 0 transport_latency_assumed book c 917,560 385,402 11.1min 4.4d 40.7d 118.1d 0 book_staleness book g 506,393 28,497 7.9min 3.3d 33.5d 118.1d 0 book_staleness book h 544,652 90,368 5.7min 3.3d 37.0d 118.1d 0 book_staleness book i 929,383 209,927 11.3min 4.2d 42.9d 118.1d 0 book_staleness book k 2,179,905 1,994,659 14.0min 4.7d 43.4d 118.1d 0 book_staleness last_trade_price c 44,138 39,488 6ms 25ms 221ms 1.3s 0 transport_latency_assumed last_trade_price g 45,675 58 86ms 273ms 6.8s 9.2s 0 transport_latency_assumed last_trade_price h 46,118 2,358 19ms 57ms 223ms 3.7s 0 transport_latency_assumed last_trade_price i 43,181 1,131 22ms 43ms 205ms 1.3s 0 transport_latency_assumed last_trade_price k 37,303 6,039 14ms 30ms 160ms 1.3s 0 transport_latency_assumed market_resolved c 1,210 1,011 5ms 46.4s 6.5min 6.6min 0 transport_latency_assumed market_resolved g 1,246 118 85ms 21.1s 4.5min 5.2min 0 transport_latency_assumed market_resolved h 1,422 123 36ms 5.9min 7.2min 7.3min 0 transport_latency_assumed market_resolved i 1,563 146 27ms 7.2min 10.6min 10.7min 0 transport_latency_assumed market_resolved k 1,509 628 21ms 6.4min 13.6min 14.6min 0 transport_latency_assumed new_market c 371 224 48ms 5.8min 1.6h 1.6h 0 transport_latency_assumed new_market g 334 28 123ms 10.7s 16.9s 1.6min 0 transport_latency_assumed new_market h 346 65 65ms 12.2s 5.2min 5.3min 0 transport_latency_assumed new_market i 367 125 46ms 2.9min 1.5h 1.5h 0 transport_latency_assumed new_market k 473 205 102ms 9.6min 9.8min 9.8min 0 transport_latency_assumed price_change c 109,277,408 101,497,992 5ms 14ms 99ms 3.8s 0 transport_latency_assumed price_change g 114,007,694 42,229 83ms 107ms 338ms 9.2s 0 transport_latency_assumed price_change h 113,447,603 3,709,344 18ms 46ms 118ms 7.4s 0 transport_latency_assumed price_change i 108,870,312 2,112,370 21ms 30ms 109ms 4.3s 0 transport_latency_assumed price_change k 93,604,518 12,041,571 13ms 22ms 87ms 3.0s 0 transport_latency_assumed tick_size_change c 5,416 5,055 5ms 11ms 52ms 390ms 0 transport_latency_assumed tick_size_change g 5,556 not meas. 83ms 105ms 212ms 487ms 0 transport_latency_assumed tick_size_change h 4,868 144 18ms 33ms 143ms 3.7s 0 transport_latency_assumed tick_size_change i 4,976 134 21ms 34ms 112ms 201ms 0 transport_latency_assumed tick_size_change k 4,588 391 13ms 21ms 63ms 148ms 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/01/2026-09-25T01.parquet sha256sum 2026-09-25T01.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.