Hour audit: 2026-09-25T03
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.
1 finding
- a machine expected this hour contributed nothing. Of the 5 machines expected to be capturing this hour, 1 contributed no rows: h. The hour is still whole on minutes; it simply rests on 4 machines rather than 5.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-25T03 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-25T03:00:00.000116739+00:00 · last event 2026-09-25T03:59:59.999972115+00:00
VOLUME 126,066,627 rows · 1,329,321,899 bytes (1.24 GiB) · 7 products, all holding rows
WITNESSES cgik — 4 machines contributed rows
captured i: 124,342,142 · g: 119,063,986 · c: 113,506,377 · k: 112,360,129 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 4,433,682 (3.52%) · g: 179,951 (0.14%) · c: 104,024,322 (82.52%) · k: 17,428,672 (13.82%) (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 126,066,627 rows exactly, so those pairs supplied none
5 expected (cghik), 1 contributed nothing: h
INTEGRITY sha256 cce0f64f321e3592a272d5d0729abce90f855bb6705f64015aa901515c0c8086
the corpus checksum ledger names this file with the same digest
joined 126,085,554 to merged 126,066,627, minus 18,927 (minus 0.0150%)
boundary drops 18,927 · 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-25T05:59:13Z as cgik
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 7/8 pass, 1 finding
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
FINDING a machine expected this hour contributed nothing
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,576,570 151,806,521 0-51 43cc854702590d1799a85916f303cd87f353adcc5b91f5180c949cf53dbeb966 book 1,821,083 87,509,032 52-58 06549586de573b3e6351723b142f4f92cad4c57cab571aff5525f74d37e5c1b9 last_trade_price 44,492 2,501,516 59-59 ba9dea5d47335e1253dbd5e1f41607528f000b3473cb5e6bbe4f050ea09e0f1f market_resolved 1,338 182,073 60-60 9b8b2fba5cdb8deae77f2c51d6e39a795485e0fb4a63e35ea2de982eb1a2ff66 new_market 892 93,411 61-61 77b33c7fc436d81b3398a4b9f069b9d11a4dfb8ce4fde16bd211d1d52995b973 price_change 110,619,348 1,085,693,591 62-483 8a952bd72324c12f4fb6b06b8771e3c520420dc431763dfb39488da95ffc44fa tick_size_change 2,904 106,933 484-484 f943d7524057e30ff07bb184bcd27546ddfdbc32c85488f10f4521849679853b EVENT MIX count share price_change 110,619,348 87.75% best_bid_ask 13,576,570 10.77% book 1,821,083 1.44% last_trade_price 44,492 0.04% tick_size_change 2,904 <0.01% market_resolved 1,338 <0.01% new_market 892 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,576,881 13,576,570 311 77,351 PARTIAL book 1,837,049 1,821,083 15,966 206,010 PARTIAL last_trade_price 44,496 44,492 4 2,575 PARTIAL market_resolved 1,338 1,338 0 1,117 PARTIAL new_market 892 892 0 612 PARTIAL price_change 110,621,994 110,619,348 2,646 136,981 PARTIAL tick_size_change 2,904 2,904 0 726 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 12,300,508 11,397,939 4ms 12ms 101ms 3.2s 0 transport_latency_assumed best_bid_ask g 12,994,550 3,866 80ms 99ms 256ms 11.8s 0 transport_latency_assumed best_bid_ask i 13,574,274 453,659 19ms 26ms 95ms 4.0s 0 transport_latency_assumed best_bid_ask k 12,172,066 1,721,106 12ms 19ms 79ms 2.8s 0 transport_latency_assumed book c 987,209 506,155 10.5min 4.6d 43.3d 118.2d 0 book_staleness book g 535,859 132,384 10.1min 3.5d 39.3d 118.2d 0 book_staleness book i 156,845 35,377 48ms 1.1d 30.4d 118.2d 0 book_staleness book k 1,296,312 1,147,167 11.5min 4.5d 43.5d 118.2d 0 book_staleness last_trade_price c 38,936 34,361 6ms 28ms 235ms 1.5s 0 transport_latency_assumed last_trade_price g 41,613 98 83ms 193ms 1.6s 11.8s 0 transport_latency_assumed last_trade_price i 44,152 2,288 21ms 46ms 254ms 1.0s 0 transport_latency_assumed last_trade_price k 39,639 7,745 14ms 33ms 207ms 850ms 0 transport_latency_assumed market_resolved c 1,111 1,033 5ms 127ms 5.7min 5.8min 0 transport_latency_assumed market_resolved g 1,099 2 81ms 212ms 38.4s 1.8min 0 transport_latency_assumed market_resolved i 1,108 121 19ms 120ms 51.8s 1.4min 0 transport_latency_assumed market_resolved k 1,145 182 13ms 49.3s 10.4min 12.5min 0 transport_latency_assumed new_market c 605 344 62ms 28.8s 1.9min 2.2min 0 transport_latency_assumed new_market g 605 77 151ms 47.3s 2.0min 2.3min 0 transport_latency_assumed new_market i 605 247 76ms 32.6s 1.9min 2.2min 0 transport_latency_assumed new_market k 635 224 71ms 1.5min 8.5min 9.1min 0 transport_latency_assumed price_change c 100,175,288 92,081,976 5ms 15ms 114ms 3.4s 0 transport_latency_assumed price_change g 105,487,576 43,524 80ms 104ms 343ms 12.1s 0 transport_latency_assumed price_change i 110,562,254 3,941,942 19ms 29ms 115ms 4.1s 0 transport_latency_assumed price_change k 98,847,668 14,551,906 12ms 21ms 93ms 4.3s 0 transport_latency_assumed tick_size_change c 2,720 2,514 5ms 12ms 78ms 142ms 0 transport_latency_assumed tick_size_change g 2,684 not meas. 81ms 100ms 218ms 347ms 0 transport_latency_assumed tick_size_change i 2,904 48 19ms 24ms 62ms 179ms 0 transport_latency_assumed tick_size_change k 2,664 342 12ms 16ms 47ms 73ms 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/03/2026-09-25T03.parquet sha256sum 2026-09-25T03.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.