Hour audit: 2026-09-26T10
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-26T10 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-26T10:00:00.000244348+00:00 · last event 2026-09-26T10:59:59.999813698+00:00
VOLUME 97,320,791 rows · 976,402,554 bytes (931.17 MiB) · 7 products, all holding rows
WITNESSES hik — 3 machines contributed rows
captured i: 97,277,038 · k: 97,274,158 · h: 97,264,153 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 2,789,201 (2.87%) · k: 90,815,863 (93.32%) · h: 3,715,727 (3.82%) (rows of the merged file that came from it; these partition it)
5 expected (cghik), 2 contributed nothing: c, g
INTEGRITY sha256 2b3e228546fc74b6cb0ac242e326ffd3d638dc36082e2684524d58f2654078ea
the corpus checksum ledger names this file with the same digest
joined 97,323,057 to merged 97,320,791, minus 2,266 (minus 0.0023%)
boundary drops 2,266 · 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-26T11:51:29Z 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,236,742 110,422,030 0-39 955a2b023b774ad32c3adea7f7263f3656c7dd0d24ac2c1cfff2ae9e9a6e6647 book 99,610 10,226,284 40-40 77b92899d78ca220a2d8caa789004ef8b51c755e998a8d56dcfcf4ad395a9f6a last_trade_price 45,950 2,646,753 41-41 ba532a0d7ac1803d6283cee05dad6e70bb645905ec48c4007a38376346a3d3ee market_resolved 494 82,268 42-42 f63f67bfff706ed7a8bd2dda2e67e60ed1e0f164899578d8d2bc86c10aec63f6 new_market 557 64,808 43-43 4374ba30da773955ef3ea6474b5e7e2a2d2966b51b2eebb2b8601ac2565780c1 price_change 86,934,574 851,745,488 44-375 dabe04bb54465fc3caad1c98b19a7e384070490455cd156d538b1a458302d27c tick_size_change 2,864 105,176 376-376 f8b1ad34d305564a5973d582069b872c00910259e90b9e59c303c962f7f462a8 EVENT MIX count share price_change 86,934,574 89.33% best_bid_ask 10,236,742 10.52% book 99,610 0.10% last_trade_price 45,950 0.05% tick_size_change 2,864 <0.01% new_market 557 <0.01% market_resolved 494 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,236,776 10,236,742 34 45,333 PARTIAL book 99,610 99,610 0 5,620 PARTIAL last_trade_price 45,950 45,950 0 2,964 PARTIAL market_resolved 494 494 0 494 PARTIAL new_market 557 557 0 425 PARTIAL price_change 86,936,806 86,934,574 2,232 86,536 PARTIAL tick_size_change 2,864 2,864 0 716 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,235,934 344,322 18ms 22ms 86ms 6.7s 0 transport_latency_assumed best_bid_ask i 10,236,006 256,292 19ms 24ms 70ms 6.2s 0 transport_latency_assumed best_bid_ask k 10,235,934 9,636,128 12ms 16ms 61ms 5.0s 0 transport_latency_assumed book h 94,512 8,745 22ms 53ms 6.5h 56.8d 0 book_staleness book i 94,398 8,929 21ms 72ms 3.3h 100.8d 0 book_staleness book k 95,990 81,936 15ms 45ms 23.7h 101.0d 0 book_staleness last_trade_price h 45,740 2,834 19ms 38ms 252ms 4.2s 0 transport_latency_assumed last_trade_price i 45,779 1,616 21ms 51ms 418ms 3.9s 0 transport_latency_assumed last_trade_price k 45,725 41,500 13ms 24ms 179ms 1.2s 0 transport_latency_assumed market_resolved h 494 18 19ms 52ms 40.3s 41.9s 0 transport_latency_assumed market_resolved i 494 23 20ms 57ms 40.2s 41.8s 0 transport_latency_assumed market_resolved k 494 453 13ms 31ms 43.9s 45.5s 0 transport_latency_assumed new_market h 425 203 65ms 10.7s 52.7s 1.8min 0 transport_latency_assumed new_market i 425 166 68ms 11.3s 44.1s 49.5s 0 transport_latency_assumed new_market k 425 188 63ms 9.2s 43.2s 1.7min 0 transport_latency_assumed price_change h 86,884,184 3,359,456 18ms 25ms 133ms 6.9s 0 transport_latency_assumed price_change i 86,897,072 2,522,088 19ms 25ms 128ms 6.2s 0 transport_latency_assumed price_change k 86,892,726 81,053,030 12ms 17ms 82ms 5.0s 0 transport_latency_assumed tick_size_change h 2,864 149 18ms 28ms 120ms 780ms 0 transport_latency_assumed tick_size_change i 2,864 87 20ms 26ms 66ms 207ms 0 transport_latency_assumed tick_size_change k 2,864 2,628 12ms 18ms 71ms 137ms 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-26/10/2026-09-26T10.parquet sha256sum 2026-09-26T10.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.