Hour audit: 2026-10-05T09
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-05T09 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-05T09:00:00.000031775+00:00 · last event 2026-10-05T09:59:59.999985309+00:00
VOLUME 113,998,571 rows · 1,280,202,446 bytes (1.19 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 113,943,322 · n: 113,871,820 · m: 113,839,565 · h: 113,793,476 · i: 113,777,744 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 54,546,627 (47.85%) · n: 49,106 (0.04%) · m: 58,430,975 (51.26%) · h: 544,811 (0.48%) · i: 427,052 (0.37%) (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 113,998,571 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 41284972eb668d4da681bcaca5c54e9393dc0f1365f54797be2a72d689d868ce
the corpus checksum ledger names this file with the same digest
joined 114,010,846 to merged 113,998,571, minus 12,275 (minus 0.0108%)
boundary drops 12,275 · 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-05T11:05:26Z 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,064,402 127,493,086 0-38 3846ea354ce50b75ced902f2f128cf521c0e22a673e3c818341d16295736c79a book 138,619 15,640,630 39-39 1b5176fc82399f6db6dd1dba4d5edd1fbfd733bee19bfebb7930bb63a8bd4533 last_trade_price 56,065 3,251,414 40-40 0af33036e79d0050dea808f118029f558177453348f0c995c0359e82bc3535cc market_resolved 1,459 223,802 41-41 b7a17eb7e2fafb7814da6a173d72949e962f27c1b7f20c541f7fdce8caeaad51 new_market 726 71,147 42-42 68350925de56fa4bce2ea4277513c0316f3cefec059b9546dd36fd3a27ab005d price_change 103,734,148 1,132,105,580 43-438 32f49904f70cfa8c02cd41443c5201f3925bb9210dc6ff75cae89779a58c8a93 tick_size_change 3,152 116,619 439-439 557f5a476f006b23c427bb551794f58c038f77039603650bbfdb7c281bd67cca EVENT MIX count share price_change 103,734,148 91.00% best_bid_ask 10,064,402 8.83% book 138,619 0.12% last_trade_price 56,065 0.05% tick_size_change 3,152 <0.01% market_resolved 1,459 <0.01% new_market 726 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,064,512 10,064,402 110 77 FULL book 138,623 138,619 4 10,990 FULL last_trade_price 56,066 56,065 1 0 FULL market_resolved 1,459 1,459 0 0 FULL new_market 726 726 0 0 FULL price_change 103,746,308 103,734,148 12,160 2,634 FULL tick_size_change 3,152 3,152 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,062,586 43,624 20ms 35ms 245ms 1.0min 0 transport_latency_assumed best_bid_ask i 10,061,936 31,267 22ms 31ms 121ms 10.7s 0 transport_latency_assumed best_bid_ask m 10,063,518 5,134,367 5ms 13ms 69ms 6.9s 0 transport_latency_assumed best_bid_ask n 10,062,362 2,228 44ms 60ms 198ms 1.1min 0 transport_latency_assumed best_bid_ask o 10,064,020 4,852,916 5ms 13ms 71ms 3.7s 0 transport_latency_assumed book h 119,065 7,025 28ms 281ms 15.3h 110.0d 0 book_staleness book i 123,283 11,198 26ms 1.2s 1.4d 126.8d 0 book_staleness book m 114,798 65,374 7ms 25ms 7.2min 109.9d 0 book_staleness book n 117,184 5,234 48ms 762ms 10.5h 109.9d 0 book_staleness book o 114,470 49,788 7ms 31ms 1.6min 109.9d 0 book_staleness last_trade_price h 55,885 272 23ms 114ms 743ms 27.1s 0 transport_latency_assumed last_trade_price i 55,863 209 25ms 166ms 1.4s 8.4s 0 transport_latency_assumed last_trade_price m 55,936 31,269 6ms 18ms 148ms 1.3s 0 transport_latency_assumed last_trade_price n 55,706 72 47ms 344ms 6.8s 43.6s 0 transport_latency_assumed last_trade_price o 56,028 24,243 6ms 23ms 184ms 1.2s 0 transport_latency_assumed market_resolved h 1,392 29 23ms 105ms 52.6s 56.9s 0 transport_latency_assumed market_resolved i 1,392 155 24ms 22.8s 50.9s 57.8s 0 transport_latency_assumed market_resolved m 1,392 616 6ms 25.8s 53.9s 54.0s 0 transport_latency_assumed market_resolved n 1,392 not meas. 46ms 157ms 55.3s 56.7s 0 transport_latency_assumed market_resolved o 1,392 659 6ms 43ms 53.4s 56.7s 0 transport_latency_assumed new_market h 458 123 195ms 28.7s 49.4s 1.7min 0 transport_latency_assumed new_market i 458 57 119ms 37.5s 1.0min 1.5min 0 transport_latency_assumed new_market m 458 257 44ms 25.2s 38.6s 1.6min 0 transport_latency_assumed new_market n 458 56 189ms 36.0s 43.3s 1.5min 0 transport_latency_assumed new_market o 458 233 48ms 36.9s 45.8s 1.7min 0 transport_latency_assumed price_change h 103,550,938 493,705 21ms 42ms 337ms 1.1min 0 transport_latency_assumed price_change i 103,531,660 384,158 22ms 38ms 415ms 15.0s 0 transport_latency_assumed price_change m 103,600,311 53,197,565 5ms 14ms 81ms 7.8s 0 transport_latency_assumed price_change n 103,631,566 41,516 44ms 75ms 1.0s 1.2min 0 transport_latency_assumed price_change o 103,703,802 49,617,204 5ms 15ms 85ms 4.6s 0 transport_latency_assumed tick_size_change h 3,152 33 21ms 37ms 197ms 251ms 0 transport_latency_assumed tick_size_change i 3,152 8 22ms 46ms 89ms 293ms 0 transport_latency_assumed tick_size_change m 3,152 1,527 5ms 13ms 40ms 109ms 0 transport_latency_assumed tick_size_change n 3,152 not meas. 44ms 55ms 114ms 343ms 0 transport_latency_assumed tick_size_change o 3,152 1,584 5ms 13ms 44ms 101ms 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/09/2026-10-05T09.parquet sha256sum 2026-10-05T09.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.