Hour audit: 2026-10-08T06
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
- the checksum ledger and the manifest disagree on this file's digest. The checksum ledger and this hour's manifest publish DIFFERENT digests for the same file. One of the two is wrong and the file should not be trusted until that is resolved.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-10-08T06 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-10-08T06:00:00.000000326+00:00 · last event 2026-10-08T06:59:59.999989467+00:00
VOLUME 116,325,458 rows · 1,328,525,851 bytes (1.24 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 115,767,182 · m: 115,757,809 · h: 115,736,295 · n: 115,707,544 · i: 115,554,962 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 55,355,913 (47.59%) · m: 59,153,454 (50.85%) · h: 988,083 (0.85%) · n: 264,100 (0.23%) · i: 563,908 (0.48%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 116,325,458 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 91557e1e6dc42bbc6026fbd067d8648487022bcef127d185cc99f5aea54afecf
the corpus checksum ledger names this file with a DIFFERENT digest
joined 116,334,956 to merged 116,325,458, minus 9,498 (minus 0.0082%)
boundary drops 9,498 · 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-10-09T11:38:37Z as himno
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
PASS every expected machine contributed
FINDING the checksum ledger and the manifest disagree on this file's digest
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 11,349,907 139,880,846 0-43 b35a3befa0d0e2e93a999506f317ddf16ce05adf037e6882fe15c92229c4a483 book 823,676 69,518,295 44-47 88bb4162aaea93e6c647f9d43c694255a1ea6b5cba0aece33a6372fff148caa7 last_trade_price 42,805 2,508,825 48-48 88602888065f8e2c8d7fb6b14f941e2cb77fa1a2c1ea032fd0cdc546a0dbd832 market_resolved 922 147,875 49-49 6d611453a439f5b0138c64000f1a795e074fcd866b14461eee8136c912d8f74b new_market 366 41,010 50-50 cb2d7bdfcf0fbe1498ef0ec5e38a54f00ced503a6a7c09ed7e9acb6780cbf145 price_change 104,105,850 1,115,027,325 51-448 2a521a191b02ea6d37ac2b2907242ea919b6cc34de32506637c86de5364ac5e3 tick_size_change 1,932 72,100 449-449 c22382a6d2d484035ee1198afe122c051435b04779bf43d28091bc5e43d32796 EVENT MIX count share price_change 104,105,850 89.50% best_bid_ask 11,349,907 9.76% book 823,676 0.71% last_trade_price 42,805 0.04% tick_size_change 1,932 <0.01% market_resolved 922 <0.01% new_market 366 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,350,089 11,349,907 182 54 FULL book 830,988 823,676 7,312 235,602 FULL last_trade_price 42,807 42,805 2 0 FULL market_resolved 922 922 0 0 FULL new_market 366 366 0 0 FULL price_change 104,107,852 104,105,850 2,002 48 FULL tick_size_change 1,932 1,932 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 11,347,578 63,350 18ms 30ms 159ms 46.9s 0 transport_latency_assumed best_bid_ask i 11,348,294 41,224 21ms 28ms 96ms 1.8s 0 transport_latency_assumed best_bid_ask m 11,348,905 5,821,357 5ms 12ms 69ms 3.2s 0 transport_latency_assumed best_bid_ask n 11,346,615 1,984 43ms 53ms 168ms 9.8s 0 transport_latency_assumed best_bid_ask o 11,348,664 5,421,992 5ms 12ms 66ms 3.5s 0 transport_latency_assumed book h 311,427 174,334 4.5min 2.4h 46.7d 131.4d 0 book_staleness book i 123,760 23,125 28ms 2.1h 30.8d 131.3d 0 book_staleness book m 305,540 195,681 3.8min 2.6h 46.7d 131.3d 0 book_staleness book n 398,068 231,250 6.6min 2.6h 46.7d 131.4d 0 book_staleness book o 308,909 199,286 4.4min 2.5h 46.7d 131.4d 0 book_staleness last_trade_price h 42,587 360 20ms 71ms 439ms 25.3s 0 transport_latency_assumed last_trade_price i 42,669 236 23ms 87ms 616ms 1.3s 0 transport_latency_assumed last_trade_price m 42,745 21,435 6ms 22ms 157ms 1.2s 0 transport_latency_assumed last_trade_price n 42,574 5 47ms 694ms 6.4s 9.7s 0 transport_latency_assumed last_trade_price o 42,716 20,769 6ms 19ms 135ms 1.2s 0 transport_latency_assumed market_resolved h 906 21 21ms 20.8s 34.2s 43.8s 0 transport_latency_assumed market_resolved i 906 16 23ms 11.7s 25.8s 57.1s 0 transport_latency_assumed market_resolved m 906 497 6ms 11.7s 25.8s 57.1s 0 transport_latency_assumed market_resolved n 906 not meas. 46ms 30.5s 44.4s 54.0s 0 transport_latency_assumed market_resolved o 906 388 6ms 13.2s 26.8s 51.1s 0 transport_latency_assumed new_market h 263 56 45ms 11.4s 36.3s 1.6min 0 transport_latency_assumed new_market i 263 45 41ms 8.4s 43.3s 1.6min 0 transport_latency_assumed new_market m 263 137 27ms 13.0s 19.9s 1.5min 0 transport_latency_assumed new_market n 263 27 73ms 13.9s 1.2min 1.7min 0 transport_latency_assumed new_market o 263 101 37ms 14.5s 19.8s 1.2min 0 transport_latency_assumed price_change h 104,031,602 749,938 18ms 35ms 243ms 48.4s 0 transport_latency_assumed price_change i 104,037,138 499,258 21ms 34ms 256ms 2.5s 0 transport_latency_assumed price_change m 104,057,518 53,113,398 5ms 14ms 103ms 3.3s 0 transport_latency_assumed price_change n 103,917,186 30,834 44ms 68ms 1.9s 10.0s 0 transport_latency_assumed price_change o 104,063,792 49,712,422 5ms 14ms 97ms 3.5s 0 transport_latency_assumed tick_size_change h 1,932 24 18ms 34ms 127ms 294ms 0 transport_latency_assumed tick_size_change i 1,932 4 21ms 33ms 72ms 86ms 0 transport_latency_assumed tick_size_change m 1,932 949 5ms 13ms 80ms 126ms 0 transport_latency_assumed tick_size_change n 1,932 not meas. 44ms 58ms 113ms 1.3s 0 transport_latency_assumed tick_size_change o 1,932 955 5ms 15ms 92ms 289ms 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-10-08/06/2026-10-08T06.parquet sha256sum 2026-10-08T06.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.