Hour audit: 2026-09-21T10
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.
1 finding
- a machine expected this hour contributed nothing. Of the 5 machines expected to be capturing this hour, 1 contributed no rows: g. The hour is still whole on minutes; it simply rests on 4 machines rather than 5.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-21T10 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-21T10:00:00.000090736+00:00 · last event 2026-09-21T10:59:59.999944198+00:00
VOLUME 116,231,916 rows · 1,227,772,368 bytes (1.14 GiB) · 7 products, all holding rows
WITNESSES cefh — 4 machines contributed rows
captured h: 115,021,300 · e: 114,748,428 · f: 111,352,665 · c: 107,578,792 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 13,820,167 (11.89%) · e: 1,066,980 (0.92%) · f: 526,514 (0.45%) · c: 100,818,255 (86.74%) (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 116,231,916 rows exactly, so those pairs supplied none
5 expected (cefgh), 1 contributed nothing: g
INTEGRITY sha256 1a6c9f64a17d3812dbc640c2635483a9f0eaf1eb4497567133ca664dc6d5827a
the corpus checksum ledger names this file with the same digest
joined 116,233,204 to merged 116,231,916, minus 1,288 (minus 0.0011%)
boundary drops 1,288 · 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-21T11:56:37Z as cefh
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 7/8 pass, 1 finding
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
FINDING a machine expected this hour contributed nothing
PASS the checksum ledger names this file
PASS the hour is whole
PASS a boundary guard ran
UPSTREAM our incident register was checked against the venue's own status feed at 2026-09-23T20:35Z and names no event in this hour. That is a statement about what they published, not a check that every message they sent reached us.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 10,167,158 115,981,092 0-38 510a41f890ab105bc41bfb233d81372b4844371ad6a1a9c059aa1f91ab71dbe6 book 932,391 63,991,838 39-42 ef0e7bd43b1ed910b49460aa625bbd65cbbeea30c8a1e3dec7c0aed640818d25 last_trade_price 61,106 3,429,874 43-43 2262a66afaac04bfd002913620eb9d5ddad7bdfb0efef3c23180f340a3add57f market_resolved 986 142,439 44-44 5f3719d0a68c36846dbc9ecaade0e158dd4e3ccc2d59648441779c0e6b543e80 new_market 3,487 336,376 45-45 fa4aced361618c4de41286c38fe89b01e0e3e7f7f43b571c17806c5b8f6c020c price_change 105,063,480 1,042,450,419 46-446 33f54ba62ebbfa8b33ab958ca00e08ee0bee9a7fe45b9b2553ddb00593da6321 tick_size_change 3,308 120,222 447-447 d24a772b5e3217b4317abd23ffd5ebaea7024e0e173cafa580899b151f83d660 EVENT MIX count share price_change 105,063,480 90.39% best_bid_ask 10,167,158 8.75% book 932,391 0.80% last_trade_price 61,106 0.05% new_market 3,487 <0.01% tick_size_change 3,308 <0.01% market_resolved 986 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,167,270 10,167,158 112 66,590 PARTIAL book 932,519 932,391 128 151,208 PARTIAL last_trade_price 61,106 61,106 0 2,950 PARTIAL market_resolved 986 986 0 874 PARTIAL new_market 3,487 3,487 0 2,195 PARTIAL price_change 105,064,528 105,063,480 1,048 116,281 PARTIAL tick_size_change 3,308 3,308 0 827 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,441,973 8,881,215 5ms 17ms 162ms 4.5s 0 transport_latency_assumed best_bid_ask e 10,153,686 86,894 40ms 63ms 385ms 30.0s 0 transport_latency_assumed best_bid_ask f 9,820,292 27,812 49ms 73ms 407ms 32.8s 0 transport_latency_assumed best_bid_ask h 10,162,913 1,171,237 18ms 35ms 281ms 47.6s 0 transport_latency_assumed book c 756,740 713,016 3.5min 2.8d 43.8d 114.5d 0 book_staleness book e 145,964 17,247 67ms 4.4min 14.0d 114.5d 0 book_staleness book f 486,403 179,589 2.4min 2.8d 40.7d 114.5d 0 book_staleness book h 133,832 22,539 23ms 318ms 17.1h 96.0d 0 book_staleness last_trade_price c 55,770 51,784 6ms 31ms 238ms 1.4s 0 transport_latency_assumed last_trade_price e 58,089 550 47ms 1.4s 12.1s 30.0s 0 transport_latency_assumed last_trade_price f 56,224 189 58ms 1.5s 12.5s 32.9s 0 transport_latency_assumed last_trade_price h 60,952 8,583 20ms 94ms 582ms 13.1s 0 transport_latency_assumed market_resolved c 881 804 5ms 30.8s 4.5min 5.1min 0 transport_latency_assumed market_resolved e 874 87 42ms 583ms 50.7s 58.7s 0 transport_latency_assumed market_resolved f 901 49 50ms 32.8s 4.9min 4.9min 0 transport_latency_assumed market_resolved h 874 46 19ms 221ms 54.2s 1.0min 0 transport_latency_assumed new_market c 2,333 1,645 125ms 35.2s 5.1min 5.6min 0 transport_latency_assumed new_market e 2,195 582 238ms 25.6s 49.4s 59.5s 0 transport_latency_assumed new_market f 2,195 459 247ms 28.7s 47.4s 35.9min 0 transport_latency_assumed new_market h 2,195 801 162ms 24.2s 44.4s 1.0min 0 transport_latency_assumed price_change c 97,317,951 91,166,707 5ms 20ms 176ms 4.7s 0 transport_latency_assumed price_change e 104,384,312 961,616 41ms 100ms 2.7s 30.1s 0 transport_latency_assumed price_change f 100,983,518 318,416 49ms 114ms 2.5s 32.9s 0 transport_latency_assumed price_change h 104,657,226 12,616,741 18ms 42ms 354ms 48.0s 0 transport_latency_assumed tick_size_change c 3,144 3,084 5ms 8ms 31ms 179ms 0 transport_latency_assumed tick_size_change e 3,308 4 40ms 44ms 107ms 265ms 0 transport_latency_assumed tick_size_change f 3,132 not meas. 48ms 61ms 311ms 590ms 0 transport_latency_assumed tick_size_change h 3,308 220 18ms 22ms 45ms 442ms 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-21/10/2026-09-21T10.parquet sha256sum 2026-09-21T10.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.