Hour audit: 2026-10-07T00
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-07T00 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-07T00:00:00.000044687+00:00 · last event 2026-10-07T00:59:59.999979501+00:00
VOLUME 119,971,070 rows · 1,337,995,913 bytes (1.25 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured n: 119,837,514 · m: 119,790,139 · i: 119,753,842 · o: 119,753,841 · h: 119,646,785 (each machine's own feed; these overlap and do not sum to the file)
supplied n: 72,720 (0.06%) · m: 61,165,074 (50.98%) · i: 477,097 (0.40%) · o: 57,501,385 (47.93%) · h: 754,794 (0.63%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 ef5904b4448b24d83561c7c760916726e2189ee9c90273998cffcc9c21f35e52
the corpus checksum ledger names this file with the same digest
joined 119,971,462 to merged 119,971,070, minus 392 (minus 0.0003%)
boundary drops 392 · 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-07T02:05:16Z 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,762,718 144,380,207 0-44 e2bae820e77b080ee6ec09c8d00650d73dd703258352cbd89ba90255dfcaac5f book 169,584 16,970,141 45-45 45f74bd1899e48f13edc4629943e1a338439e1fbeb64d51c6739f5d61556b489 last_trade_price 51,460 2,956,383 46-46 fcdf95a8a9fde6baf736b90d433cf455c332bab65bb784cf8e0f6d2b8d859cf9 market_resolved 682 106,373 47-47 7bfe7a30eaeda7efa1def16f12b64751fb93597a04d705091ac5694a385a5b1c new_market 664 67,193 48-48 39fb4e9a97c6dd94b644f2b867daca19e1b9c2398deb07c5262e952a062d4f85 price_change 107,983,190 1,172,048,396 49-460 254fcc6b5cbfba0d153899ea925831a9103957a2718558910a845942a7002370 tick_size_change 2,772 102,372 461-461 1444ad31530f2f8a6f3efaf07996c2477f0f7468da66884da97271c037221ee6 EVENT MIX count share price_change 107,983,190 90.01% best_bid_ask 11,762,718 9.80% book 169,584 0.14% last_trade_price 51,460 0.04% tick_size_change 2,772 <0.01% market_resolved 682 <0.01% new_market 664 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,762,760 11,762,718 42 52 FULL book 169,586 169,584 2 27,551 FULL last_trade_price 51,460 51,460 0 0 FULL market_resolved 682 682 0 0 FULL new_market 664 664 0 0 FULL price_change 107,983,538 107,983,190 348 46 FULL tick_size_change 2,772 2,772 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 11,755,663 68,881 18ms 26ms 113ms 39.1s 0 transport_latency_assumed best_bid_ask i 11,758,109 40,208 21ms 29ms 99ms 4.3s 0 transport_latency_assumed best_bid_ask m 11,758,820 6,106,292 4ms 12ms 67ms 6.2s 0 transport_latency_assumed best_bid_ask n 11,761,058 3,663 44ms 55ms 146ms 6.5s 0 transport_latency_assumed best_bid_ask o 11,758,531 5,543,674 4ms 12ms 67ms 7.8s 0 transport_latency_assumed book h 111,193 8,570 22ms 206ms 23.9h 111.5d 0 book_staleness book i 124,448 20,561 25ms 33.6min 9.9d 111.6d 0 book_staleness book m 121,890 67,724 7ms 10.2min 4.5d 111.6d 0 book_staleness book n 109,520 6,343 47ms 227ms 21.9h 111.6d 0 book_staleness book o 119,917 66,386 7ms 5.9min 3.4d 111.6d 0 book_staleness last_trade_price h 50,840 441 20ms 53ms 430ms 20.1s 0 transport_latency_assumed last_trade_price i 51,128 268 23ms 93ms 1.0s 2.8s 0 transport_latency_assumed last_trade_price m 51,058 25,152 6ms 21ms 161ms 3.1s 0 transport_latency_assumed last_trade_price n 51,337 108 47ms 126ms 721ms 2.9s 0 transport_latency_assumed last_trade_price o 51,084 25,491 6ms 20ms 143ms 1.3s 0 transport_latency_assumed market_resolved h 641 1 20ms 74ms 48.2s 51.1s 0 transport_latency_assumed market_resolved i 641 51 22ms 93ms 43.1s 45.0s 0 transport_latency_assumed market_resolved m 641 318 5ms 28ms 43.5s 45.1s 0 transport_latency_assumed market_resolved n 641 41 46ms 120ms 27.1s 59.2s 0 transport_latency_assumed market_resolved o 641 271 5ms 46ms 52.3s 54.1s 0 transport_latency_assumed new_market h 414 69 65ms 15.5s 35.5s 1.9min 0 transport_latency_assumed new_market i 414 89 53ms 9.0s 33.7s 1.4min 0 transport_latency_assumed new_market m 414 256 34ms 24.2s 36.5s 1.3min 0 transport_latency_assumed new_market n 414 43 123ms 7.7s 33.5s 1.5min 0 transport_latency_assumed new_market o 414 207 40ms 17.7s 27.0s 1.6min 0 transport_latency_assumed price_change h 107,725,262 676,820 18ms 29ms 181ms 39.4s 0 transport_latency_assumed price_change i 107,816,330 415,908 21ms 32ms 235ms 4.4s 0 transport_latency_assumed price_change m 107,854,544 54,963,892 4ms 13ms 78ms 6.3s 0 transport_latency_assumed price_change n 107,911,772 62,518 44ms 61ms 262ms 7.6s 0 transport_latency_assumed price_change o 107,820,482 51,864,052 5ms 13ms 75ms 8.1s 0 transport_latency_assumed tick_size_change h 2,772 12 18ms 32ms 210ms 775ms 0 transport_latency_assumed tick_size_change i 2,772 12 21ms 33ms 82ms 217ms 0 transport_latency_assumed tick_size_change m 2,772 1,440 4ms 14ms 69ms 364ms 0 transport_latency_assumed tick_size_change n 2,772 4 45ms 73ms 220ms 505ms 0 transport_latency_assumed tick_size_change o 2,772 1,304 4ms 13ms 69ms 125ms 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/00/2026-10-07T00.parquet sha256sum 2026-10-07T00.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.