Hour audit: 2026-09-12T18
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-12T18 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-12T18:00:00.000002871+00:00 · last event 2026-09-12T18:59:59.999637199+00:00
VOLUME 138,193,516 rows · 1,554,662,022 bytes (1.45 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 132,653,556 · e: 132,644,910 · f: 122,240,503 · g: 122,192,630 · c: 53,816,261 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 78,737,553 (56.98%) · e: 6,616,411 (4.79%) · f: 998,499 (0.72%) · g: 293,002 (0.21%) · c: 51,548,051 (37.30%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 138,193,516 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 0da4c31a42af32f11518b5eabfb621d7f0e13907d421e22012a7f4f5c2ff8535
the corpus checksum ledger names this file with the same digest
joined 138,213,139 to merged 138,193,516, minus 19,623 (minus 0.0142%)
boundary drops 19,623 · 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-12T20:01:35Z 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 13,519,414 156,551,524 0-51 2365d18abe357076fc6a0d6fffc76e674167d491a6e7d9d0b973415496cd1083 book 5,638,485 151,922,335 52-73 a2607e23b4a655445842be0c0a0e6649e8c72ace7d2f16a2ed51a6507106aa89 last_trade_price 66,277 3,820,603 74-74 dfb67644f5143a1654738a96977cbc1ecc8f74a3ba85c5192054e9c3a1ac5851 market_resolved 5,847 654,665 75-75 7795e85fa4351c7a5d55e9b0d5a86fb2fa6888bb594626e4d81168e7552e295e new_market 28,895 567,560 76-76 660b08631278c1baa19994dd3e177d8cb79221a4c628a156cd69d56503faff07 price_change 118,925,846 1,239,256,418 77-530 4fb3a941749a4035ad4bf1bd4f9d8e4c5cb1f4866876447a611697c5ac82f96f tick_size_change 8,752 318,334 531-531 9c363cd0b6d597abafb87d9e236c8d5b05049d98127b11eb17453642205e5358 EVENT MIX count share price_change 118,925,846 86.06% best_bid_ask 13,519,414 9.78% book 5,638,485 4.08% last_trade_price 66,277 0.05% new_market 28,895 0.02% tick_size_change 8,752 <0.01% market_resolved 5,847 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,519,698 13,519,414 284 25,905 FULL book 5,654,403 5,638,485 15,918 198,039 FULL last_trade_price 66,278 66,277 1 2,206 FULL market_resolved 5,847 5,847 0 1,558 FULL new_market 28,995 28,895 100 2,008 FULL price_change 118,929,166 118,925,846 3,320 27,165 FULL tick_size_change 8,752 8,752 0 1,418 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 5,029,109 4,812,989 6ms 14ms 94ms 3.9s 0 transport_latency_assumed best_bid_ask e 13,517,757 657,728 41ms 47ms 173ms 5.4s 0 transport_latency_assumed best_bid_ask f 12,369,882 76,913 47ms 55ms 195ms 9.6s 0 transport_latency_assumed best_bid_ask g 12,361,167 6,441 77ms 93ms 345ms 19.1s 0 transport_latency_assumed best_bid_ask h 13,518,339 7,965,343 18ms 39ms 166ms 34.7s 0 transport_latency_assumed book c 5,349,569 5,215,379 12.2min 1.0d 32.0d 105.9d 0 book_staleness book e 140,228 12,109 43ms 125ms 2.9s 32.0d 0 book_staleness book f 925,026 118,445 5.8min 1.0d 31.2d 105.9d 0 book_staleness book g 945,986 211,786 4.5min 1.0d 31.2d 105.9d 0 book_staleness book h 141,424 80,766 23ms 75ms 1.4min 87.3d 0 book_staleness last_trade_price c 22,832 21,696 12ms 48ms 214ms 4.9s 0 transport_latency_assumed last_trade_price e 66,195 3,684 48ms 129ms 1.4s 5.4s 0 transport_latency_assumed last_trade_price f 59,163 629 54ms 134ms 1.7s 5.0s 0 transport_latency_assumed last_trade_price g 59,223 65 92ms 254ms 4.9s 19.1s 0 transport_latency_assumed last_trade_price h 66,209 40,203 26ms 76ms 401ms 32.6s 0 transport_latency_assumed market_resolved c 3,114 3,077 11ms 19.4min 24.0min 24.4min 0 transport_latency_assumed market_resolved e 3,861 119 87ms 178ms 391ms 861ms 0 transport_latency_assumed market_resolved f 3,876 194 101ms 208ms 5.7min 6.2min 0 transport_latency_assumed market_resolved g 3,799 209 128ms 357ms 5.0min 5.3min 0 transport_latency_assumed market_resolved h 3,861 2,248 35ms 73ms 337ms 1.0min 0 transport_latency_assumed new_market c 28,899 28,236 1.0h 1.8h 2.1h 2.1h 0 transport_latency_assumed new_market e 885 181 186ms 20.5s 26.2s 7.5min 0 transport_latency_assumed new_market f 887 105 211ms 13.7s 5.1min 27.0min 0 transport_latency_assumed new_market g 860 90 279ms 17.2s 26.2s 9.3min 0 transport_latency_assumed new_market h 885 283 164ms 19.8s 31.8s 8.7min 0 transport_latency_assumed price_change c 43,379,478 41,463,582 6ms 15ms 106ms 4.5s 0 transport_latency_assumed price_change e 118,907,232 5,942,348 41ms 50ms 245ms 5.4s 0 transport_latency_assumed price_change f 108,873,633 802,182 47ms 59ms 272ms 9.7s 0 transport_latency_assumed price_change g 108,813,555 74,411 77ms 99ms 489ms 19.2s 0 transport_latency_assumed price_change h 118,914,086 70,643,323 18ms 42ms 214ms 34.9s 0 transport_latency_assumed tick_size_change c 3,260 3,092 6ms 14ms 50ms 135ms 0 transport_latency_assumed tick_size_change e 8,752 242 41ms 46ms 98ms 1.4s 0 transport_latency_assumed tick_size_change f 8,036 31 47ms 53ms 113ms 917ms 0 transport_latency_assumed tick_size_change g 8,040 not meas. 77ms 91ms 184ms 2.0s 0 transport_latency_assumed tick_size_change h 8,752 5,387 18ms 29ms 78ms 893ms 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-12/18/2026-09-12T18.parquet sha256sum 2026-09-12T18.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.