Hour audit: 2026-09-28T23
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-28T23 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-28T23:00:00.000021390+00:00 · last event 2026-09-28T23:59:59.999925070+00:00
VOLUME 87,065,326 rows · 915,776,716 bytes (873.35 MiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured c: 86,995,676 · h: 86,968,466 · i: 86,957,841 · k: 86,953,235 · g: 86,362,071 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 77,619,439 (89.15%) · h: 2,997,506 (3.44%) · i: 1,960,649 (2.25%) · k: 4,439,575 (5.10%) · g: 48,157 (0.06%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 4e0032f435316be6b834d4fe821c06239df6f5a4584a14ceb5bb8b3bb292bbcf
the corpus checksum ledger names this file with the same digest
joined 87,067,115 to merged 87,065,326, minus 1,789 (minus 0.0021%)
boundary drops 1,789 · 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-29T01:39:54Z 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 9,417,988 110,107,448 0-35 0e8a8808e3fc27a9ceca95e077b585f7eff75463a3c31152dfd1740d7ea81f45 book 168,184 14,624,192 36-36 a59ed5aaa84e515adedfa2b1010d779bf0cc7efb835061a8fb26014b2d40806f last_trade_price 60,485 3,280,536 37-37 368cd1012654b82172a0c97ef633e9ad1d425dbd61631fe83b14e7e9eb33b1ab market_resolved 869 136,243 38-38 9733cf1f713afd999c60fafcb62ee91a1b65c0f2c402c838446a123fa9e30ac0 new_market 9,562 951,125 39-39 e1c0661a8ada72fb20e4a962ce8284c4d97432896ad1bc4e103c364f35913629 price_change 77,405,686 785,588,793 40-335 ca4b1cba242750b87429a73ba013127b4b96e400d4413df160161558a4a97c0f tick_size_change 2,552 94,498 336-336 e73ecbff6162f86723e9fa6cfd5740b1252f8ee58b13631eac4212d8531b7dba EVENT MIX count share price_change 77,405,686 88.91% best_bid_ask 9,417,988 10.82% book 168,184 0.19% last_trade_price 60,485 0.07% new_market 9,562 0.01% tick_size_change 2,552 <0.01% market_resolved 869 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,418,259 9,417,988 271 1,415 FULL book 168,198 168,184 14 10,150 FULL last_trade_price 60,485 60,485 0 0 FULL market_resolved 869 869 0 0 FULL new_market 9,562 9,562 0 0 FULL price_change 77,407,190 77,405,686 1,504 989 FULL tick_size_change 2,552 2,552 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,413,727 8,467,554 5ms 22ms 235ms 7.9s 0 transport_latency_assumed best_bid_ask g 9,386,608 4,342 83ms 204ms 865ms 28.5s 0 transport_latency_assumed best_bid_ask h 9,411,843 312,726 17ms 38ms 651ms 58.7s 0 transport_latency_assumed best_bid_ask i 9,412,106 200,386 23ms 40ms 296ms 34.9s 0 transport_latency_assumed best_bid_ask k 9,411,333 432,980 13ms 39ms 366ms 37.8s 0 transport_latency_assumed book c 143,035 119,477 8ms 2.4s 1.8d 122.0d 0 book_staleness book g 121,737 10,850 172ms 13.2s 1.8d 103.5d 0 book_staleness book h 134,886 10,019 24ms 522ms 5.2h 103.5d 0 book_staleness book i 134,901 9,099 29ms 435ms 4.8h 103.4d 0 book_staleness book k 140,820 18,739 18ms 1.9s 1.4d 103.5d 0 book_staleness last_trade_price c 60,268 52,233 6ms 53ms 311ms 3.7s 0 transport_latency_assumed last_trade_price g 50,374 28 140ms 5.0s 20.0s 28.4s 0 transport_latency_assumed last_trade_price h 60,085 2,007 20ms 148ms 1.2s 37.2s 0 transport_latency_assumed last_trade_price i 60,022 1,888 25ms 145ms 723ms 6.7s 0 transport_latency_assumed last_trade_price k 60,072 4,329 14ms 89ms 397ms 6.5s 0 transport_latency_assumed market_resolved c 841 710 5ms 88ms 48.6s 56.4s 0 transport_latency_assumed market_resolved g 841 8 89ms 519ms 52.7s 53.2s 0 transport_latency_assumed market_resolved h 841 30 19ms 138ms 46.0s 53.4s 0 transport_latency_assumed market_resolved i 841 79 31ms 226ms 53.4s 53.4s 0 transport_latency_assumed market_resolved k 841 42 14ms 120ms 47.1s 54.3s 0 transport_latency_assumed new_market c 6,009 2,902 110ms 1.0min 1.7min 2.5min 0 transport_latency_assumed new_market g 6,009 719 267ms 57.7s 1.6min 2.4min 0 transport_latency_assumed new_market h 6,009 2,622 124ms 57.3s 1.7min 2.4min 0 transport_latency_assumed new_market i 6,009 1,968 116ms 52.4s 1.7min 2.5min 0 transport_latency_assumed new_market k 6,009 1,351 189ms 59.1s 1.7min 2.5min 0 transport_latency_assumed price_change c 77,369,244 68,974,248 5ms 27ms 245ms 9.8s 0 transport_latency_assumed price_change g 76,793,950 32,206 84ms 292ms 4.5s 28.5s 0 transport_latency_assumed price_change h 77,352,250 2,670,042 18ms 49ms 717ms 1.0min 0 transport_latency_assumed price_change i 77,341,410 1,747,172 24ms 51ms 356ms 34.9s 0 transport_latency_assumed price_change k 77,331,608 3,982,018 13ms 48ms 371ms 38.1s 0 transport_latency_assumed tick_size_change c 2,552 2,315 5ms 18ms 243ms 311ms 0 transport_latency_assumed tick_size_change g 2,552 4 82ms 166ms 569ms 1.0s 0 transport_latency_assumed tick_size_change h 2,552 60 18ms 37ms 369ms 1.6s 0 transport_latency_assumed tick_size_change i 2,552 57 24ms 45ms 256ms 1.0s 0 transport_latency_assumed tick_size_change k 2,552 116 13ms 28ms 434ms 814ms 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-28/23/2026-09-28T23.parquet sha256sum 2026-09-28T23.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.