Hour audit: 2026-09-14T13
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-14T13 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-14T13:00:00.000213312+00:00 · last event 2026-09-14T13:59:59.999951160+00:00
VOLUME 114,508,171 rows · 1,196,315,517 bytes (1.11 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 113,759,442 · h: 113,753,388 · e: 113,653,577 · g: 113,481,534 · c: 105,561,366 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 173,254 (0.15%) · h: 13,560,123 (11.84%) · e: 560,163 (0.49%) · g: 35,809 (0.03%) · c: 100,178,822 (87.49%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 114,508,171 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 59fd7213b9152b4a3e2ba7e894327d90a2ab015c89489c0cf3d7a949be476e3e
the corpus checksum ledger names this file with the same digest
joined 114,510,275 to merged 114,508,171, minus 2,104 (minus 0.0018%)
boundary drops 2,104 · 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:01:03Z 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,365,250 126,327,737 0-43 ff073ea3d2e59634443ea3059545a7a27f1dbbe9e0bda904f8d547d88936fd3c book 811,323 63,558,861 44-47 55621ceafa816f7966cc1ac4dc9b23d1e96af52af966c81ccce1fdf1f5c2846c last_trade_price 63,679 3,610,966 48-48 6b857f29f2ab60f4e4060555e71fe1d5a210af12f9960b53ea2d8d8d27abfd0d market_resolved 719 100,842 49-49 eae69c001f4c92e39a784a500e7a5c40c95d8146b0e65ade0ac6228d8a7ee4ac new_market 1,158 115,443 50-50 d16b0369d024fc40f0dd375d4886b4623b51d2b2cef036c1b24372d14514256f price_change 102,262,922 1,001,181,624 51-441 106b938b9dbc1840d4e58e15e6923982a08c5dba40fa7f0bd465cce9a37830ac tick_size_change 3,120 113,119 442-442 46168f6a2ff4165e60da9fc47905f512bfb19cd0cf3c5d2064394e2f42c48f40 EVENT MIX count share price_change 102,262,922 89.31% best_bid_ask 11,365,250 9.93% book 811,323 0.71% last_trade_price 63,679 0.06% tick_size_change 3,120 <0.01% new_market 1,158 <0.01% market_resolved 719 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,365,486 11,365,250 236 1,026 FULL book 811,332 811,323 9 162,060 FULL last_trade_price 63,680 63,679 1 134 FULL market_resolved 719 719 0 2 FULL new_market 1,158 1,158 0 0 FULL price_change 102,264,780 102,262,922 1,858 572 FULL tick_size_change 3,120 3,120 0 52 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,458,201 9,946,680 5ms 13ms 93ms 7.0s 0 transport_latency_assumed best_bid_ask e 11,359,716 54,460 42ms 50ms 201ms 13.8s 0 transport_latency_assumed best_bid_ask f 11,362,481 14,699 48ms 58ms 213ms 13.9s 0 transport_latency_assumed best_bid_ask g 11,355,273 1,165 81ms 99ms 405ms 22.3s 0 transport_latency_assumed best_bid_ask h 11,364,048 1,348,246 18ms 27ms 115ms 43.7s 0 transport_latency_assumed book c 788,012 774,757 11.4min 2.3d 35.9d 107.6d 0 book_staleness book e 134,063 2,227 45ms 779ms 2.1h 89.1d 0 book_staleness book f 134,138 1,991 51ms 1.0s 2.4min 89.0d 0 book_staleness book g 155,951 15,891 98ms 14.0min 7.1d 107.6d 0 book_staleness book h 133,226 16,457 22ms 65ms 1.0s 89.0d 0 book_staleness last_trade_price c 58,776 55,376 11ms 47ms 208ms 4.7s 0 transport_latency_assumed last_trade_price e 62,716 323 54ms 427ms 8.7s 13.8s 0 transport_latency_assumed last_trade_price f 63,383 232 60ms 564ms 8.5s 13.9s 0 transport_latency_assumed last_trade_price g 61,753 44 101ms 722ms 12.0s 22.3s 0 transport_latency_assumed last_trade_price h 63,608 7,704 24ms 79ms 356ms 7.0s 0 transport_latency_assumed market_resolved c 614 602 6ms 4.1min 4.6min 5.6min 0 transport_latency_assumed market_resolved e 613 6 42ms 119ms 348ms 40.9s 0 transport_latency_assumed market_resolved f 613 not meas. 49ms 128ms 298ms 43.8s 0 transport_latency_assumed market_resolved g 612 not meas. 84ms 239ms 547ms 59.9s 0 transport_latency_assumed market_resolved h 613 111 19ms 58ms 127ms 41.2s 0 transport_latency_assumed new_market c 725 473 93ms 13.6s 23.4s 1.2min 0 transport_latency_assumed new_market e 725 167 221ms 16.4s 26.2s 1.3min 0 transport_latency_assumed new_market f 725 108 188ms 16.7s 25.3s 58.8s 0 transport_latency_assumed new_market g 725 79 341ms 16.6s 27.7s 1.1min 0 transport_latency_assumed new_market h 725 331 138ms 17.3s 23.9s 1.1min 0 transport_latency_assumed price_change c 94,252,126 89,398,112 6ms 14ms 107ms 7.0s 0 transport_latency_assumed price_change e 102,092,624 502,972 42ms 60ms 596ms 13.9s 0 transport_latency_assumed price_change f 102,194,982 156,224 48ms 68ms 772ms 13.9s 0 transport_latency_assumed price_change g 101,904,100 18,630 82ms 116ms 2.1s 22.4s 0 transport_latency_assumed price_change h 102,188,048 12,186,984 18ms 30ms 147ms 44.8s 0 transport_latency_assumed tick_size_change c 2,912 2,822 5ms 9ms 50ms 122ms 0 transport_latency_assumed tick_size_change e 3,120 8 41ms 49ms 106ms 215ms 0 transport_latency_assumed tick_size_change f 3,120 not meas. 48ms 55ms 149ms 208ms 0 transport_latency_assumed tick_size_change g 3,120 not meas. 81ms 99ms 261ms 338ms 0 transport_latency_assumed tick_size_change h 3,120 290 18ms 28ms 62ms 126ms 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/13/2026-09-14T13.parquet sha256sum 2026-09-14T13.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.