Hour audit: 2026-09-14T02
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-14T02 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-14T02:00:00.000161229+00:00 · last event 2026-09-14T02:59:59.999930110+00:00
VOLUME 109,284,157 rows · 1,067,118,192 bytes (1017.68 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 109,248,156 · f: 109,235,618 · g: 109,214,642 · h: 109,169,261 · e: 109,161,971 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 105,708,178 (96.73%) · f: 90,633 (0.08%) · g: 27,425 (0.03%) · h: 3,209,583 (2.94%) · e: 248,338 (0.23%) (rows of the merged file that came from it; these partition it)
5 product-machine pairs publish no supplied count; the figures above still sum to the file's 109,284,157 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 baa9490d4127180830f2ca38ee6a4b9027fd84261ca6512a61a7a393ec530f5d
the corpus checksum ledger names this file with the same digest
joined 109,286,343 to merged 109,284,157, minus 2,186 (minus 0.0020%)
boundary drops 2,186 · 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-14T04:35:26Z 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 11,830,019 124,072,421 0-45 5d8045843d2297d517b08d2e4c9e1af9ed1a8f9982883a5190c095e393fc1654 book 120,238 12,687,652 46-46 0758034e58ea43c2861a19170744ce74117c050aa44f2161cb685790d3aab432 last_trade_price 43,471 2,487,799 47-47 e102ee163f34aec412b7eb572a7ddba0f8fd3045421e07052f1004c9c6475924 market_resolved 1,122 184,157 48-48 b382f07c2dcb8a6c02d76e779ce213f579485471d0ee7b5b31f69591fcc39a46 new_market 735 82,980 49-49 aeaeaf905a9fd9046a315c33cca2d405ea8069e87cf33c6f5178d713543dbe5a price_change 97,286,276 926,274,009 50-421 ee123142bb11a7bbc7422a7340415c3b84ac3edf5553560ad1fe6e683507bbcb tick_size_change 2,296 81,714 422-422 be50fb057f91c512cce528f0314c9038584bdf204808a9ab619ae67dfa739fa0 EVENT MIX count share price_change 97,286,276 89.02% best_bid_ask 11,830,019 10.83% book 120,238 0.11% last_trade_price 43,471 0.04% tick_size_change 2,296 <0.01% market_resolved 1,122 <0.01% new_market 735 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,830,267 11,830,019 248 148 FULL book 120,240 120,238 2 12,563 FULL last_trade_price 43,471 43,471 0 1 FULL market_resolved 1,122 1,122 0 0 FULL new_market 735 735 0 0 FULL price_change 97,288,212 97,286,276 1,936 190 FULL tick_size_change 2,296 2,296 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,829,691 11,482,694 4ms 8ms 63ms 4.9s 0 transport_latency_assumed best_bid_ask e 11,828,456 24,076 39ms 43ms 107ms 3.5s 0 transport_latency_assumed best_bid_ask f 11,828,520 8,209 47ms 52ms 125ms 3.1s 0 transport_latency_assumed best_bid_ask g 11,826,742 542 82ms 100ms 247ms 9.3s 0 transport_latency_assumed best_bid_ask h 11,828,374 314,498 18ms 23ms 85ms 43.4s 0 transport_latency_assumed book c 94,623 89,817 6ms 28ms 9.5h 88.6d 0 book_staleness book e 92,154 2,181 40ms 75ms 13.7min 88.6d 0 book_staleness book f 91,506 853 48ms 89ms 2.7s 88.6d 0 book_staleness book g 111,738 21,127 87ms 54.0min 6.7d 107.2d 0 book_staleness book h 92,930 6,260 21ms 46ms 45.6min 88.5d 0 book_staleness last_trade_price c 43,402 41,421 10ms 43ms 219ms 5.0s 0 transport_latency_assumed last_trade_price e 43,379 196 45ms 95ms 366ms 5.0s 0 transport_latency_assumed last_trade_price f 43,386 69 53ms 106ms 377ms 5.0s 0 transport_latency_assumed last_trade_price g 43,332 34 91ms 184ms 701ms 5.9s 0 transport_latency_assumed last_trade_price h 43,361 1,751 23ms 60ms 260ms 9.2s 0 transport_latency_assumed market_resolved c 1,118 1,098 4ms 8ms 29ms 261ms 0 transport_latency_assumed market_resolved e 1,118 not meas. 40ms 122ms 287ms 687ms 0 transport_latency_assumed market_resolved f 1,118 not meas. 48ms 129ms 345ms 56.0s 0 transport_latency_assumed market_resolved g 1,118 not meas. 87ms 247ms 562ms 56.5s 0 transport_latency_assumed market_resolved h 1,118 24 19ms 63ms 178ms 59.7s 0 transport_latency_assumed new_market c 522 322 56ms 13.4s 34.9s 3.3h 0 transport_latency_assumed new_market e 522 99 139ms 14.8s 37.4s 4.9h 0 transport_latency_assumed new_market f 522 98 135ms 15.6s 36.9s 4.4h 0 transport_latency_assumed new_market g 522 46 143ms 11.9s 32.3s 34.1min 0 transport_latency_assumed new_market h 522 170 111ms 13.3s 42.4s 2.9h 0 transport_latency_assumed price_change c 97,276,504 94,090,614 5ms 9ms 71ms 6.5s 0 transport_latency_assumed price_change e 97,194,046 221,778 39ms 45ms 131ms 5.0s 0 transport_latency_assumed price_change f 97,268,270 81,404 47ms 55ms 152ms 4.9s 0 transport_latency_assumed price_change g 97,228,894 5,676 82ms 101ms 295ms 9.5s 0 transport_latency_assumed price_change h 97,200,660 2,886,804 18ms 25ms 96ms 43.4s 0 transport_latency_assumed tick_size_change c 2,296 2,212 4ms 9ms 166ms 205ms 0 transport_latency_assumed tick_size_change e 2,296 8 39ms 43ms 77ms 147ms 0 transport_latency_assumed tick_size_change f 2,296 not meas. 47ms 54ms 98ms 131ms 0 transport_latency_assumed tick_size_change g 2,296 not meas. 82ms 96ms 146ms 272ms 0 transport_latency_assumed tick_size_change h 2,296 76 18ms 25ms 56ms 1.7s 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-14/02/2026-09-14T02.parquet sha256sum 2026-09-14T02.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.