Hour audit: 2026-09-14T14
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-14T14 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-14T14:00:00.000030289+00:00 · last event 2026-09-14T14:59:59.999897511+00:00
VOLUME 115,462,959 rows · 1,234,397,221 bytes (1.15 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 114,301,872 · f: 114,268,539 · e: 114,258,442 · g: 113,925,457 · c: 102,471,719 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 17,695,489 (15.33%) · f: 400,924 (0.35%) · e: 1,048,829 (0.91%) · g: 69,358 (0.06%) · c: 96,248,359 (83.36%) (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 115,462,959 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 85a28f95ee7632d788de1c73941de4b4a6eb55d6ea873a2087db954394f62f14
the corpus checksum ledger names this file with the same digest
joined 115,465,173 to merged 115,462,959, minus 2,214 (minus 0.0019%)
boundary drops 2,214 · 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-14T15:59:45Z 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,691,757 122,606,520 0-40 5767ee875c69265ba6b1caaee847a5c97a1b484c3a4d18488633c94d0b050fe6 book 1,198,757 72,345,526 41-45 851a93d1e3dde9bd689f84f9bbf3e98908fe1647ef418769ccfa01f984428613 last_trade_price 58,858 3,409,039 46-46 d154ef7473ddc4a4743259b61f4b73fee168cac89ba03d6df141e179810014c3 market_resolved 979 149,766 47-47 9ead88c754be4b116eefe2b52953c81edb89e7b918dd81607c1a42816c938665 new_market 3,441 325,412 48-48 d38e849015876a3978013d859f23960e748d2794403440590857aa63ca207286 price_change 103,506,255 1,034,140,522 49-443 e7c8ce568b4e51972ac4fc8c6036cf76b0aef2dba29dc8a02e4c74185b2965d5 tick_size_change 2,912 107,876 444-444 3c747426964a464dd3023198892147c54a5b42568ab77669de2a0dfd6ba3aa76 EVENT MIX count share price_change 103,506,255 89.64% best_bid_ask 10,691,757 9.26% book 1,198,757 1.04% last_trade_price 58,858 0.05% new_market 3,441 <0.01% tick_size_change 2,912 <0.01% market_resolved 979 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,692,039 10,691,757 282 1,977 FULL book 1,198,815 1,198,757 58 162,438 FULL last_trade_price 58,862 58,858 4 262 FULL market_resolved 979 979 0 82 FULL new_market 3,477 3,441 36 50 FULL price_change 103,508,089 103,506,255 1,834 1,542 FULL tick_size_change 2,912 2,912 0 36 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,472,181 8,904,292 6ms 15ms 179ms 4.2s 0 transport_latency_assumed best_bid_ask e 10,687,781 96,500 43ms 57ms 371ms 22.1s 0 transport_latency_assumed best_bid_ask f 10,687,838 35,673 48ms 65ms 404ms 39.3s 0 transport_latency_assumed best_bid_ask g 10,678,993 2,723 81ms 112ms 832ms 1.2min 0 transport_latency_assumed best_bid_ask h 10,689,490 1,652,569 18ms 33ms 302ms 52.9s 0 transport_latency_assumed book c 1,159,988 1,148,736 20.7min 2.8d 36.9d 107.7d 0 book_staleness book e 127,616 3,671 47ms 2.3s 9.0h 89.1d 0 book_staleness book f 126,630 2,691 52ms 1.9s 2.6h 89.2d 0 book_staleness book g 173,644 22,889 155ms 5.3h 14.9d 107.7d 0 book_staleness book h 125,590 20,770 22ms 104ms 5.8s 89.2d 0 book_staleness last_trade_price c 51,707 48,466 11ms 51ms 292ms 5.0s 0 transport_latency_assumed last_trade_price e 58,273 564 59ms 702ms 8.6s 22.1s 0 transport_latency_assumed last_trade_price f 58,327 189 65ms 859ms 9.1s 39.2s 0 transport_latency_assumed last_trade_price g 57,266 98 103ms 936ms 17.0s 1.2min 0 transport_latency_assumed last_trade_price h 58,772 9,541 24ms 90ms 571ms 40.1s 0 transport_latency_assumed market_resolved c 837 797 6ms 17ms 397ms 5.6min 0 transport_latency_assumed market_resolved e 915 54 44ms 228ms 1.0min 1.0min 0 transport_latency_assumed market_resolved f 915 5 50ms 244ms 1.0min 1.0min 0 transport_latency_assumed market_resolved g 915 not meas. 83ms 241ms 583ms 1.0min 0 transport_latency_assumed market_resolved h 915 123 19ms 103ms 1.0min 1.0min 0 transport_latency_assumed new_market c 2,074 1,308 178ms 2.2min 4.2min 4.3min 0 transport_latency_assumed new_market e 2,038 376 256ms 1.1min 1.9min 2.8min 0 transport_latency_assumed new_market f 2,031 520 235ms 1.1min 1.8min 2.8min 0 transport_latency_assumed new_market g 2,031 312 384ms 1.2min 2.0min 2.7min 0 transport_latency_assumed new_market h 2,031 925 194ms 1.1min 1.7min 2.5min 0 transport_latency_assumed price_change c 91,782,164 86,142,241 6ms 17ms 189ms 5.7s 0 transport_latency_assumed price_change e 103,378,907 947,632 43ms 76ms 1.5s 22.1s 0 transport_latency_assumed price_change f 103,389,886 361,834 49ms 86ms 1.9s 39.3s 0 transport_latency_assumed price_change g 103,009,696 43,336 83ms 167ms 4.2s 1.2min 0 transport_latency_assumed price_change h 103,422,162 16,011,212 18ms 38ms 349ms 53.3s 0 transport_latency_assumed tick_size_change c 2,768 2,519 6ms 35ms 206ms 676ms 0 transport_latency_assumed tick_size_change e 2,912 32 44ms 82ms 339ms 580ms 0 transport_latency_assumed tick_size_change f 2,912 12 49ms 81ms 375ms 550ms 0 transport_latency_assumed tick_size_change g 2,912 not meas. 82ms 188ms 614ms 1.3s 0 transport_latency_assumed tick_size_change h 2,912 349 18ms 43ms 305ms 781ms 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/14/2026-09-14T14.parquet sha256sum 2026-09-14T14.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.