Hour audit: 2026-09-25T18
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, 2 contributed no rows: c, g. The hour is still whole on minutes; it simply rests on 3 machines rather than 5.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-25T18 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-25T18:00:00.000067963+00:00 · last event 2026-09-25T18:59:59.999803646+00:00
VOLUME 118,810,639 rows · 1,272,572,094 bytes (1.19 GiB) · 7 products, all holding rows
WITNESSES hik — 3 machines contributed rows
captured h: 117,841,795 · k: 117,830,621 · i: 108,811,099 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 10,401,309 (8.75%) · k: 102,024,364 (85.87%) · i: 6,384,966 (5.37%) (rows of the merged file that came from it; these partition it)
5 expected (cghik), 2 contributed nothing: c, g
INTEGRITY sha256 7af13e6d291039507ddb0b9ccd55ac1d97ff23290c55038bbd319b8ab590d0a5
the corpus checksum ledger names this file with the same digest
joined 118,812,276 to merged 118,810,639, minus 1,637 (minus 0.0014%)
boundary drops 1,637 · 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-25T23:39:22Z as hik
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 10,715,487 122,202,209 0-40 5d19ec0b309e5a94318e10ba16a006a7080f6e73adfc0faf4d453f2569c55eb9 book 1,093,127 69,078,755 41-45 0dd7fd4f26635aaa08cbf9263120261a7d565481236f1bbac91805163a4998ad last_trade_price 60,729 3,483,214 46-46 fc131ca8cd3c8ba3a4b414c8a710b6a322593ae874111e9a1ead8ee4cf2b8862 market_resolved 1,105 140,182 47-47 338ab2d7fe6c64bfd496767077e82a5f0dd498636b0c4c49cbd877e99ae86dea new_market 4,749 436,379 48-48 e7bc5d7cbd676d082b0ac7b1ac21222cafe56e82718ace93cf52de6d86920bb9 price_change 106,933,090 1,075,795,098 49-456 340f8d2ecec71470a659401e6a0c008e8768b10b05b743b85271b64678c3b853 tick_size_change 2,352 87,517 457-457 b69beb50a08005711bbe7e6cdf8770927c8b84445d7f6a853571551dd91bd568 EVENT MIX count share price_change 106,933,090 90.00% best_bid_ask 10,715,487 9.02% book 1,093,127 0.92% last_trade_price 60,729 0.05% new_market 4,749 <0.01% tick_size_change 2,352 <0.01% market_resolved 1,105 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,715,547 10,715,487 60 55,282 PARTIAL book 1,094,093 1,093,127 966 211,746 PARTIAL last_trade_price 60,729 60,729 0 3,770 PARTIAL market_resolved 1,105 1,105 0 849 PARTIAL new_market 4,750 4,749 1 2,802 PARTIAL price_change 106,933,700 106,933,090 610 87,977 PARTIAL tick_size_change 2,352 2,352 0 588 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,714,464 905,269 19ms 55ms 356ms 44.8s 0 transport_latency_assumed best_bid_ask i 9,848,831 446,263 21ms 36ms 171ms 8.0s 0 transport_latency_assumed best_bid_ask k 10,714,449 9,363,955 13ms 31ms 223ms 13.7s 0 transport_latency_assumed book h 157,934 26,601 39ms 3.2h 18.3d 100.3d 0 book_staleness book i 1,068,975 953,735 1.5h 3.9d 41.2d 118.8d 0 book_staleness book k 161,412 112,791 24ms 4.4h 18.3d 118.8d 0 book_staleness last_trade_price h 60,609 5,527 21ms 123ms 664ms 11.0s 0 transport_latency_assumed last_trade_price i 55,389 3,321 24ms 106ms 656ms 3.9s 0 transport_latency_assumed last_trade_price k 60,572 51,881 14ms 63ms 319ms 3.5s 0 transport_latency_assumed market_resolved h 849 51 28ms 21.2s 48.0s 48.4s 0 transport_latency_assumed market_resolved i 981 292 25ms 8.6min 13.1min 13.1min 0 transport_latency_assumed market_resolved k 849 762 15ms 21.1s 46.8s 48.1s 0 transport_latency_assumed new_market h 2,801 818 131ms 335ms 2.9min 4.7min 0 transport_latency_assumed new_market i 3,988 2,562 162ms 13.5min 15.0min 15.7min 0 transport_latency_assumed new_market k 2,801 1,369 94ms 339ms 2.8min 5.1min 0 transport_latency_assumed price_change h 106,902,786 9,462,804 19ms 64ms 428ms 46.0s 0 transport_latency_assumed price_change i 97,830,703 4,978,641 22ms 46ms 263ms 8.0s 0 transport_latency_assumed price_change k 106,888,186 92,491,645 13ms 37ms 248ms 13.8s 0 transport_latency_assumed tick_size_change h 2,352 239 19ms 76ms 445ms 980ms 0 transport_latency_assumed tick_size_change i 2,232 152 22ms 59ms 258ms 345ms 0 transport_latency_assumed tick_size_change k 2,352 1,961 14ms 54ms 310ms 413ms 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/18/2026-09-25T18.parquet sha256sum 2026-09-25T18.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.