Hour audit: 2026-10-07T15
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-07T15 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-07T15:00:00.000043326+00:00 · last event 2026-10-07T15:59:59.999999914+00:00
VOLUME 121,787,408 rows · 1,435,331,620 bytes (1.34 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured i: 121,588,885 · m: 120,960,039 · o: 120,949,073 · h: 120,872,580 · n: 120,365,954 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 1,575,065 (1.29%) · m: 58,434,150 (47.98%) · o: 60,643,518 (49.79%) · h: 1,083,988 (0.89%) · n: 50,687 (0.04%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 121,787,408 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 2d98345152f54753b8641cac883e8625236362f95738fb12d5b60082dfcf4c41
the corpus checksum ledger names this file with the same digest
joined 121,789,024 to merged 121,787,408, minus 1,616 (minus 0.0013%)
boundary drops 1,616 · 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-07T17:18:48Z 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 9,609,948 127,477,614 0-36 669325463bb9fe489fc2dc5d0eaa47cc9412ca271712d7f7803f7727d587a3af book 947,029 77,035,513 37-40 f1125b0e45c050ee8f92036f2c5024884082b2c56c3b8956d81539c3d034cb8a last_trade_price 60,504 3,533,557 41-41 2c466ecf152fe8af3920cb5e0869ff97481464144219f9b358ec24f96bdf3bad market_resolved 1,104 173,350 42-42 6d96967553f6bc795d04bdaa3dd62c3655e208bc5ccbaeee76ad7e33f0873490 new_market 1,557 143,357 43-43 6eacf0aac3d4a689bda7fc87c241fcb021f3b77a057bbfdf23ff7a159afc31e4 price_change 111,163,610 1,225,444,496 44-468 b08ea4e5186662972108a08b32b366b10f029aa7277a1bf8bbbba63781a3e773 tick_size_change 3,656 134,546 469-469 b41519bd7a9ab75b61806c156f4884a0e897365bfe9b1fc53af0f3e1607919fa EVENT MIX count share price_change 111,163,610 91.28% best_bid_ask 9,609,948 7.89% book 947,029 0.78% last_trade_price 60,504 0.05% tick_size_change 3,656 <0.01% new_market 1,557 <0.01% market_resolved 1,104 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,610,030 9,609,948 82 60 FULL book 947,263 947,029 234 257,384 FULL last_trade_price 60,504 60,504 0 2 FULL market_resolved 1,104 1,104 0 0 FULL new_market 1,557 1,557 0 0 FULL price_change 111,164,910 111,163,610 1,300 49 FULL tick_size_change 3,656 3,656 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 9,607,798 77,331 20ms 42ms 227ms 47.8s 0 transport_latency_assumed best_bid_ask i 9,602,735 59,246 22ms 36ms 178ms 11.6s 0 transport_latency_assumed best_bid_ask m 9,609,663 4,606,962 6ms 18ms 102ms 6.1s 0 transport_latency_assumed best_bid_ask n 9,600,822 2,569 45ms 69ms 431ms 26.7s 0 transport_latency_assumed best_bid_ask o 9,609,593 4,863,840 5ms 18ms 108ms 6.1s 0 transport_latency_assumed book h 137,227 14,546 30ms 20.7s 3.0d 130.7d 0 book_staleness book i 925,108 779,593 12.6min 1.9d 46.1d 130.7d 0 book_staleness book m 132,988 69,274 9ms 144ms 1.7d 112.2d 0 book_staleness book n 132,744 13,019 63ms 25.7s 5.6d 112.2d 0 book_staleness book o 136,146 70,597 9ms 3.0s 2.2d 130.7d 0 book_staleness last_trade_price h 59,959 535 24ms 178ms 1.2s 11.6s 0 transport_latency_assumed last_trade_price i 60,010 325 27ms 275ms 3.7s 11.6s 0 transport_latency_assumed last_trade_price m 60,456 29,961 7ms 30ms 183ms 1.5s 0 transport_latency_assumed last_trade_price n 57,774 18 59ms 2.5s 11.9s 26.8s 0 transport_latency_assumed last_trade_price o 60,442 29,665 7ms 32ms 215ms 3.1s 0 transport_latency_assumed market_resolved h 1,066 15 24ms 16.8s 42.3s 42.4s 0 transport_latency_assumed market_resolved i 1,066 144 26ms 16.7s 42.1s 42.2s 0 transport_latency_assumed market_resolved m 1,066 441 7ms 17.0s 42.2s 42.3s 0 transport_latency_assumed market_resolved n 1,066 38 48ms 28.2s 45.7s 45.7s 0 transport_latency_assumed market_resolved o 1,066 466 7ms 17.8s 43.4s 43.5s 0 transport_latency_assumed new_market h 922 217 152ms 1.4min 17.5min 17.6min 0 transport_latency_assumed new_market i 922 373 112ms 17.1min 17.5min 17.6min 0 transport_latency_assumed new_market m 922 532 60ms 17.4min 17.6min 17.6min 0 transport_latency_assumed new_market n 922 125 200ms 1.4min 17.5min 17.6min 0 transport_latency_assumed new_market o 922 310 81ms 17.4min 17.5min 17.6min 0 transport_latency_assumed price_change h 111,061,952 991,316 20ms 52ms 449ms 50.5s 0 transport_latency_assumed price_change i 110,995,388 735,368 22ms 49ms 582ms 11.8s 0 transport_latency_assumed price_change m 111,151,288 53,725,108 6ms 20ms 119ms 6.3s 0 transport_latency_assumed price_change n 110,568,970 34,918 45ms 118ms 4.5s 26.8s 0 transport_latency_assumed price_change o 111,137,248 55,676,900 6ms 21ms 132ms 6.5s 0 transport_latency_assumed tick_size_change h 3,656 28 20ms 36ms 102ms 739ms 0 transport_latency_assumed tick_size_change i 3,656 16 22ms 41ms 109ms 412ms 0 transport_latency_assumed tick_size_change m 3,656 1,872 5ms 14ms 62ms 219ms 0 transport_latency_assumed tick_size_change n 3,656 not meas. 44ms 55ms 125ms 2.0s 0 transport_latency_assumed tick_size_change o 3,656 1,740 5ms 15ms 74ms 193ms 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/15/2026-10-07T15.parquet sha256sum 2026-10-07T15.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.