Hour audit: 2026-09-28T21
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-09-28T21 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-28T21:00:00.000004061+00:00 · last event 2026-09-28T21:59:59.999983226+00:00
VOLUME 89,117,604 rows · 939,414,033 bytes (895.90 MiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured c: 88,912,398 · k: 88,891,553 · h: 88,889,308 · i: 88,876,738 · g: 88,799,692 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 80,619,190 (90.46%) · k: 2,690,122 (3.02%) · h: 659,962 (0.74%) · i: 5,099,970 (5.72%) · g: 48,360 (0.05%) (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 89,117,604 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 6822c17cf58f13e7e3ba5816287333fe5233b8ee97851f46813339215e847b4d
the corpus checksum ledger names this file with the same digest
joined 89,118,949 to merged 89,117,604, minus 1,345 (minus 0.0015%)
boundary drops 1,345 · 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-09-29T00:05:22Z as cghik
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,542,701 108,607,188 0-36 7f9672d9f2e0894eaabda3c9319b77f8a836cbad6b18bcbd0e2729a26369dfcd book 310,266 30,765,031 37-38 6a95304ecb378bc33c354aa7ff33c47fdbb653dfcd8d137152507c56b662ba00 last_trade_price 45,029 2,604,621 39-39 756b7a09439ab6fa3a3bb49caa4adbf96095a0827c26e9391cc7c0e237be040d market_resolved 1,008 146,405 40-40 5ccfe4aa3b76b12575040de8059372e9049d949e9f3fa94963271b84983cec7b new_market 596 66,195 41-41 4be1d3225b167a6fb02af9cce5a353113be542383ae5219ce4e13bb3a191fdea price_change 79,215,604 796,114,411 42-344 e8dbba6184e1160e29e8c24ccc79ca252dd688d8929a9e14a7f165f339bdc78f tick_size_change 2,400 88,886 345-345 97e5474bab122f58082b3d942570cb610a151e4338f32620f14db93cd671804c EVENT MIX count share price_change 79,215,604 88.89% best_bid_ask 9,542,701 10.71% book 310,266 0.35% last_trade_price 45,029 0.05% tick_size_change 2,400 <0.01% market_resolved 1,008 <0.01% new_market 596 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,542,869 9,542,701 168 147 FULL book 310,374 310,266 108 98,286 FULL last_trade_price 45,030 45,029 1 0 FULL market_resolved 1,008 1,008 0 0 FULL new_market 596 596 0 0 FULL price_change 79,216,672 79,215,604 1,068 131 FULL tick_size_change 2,400 2,400 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,541,725 8,729,176 5ms 10ms 88ms 4.6s 0 transport_latency_assumed best_bid_ask g 9,539,345 347 80ms 98ms 316ms 12.4s 0 transport_latency_assumed best_bid_ask h 9,541,135 50,532 18ms 22ms 92ms 7.8s 0 transport_latency_assumed best_bid_ask i 9,540,622 520,931 11ms 16ms 83ms 4.2s 0 transport_latency_assumed best_bid_ask k 9,541,144 241,715 12ms 18ms 69ms 6.3s 0 transport_latency_assumed book c 146,298 125,742 12ms 10.8h 27.2d 120.4d 0 book_staleness book g 141,461 42,937 196ms 10.8h 23.3d 122.0d 0 book_staleness book h 145,209 46,859 36ms 10.8h 24.0d 103.5d 0 book_staleness book i 144,191 49,704 35ms 10.8h 23.3d 122.0d 0 book_staleness book k 140,964 45,024 23ms 10.8h 23.3d 122.0d 0 book_staleness last_trade_price c 44,864 39,605 6ms 24ms 267ms 1.8s 0 transport_latency_assumed last_trade_price g 44,547 21 88ms 612ms 4.9s 12.5s 0 transport_latency_assumed last_trade_price h 44,763 749 19ms 56ms 491ms 3.7s 0 transport_latency_assumed last_trade_price i 44,590 2,515 13ms 82ms 843ms 2.3s 0 transport_latency_assumed last_trade_price k 44,770 2,139 13ms 37ms 314ms 1.2s 0 transport_latency_assumed market_resolved c 961 866 5ms 17ms 32.6s 33.7s 0 transport_latency_assumed market_resolved g 961 not meas. 81ms 216ms 31.4s 54.2s 0 transport_latency_assumed market_resolved h 961 10 19ms 49ms 29.4s 54.2s 0 transport_latency_assumed market_resolved i 961 106 12ms 74ms 54.4s 58.6s 0 transport_latency_assumed market_resolved k 961 26 13ms 33ms 28.1s 53.4s 0 transport_latency_assumed new_market c 432 196 75ms 10.8s 1.2min 1.5min 0 transport_latency_assumed new_market g 432 39 240ms 12.5s 1.1min 1.7min 0 transport_latency_assumed new_market h 432 117 108ms 13.9s 1.2min 1.7min 0 transport_latency_assumed new_market i 432 160 77ms 10.9s 1.0min 1.6min 0 transport_latency_assumed new_market k 432 84 86ms 597ms 26.1s 1.2min 0 transport_latency_assumed price_change c 79,175,718 71,721,456 5ms 12ms 113ms 5.3s 0 transport_latency_assumed price_change g 79,070,546 5,016 80ms 115ms 1.5s 12.5s 0 transport_latency_assumed price_change h 79,154,408 561,674 18ms 26ms 163ms 7.9s 0 transport_latency_assumed price_change i 79,143,542 4,526,358 11ms 19ms 210ms 5.3s 0 transport_latency_assumed price_change k 79,160,882 2,401,100 12ms 20ms 104ms 6.4s 0 transport_latency_assumed tick_size_change c 2,400 2,149 5ms 11ms 194ms 355ms 0 transport_latency_assumed tick_size_change g 2,400 not meas. 79ms 93ms 396ms 1.2s 0 transport_latency_assumed tick_size_change h 2,400 21 18ms 21ms 110ms 2.5s 0 transport_latency_assumed tick_size_change i 2,400 196 11ms 15ms 49ms 138ms 0 transport_latency_assumed tick_size_change k 2,400 34 12ms 16ms 125ms 264ms 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-09-28/21/2026-09-28T21.parquet sha256sum 2026-09-28T21.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.