Hour audit: 2026-10-05T13
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-05T13 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-05T13:00:00.000451301+00:00 · last event 2026-10-05T13:59:59.999890769+00:00
VOLUME 111,171,479 rows · 1,248,134,871 bytes (1.16 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured h: 110,523,295 · n: 110,412,099 · m: 110,068,974 · o: 110,000,267 · i: 109,500,646 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 769,563 (0.69%) · n: 42,169 (0.04%) · m: 55,963,700 (50.34%) · o: 53,906,488 (48.49%) · i: 489,559 (0.44%) (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 111,171,479 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 90e4c5923a888f111f2fea7595860bf2a504028b3e0be25528a1745e2e8fa7b1
the corpus checksum ledger names this file with the same digest
joined 111,172,009 to merged 111,171,479, minus 530 (minus 0.0005%)
boundary drops 530 · 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-05T15:00:20Z 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,905,768 124,820,822 0-37 01a645037fb27e9fb439f47d47b779e6014db3af55f1cd638e86b6ac1f2702ee book 136,227 15,155,113 38-38 75f0ae1d6080e166d677b6f4cae278ade21532eb577497eb892731424fb06d8f last_trade_price 59,253 3,403,985 39-39 8309de380edf045bc7df7f12ad8c038e78842760db32a32b9cba82b1c4cb89ab market_resolved 999 154,005 40-40 1e1a1f214c9487c93bb9444cfa7043c53f6d39652af350050ac6caba1880cd6b new_market 1,408 139,933 41-41 0b10df6ff154f1f11731e4f1c65969a0a5a3607660fd06b133079c6e0270ec3a price_change 101,063,996 1,103,054,809 42-427 36852cf700fa6886231416095a7f56f99709da0784c9adacbec5ac9fe5fbf872 tick_size_change 3,828 138,722 428-428 65a8b545645a4f1c564c7980832fb6968dda91075a2c71afd906acdbac9b00c9 EVENT MIX count share price_change 101,063,996 90.91% best_bid_ask 9,905,768 8.91% book 136,227 0.12% last_trade_price 59,253 0.05% tick_size_change 3,828 <0.01% new_market 1,408 <0.01% market_resolved 999 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,905,816 9,905,768 48 2,824 FULL book 136,229 136,227 2 6,446 FULL last_trade_price 59,253 59,253 0 126 FULL market_resolved 999 999 0 22 FULL new_market 1,408 1,408 0 0 FULL price_change 101,064,476 101,063,996 480 5,731 FULL tick_size_change 3,828 3,828 0 35 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 9,848,726 66,776 19ms 30ms 167ms 1.6min 0 transport_latency_assumed best_bid_ask i 9,815,766 40,796 21ms 32ms 125ms 7.3s 0 transport_latency_assumed best_bid_ask m 9,790,074 4,960,923 5ms 14ms 81ms 5.0s 0 transport_latency_assumed best_bid_ask n 9,852,871 1,912 44ms 65ms 266ms 18.8s 0 transport_latency_assumed best_bid_ask o 9,801,724 4,835,361 5ms 14ms 80ms 5.1s 0 transport_latency_assumed book h 124,214 5,598 23ms 181ms 3.8h 110.1d 0 book_staleness book i 118,435 2,407 25ms 191ms 10.5s 66.2d 0 book_staleness book m 122,073 66,051 7ms 32ms 46.7min 110.0d 0 book_staleness book n 123,561 6,016 51ms 2.7s 6.1h 110.1d 0 book_staleness book o 118,160 56,155 7ms 32ms 1.2min 110.0d 0 book_staleness last_trade_price h 59,082 484 21ms 103ms 683ms 19.9s 0 transport_latency_assumed last_trade_price i 57,651 293 24ms 151ms 1.1s 7.3s 0 transport_latency_assumed last_trade_price m 58,882 31,974 6ms 20ms 174ms 4.6s 0 transport_latency_assumed last_trade_price n 57,963 36 50ms 848ms 9.7s 18.8s 0 transport_latency_assumed last_trade_price o 57,437 26,466 6ms 23ms 156ms 4.8s 0 transport_latency_assumed market_resolved h 942 15 20ms 34.1s 49.2s 1.8min 0 transport_latency_assumed market_resolved i 942 166 23ms 22.7s 52.7s 2.4min 0 transport_latency_assumed market_resolved m 942 450 6ms 23.2s 56.1s 2.5min 0 transport_latency_assumed market_resolved n 939 not meas. 47ms 31.3s 43.4s 57.6s 0 transport_latency_assumed market_resolved o 943 368 6ms 27.9s 40.0s 1.7min 0 transport_latency_assumed new_market h 885 166 138ms 32.4s 39.5s 157.7d 0 transport_latency_assumed new_market i 885 244 103ms 31.2s 44.8s 157.8d 0 transport_latency_assumed new_market m 885 423 49ms 33.1s 47.7s 157.8d 0 transport_latency_assumed new_market n 885 123 165ms 26.2s 39.8s 157.8d 0 transport_latency_assumed new_market o 885 452 46ms 20.5s 35.7s 157.8d 0 transport_latency_assumed price_change h 100,485,630 696,496 19ms 37ms 298ms 1.6min 0 transport_latency_assumed price_change i 99,503,171 445,632 22ms 41ms 382ms 7.3s 0 transport_latency_assumed price_change m 100,092,314 50,901,836 5ms 16ms 94ms 5.4s 0 transport_latency_assumed price_change n 100,372,084 34,082 45ms 89ms 2.5s 18.8s 0 transport_latency_assumed price_change o 100,017,342 48,985,950 5ms 16ms 92ms 5.3s 0 transport_latency_assumed tick_size_change h 3,816 28 19ms 33ms 100ms 185ms 0 transport_latency_assumed tick_size_change i 3,796 21 22ms 40ms 83ms 301ms 0 transport_latency_assumed tick_size_change m 3,804 2,043 5ms 14ms 91ms 235ms 0 transport_latency_assumed tick_size_change n 3,796 not meas. 45ms 66ms 164ms 3.2s 0 transport_latency_assumed tick_size_change o 3,776 1,736 5ms 16ms 69ms 261ms 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-05/13/2026-10-05T13.parquet sha256sum 2026-10-05T13.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.