Hour audit: 2026-10-08T13
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-08T13 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-08T13:00:00.000148294+00:00 · last event 2026-10-08T13:59:59.999933486+00:00
VOLUME 129,850,656 rows · 1,506,277,150 bytes (1.40 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured h: 129,679,553 · o: 129,499,784 · m: 129,454,486 · n: 129,196,148 · i: 128,456,523 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 2,073,171 (1.60%) · o: 59,782,794 (46.04%) · m: 66,630,391 (51.31%) · n: 184,164 (0.14%) · i: 1,180,136 (0.91%) (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 129,850,656 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 abff4402db19cabacd0c5a824807968cb7ab998bd6888f4b2c582e64c0b6ef57
the corpus checksum ledger names this file with the same digest
joined 129,851,607 to merged 129,850,656, minus 951 (minus 0.0007%)
boundary drops 951 · 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-08T15:08:08Z 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,706,063 149,124,813 0-44 43920c52d588ecd529e0b0b26d3340f08d07357a8134aa46fbdaf44a8425b490 book 187,937 20,779,280 45-45 f59b685051948ec757e5f44724f778e3fc3d6b20af431052f3e1008f99337ea6 last_trade_price 66,809 3,831,931 46-46 3cdd530b8e493cbd33ba583b7794bf2324df62f636b4d54e2b639536a49ee1b2 market_resolved 742 120,655 47-47 0d006adb6f1bb2e51b527fdd5164e8eb3d4500e5f9b4caad493d0eda3f0dd0dc new_market 1,563 149,420 48-48 e89f80cb801cf31473b343cec90f98fb6d66e920ba5adc7a4f1133a89079ce5a price_change 117,884,806 1,330,692,083 49-498 3724b525dfb1597a4aaba495859760449031fe9af7690f126a823f109dc26bf9 tick_size_change 2,736 102,101 499-499 933013e113d7b2ea5c0f088e4f560c144b64dc087340973e9681b0b021e07272 EVENT MIX count share price_change 117,884,806 90.78% best_bid_ask 11,706,063 9.02% book 187,937 0.14% last_trade_price 66,809 0.05% tick_size_change 2,736 <0.01% new_market 1,563 <0.01% market_resolved 742 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,706,181 11,706,063 118 190 FULL book 187,945 187,937 8 16,471 FULL last_trade_price 66,810 66,809 1 2 FULL market_resolved 742 742 0 0 FULL new_market 1,563 1,563 0 0 FULL price_change 117,885,630 117,884,806 824 94 FULL tick_size_change 2,736 2,736 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 11,702,818 160,573 19ms 40ms 309ms 2.0min 0 transport_latency_assumed best_bid_ask i 11,672,227 102,630 22ms 42ms 268ms 26.0s 0 transport_latency_assumed best_bid_ask m 11,696,405 5,970,469 6ms 22ms 138ms 5.7s 0 transport_latency_assumed best_bid_ask n 11,698,377 9,683 46ms 76ms 361ms 24.8s 0 transport_latency_assumed best_bid_ask o 11,697,746 5,462,708 6ms 23ms 138ms 12.0s 0 transport_latency_assumed book h 143,520 11,065 26ms 480ms 9.1h 131.6d 0 book_staleness book i 138,993 10,173 28ms 1.9s 5.6h 113.1d 0 book_staleness book m 146,448 79,913 9ms 183ms 9.6h 113.1d 0 book_staleness book n 144,192 12,784 57ms 7.6s 9.6h 113.1d 0 book_staleness book o 147,094 74,002 9ms 194ms 9.7h 113.1d 0 book_staleness last_trade_price h 66,525 1,111 22ms 163ms 1.1s 34.7s 0 transport_latency_assumed last_trade_price i 64,041 561 28ms 532ms 9.8s 25.8s 0 transport_latency_assumed last_trade_price m 66,227 33,674 8ms 38ms 277ms 2.9s 0 transport_latency_assumed last_trade_price n 65,035 247 54ms 1.0s 10.1s 24.5s 0 transport_latency_assumed last_trade_price o 66,206 31,216 8ms 37ms 231ms 5.1s 0 transport_latency_assumed market_resolved h 720 4 21ms 41.5s 55.4s 57.2s 0 transport_latency_assumed market_resolved i 720 89 23ms 30.2s 43.5s 45.8s 0 transport_latency_assumed market_resolved m 720 352 6ms 34.9s 47.9s 50.3s 0 transport_latency_assumed market_resolved n 720 22 47ms 326ms 58.2s 58.3s 0 transport_latency_assumed market_resolved o 720 275 7ms 33.4s 46.3s 48.9s 0 transport_latency_assumed new_market h 950 249 179ms 17.4s 29.2s 1.6min 0 transport_latency_assumed new_market i 950 253 82ms 14.8s 27.8s 1.6min 0 transport_latency_assumed new_market m 950 569 51ms 18.6s 47.8s 1.6min 0 transport_latency_assumed new_market n 950 174 82ms 17.3s 37.7s 1.4min 0 transport_latency_assumed new_market o 950 318 87ms 15.7s 28.3s 1.8min 0 transport_latency_assumed price_change h 117,762,284 1,900,110 20ms 52ms 577ms 2.0min 0 transport_latency_assumed price_change i 116,576,856 1,066,394 22ms 67ms 1.9s 26.2s 0 transport_latency_assumed price_change m 117,541,000 60,543,994 6ms 27ms 173ms 9.1s 0 transport_latency_assumed price_change n 117,284,138 161,254 47ms 119ms 4.3s 24.8s 0 transport_latency_assumed price_change o 117,584,332 54,213,054 6ms 27ms 162ms 18.6s 0 transport_latency_assumed tick_size_change h 2,736 59 20ms 47ms 205ms 3.3s 0 transport_latency_assumed tick_size_change i 2,736 36 22ms 48ms 226ms 640ms 0 transport_latency_assumed tick_size_change m 2,736 1,420 6ms 29ms 72ms 300ms 0 transport_latency_assumed tick_size_change n 2,736 not meas. 47ms 79ms 194ms 343ms 0 transport_latency_assumed tick_size_change o 2,736 1,221 7ms 31ms 150ms 226ms 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-08/13/2026-10-08T13.parquet sha256sum 2026-10-08T13.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.