Hour audit: 2026-10-06T16
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 does not name this file. No line in the corpus checksum ledger names this file, so the documented verification step passes over it in silence rather than checking it. The manifest below still carries the digest.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-10-06T16 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-10-06T16:00:00.001502035+00:00 · last event 2026-10-06T16:59:59.999997240+00:00
VOLUME 118,397,188 rows · 1,371,585,386 bytes (1.28 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured i: 118,138,803 · o: 118,096,181 · h: 118,088,970 · m: 118,086,931 · n: 117,676,644 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 1,262,234 (1.07%) · o: 58,869,301 (49.72%) · h: 1,005,768 (0.85%) · m: 57,147,476 (48.27%) · n: 112,409 (0.09%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 118,397,188 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 3e5e8f9fef42e387f76eb53e29a556bf85ecd5ca91a62dbb0d5b0199669f2d75
no line in the corpus checksum ledger names this file
joined 118,398,720 to merged 118,397,188, minus 1,532 (minus 0.0013%)
boundary drops 1,532 · 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-06T18:05:40Z 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 does not name 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,574,972 135,623,767 0-40 271690b6cb05ee4620ab47b59845391d967404b5518be7ed72accc1c53f516dd book 393,716 40,127,567 41-42 b8b6360bb72b65d5dd85f3a06ee0521204e01681e6955556a0a3c56ee73ef7f0 last_trade_price 64,699 3,721,411 43-43 ff9539f65673db60f8d2f076cf41a25c86995e5ed5eee3c49f79ead3b19da271 market_resolved 1,176 194,099 44-44 76fa5c96e999f0315968ade1c2757352c8036341817adb6dabf3fecc7224d242 new_market 5,535 514,673 45-45 6a2f726f239e5aba7e7442764349a014072cae443388f2d1040c3cb0c4acf1e0 price_change 107,353,810 1,189,932,228 46-455 82c199ae09bc3b176f6c0d0b4e79e4ca1cf4e6224c5623e5895642e3b9f2cb5e tick_size_change 3,280 121,258 456-456 2647de5977f10eded477bc31c9e7bb2ee961dcd500a7d7dad588a1b843915e61 EVENT MIX count share price_change 107,353,810 90.67% best_bid_ask 10,574,972 8.93% book 393,716 0.33% last_trade_price 64,699 0.05% new_market 5,535 <0.01% tick_size_change 3,280 <0.01% market_resolved 1,176 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,575,064 10,574,972 92 127 FULL book 394,160 393,716 444 110,708 FULL last_trade_price 64,699 64,699 0 0 FULL market_resolved 1,176 1,176 0 0 FULL new_market 5,535 5,535 0 0 FULL price_change 107,354,806 107,353,810 996 62 FULL tick_size_change 3,280 3,280 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,573,554 87,956 20ms 47ms 443ms 56.7s 0 transport_latency_assumed best_bid_ask i 10,570,660 95,583 22ms 39ms 219ms 15.0s 0 transport_latency_assumed best_bid_ask m 10,574,323 5,140,315 5ms 19ms 142ms 4.7s 0 transport_latency_assumed best_bid_ask n 10,569,282 5,995 46ms 84ms 451ms 39.5s 0 transport_latency_assumed best_bid_ask o 10,574,556 5,245,123 5ms 19ms 155ms 7.1s 0 transport_latency_assumed book h 145,709 10,442 33ms 2.7s 1.2d 129.8d 0 book_staleness book i 356,304 220,391 1.5min 18.7h 45.1d 129.8d 0 book_staleness book m 144,416 73,549 8ms 661ms 18.2h 111.2d 0 book_staleness book n 148,954 14,760 67ms 14.3s 3.1d 129.8d 0 book_staleness book o 146,516 74,574 8ms 2.0s 1.3d 111.3d 0 book_staleness last_trade_price h 64,511 516 24ms 299ms 3.0s 38.6s 0 transport_latency_assumed last_trade_price i 64,163 521 28ms 412ms 4.4s 15.0s 0 transport_latency_assumed last_trade_price m 64,566 31,125 7ms 33ms 225ms 1.5s 0 transport_latency_assumed last_trade_price n 63,372 108 60ms 768ms 8.8s 39.5s 0 transport_latency_assumed last_trade_price o 64,631 32,429 7ms 34ms 232ms 2.9s 0 transport_latency_assumed market_resolved h 1,174 5 24ms 532ms 37.1s 38.3s 0 transport_latency_assumed market_resolved i 1,174 131 25ms 462ms 32.0s 1.1min 0 transport_latency_assumed market_resolved m 1,174 485 7ms 227ms 34.3s 1.2min 0 transport_latency_assumed market_resolved n 1,174 1 51ms 897ms 49.4s 50.6s 0 transport_latency_assumed market_resolved o 1,174 554 7ms 223ms 38.6s 40.3s 0 transport_latency_assumed new_market h 3,198 497 136ms 1.6min 21.0d 21.0d 0 transport_latency_assumed new_market i 3,198 986 82ms 1.4min 21.0d 21.0d 0 transport_latency_assumed new_market m 3,198 1,721 67ms 1.4min 21.0d 21.0d 0 transport_latency_assumed new_market n 3,198 431 205ms 1.7min 21.0d 21.0d 0 transport_latency_assumed new_market o 3,198 1,900 57ms 1.5min 21.0d 21.0d 0 transport_latency_assumed price_change h 107,297,544 906,272 20ms 67ms 954ms 56.7s 0 transport_latency_assumed price_change i 107,140,024 944,598 22ms 59ms 1.2s 15.0s 0 transport_latency_assumed price_change m 107,295,974 51,898,732 5ms 21ms 156ms 7.3s 0 transport_latency_assumed price_change n 106,887,384 91,114 47ms 129ms 2.9s 39.6s 0 transport_latency_assumed price_change o 107,302,826 53,513,094 5ms 22ms 167ms 7.1s 0 transport_latency_assumed tick_size_change h 3,280 80 21ms 45ms 276ms 23.6s 0 transport_latency_assumed tick_size_change i 3,280 24 22ms 51ms 292ms 2.1s 0 transport_latency_assumed tick_size_change m 3,280 1,549 6ms 24ms 195ms 522ms 0 transport_latency_assumed tick_size_change n 3,280 not meas. 46ms 77ms 231ms 10.2s 0 transport_latency_assumed tick_size_change o 3,280 1,627 5ms 28ms 82ms 432ms 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-06/16/2026-10-06T16.parquet sha256sum 2026-10-06T16.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.