Hour audit: 2026-10-05T15
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-05T15 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-05T15:00:00.000402461+00:00 · last event 2026-10-05T15:59:59.999894847+00:00
VOLUME 116,970,124 rows · 1,323,978,578 bytes (1.23 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured h: 116,145,699 · o: 115,929,429 · i: 115,895,326 · n: 115,868,582 · m: 115,767,512 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 1,240,716 (1.06%) · o: 59,450,189 (50.83%) · i: 1,082,347 (0.93%) · n: 77,468 (0.07%) · m: 55,119,404 (47.12%) (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 116,970,124 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 fb9c01272e5a7bfdaeb45d48b5aea91055cece336ce8c4f4ad1e4a71d81e521c
the corpus checksum ledger names this file with the same digest
joined 116,971,105 to merged 116,970,124, minus 981 (minus 0.0008%)
boundary drops 981 · 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-05T17:01:59Z 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,915,950 126,463,097 0-37 3c62c3de2964359e7dd12ca321ec2bb0a88274b5a7ccbe4a92784ed0dcb8dda2 book 154,899 17,573,684 38-38 f588e8e5fec1b017b76ca9bd5828b8915aaded885567defda3f6dcaf883167d6 last_trade_price 65,838 3,714,480 39-39 cfb80a18741440d4ae95322dbaf8abdabda97f969c25bf298a0ddfedff010b61 market_resolved 1,333 194,677 40-40 aba4418390b50f6fc51f9582339d4df2eb0bae7b63873d383969e350f01b766c new_market 3,162 303,653 41-41 4bf18898b9f0f405015972a8a7fe3aee29acc3936cee5fcf81aa49d1521b23f4 price_change 106,825,962 1,174,285,711 42-449 16ecac0e35f22b92507770acbe598a56c98531a56bc152742a30802b3799e80d tick_size_change 2,980 110,680 450-450 dbdc6571070f92105346e4d5c39f77bb6536f36248615d23b791a3340282b234 EVENT MIX count share price_change 106,825,962 91.33% best_bid_ask 9,915,950 8.48% book 154,899 0.13% last_trade_price 65,838 0.06% new_market 3,162 <0.01% tick_size_change 2,980 <0.01% market_resolved 1,333 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,916,046 9,915,950 96 3,009 FULL book 154,903 154,899 4 7,362 FULL last_trade_price 65,839 65,838 1 137 FULL market_resolved 1,333 1,333 0 21 FULL new_market 3,162 3,162 0 0 FULL price_change 106,826,842 106,825,962 880 6,508 FULL tick_size_change 2,980 2,980 0 30 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 9,849,152 100,092 19ms 36ms 331ms 54.5s 0 transport_latency_assumed best_bid_ask i 9,854,800 85,047 22ms 38ms 237ms 9.5s 0 transport_latency_assumed best_bid_ask m 9,820,509 4,708,907 6ms 20ms 128ms 5.3s 0 transport_latency_assumed best_bid_ask n 9,864,785 3,175 45ms 78ms 440ms 24.8s 0 transport_latency_assumed best_bid_ask o 9,807,766 5,018,729 6ms 19ms 120ms 9.7s 0 transport_latency_assumed book h 138,250 4,867 26ms 352ms 1.7h 110.2d 0 book_staleness book i 136,404 6,198 28ms 993ms 4.0h 110.1d 0 book_staleness book m 138,880 68,100 8ms 72ms 3.1h 127.1d 0 book_staleness book n 136,373 7,608 66ms 5.0s 7.9h 128.7d 0 book_staleness book o 136,226 68,126 8ms 45ms 6.6s 110.2d 0 book_staleness last_trade_price h 65,578 581 22ms 195ms 1.3s 26.2s 0 transport_latency_assumed last_trade_price i 64,206 614 27ms 481ms 3.1s 9.3s 0 transport_latency_assumed last_trade_price m 65,372 31,334 7ms 31ms 232ms 2.2s 0 transport_latency_assumed last_trade_price n 62,975 123 66ms 3.2s 11.0s 24.9s 0 transport_latency_assumed last_trade_price o 65,553 33,186 7ms 29ms 215ms 8.9s 0 transport_latency_assumed market_resolved h 1,203 94 21ms 114ms 53.3s 2.4min 0 transport_latency_assumed market_resolved i 1,200 214 25ms 33.0s 49.1s 2.4min 0 transport_latency_assumed market_resolved m 1,204 484 8ms 38.0s 54.0s 2.1min 0 transport_latency_assumed market_resolved n 1,202 2 47ms 360ms 49.3s 2.2min 0 transport_latency_assumed market_resolved o 1,200 539 8ms 38.7s 52.8s 2.5min 0 transport_latency_assumed new_market h 1,943 470 152ms 2.8min 3.3min 3.4min 0 transport_latency_assumed new_market i 1,943 629 53ms 1.8min 3.3min 3.4min 0 transport_latency_assumed new_market m 1,943 808 59ms 1.2min 3.2min 3.4min 0 transport_latency_assumed new_market n 1,943 410 209ms 3.1min 3.3min 3.4min 0 transport_latency_assumed new_market o 1,943 845 64ms 3.0min 3.3min 3.4min 0 transport_latency_assumed price_change h 106,086,601 1,134,574 19ms 51ms 614ms 55.2s 0 transport_latency_assumed price_change i 105,833,821 989,605 22ms 58ms 1.1s 9.5s 0 transport_latency_assumed price_change m 105,736,652 50,308,384 6ms 23ms 170ms 5.9s 0 transport_latency_assumed price_change n 105,798,336 66,150 46ms 151ms 4.8s 25.1s 0 transport_latency_assumed price_change o 105,913,805 54,327,249 6ms 22ms 157ms 10.5s 0 transport_latency_assumed tick_size_change h 2,972 38 20ms 40ms 148ms 20.8s 0 transport_latency_assumed tick_size_change i 2,952 40 22ms 46ms 143ms 381ms 0 transport_latency_assumed tick_size_change m 2,952 1,387 6ms 21ms 80ms 282ms 0 transport_latency_assumed tick_size_change n 2,968 not meas. 46ms 75ms 263ms 358ms 0 transport_latency_assumed tick_size_change o 2,936 1,515 6ms 21ms 72ms 222ms 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/15/2026-10-05T15.parquet sha256sum 2026-10-05T15.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.