Hour audit: 2026-09-16T13
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-16T13 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-16T13:00:00.000017337+00:00 · last event 2026-09-16T13:59:59.999257145+00:00
VOLUME 119,059,869 rows · 1,276,841,840 bytes (1.19 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 118,286,879 · f: 118,154,463 · e: 118,091,356 · g: 117,493,734 · c: 114,381,078 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 10,279,538 (8.63%) · f: 366,342 (0.31%) · e: 763,370 (0.64%) · g: 46,226 (0.04%) · c: 107,604,393 (90.38%) (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 119,059,869 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 2107b4285a8c9ea11bd14276609eca6527529cb350f36965f52a2b8f0626d9d0
the corpus checksum ledger names this file with the same digest
joined 119,064,555 to merged 119,059,869, minus 4,686 (minus 0.0039%)
boundary drops 4,686 · 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-16T15:04:02Z as cefgh
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 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 12,409,942 143,804,932 0-47 77444ce9376bab65723538fed37468ee64d50063c4249af27ef1efc824915aac book 975,334 72,875,639 48-51 a6993db33035bcb43eac1ce12d2384845b456ff60715a1583118e0d8fe4a55e2 last_trade_price 60,618 3,438,632 52-52 2986529ac2567206a97db7fe0c7781067a7eea0bf4fd3c0265aa76cf17f49cce market_resolved 907 146,850 53-53 6980ab597f5367e567ffa8ce9412d6ad92a5614ef2932c6abff3d557cdf6d985 new_market 1,442 141,160 54-54 37626c1718e2994dd6b0b84a69e38fb51a79301c0b675889ae9747e4f95a1310 price_change 105,607,430 1,054,929,729 55-457 e46f51dd43567adf8ceaea17741d6c7a2164f8ecba68854fb25c71c8049e7389 tick_size_change 4,196 151,374 458-458 f9c3ed8adfd434a089a213465560a0466775cf87e31e2c5ac3c1121a990ef6dd EVENT MIX count share price_change 105,607,430 88.70% best_bid_ask 12,409,942 10.42% book 975,334 0.82% last_trade_price 60,618 0.05% tick_size_change 4,196 <0.01% new_market 1,442 <0.01% market_resolved 907 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,410,048 12,409,942 106 480 FULL book 978,984 975,334 3,650 171,789 FULL last_trade_price 60,618 60,618 0 62 FULL market_resolved 907 907 0 6 FULL new_market 1,442 1,442 0 0 FULL price_change 105,608,360 105,607,430 930 152 FULL tick_size_change 4,196 4,196 0 33 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,959,238 11,290,328 5ms 15ms 109ms 5.0s 0 transport_latency_assumed best_bid_ask e 12,402,879 61,578 39ms 51ms 248ms 32.1s 0 transport_latency_assumed best_bid_ask f 12,402,272 21,768 46ms 61ms 268ms 23.4s 0 transport_latency_assumed best_bid_ask g 12,397,352 2,270 79ms 101ms 542ms 26.8s 0 transport_latency_assumed best_bid_ask h 12,403,657 1,033,998 19ms 32ms 161ms 52.9s 0 transport_latency_assumed book c 629,934 520,947 2.5min 22.0h 35.8d 109.6d 0 book_staleness book e 326,365 146,476 30.4s 46.0min 25.0d 109.7d 0 book_staleness book f 315,181 138,928 25.7s 36.5min 25.0d 109.6d 0 book_staleness book g 145,443 17,641 96ms 2.7min 9.1d 109.6d 0 book_staleness book h 325,186 151,342 29.4s 38.6min 25.0d 109.6d 0 book_staleness last_trade_price c 58,144 54,511 11ms 54ms 274ms 5.0s 0 transport_latency_assumed last_trade_price e 59,388 432 57ms 750ms 8.1s 31.2s 0 transport_latency_assumed last_trade_price f 59,311 144 65ms 845ms 7.2s 23.6s 0 transport_latency_assumed last_trade_price g 57,695 51 99ms 1.3s 11.4s 26.7s 0 transport_latency_assumed last_trade_price h 60,088 5,480 27ms 111ms 679ms 11.0s 0 transport_latency_assumed market_resolved c 872 834 5ms 26ms 3.7min 5.5min 0 transport_latency_assumed market_resolved e 869 11 40ms 137ms 625ms 39.2s 0 transport_latency_assumed market_resolved f 868 not meas. 46ms 127ms 658ms 39.2s 0 transport_latency_assumed market_resolved g 869 1 82ms 229ms 920ms 54.3s 0 transport_latency_assumed market_resolved h 869 61 20ms 60ms 241ms 42.5s 0 transport_latency_assumed new_market c 911 515 121ms 4.1min 17.2min 17.3min 0 transport_latency_assumed new_market e 911 242 288ms 4.1min 17.2min 17.3min 0 transport_latency_assumed new_market f 911 152 221ms 4.0min 17.2min 17.3min 0 transport_latency_assumed new_market g 911 217 458ms 4.0min 17.1min 17.3min 0 transport_latency_assumed new_market h 911 316 189ms 4.0min 17.3min 17.3min 0 transport_latency_assumed price_change c 101,727,911 95,733,497 6ms 18ms 131ms 5.6s 0 transport_latency_assumed price_change e 105,296,748 554,580 39ms 68ms 1.2s 32.3s 0 transport_latency_assumed price_change f 105,371,728 205,342 46ms 80ms 1.5s 23.9s 0 transport_latency_assumed price_change g 104,887,272 26,046 80ms 131ms 2.9s 26.8s 0 transport_latency_assumed price_change h 105,491,972 9,087,965 19ms 38ms 240ms 53.0s 0 transport_latency_assumed tick_size_change c 4,068 3,761 6ms 22ms 98ms 358ms 0 transport_latency_assumed tick_size_change e 4,196 51 39ms 57ms 278ms 9.6s 0 transport_latency_assumed tick_size_change f 4,192 8 46ms 85ms 231ms 4.6s 0 transport_latency_assumed tick_size_change g 4,192 not meas. 79ms 100ms 728ms 2.6s 0 transport_latency_assumed tick_size_change h 4,196 376 20ms 40ms 153ms 384ms 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-16/13/2026-09-16T13.parquet sha256sum 2026-09-16T13.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.