Hour audit: 2026-09-26T07
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-26T07 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-26T07:00:00.000007864+00:00 · last event 2026-09-26T07:59:59.999895107+00:00
VOLUME 95,810,500 rows · 947,023,088 bytes (903.15 MiB) · 7 products, all holding rows
WITNESSES hik — 3 machines contributed rows
captured h: 95,721,853 · k: 95,710,706 · i: 95,702,497 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 3,838,942 (4.01%) · k: 89,851,187 (93.78%) · i: 2,120,371 (2.21%) (rows of the merged file that came from it; these partition it)
5 expected (cghik), 2 contributed nothing: c, g
INTEGRITY sha256 514b94a308aee342e0049ceaccfd577ebb56cd9658977bf9361efc9df88670c5
the corpus checksum ledger names this file with the same digest
joined 95,810,632 to merged 95,810,500, minus 132 (minus 0.0001%)
boundary drops 132 · 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-26T08:49:57Z 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,610,042 113,968,029 0-40 4560a31c9b4b762fb14eff65c0cfdeace2da02956e4baf9c198401040e0b98c0 book 184,157 18,554,394 41-41 9057dd42d0e22bd650605acd2840dbf038b092f6e3241567ac22725dd232d66a last_trade_price 43,133 2,510,713 42-42 3c297d07d0dc40b93896c0c7e40f8905025a98780c806dc3106ab6ced86e714c market_resolved 554 91,942 43-43 640415d51fe687d581af0a3c01a656201b0050d023684a3f437682ab9ad7cefa new_market 1,574 158,870 44-44 8fd2a76cc86bd2c9c74a90e7b039a8fdfcf6eb70a7dc50b76f66ac5430708cf2 price_change 84,969,276 810,584,513 45-369 daa66062649adc3065ab41cce2f94cc06c92e0628f760c496897ed5626426ed5 tick_size_change 1,764 62,672 370-370 700f7e6775c6a806405e2cff7edf89fe524cac3c05e3ff190a6a80db5e70e1ba EVENT MIX count share price_change 84,969,276 88.68% best_bid_ask 10,610,042 11.07% book 184,157 0.19% last_trade_price 43,133 0.05% tick_size_change 1,764 <0.01% new_market 1,574 <0.01% market_resolved 554 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,610,056 10,610,042 14 52,991 PARTIAL book 184,165 184,157 8 50,107 PARTIAL last_trade_price 43,133 43,133 0 3,096 PARTIAL market_resolved 554 554 0 554 PARTIAL new_market 1,574 1,574 0 1,054 PARTIAL price_change 84,969,386 84,969,276 110 95,040 PARTIAL tick_size_change 1,764 1,764 0 441 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,608,754 386,404 18ms 34ms 257ms 50.6s 0 transport_latency_assumed best_bid_ask i 10,608,932 203,808 20ms 24ms 100ms 4.2s 0 transport_latency_assumed best_bid_ask k 10,608,962 10,019,830 12ms 15ms 113ms 58.6s 0 transport_latency_assumed book h 130,257 45,104 28ms 15.8h 20.7d 119.4d 0 book_staleness book i 107,202 24,431 23ms 28.1min 16.9d 119.4d 0 book_staleness book k 128,807 114,622 17ms 14.3h 20.7d 117.8d 0 book_staleness last_trade_price h 43,070 2,122 19ms 51ms 393ms 42.6s 0 transport_latency_assumed last_trade_price i 43,101 1,534 22ms 38ms 287ms 2.8s 0 transport_latency_assumed last_trade_price k 43,079 39,477 13ms 22ms 273ms 10.3s 0 transport_latency_assumed market_resolved h 554 16 26ms 35.9s 43.5s 46.2s 0 transport_latency_assumed market_resolved i 554 74 22ms 35.3s 42.9s 45.3s 0 transport_latency_assumed market_resolved k 554 464 13ms 41.0s 48.6s 50.2s 0 transport_latency_assumed new_market h 1,054 520 212ms 28.4s 38.4s 1.7min 0 transport_latency_assumed new_market i 1,054 580 142ms 26.4s 34.9s 1.8min 0 transport_latency_assumed new_market k 1,054 474 207ms 21.9s 35.9s 1.6min 0 transport_latency_assumed price_change h 84,936,400 3,404,740 18ms 37ms 317ms 52.6s 0 transport_latency_assumed price_change i 84,939,890 1,889,940 21ms 25ms 178ms 5.0s 0 transport_latency_assumed price_change k 84,926,486 79,674,596 12ms 17ms 149ms 1.1min 0 transport_latency_assumed tick_size_change h 1,764 36 18ms 24ms 59ms 11.5s 0 transport_latency_assumed tick_size_change i 1,764 4 20ms 23ms 38ms 119ms 0 transport_latency_assumed tick_size_change k 1,764 1,724 12ms 14ms 33ms 37ms 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/07/2026-09-26T07.parquet sha256sum 2026-09-26T07.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.