Hour audit: 2026-10-07T20
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-10-07T20 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-07T20:00:00.000128772+00:00 · last event 2026-10-07T20:59:59.999988729+00:00
VOLUME 101,629,275 rows · 1,189,886,595 bytes (1.11 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured i: 101,011,902 · m: 100,829,444 · o: 100,823,952 · n: 100,688,024 · h: 100,666,526 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 1,075,650 (1.06%) · m: 50,535,398 (49.73%) · o: 48,994,620 (48.21%) · n: 253,684 (0.25%) · h: 769,923 (0.76%) (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 101,629,275 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 78b2a57f6e756339421a4438ea606431be2958f48199a5d8ebb9159f90d39f50
the corpus checksum ledger names this file with the same digest
joined 101,635,675 to merged 101,629,275, minus 6,400 (minus 0.0063%)
boundary drops 6,400 · 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-07T21:59:55Z 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 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,066,242 117,830,896 0-34 a220ef5ceddba090c4cecd4e039042d9a4ab5be3dc32e030b657d362a086effd book 1,146,543 86,896,773 35-39 5b599cd14a5d1a4ac6b4524095dde203a5518dd719cca6872d2b188bb913a2a2 last_trade_price 49,056 2,834,850 40-40 a94e8d11795bf27c668413257d584b36834e44cb181fb6b2afb9b46779f3cf3b market_resolved 638 99,686 41-41 39b109cff6c26e75b99130536ff4706396db5e49082cd1fd64589428a01c0ca9 new_market 2,662 272,715 42-42 ba5b6617b0537adc4504e6390225112ae976b57ca43be7fadc3987e902e72418 price_change 91,361,670 980,697,812 43-391 761c94d50ee3442f23bd093d696eb48d055c10802adaf9431397d27ef77cce08 tick_size_change 2,464 92,075 392-392 50b382d5a472a80a1b638655a9409a32aa5d71be0e4fb512111a7dbd65f927a9 EVENT MIX count share price_change 91,361,670 89.90% best_bid_ask 9,066,242 8.92% book 1,146,543 1.13% last_trade_price 49,056 0.05% new_market 2,662 <0.01% tick_size_change 2,464 <0.01% market_resolved 638 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,066,485 9,066,242 243 85 FULL book 1,150,433 1,146,543 3,890 251,151 FULL last_trade_price 49,057 49,056 1 5 FULL market_resolved 638 638 0 0 FULL new_market 2,662 2,662 0 0 FULL price_change 91,363,936 91,361,670 2,266 86 FULL tick_size_change 2,464 2,464 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 9,062,428 56,384 18ms 30ms 519ms 54.5s 0 transport_latency_assumed best_bid_ask i 9,063,087 64,840 21ms 31ms 195ms 6.6s 0 transport_latency_assumed best_bid_ask m 9,064,048 4,547,908 5ms 13ms 143ms 4.9s 0 transport_latency_assumed best_bid_ask n 9,062,555 3,486 43ms 63ms 455ms 19.2s 0 transport_latency_assumed best_bid_ask o 9,064,816 4,393,624 5ms 13ms 180ms 11.8s 0 transport_latency_assumed book h 291,683 111,128 1.7min 1.1d 46.3d 130.9d 0 book_staleness book i 613,492 356,405 8.9min 1.9d 46.3d 130.9d 0 book_staleness book m 408,369 239,264 4.6min 1.3d 46.3d 130.9d 0 book_staleness book n 433,340 210,994 5.0min 1.4d 46.3d 130.9d 0 book_staleness book o 398,816 228,752 4.3min 1.3d 46.3d 130.9d 0 book_staleness last_trade_price h 48,654 291 21ms 235ms 2.0s 51.9s 0 transport_latency_assumed last_trade_price i 48,767 234 25ms 368ms 1.8s 4.8s 0 transport_latency_assumed last_trade_price m 48,863 25,370 6ms 23ms 221ms 1.9s 0 transport_latency_assumed last_trade_price n 48,702 35 59ms 1.9s 12.4s 19.2s 0 transport_latency_assumed last_trade_price o 48,994 23,126 6ms 29ms 245ms 3.2s 0 transport_latency_assumed market_resolved h 607 4 34ms 45.2s 51.3s 51.6s 0 transport_latency_assumed market_resolved i 607 155 39ms 34.6s 40.8s 41.1s 0 transport_latency_assumed market_resolved m 607 227 7ms 34.8s 41.0s 41.1s 0 transport_latency_assumed market_resolved n 607 32 59ms 41.1s 55.1s 55.2s 0 transport_latency_assumed market_resolved o 607 220 7ms 34.7s 40.8s 41.1s 0 transport_latency_assumed new_market h 1,659 308 203ms 13.9s 58.5s 454.1d 0 transport_latency_assumed new_market i 1,659 398 129ms 16.7s 55.4s 454.1d 0 transport_latency_assumed new_market m 1,659 837 85ms 16.1s 51.7s 454.1d 0 transport_latency_assumed new_market n 1,659 371 225ms 16.1s 56.1s 454.2d 0 transport_latency_assumed new_market o 1,659 748 101ms 13.5s 59.6s 454.1d 0 transport_latency_assumed price_change h 91,259,031 601,780 18ms 40ms 764ms 1.3min 0 transport_latency_assumed price_change i 91,281,826 653,610 21ms 43ms 547ms 9.1s 0 transport_latency_assumed price_change m 91,303,434 45,720,508 5ms 14ms 159ms 6.1s 0 transport_latency_assumed price_change n 91,138,697 38,766 44ms 107ms 2.4s 19.2s 0 transport_latency_assumed price_change o 91,306,596 44,347,006 5ms 15ms 190ms 12.0s 0 transport_latency_assumed tick_size_change h 2,464 28 18ms 24ms 110ms 789ms 0 transport_latency_assumed tick_size_change i 2,464 8 21ms 31ms 77ms 154ms 0 transport_latency_assumed tick_size_change m 2,464 1,284 5ms 12ms 73ms 278ms 0 transport_latency_assumed tick_size_change n 2,464 not meas. 43ms 56ms 223ms 687ms 0 transport_latency_assumed tick_size_change o 2,464 1,144 5ms 12ms 58ms 179ms 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-07/20/2026-10-07T20.parquet sha256sum 2026-10-07T20.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.