Hour audit: 2026-10-04T21
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-04T21 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-04T21:00:00.000068130+00:00 · last event 2026-10-04T21:59:59.999911230+00:00
VOLUME 127,084,468 rows · 1,493,787,983 bytes (1.39 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 126,549,410 · m: 126,473,656 · h: 126,440,861 · i: 126,428,784 · n: 120,727,180 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 59,236,471 (46.61%) · m: 65,786,830 (51.77%) · h: 958,915 (0.75%) · i: 498,585 (0.39%) · n: 603,667 (0.48%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 0796f185e9bd06df3cb13db142189b2a995d615e425ee2bf1aff84810cf409b2
the corpus checksum ledger names this file with the same digest
joined 127,085,778 to merged 127,084,468, minus 1,310 (minus 0.0010%)
boundary drops 1,310 · 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-04T23:21:49Z 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,033,513 139,581,452 0-42 1c3692ff559c0e998a5ac0bed3b32f0ec50f01710fca054b081eb6234ee556a9 book 648,879 63,707,491 43-45 75540fcf6361130ef41bac6fedffcc4fe328b2e27009c88b4b79addd2b527d6a last_trade_price 68,859 3,914,868 46-46 109aa9eaa4a4f5ee1a81ab29e09d90d6cda9d4d996d2b5e44805f42361e62c8f market_resolved 2,869 385,498 47-47 6c26cbea61c74c7f74ee5b7669ac9dcece6f8c72d3a0c30748f07a795266d22a new_market 3,550 324,073 48-48 88479279f2af1543290e51bff1b2648976ece96a081164563f3884fb5ee338b9 price_change 115,321,490 1,284,230,691 49-488 0a793d235970ee19fd114bede79da0a33386bb54d7c70012ad9e5bf832ae5845 tick_size_change 5,308 196,041 489-489 91e3f0973a8f5b3129e03a109282ddf2178dc5d526157d5d787259ec5f935845 EVENT MIX count share price_change 115,321,490 90.74% best_bid_ask 11,033,513 8.68% book 648,879 0.51% last_trade_price 68,859 0.05% tick_size_change 5,308 <0.01% new_market 3,550 <0.01% market_resolved 2,869 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,033,639 11,033,513 126 745 FULL book 648,891 648,879 12 235,479 FULL last_trade_price 68,859 68,859 0 86 FULL market_resolved 2,869 2,869 0 0 FULL new_market 3,550 3,550 0 0 FULL price_change 115,322,662 115,321,490 1,172 2,132 FULL tick_size_change 5,308 5,308 0 69 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 11,030,298 78,369 19ms 34ms 436ms 1.4min 0 transport_latency_assumed best_bid_ask i 11,030,805 40,901 22ms 38ms 302ms 11.9s 0 transport_latency_assumed best_bid_ask m 11,032,004 5,742,801 5ms 16ms 146ms 5.7s 0 transport_latency_assumed best_bid_ask n 10,517,016 8,671 48ms 79ms 428ms 23.8s 0 transport_latency_assumed best_bid_ask o 11,032,272 5,162,771 5ms 16ms 171ms 17.6s 0 transport_latency_assumed book h 143,663 3,776 25ms 287ms 19.7min 109.4d 0 book_staleness book i 143,665 3,778 28ms 542ms 8.0min 109.4d 0 book_staleness book m 142,816 75,592 8ms 43ms 6.3s 63.4d 0 book_staleness book n 631,603 491,739 9.3min 23.4h 43.3d 128.0d 0 book_staleness book o 151,805 73,994 8ms 228ms 12.3h 109.4d 0 book_staleness last_trade_price h 68,472 530 21ms 154ms 1.6s 50.3s 0 transport_latency_assumed last_trade_price i 68,535 232 27ms 321ms 3.2s 11.4s 0 transport_latency_assumed last_trade_price m 68,746 36,691 6ms 25ms 269ms 5.7s 0 transport_latency_assumed last_trade_price n 64,737 131 58ms 674ms 8.2s 23.9s 0 transport_latency_assumed last_trade_price o 68,707 31,275 7ms 24ms 248ms 3.7s 0 transport_latency_assumed market_resolved h 2,360 15 21ms 200ms 46.5s 54.7s 0 transport_latency_assumed market_resolved i 2,360 6 25ms 339ms 55.2s 56.2s 0 transport_latency_assumed market_resolved m 2,360 1,404 7ms 8.2s 53.8s 56.3s 0 transport_latency_assumed market_resolved n 2,703 427 53ms 7.3min 11.2min 11.4min 0 transport_latency_assumed market_resolved o 2,360 1,017 7ms 42ms 50.0s 55.8s 0 transport_latency_assumed new_market h 2,080 419 241ms 43.6s 1.0min 1.8min 0 transport_latency_assumed new_market i 2,080 800 356ms 45.7s 1.0min 1.8min 0 transport_latency_assumed new_market m 2,080 980 105ms 47.5s 1.0min 1.5min 0 transport_latency_assumed new_market n 2,486 469 15.1s 4.4min 5.7min 5.8min 0 transport_latency_assumed new_market o 2,080 882 266ms 47.0s 1.0min 1.6min 0 transport_latency_assumed price_change h 115,188,680 875,751 19ms 41ms 658ms 1.4min 0 transport_latency_assumed price_change i 115,176,031 452,834 22ms 48ms 599ms 16.2s 0 transport_latency_assumed price_change m 115,220,342 59,926,836 5ms 18ms 189ms 6.4s 0 transport_latency_assumed price_change n 109,503,603 102,216 49ms 96ms 1.6s 23.9s 0 transport_latency_assumed price_change o 115,286,878 53,963,853 6ms 18ms 208ms 26.1s 0 transport_latency_assumed tick_size_change h 5,308 55 19ms 44ms 1.1s 35.6s 0 transport_latency_assumed tick_size_change i 5,308 34 23ms 51ms 287ms 3.2s 0 transport_latency_assumed tick_size_change m 5,308 2,526 6ms 32ms 412ms 605ms 0 transport_latency_assumed tick_size_change n 5,032 14 49ms 79ms 336ms 853ms 0 transport_latency_assumed tick_size_change o 5,308 2,679 5ms 20ms 217ms 530ms 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-04/21/2026-10-04T21.parquet sha256sum 2026-10-04T21.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.