Hour audit: 2026-09-12T12
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-12T12 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-12T12:00:00.000047575+00:00 · last event 2026-09-12T12:59:59.999986704+00:00
VOLUME 126,255,594 rows · 1,369,022,073 bytes (1.28 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 121,162,588 · g: 121,133,709 · e: 121,130,543 · f: 116,159,883 · c: 58,593,457 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 65,668,944 (52.01%) · g: 56,324 (0.04%) · e: 3,599,881 (2.85%) · f: 602,487 (0.48%) · c: 56,327,958 (44.61%) (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 126,255,594 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 58a6a25efe07925d902412a7ae21459d6b82135d8f2d990dd5284afe87b4a36a
the corpus checksum ledger names this file with the same digest
joined 126,257,910 to merged 126,255,594, minus 2,316 (minus 0.0018%)
boundary drops 2,316 · 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-12T13:59:53Z 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,223,284 126,309,398 0-42 0214a68f33b6a832068a8b6f67d2e0c64c607050e6ab5518e4ec60c133fcc3af book 5,206,272 146,151,728 43-62 82a48a740354e00e427bd659f5b192218b69b35c5702c3bbb195968b2ab585a4 last_trade_price 59,907 3,497,281 63-63 b259494234bdba92175f7a6bf28b71a561f938769b17b94e6657f0dba63ebfd1 market_resolved 4,683 165,172 64-64 6aae261ddfbfa712a241ccff473b4121abc50be9f24833e62549d8737a3f40bc new_market 4,706 139,925 65-65 ced160f3a60bd2591da81d2ca0978ac02143975bea683c869d11f98c1eaefc35 price_change 109,750,058 1,091,079,171 66-484 aa2bee2d0539415dfb89f584b8e4252f3eb1dc359c6b0d15cd030d90f0b10e8a tick_size_change 6,684 244,541 485-485 4fe1baa85976501c01e9d36762c0b5b15066ef6af770813520d5b0268b71ffae EVENT MIX count share price_change 109,750,058 86.93% best_bid_ask 11,223,284 8.89% book 5,206,272 4.12% last_trade_price 59,907 0.05% tick_size_change 6,684 <0.01% new_market 4,706 <0.01% market_resolved 4,683 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,223,521 11,223,284 237 16,556 FULL book 5,206,322 5,206,272 50 203,418 FULL last_trade_price 59,908 59,907 1 1,606 FULL market_resolved 4,683 4,683 0 114 FULL new_market 4,706 4,706 0 2 FULL price_change 109,752,086 109,750,058 2,028 12,555 FULL tick_size_change 6,684 6,684 0 1,122 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 5,119,538 4,911,657 5ms 12ms 75ms 4.8s 0 transport_latency_assumed best_bid_ask e 11,221,045 321,578 40ms 45ms 134ms 4.0s 0 transport_latency_assumed best_bid_ask f 10,746,809 44,644 48ms 54ms 175ms 10.1s 0 transport_latency_assumed best_bid_ask g 11,218,270 3,871 76ms 93ms 306ms 13.8s 0 transport_latency_assumed best_bid_ask h 11,220,704 5,941,534 18ms 27ms 137ms 56.1s 0 transport_latency_assumed book c 5,037,974 5,019,806 14.7min 18.8h 31.7d 105.6d 0 book_staleness book e 127,829 7,949 43ms 107ms 33.2min 87.1d 0 book_staleness book f 560,186 93,138 4.4min 16.7h 27.8d 105.6d 0 book_staleness book g 157,347 10,506 88ms 19.3min 5.1d 105.6d 0 book_staleness book h 152,732 74,873 23ms 9.6min 4.9d 87.1d 0 book_staleness last_trade_price c 25,075 23,755 11ms 45ms 221ms 4.8s 0 transport_latency_assumed last_trade_price e 59,765 2,143 47ms 104ms 560ms 4.9s 0 transport_latency_assumed last_trade_price f 56,780 314 54ms 113ms 685ms 7.6s 0 transport_latency_assumed last_trade_price g 59,621 40 91ms 208ms 1.1s 11.2s 0 transport_latency_assumed last_trade_price h 59,750 33,655 23ms 64ms 282ms 19.5s 0 transport_latency_assumed market_resolved c 4,199 4,123 21.4min 41.7min 55.6min 57.1min 0 transport_latency_assumed market_resolved e 851 101 43ms 16.2s 1.0min 1.0min 0 transport_latency_assumed market_resolved f 804 13 48ms 132ms 57.7s 5.0min 0 transport_latency_assumed market_resolved g 851 4 83ms 255ms 59.5s 1.0min 0 transport_latency_assumed market_resolved h 851 442 18ms 66ms 55.3s 59.0s 0 transport_latency_assumed new_market c 4,448 4,040 13.9min 31.7min 49.7min 56.6min 0 transport_latency_assumed new_market e 746 172 187ms 12.6s 24.4s 1.0min 0 transport_latency_assumed new_market f 748 94 184ms 20.8s 40.1s 1.4min 0 transport_latency_assumed new_market g 746 121 285ms 15.3s 23.7s 1.2min 0 transport_latency_assumed new_market h 746 279 153ms 17.5s 23.2s 1.2min 0 transport_latency_assumed price_change c 48,399,975 46,362,386 5ms 12ms 87ms 5.6s 0 transport_latency_assumed price_change e 109,713,623 3,267,734 40ms 46ms 190ms 4.0s 0 transport_latency_assumed price_change f 104,787,968 464,277 48ms 55ms 226ms 10.1s 0 transport_latency_assumed price_change g 109,690,190 41,782 77ms 96ms 401ms 14.2s 0 transport_latency_assumed price_change h 109,721,121 59,613,879 18ms 29ms 166ms 56.2s 0 transport_latency_assumed tick_size_change c 2,248 2,191 5ms 9ms 31ms 67ms 0 transport_latency_assumed tick_size_change e 6,684 204 40ms 44ms 59ms 125ms 0 transport_latency_assumed tick_size_change f 6,588 7 47ms 51ms 75ms 130ms 0 transport_latency_assumed tick_size_change g 6,684 not meas. 76ms 89ms 106ms 223ms 0 transport_latency_assumed tick_size_change h 6,684 4,282 18ms 25ms 77ms 1.6s 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/12/2026-09-12T12.parquet sha256sum 2026-09-12T12.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.