Hour audit: 2026-09-11T12
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-11T12 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-11T12:00:00.000348680+00:00 · last event 2026-09-11T12:59:59.999467676+00:00
VOLUME 111,408,088 rows · 1,200,755,996 bytes (1.12 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 109,699,787 · f: 109,653,919 · e: 109,642,527 · g: 109,481,914 · c: 91,678,766 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 22,247,013 (19.97%) · f: 381,613 (0.34%) · e: 1,311,064 (1.18%) · g: 43,144 (0.04%) · c: 87,425,254 (78.47%) (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 111,408,088 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 a329c199ab5caffb3d1da1bfa298465e601b5e7b54fa3b85bbc7ea6f8d8c9e68
the corpus checksum ledger names this file with the same digest
joined 111,410,904 to merged 111,408,088, minus 2,816 (minus 0.0025%)
boundary drops 2,816 · 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-11T14:36:11Z 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,056,838 116,091,724 0-38 ffb09e0547e2c05b3d4c324cfd2197d80d7f3ac17eac853dec5a07e003ff6500 book 1,989,214 98,861,324 39-46 53bb19486a15e2ff4de8c520b6bfa67f147c6d0d2d12b81497374eca9064ba5d last_trade_price 76,366 4,268,574 47-47 619d3cdba9fa01be89f5a94c2b4b00be4d1663d88d065477045d2032149832b8 market_resolved 908 122,946 48-48 a3719624883572bd2983df8bebbf6cf3bce0f34c5bb0abe65275d6ae40bb3804 new_market 940 99,045 49-49 c366bd963b515fb1fb472e64ca7c40c17cca4ace36d97691c02bc875e4abe8d8 price_change 99,280,810 979,931,397 50-428 24b665c6c132318f00033ff5af3f01242b38b08c099dad3ed5ade0743b0dfcc2 tick_size_change 3,012 111,936 429-429 de2c17d02344b1e5a679584ab7ba2f22e8e2c94bfc5eb9a9120a0920d4932388 EVENT MIX count share price_change 99,280,810 89.11% best_bid_ask 10,056,838 9.03% book 1,989,214 1.79% last_trade_price 76,366 0.07% tick_size_change 3,012 <0.01% new_market 940 <0.01% market_resolved 908 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,056,920 10,056,838 82 1,947 FULL book 1,990,466 1,989,214 1,252 201,697 FULL last_trade_price 76,366 76,366 0 376 FULL market_resolved 908 908 0 11 FULL new_market 940 940 0 3 FULL price_change 99,282,292 99,280,810 1,482 936 FULL tick_size_change 3,012 3,012 0 159 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,254,461 7,875,767 5ms 12ms 143ms 7.1s 0 transport_latency_assumed best_bid_ask e 10,054,324 118,569 39ms 48ms 209ms 6.1s 0 transport_latency_assumed best_bid_ask f 10,054,409 27,217 46ms 57ms 218ms 5.9s 0 transport_latency_assumed best_bid_ask g 10,052,497 3,984 77ms 100ms 394ms 16.9s 0 transport_latency_assumed best_bid_ask h 10,054,148 2,031,301 18ms 28ms 165ms 8.2s 0 transport_latency_assumed book c 1,843,351 1,744,420 14.8min 1.3d 30.7d 104.6d 0 book_staleness book e 268,413 54,269 114ms 7.0h 16.7d 104.6d 0 book_staleness book f 275,635 56,783 128ms 7.3h 16.7d 104.6d 0 book_staleness book g 170,436 6,953 86ms 5.4s 23.4h 86.1d 0 book_staleness book h 323,398 126,789 1.8s 9.7h 19.9d 104.6d 0 book_staleness last_trade_price c 62,513 59,270 10ms 40ms 258ms 4.9s 0 transport_latency_assumed last_trade_price e 76,244 1,025 48ms 185ms 3.1s 6.1s 0 transport_latency_assumed last_trade_price f 76,242 468 55ms 174ms 3.5s 5.9s 0 transport_latency_assumed last_trade_price g 75,757 40 94ms 549ms 9.8s 17.0s 0 transport_latency_assumed last_trade_price h 76,159 15,563 24ms 68ms 374ms 7.3s 0 transport_latency_assumed market_resolved c 780 759 6ms 5.4min 8.5min 9.2min 0 transport_latency_assumed market_resolved e 750 22 41ms 123ms 45.7s 45.8s 0 transport_latency_assumed market_resolved f 750 4 48ms 187ms 45.7s 45.8s 0 transport_latency_assumed market_resolved g 750 not meas. 84ms 251ms 59.1s 59.2s 0 transport_latency_assumed market_resolved h 750 123 19ms 64ms 45.8s 45.8s 0 transport_latency_assumed new_market c 666 385 128ms 4.3min 6.0min 6.0min 0 transport_latency_assumed new_market e 636 151 157ms 10.7s 21.1s 57.8s 0 transport_latency_assumed new_market f 639 146 185ms 15.7s 22.9s 1.7min 0 transport_latency_assumed new_market g 636 27 280ms 12.0s 21.2s 1.1min 0 transport_latency_assumed new_market h 636 231 136ms 394ms 19.6s 1.1min 0 transport_latency_assumed price_change c 81,514,619 77,742,345 5ms 13ms 140ms 7.1s 0 transport_latency_assumed price_change e 99,239,148 1,137,006 39ms 54ms 369ms 6.1s 0 transport_latency_assumed price_change f 99,243,232 296,986 46ms 62ms 312ms 5.9s 0 transport_latency_assumed price_change g 99,178,826 32,140 78ms 116ms 766ms 17.0s 0 transport_latency_assumed price_change h 99,241,684 20,072,333 18ms 31ms 192ms 8.4s 0 transport_latency_assumed tick_size_change c 2,376 2,308 5ms 9ms 30ms 105ms 0 transport_latency_assumed tick_size_change e 3,012 22 40ms 46ms 115ms 212ms 0 transport_latency_assumed tick_size_change f 3,012 9 46ms 54ms 132ms 344ms 0 transport_latency_assumed tick_size_change g 3,012 not meas. 77ms 91ms 228ms 288ms 0 transport_latency_assumed tick_size_change h 3,012 673 18ms 29ms 74ms 276ms 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/12/2026-09-11T12.parquet sha256sum 2026-09-11T12.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.