Hour audit: 2026-09-14T09
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-14T09 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-14T09:00:00.000001949+00:00 · last event 2026-09-14T09:59:59.999999159+00:00
VOLUME 108,555,828 rows · 1,099,122,419 bytes (1.02 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 108,181,589 · e: 108,163,487 · g: 108,158,537 · h: 108,153,594 · c: 104,212,260 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 93,344 (0.09%) · e: 281,570 (0.26%) · g: 17,551 (0.02%) · h: 7,518,951 (6.93%) · c: 100,644,412 (92.71%) (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 108,555,828 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 8ce574f92f241b73ba362a7a8c37ac65048a2296899e1a98626cf31c62282454
the corpus checksum ledger names this file with the same digest
joined 108,557,896 to merged 108,555,828, minus 2,068 (minus 0.0019%)
boundary drops 2,068 · 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-14T10:58: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 10,747,512 115,494,310 0-40 3748720d2e350b0227ee62ad553c8fc1df92fd5eb984b5c3f449a15f28135ec1 book 455,767 49,526,507 41-42 bd9420d7481142459279594aa80fe0889c9e04e5ad8ad8e49971e82247167444 last_trade_price 49,373 2,838,303 43-43 2f131eed68da676380e6ec0389aa40b80089752baec3e816b21988a323f74d57 market_resolved 880 142,741 44-44 a09419a6659b98d683acca1e62e82bd7b64727fdb3271a145c68187c0c83a76d new_market 262 32,319 45-45 04256885571c642167764bba93d206277d5c1685b6137e89aec53a615a6010f7 price_change 97,299,798 929,769,117 46-417 8eee395e0b2bb359cc9deabeb321ef7c665e1e0294c3a210a968ad5fed28709f tick_size_change 2,236 83,192 418-418 02307f62534ef8c9ea5fc46e074600d61cacd575bb804b84690a85e180f1e711 EVENT MIX count share price_change 97,299,798 89.63% best_bid_ask 10,747,512 9.90% book 455,767 0.42% last_trade_price 49,373 0.05% tick_size_change 2,236 <0.01% market_resolved 880 <0.01% new_market 262 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,747,738 10,747,512 226 401 FULL book 455,789 455,767 22 163,563 FULL last_trade_price 49,373 49,373 0 66 FULL market_resolved 880 880 0 3 FULL new_market 262 262 0 0 FULL price_change 97,301,618 97,299,798 1,820 402 FULL tick_size_change 2,236 2,236 0 11 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,336,770 10,002,729 5ms 9ms 60ms 11.5s 0 transport_latency_assumed best_bid_ask e 10,746,177 23,434 40ms 44ms 107ms 2.3s 0 transport_latency_assumed best_bid_ask f 10,746,350 7,211 47ms 52ms 125ms 6.3s 0 transport_latency_assumed best_bid_ask g 10,744,461 345 81ms 95ms 209ms 14.2s 0 transport_latency_assumed best_bid_ask h 10,746,872 713,793 18ms 23ms 71ms 3.8s 0 transport_latency_assumed book c 442,266 431,715 4.6min 1.7d 33.6d 107.5d 0 book_staleness book e 104,489 2,440 42ms 122ms 1.7h 89.0d 0 book_staleness book f 102,579 484 49ms 125ms 897ms 88.8d 0 book_staleness book g 121,128 12,550 87ms 5.9min 6.9d 89.0d 0 book_staleness book h 102,993 8,578 21ms 50ms 734ms 89.0d 0 book_staleness last_trade_price c 47,486 45,134 10ms 45ms 215ms 5.0s 0 transport_latency_assumed last_trade_price e 49,243 293 47ms 118ms 694ms 5.0s 0 transport_latency_assumed last_trade_price f 49,306 96 54ms 139ms 686ms 6.4s 0 transport_latency_assumed last_trade_price g 49,186 13 92ms 236ms 1.6s 14.3s 0 transport_latency_assumed last_trade_price h 49,283 3,837 23ms 69ms 275ms 5.0s 0 transport_latency_assumed market_resolved c 840 830 5ms 8ms 2.4min 4.4min 0 transport_latency_assumed market_resolved e 843 26 41ms 121ms 1.0min 1.0min 0 transport_latency_assumed market_resolved f 843 not meas. 49ms 128ms 1.0min 1.0min 0 transport_latency_assumed market_resolved g 843 3 85ms 234ms 383ms 735ms 0 transport_latency_assumed market_resolved h 843 21 19ms 57ms 1.0min 1.0min 0 transport_latency_assumed new_market c 208 158 27ms 13.7s 21.6s 4.0min 0 transport_latency_assumed new_market e 207 11 61ms 442ms 56.1s 1.6min 0 transport_latency_assumed new_market f 207 16 60ms 274ms 15.7s 1.2min 0 transport_latency_assumed new_market g 207 18 84ms 397ms 20.7s 1.2min 0 transport_latency_assumed new_market h 207 59 32ms 142ms 13.6s 55.5s 0 transport_latency_assumed price_change c 93,382,498 90,161,754 5ms 10ms 68ms 14.0s 0 transport_latency_assumed price_change e 97,260,292 255,358 40ms 46ms 149ms 2.3s 0 transport_latency_assumed price_change f 97,280,068 85,536 48ms 55ms 170ms 6.3s 0 transport_latency_assumed price_change g 97,240,476 4,622 81ms 99ms 296ms 14.2s 0 transport_latency_assumed price_change h 97,251,160 6,792,528 18ms 25ms 86ms 3.8s 0 transport_latency_assumed tick_size_change c 2,192 2,092 5ms 11ms 130ms 282ms 0 transport_latency_assumed tick_size_change e 2,236 8 40ms 44ms 106ms 357ms 0 transport_latency_assumed tick_size_change f 2,236 1 47ms 51ms 129ms 209ms 0 transport_latency_assumed tick_size_change g 2,236 not meas. 80ms 92ms 163ms 361ms 0 transport_latency_assumed tick_size_change h 2,236 135 18ms 23ms 69ms 155ms 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/09/2026-09-14T09.parquet sha256sum 2026-09-14T09.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.