Hour audit: 2026-10-01T14
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-01T14 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-01T14:00:00.000141086+00:00 · last event 2026-10-01T14:59:59.999906124+00:00
VOLUME 130,584,607 rows · 1,440,558,221 bytes (1.34 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured i: 129,523,967 · m: 129,080,638 · h: 129,068,570 · k: 117,048,081 · g: 116,777,436 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 696,519 (0.53%) · m: 121,909,171 (93.36%) · h: 1,283,313 (0.98%) · k: 6,047,189 (4.63%) · g: 648,415 (0.50%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 5ad9750f95f7682a0faad27577fd4f80f917ce8ae39f090cbe281b1a4d105177
the corpus checksum ledger names this file with the same digest
joined 130,589,663 to merged 130,584,607, minus 5,056 (minus 0.0039%)
boundary drops 5,056 · 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-01T17:13:10Z as ghikm
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,578,979 135,252,204 0-44 3d950ca05a6bace8358862be48dcca03c15ae3ab2e6ddcf64a45b0b534a2b832 book 1,664,536 99,183,292 45-51 9698a72a810e5abdc5646aeda550714fe3f134e6752c53ab653f6256e38934e2 last_trade_price 64,246 3,657,629 52-52 2c3be487bcf3fe706f74136b8c7e8d04e484f6b3454986f6834319dd076feab8 market_resolved 1,087 133,848 53-53 042d02f9269d5f60b57f61a10af3c70d6545a313839b07e7ee38c6e2c6dc8bb5 new_market 4,073 294,160 54-54 b108eecf4034bb019ac6e241a98da8f022222e60e16e0dd201e7d1b55602f678 price_change 117,269,126 1,200,452,832 55-502 f59fe15eb48853e2f2f37e0517184b128a27404af58f4025f4944ff677f4cbf5 tick_size_change 2,560 95,610 503-503 dd16d28604561fff55d17784fbbadfb7c2e3ffd84e2c4feede3dda0881cb5f06 EVENT MIX count share price_change 117,269,126 89.80% best_bid_ask 11,578,979 8.87% book 1,664,536 1.27% last_trade_price 64,246 0.05% new_market 4,073 <0.01% tick_size_change 2,560 <0.01% market_resolved 1,087 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,579,259 11,578,979 280 2,664 FULL book 1,665,040 1,664,536 504 190,890 FULL last_trade_price 64,246 64,246 0 355 FULL market_resolved 1,087 1,087 0 120 FULL new_market 4,123 4,073 50 444 FULL price_change 117,273,348 117,269,126 4,222 1,545 FULL tick_size_change 2,560 2,560 0 91 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 10,354,280 7,171 75ms 92ms 471ms 24.3s 0 transport_latency_assumed best_bid_ask h 11,575,237 90,731 19ms 33ms 619ms 1.1min 0 transport_latency_assumed best_bid_ask i 11,574,544 42,787 27ms 44ms 191ms 29.5s 0 transport_latency_assumed best_bid_ask k 10,388,099 438,014 14ms 24ms 193ms 59.2s 0 transport_latency_assumed best_bid_ask m 11,577,635 11,000,276 6ms 12ms 79ms 5.7s 0 transport_latency_assumed book g 1,088,433 557,017 59.0min 3.6d 40.0d 124.7d 0 book_staleness book h 363,773 92,190 1.7min 2.3d 40.0d 124.7d 0 book_staleness book i 665,488 197,778 20.1min 3.0d 40.0d 124.7d 0 book_staleness book k 1,101,340 619,211 1.0h 3.7d 40.0d 124.7d 0 book_staleness book m 319,690 198,340 46.5s 1.6d 33.8d 124.7d 0 book_staleness last_trade_price g 57,426 44 76ms 188ms 5.7s 24.3s 0 transport_latency_assumed last_trade_price h 64,171 726 20ms 34ms 698ms 1.0min 0 transport_latency_assumed last_trade_price i 64,218 219 37ms 49ms 282ms 24.7s 0 transport_latency_assumed last_trade_price k 58,138 2,690 15ms 26ms 208ms 9.5s 0 transport_latency_assumed last_trade_price m 64,230 60,567 7ms 13ms 105ms 1.2s 0 transport_latency_assumed market_resolved g 879 216 108ms 19.5min 25.4min 25.4min 0 transport_latency_assumed market_resolved h 706 3 21ms 33.7s 41.6s 45.0s 0 transport_latency_assumed market_resolved i 706 95 41ms 21.5s 56.9s 57.0s 0 transport_latency_assumed market_resolved k 799 180 18ms 8.5min 15.0min 15.0min 0 transport_latency_assumed market_resolved m 706 593 6ms 23.0s 34.2s 49.6s 0 transport_latency_assumed new_market g 3,101 1,639 5.8min 19.7min 20.6min 13.6d 0 transport_latency_assumed new_market h 1,377 336 411ms 55.6s 1.2min 1.3min 0 transport_latency_assumed new_market i 1,377 447 240ms 57.7s 1.1min 1.7min 0 transport_latency_assumed new_market k 1,948 805 20.2s 6.3min 10.3min 11.6min 0 transport_latency_assumed new_market m 1,377 846 287ms 56.4s 1.2min 1.6min 0 transport_latency_assumed price_change g 105,270,997 82,324 75ms 98ms 1.1s 24.3s 0 transport_latency_assumed price_change h 117,060,746 1,099,304 20ms 33ms 765ms 2.0min 0 transport_latency_assumed price_change i 117,215,074 455,172 38ms 46ms 283ms 46.9s 0 transport_latency_assumed price_change k 105,495,417 4,986,204 14ms 25ms 267ms 1.2min 0 transport_latency_assumed price_change m 117,114,440 110,646,122 6ms 13ms 125ms 6.0s 0 transport_latency_assumed tick_size_change g 2,320 4 75ms 191ms 609ms 836ms 0 transport_latency_assumed tick_size_change h 2,560 23 20ms 38ms 2.9s 39.0s 0 transport_latency_assumed tick_size_change i 2,560 21 38ms 49ms 550ms 1.5s 0 transport_latency_assumed tick_size_change k 2,340 85 14ms 74ms 876ms 8.1s 0 transport_latency_assumed tick_size_change m 2,560 2,427 6ms 15ms 327ms 503ms 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-01/14/2026-10-01T14.parquet sha256sum 2026-10-01T14.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.