Hour audit: 2026-10-06T04
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-06T04 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-06T04:00:00.000027099+00:00 · last event 2026-10-06T04:59:59.999982779+00:00
VOLUME 108,745,318 rows · 1,199,739,598 bytes (1.12 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured i: 108,618,596 · h: 108,583,041 · o: 108,498,369 · m: 108,409,596 · n: 108,380,712 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 824,464 (0.76%) · h: 623,050 (0.57%) · o: 54,536,102 (50.15%) · m: 52,668,289 (48.43%) · n: 93,413 (0.09%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 dcd09d2873c704435f308e64aa4eeb56ef427a35bf6ec2e1924ce150933c21ac
the corpus checksum ledger names this file with the same digest
joined 108,746,302 to merged 108,745,318, minus 984 (minus 0.0009%)
boundary drops 984 · 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-06T05:59:33Z 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 10,969,064 135,310,555 0-41 e8c499656cef3d8d814cab27263011cea7fd16e624ec5ada9e322a6412e818c9 book 201,567 21,077,381 42-42 b9a38c767af832f767fc80530f3a6fc8b09240a97c3d6851505dc073379919cd last_trade_price 44,967 2,580,099 43-43 43169bafbde4c2598d47e38498ba6cd2a3bcdb33ba75086a0559e52411349427 market_resolved 1,232 181,187 44-44 a64689d647dfdb253f94744a4c10c06f2eb14b8a6fa9f1e54e92e04d72c6f4c2 new_market 3,376 318,023 45-45 2bade2a4c1e7095901ee22bd35bd69db662c1e338553c280f992a4caf7415245 price_change 97,522,720 1,038,943,441 46-418 532e77be6e4caf9de762c3dbd31f7f385ee06c51dd608cd900f32aa8b22f5d39 tick_size_change 2,392 88,880 419-419 75ff9153444344040bc217e2c170d1c84ebf810fbc13d8961ef0b26955bcf900 EVENT MIX count share price_change 97,522,720 89.68% best_bid_ask 10,969,064 10.09% book 201,567 0.19% last_trade_price 44,967 0.04% new_market 3,376 <0.01% tick_size_change 2,392 <0.01% market_resolved 1,232 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,969,182 10,969,064 118 126 FULL book 201,580 201,567 13 48,455 FULL last_trade_price 44,968 44,967 1 0 FULL market_resolved 1,242 1,232 10 10 FULL new_market 3,376 3,376 0 0 FULL price_change 97,523,562 97,522,720 842 1,234 FULL tick_size_change 2,392 2,392 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,965,080 46,937 18ms 37ms 1.3s 1.8min 0 transport_latency_assumed best_bid_ask i 10,967,610 69,491 21ms 29ms 176ms 3.4s 0 transport_latency_assumed best_bid_ask m 10,967,994 5,375,457 4ms 12ms 134ms 7.8s 0 transport_latency_assumed best_bid_ask n 10,965,146 7,331 43ms 61ms 386ms 20.0s 0 transport_latency_assumed best_bid_ask o 10,967,882 5,469,848 4ms 13ms 168ms 19.2s 0 transport_latency_assumed book h 134,079 39,391 39ms 5.1h 28.7d 129.3d 0 book_staleness book i 132,858 39,658 31ms 4.9h 28.7d 110.7d 0 book_staleness book m 103,598 55,473 6ms 3.8s 1.8d 110.7d 0 book_staleness book n 104,452 11,880 49ms 31.3s 1.8d 110.8d 0 book_staleness book o 104,175 55,165 6ms 5.4s 2.6d 110.8d 0 book_staleness last_trade_price h 44,841 373 20ms 118ms 2.8s 52.7s 0 transport_latency_assumed last_trade_price i 44,853 396 23ms 92ms 940ms 3.4s 0 transport_latency_assumed last_trade_price m 44,813 22,361 6ms 22ms 290ms 7.6s 0 transport_latency_assumed last_trade_price n 44,372 67 47ms 321ms 5.6s 19.5s 0 transport_latency_assumed last_trade_price o 44,832 21,770 6ms 22ms 313ms 2.9s 0 transport_latency_assumed market_resolved h 1,131 79 23ms 4.8s 51.9s 1.2min 0 transport_latency_assumed market_resolved i 1,121 121 23ms 15.4s 52.1s 1.0min 0 transport_latency_assumed market_resolved m 1,121 483 5ms 20.3s 44.7s 56.8s 0 transport_latency_assumed market_resolved n 1,131 30 45ms 225ms 52.2s 52.6s 0 transport_latency_assumed market_resolved o 1,131 519 5ms 27.8s 50.8s 1.0min 0 transport_latency_assumed new_market h 2,036 262 290ms 31.2s 1.2min 1.4min 0 transport_latency_assumed new_market i 2,036 489 190ms 32.2s 1.2min 1.6min 0 transport_latency_assumed new_market m 2,036 1,227 114ms 32.8s 1.2min 1.9min 0 transport_latency_assumed new_market n 2,036 336 255ms 28.5s 1.2min 1.7min 0 transport_latency_assumed new_market o 2,036 1,062 115ms 30.0s 1.2min 1.6min 0 transport_latency_assumed price_change h 97,433,482 535,992 19ms 46ms 1.5s 1.9min 0 transport_latency_assumed price_change i 97,467,726 714,278 21ms 35ms 292ms 3.4s 0 transport_latency_assumed price_change m 97,287,642 47,212,079 4ms 14ms 155ms 8.2s 0 transport_latency_assumed price_change n 97,261,183 73,760 44ms 77ms 978ms 20.1s 0 transport_latency_assumed price_change o 97,375,921 48,986,611 4ms 14ms 193ms 20.4s 0 transport_latency_assumed tick_size_change h 2,392 16 20ms 39ms 1.1s 7.4s 0 transport_latency_assumed tick_size_change i 2,392 31 21ms 43ms 254ms 648ms 0 transport_latency_assumed tick_size_change m 2,392 1,209 4ms 18ms 221ms 672ms 0 transport_latency_assumed tick_size_change n 2,392 9 43ms 68ms 742ms 1.1s 0 transport_latency_assumed tick_size_change o 2,392 1,127 4ms 19ms 330ms 602ms 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/04/2026-10-06T04.parquet sha256sum 2026-10-06T04.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.