Hour audit: 2026-10-06T01
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-06T01 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-06T01:00:00.000088728+00:00 · last event 2026-10-06T01:59:59.999887397+00:00
VOLUME 122,586,619 rows · 1,365,823,657 bytes (1.27 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured h: 122,496,019 · n: 122,392,236 · o: 122,375,034 · m: 122,331,653 · i: 122,096,642 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 1,125,734 (0.92%) · n: 92,273 (0.08%) · o: 59,300,309 (48.37%) · m: 61,240,654 (49.96%) · i: 827,649 (0.68%) (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 122,586,619 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 3698b368918087493df5adaf372319d32e2d2c4d6fc4b034db275d0c2da4a0d9
the corpus checksum ledger names this file with the same digest
joined 122,593,271 to merged 122,586,619, minus 6,652 (minus 0.0054%)
boundary drops 6,652 · 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-06T03:21:56Z 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,875,494 148,151,400 0-45 c4f33f5efb3f71a7b0226237bf1f68604fe269630ed29c9b66b7374c5c7c1e69 book 132,470 14,239,921 46-46 79e44dd68e08def97557e2f835e28474ff4f1daca5d72d9be8c4b07e459de59f last_trade_price 50,290 2,927,940 47-47 cb3611871a7e192ef849d40f4f0ff21a292852e5ae424c9e115443469f4a4c30 market_resolved 807 132,997 48-48 3a27b0eb9d4c6fe43a1606b5235a5de7befa890fb75e9f2878814db933ebabdf new_market 3,956 360,260 49-49 3bd98da3980617c3b014b505c9462fc1b36595b3ff497913b858d005a9dc22a0 price_change 110,520,746 1,198,508,932 50-471 06949471259ea4f7895c8eff4bf65b117f795e7286eb44f86659ea5a03959424 tick_size_change 2,856 105,651 472-472 9ec7ef0ad255f187da9e95883342244fb7e7d3065beb94969f5e1a0dd7f08fcb EVENT MIX count share price_change 110,520,746 90.16% best_bid_ask 11,875,494 9.69% book 132,470 0.11% last_trade_price 50,290 0.04% new_market 3,956 <0.01% tick_size_change 2,856 <0.01% market_resolved 807 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,876,162 11,875,494 668 56 FULL book 132,704 132,470 234 8,585 FULL last_trade_price 50,290 50,290 0 0 FULL market_resolved 807 807 0 0 FULL new_market 3,960 3,956 4 9 FULL price_change 110,526,492 110,520,746 5,746 1,313 FULL tick_size_change 2,856 2,856 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 11,875,175 92,631 19ms 31ms 329ms 49.1s 0 transport_latency_assumed best_bid_ask i 11,866,474 78,276 21ms 33ms 156ms 5.2s 0 transport_latency_assumed best_bid_ask m 11,873,905 5,942,274 4ms 15ms 103ms 5.0s 0 transport_latency_assumed best_bid_ask n 11,873,931 6,511 45ms 66ms 220ms 9.3s 0 transport_latency_assumed best_bid_ask o 11,874,490 5,755,802 4ms 16ms 107ms 3.6s 0 transport_latency_assumed book h 112,590 9,568 23ms 1.8s 16.5h 129.1d 0 book_staleness book i 110,553 7,745 25ms 1.2s 57.6min 110.5d 0 book_staleness book m 110,430 59,585 7ms 152ms 8.6h 110.6d 0 book_staleness book n 107,841 3,839 48ms 1.2s 2.8h 110.6d 0 book_staleness book o 109,606 51,733 7ms 106ms 6.3h 110.6d 0 book_staleness last_trade_price h 50,203 577 21ms 60ms 641ms 15.6s 0 transport_latency_assumed last_trade_price i 49,767 304 24ms 178ms 2.0s 5.2s 0 transport_latency_assumed last_trade_price m 50,053 25,702 6ms 22ms 184ms 1.4s 0 transport_latency_assumed last_trade_price n 49,984 53 48ms 209ms 6.5s 9.3s 0 transport_latency_assumed last_trade_price o 50,138 23,654 6ms 23ms 191ms 1.7s 0 transport_latency_assumed market_resolved h 793 6 21ms 90ms 54.0s 54.0s 0 transport_latency_assumed market_resolved i 793 76 23ms 98ms 52.7s 52.7s 0 transport_latency_assumed market_resolved m 793 370 6ms 44ms 38.5s 41.9s 0 transport_latency_assumed market_resolved n 793 not meas. 47ms 189ms 56.9s 56.9s 0 transport_latency_assumed market_resolved o 793 355 6ms 40ms 45.0s 48.4s 0 transport_latency_assumed new_market h 2,314 481 88ms 53.0s 1.5min 1.4h 0 transport_latency_assumed new_market i 2,314 730 61ms 52.4s 1.5min 1.4h 0 transport_latency_assumed new_market m 2,314 1,179 54ms 56.1s 1.4min 1.4h 0 transport_latency_assumed new_market n 2,314 270 126ms 53.7s 1.7min 1.4h 0 transport_latency_assumed new_market o 2,305 1,296 48ms 54.8s 1.5min 1.4h 0 transport_latency_assumed price_change h 110,452,088 1,022,455 19ms 36ms 495ms 49.7s 0 transport_latency_assumed price_change i 110,063,885 740,494 21ms 41ms 577ms 5.2s 0 transport_latency_assumed price_change m 110,291,302 55,210,148 5ms 17ms 124ms 5.0s 0 transport_latency_assumed price_change n 110,354,517 81,600 45ms 78ms 642ms 10.5s 0 transport_latency_assumed price_change o 110,334,846 53,466,049 5ms 17ms 127ms 4.3s 0 transport_latency_assumed tick_size_change h 2,856 16 19ms 28ms 213ms 2.5s 0 transport_latency_assumed tick_size_change i 2,856 24 21ms 28ms 58ms 153ms 0 transport_latency_assumed tick_size_change m 2,856 1,396 4ms 11ms 87ms 584ms 0 transport_latency_assumed tick_size_change n 2,856 not meas. 44ms 61ms 126ms 234ms 0 transport_latency_assumed tick_size_change o 2,856 1,420 4ms 11ms 66ms 218ms 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/01/2026-10-06T01.parquet sha256sum 2026-10-06T01.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.