Hour audit: 2026-09-25T21
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-25T21 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-25T21:00:00.000156888+00:00 · last event 2026-09-25T21:59:59.999673851+00:00
VOLUME 109,357,767 rows · 1,138,607,484 bytes (1.06 GiB) · 7 products, all holding rows
WITNESSES hik — 3 machines contributed rows
captured k: 108,823,328 · i: 108,680,131 · h: 103,994,688 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 98,815,583 (90.36%) · i: 4,221,563 (3.86%) · h: 6,320,621 (5.78%) (rows of the merged file that came from it; these partition it)
5 expected (cghik), 2 contributed nothing: c, g
INTEGRITY sha256 70ddaa6108e2b678bddfb695280364bd43c1d755ca87db2f57449602f7d86ee5
the corpus checksum ledger names this file with the same digest
joined 109,358,695 to merged 109,357,767, minus 928 (minus 0.0008%)
boundary drops 928 · 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-26T00:40:35Z 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,027,092 110,922,580 0-38 10613d62e30b2ea56ddfc51a28ec95508d7212d262dd21784d75cfa87cafaac4 book 744,411 60,742,213 39-41 98e916942e0bdd37b08be7843d147a429e67c906c450523981ec43d3e14b8f0d last_trade_price 50,005 2,886,585 42-42 cf5c2bb6b66353dda899974ed9d96eb88bcf4d200b8579c8e451a6188c8820e0 market_resolved 475 69,891 43-43 42262f19cd070c31aba5631d71bb9f20d5d4d603758e612799598cda1dab2c90 new_market 1,918 209,898 44-44 92970431594f63cc03aeccf89ee2aa7638b2c0bfc1d36e95fe4719a78b8d3fe1 price_change 98,531,170 962,435,288 45-420 847bfcc6e4ce3b4a962d950ed2848394bf6a0b1288cdb7d7747390539329cdbb tick_size_change 2,696 98,268 421-421 6536e9b35c315038eeae465f2dc9d02c92daa768ed8f2f3f77a847b6086605af EVENT MIX count share price_change 98,531,170 90.10% best_bid_ask 10,027,092 9.17% book 744,411 0.68% last_trade_price 50,005 0.05% tick_size_change 2,696 <0.01% new_market 1,918 <0.01% market_resolved 475 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,027,116 10,027,092 24 50,221 PARTIAL book 745,105 744,411 694 216,604 PARTIAL last_trade_price 50,005 50,005 0 3,896 PARTIAL market_resolved 475 475 0 432 PARTIAL new_market 1,918 1,918 0 1,401 PARTIAL price_change 98,531,380 98,531,170 210 86,516 PARTIAL tick_size_change 2,696 2,696 0 674 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 9,540,197 488,228 18ms 50ms 251ms 1.2min 0 transport_latency_assumed best_bid_ask i 10,025,869 350,449 20ms 27ms 137ms 5.4s 0 transport_latency_assumed best_bid_ask k 10,024,887 9,188,415 12ms 19ms 148ms 11.9s 0 transport_latency_assumed book h 681,996 540,688 1.1h 4.0d 34.3d 119.0d 0 book_staleness book i 104,235 10,115 22ms 172ms 58.9min 100.3d 0 book_staleness book k 271,982 193,608 1.3min 3.1d 34.3d 119.0d 0 book_staleness last_trade_price h 47,920 4,002 20ms 85ms 478ms 40.8s 0 transport_latency_assumed last_trade_price i 49,822 2,408 22ms 104ms 596ms 2.7s 0 transport_latency_assumed last_trade_price k 49,724 43,595 13ms 47ms 333ms 10.5s 0 transport_latency_assumed market_resolved h 449 50 28ms 42.9s 8.7min 9.3min 0 transport_latency_assumed market_resolved i 432 14 22ms 123ms 36.7s 39.7s 0 transport_latency_assumed market_resolved k 432 411 14ms 133ms 53.7s 56.2s 0 transport_latency_assumed new_market h 1,425 573 120ms 16.3s 4.8min 241.0d 0 transport_latency_assumed new_market i 1,401 670 116ms 33.4s 2.1min 241.0d 0 transport_latency_assumed new_market k 1,401 675 108ms 22.9s 2.2min 241.0d 0 transport_latency_assumed price_change h 93,720,201 5,286,974 18ms 54ms 296ms 1.5min 0 transport_latency_assumed price_change i 98,495,676 3,857,852 20ms 33ms 210ms 6.2s 0 transport_latency_assumed price_change k 98,472,206 89,386,344 12ms 23ms 166ms 12.1s 0 transport_latency_assumed tick_size_change h 2,500 106 18ms 44ms 87ms 253ms 0 transport_latency_assumed tick_size_change i 2,696 55 20ms 24ms 53ms 134ms 0 transport_latency_assumed tick_size_change k 2,696 2,535 12ms 15ms 82ms 233ms 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/21/2026-09-25T21.parquet sha256sum 2026-09-25T21.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.