Hour audit: 2026-10-06T02
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-06T02 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-06T02:00:00.000179212+00:00 · last event 2026-10-06T02:59:59.999953686+00:00
VOLUME 118,893,031 rows · 1,366,534,755 bytes (1.27 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured i: 118,335,558 · h: 118,315,723 · o: 118,294,153 · m: 118,206,140 · n: 117,932,763 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 1,711,490 (1.44%) · h: 1,142,253 (0.96%) · o: 56,129,135 (47.21%) · m: 59,744,177 (50.25%) · n: 165,976 (0.14%) (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,893,031 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 1eafca6b13d6a1e2895b0e472bf2672132b64b753c158a860daea913446b95d7
the corpus checksum ledger names this file with the same digest
joined 118,895,310 to merged 118,893,031, minus 2,279 (minus 0.0019%)
boundary drops 2,279 · 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-06T04:04:05Z 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 11,661,237 147,110,522 0-44 30f98cfcce64e14c3caa1ad3425fed3a88d0edbf4869e2c130b88680573aef81 book 572,805 52,644,660 45-47 496237f2459eaee8ce43938f4ebc1c12efed5d9ad81855ad06a6949b8eda024d last_trade_price 43,215 2,514,808 48-48 c862fb164fba171c16cd9b79fd91c5f2a53b4503018fbcbb94144aca86feded7 market_resolved 788 124,322 49-49 7e8f3a928e5b314db655cae0ebfa7978b2c37758a14a8ef07ec890b5d91059bd new_market 7,502 764,909 50-50 b49337d23f248367b5bc8681689d8178c27bce5b170de47cda57dbbfc6b1fd7e price_change 106,604,920 1,161,924,447 51-457 c149a3e43c3e3e8267a198bdc1d7a9df7340d94f236a00e3a47eb8d17d412621 tick_size_change 2,564 95,707 458-458 f6f150cc30753294cd2bc00ceee469ccd584566e5c1e6764d255499d70c3d73c EVENT MIX count share price_change 106,604,920 89.66% best_bid_ask 11,661,237 9.81% book 572,805 0.48% last_trade_price 43,215 0.04% new_market 7,502 <0.01% tick_size_change 2,564 <0.01% market_resolved 788 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,661,330 11,661,237 93 137 FULL book 572,833 572,805 28 180,766 FULL last_trade_price 43,217 43,215 2 1 FULL market_resolved 788 788 0 0 FULL new_market 7,502 7,502 0 0 FULL price_change 106,607,076 106,604,920 2,156 1,338 FULL tick_size_change 2,564 2,564 0 7 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 11,658,366 90,712 19ms 43ms 1.3s 2.9min 0 transport_latency_assumed best_bid_ask i 11,649,427 133,660 21ms 35ms 174ms 5.8s 0 transport_latency_assumed best_bid_ask m 11,659,566 5,877,413 4ms 17ms 161ms 7.2s 0 transport_latency_assumed best_bid_ask n 11,654,394 11,221 44ms 75ms 328ms 23.4s 0 transport_latency_assumed best_bid_ask o 11,660,598 5,548,231 4ms 19ms 176ms 6.8s 0 transport_latency_assumed book h 129,407 29,026 32ms 4.0h 28.7d 110.7d 0 book_staleness book i 456,539 324,118 10.5min 1.3d 44.5d 129.2d 0 book_staleness book m 171,318 111,962 171ms 10.2h 31.5d 129.2d 0 book_staleness book n 121,745 23,462 61ms 1.9h 26.7d 129.2d 0 book_staleness book o 147,101 84,237 18ms 6.8h 28.7d 110.7d 0 book_staleness last_trade_price h 42,948 555 21ms 82ms 4.4s 1.2min 0 transport_latency_assumed last_trade_price i 42,524 448 23ms 98ms 2.6s 5.8s 0 transport_latency_assumed last_trade_price m 43,027 22,221 6ms 25ms 225ms 2.7s 0 transport_latency_assumed last_trade_price n 42,427 29 48ms 207ms 7.6s 23.4s 0 transport_latency_assumed last_trade_price o 43,171 19,962 6ms 28ms 219ms 2.2s 0 transport_latency_assumed market_resolved h 747 37 21ms 68ms 16.4s 57.6s 0 transport_latency_assumed market_resolved i 747 51 23ms 92ms 40.0s 42.4s 0 transport_latency_assumed market_resolved m 747 351 6ms 37ms 48.9s 51.3s 0 transport_latency_assumed market_resolved n 747 11 47ms 114ms 345ms 719ms 0 transport_latency_assumed market_resolved o 747 338 6ms 49ms 55.2s 57.5s 0 transport_latency_assumed new_market h 5,057 1,029 37.0s 1.6min 2.1min 7.0min 0 transport_latency_assumed new_market i 5,057 2,232 25.9s 1.4min 6.3min 6.3min 0 transport_latency_assumed new_market m 5,057 1,330 1.1min 2.1min 2.5min 2.7min 0 transport_latency_assumed new_market n 5,057 1,545 43.1s 1.8min 2.1min 2.3min 0 transport_latency_assumed new_market o 5,057 1,366 1.1min 2.1min 2.5min 2.7min 0 transport_latency_assumed price_change h 106,476,634 1,020,878 19ms 53ms 1.7s 2.9min 0 transport_latency_assumed price_change i 106,178,728 1,250,961 21ms 42ms 388ms 5.9s 0 transport_latency_assumed price_change m 106,323,861 53,729,652 5ms 19ms 174ms 7.3s 0 transport_latency_assumed price_change n 106,105,829 129,708 45ms 94ms 1.1s 23.5s 0 transport_latency_assumed price_change o 106,434,915 50,473,721 5ms 21ms 189ms 7.7s 0 transport_latency_assumed tick_size_change h 2,564 16 19ms 35ms 2.2s 35.6s 0 transport_latency_assumed tick_size_change i 2,536 20 21ms 29ms 64ms 360ms 0 transport_latency_assumed tick_size_change m 2,564 1,248 4ms 13ms 70ms 1.7s 0 transport_latency_assumed tick_size_change n 2,564 not meas. 44ms 70ms 199ms 281ms 0 transport_latency_assumed tick_size_change o 2,564 1,280 4ms 12ms 60ms 669ms 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/02/2026-10-06T02.parquet sha256sum 2026-10-06T02.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.