Hour audit: 2026-09-11T15
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-11T15 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-11T15:00:00.000036165+00:00 · last event 2026-09-11T15:59:59.998825335+00:00
VOLUME 121,970,982 rows · 1,347,114,516 bytes (1.25 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 119,362,869 · e: 119,358,192 · h: 119,335,087 · g: 119,004,879 · c: 89,848,676 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 794,848 (0.65%) · e: 2,973,041 (2.44%) · h: 35,356,150 (28.99%) · g: 79,729 (0.07%) · c: 82,767,214 (67.86%) (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 121,970,982 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 79b795320af71c5a89c496cc137bcbbf2c20c04de9823b55de33eb1287d256ce
the corpus checksum ledger names this file with the same digest
joined 121,975,253 to merged 121,970,982, minus 4,271 (minus 0.0035%)
boundary drops 4,271 · 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-11T17:37:58Z 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,043,049 129,773,104 0-42 93f4d83fe96051d8b4ea8129cad0c584d2c52645f8a7d54516da2785d4bada57 book 2,720,822 110,193,136 43-53 57c24cae9513147925f0f3da66d7f2bf7be514dc44e2d6649105c84315fafd80 last_trade_price 68,477 3,985,780 54-54 abbdba909a01a875c28986bc5116cd2c43b0a9b44a5a1651a461255f7408a3ec market_resolved 927 106,628 55-55 4921b5f52e9fff44a63797ca2f69372fc021461b6252d5cbfab61818fd6f3eae new_market 4,537 447,878 56-56 819aee7a7ccc9c0fe3aa7473a4ea1a07b722734633d0e2fdf92d7a716c56d235 price_change 108,129,354 1,101,079,261 57-469 1416d3d27c1e06260263d23d8da45d43e8fa786930cc6b024a2c3eef8b2a5ea0 tick_size_change 3,816 139,408 470-470 9ac171ee87688e3ce8ed147e41e07df6ed043fbb60f1540cd01b4ddc1b4bb512 EVENT MIX count share price_change 108,129,354 88.65% best_bid_ask 11,043,049 9.05% book 2,720,822 2.23% last_trade_price 68,477 0.06% new_market 4,537 <0.01% tick_size_change 3,816 <0.01% market_resolved 927 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,043,428 11,043,049 379 5,352 FULL book 2,721,948 2,720,822 1,126 201,991 FULL last_trade_price 68,481 68,477 4 688 FULL market_resolved 927 927 0 59 FULL new_market 4,537 4,537 0 82 FULL price_change 108,132,116 108,129,354 2,762 2,433 FULL tick_size_change 3,816 3,816 0 216 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,142,365 7,493,747 5ms 22ms 291ms 8.6s 0 transport_latency_assumed best_bid_ask e 11,036,916 268,847 37ms 61ms 348ms 17.3s 0 transport_latency_assumed best_bid_ask f 11,036,780 71,875 45ms 76ms 381ms 11.0s 0 transport_latency_assumed best_bid_ask g 11,028,700 6,281 86ms 195ms 815ms 30.2s 0 transport_latency_assumed best_bid_ask h 11,036,271 3,202,299 18ms 39ms 479ms 47.6s 0 transport_latency_assumed book c 2,660,227 2,633,465 20.3min 1.4d 30.9d 104.7d 0 book_staleness book e 157,977 11,973 46ms 2.6s 17.7h 86.2d 0 book_staleness book f 167,439 11,039 61ms 36.3s 2.3d 104.7d 0 book_staleness book g 175,712 17,632 173ms 15.0min 4.2d 104.7d 0 book_staleness book h 153,571 46,713 24ms 229ms 6.8h 86.2d 0 book_staleness last_trade_price c 49,938 45,935 11ms 65ms 467ms 6.3s 0 transport_latency_assumed last_trade_price e 68,376 1,786 62ms 502ms 7.1s 17.3s 0 transport_latency_assumed last_trade_price f 68,359 472 71ms 547ms 4.6s 11.0s 0 transport_latency_assumed last_trade_price g 66,529 59 133ms 2.4s 16.8s 30.3s 0 transport_latency_assumed last_trade_price h 68,166 20,225 26ms 106ms 697ms 7.6s 0 transport_latency_assumed market_resolved c 780 742 16ms 10.1min 17.8min 18.4min 0 transport_latency_assumed market_resolved e 629 10 38ms 307ms 741ms 1.0min 0 transport_latency_assumed market_resolved f 629 8 47ms 349ms 770ms 2.2s 0 transport_latency_assumed market_resolved g 629 1 98ms 630ms 1.5s 59.3s 0 transport_latency_assumed market_resolved h 629 166 20ms 142ms 547ms 44.7s 0 transport_latency_assumed new_market c 2,892 1,748 132ms 26.0s 8.4min 12.8min 0 transport_latency_assumed new_market e 2,908 678 225ms 23.4s 51.4s 1.1min 0 transport_latency_assumed new_market f 2,910 494 226ms 24.5s 50.5s 1.2min 0 transport_latency_assumed new_market g 2,910 365 346ms 23.9s 50.6s 1.1min 0 transport_latency_assumed new_market h 2,910 1,252 160ms 23.2s 49.9s 1.2min 0 transport_latency_assumed price_change c 78,989,522 72,588,721 6ms 25ms 328ms 11.0s 0 transport_latency_assumed price_change e 108,087,570 2,689,659 38ms 87ms 887ms 17.3s 0 transport_latency_assumed price_change f 108,082,936 710,936 46ms 102ms 888ms 11.0s 0 transport_latency_assumed price_change g 107,726,583 55,391 87ms 267ms 4.3s 30.4s 0 transport_latency_assumed price_change h 108,069,724 32,084,647 19ms 44ms 567ms 48.1s 0 transport_latency_assumed tick_size_change c 2,952 2,856 5ms 11ms 88ms 196ms 0 transport_latency_assumed tick_size_change e 3,816 88 37ms 49ms 281ms 755ms 0 transport_latency_assumed tick_size_change f 3,816 24 45ms 67ms 375ms 714ms 0 transport_latency_assumed tick_size_change g 3,816 not meas. 84ms 160ms 517ms 2.1s 0 transport_latency_assumed tick_size_change h 3,816 848 19ms 42ms 183ms 1.8s 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-11/15/2026-09-11T15.parquet sha256sum 2026-09-11T15.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.