Hour audit: 2026-09-11T13
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-11T13 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-11T13:00:00.000246153+00:00 · last event 2026-09-11T13:59:59.999932662+00:00
VOLUME 114,513,342 rows · 1,231,425,490 bytes (1.15 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 112,640,521 · f: 112,625,118 · g: 112,447,494 · e: 109,019,121 · c: 93,746,977 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 23,311,282 (20.36%) · f: 410,402 (0.36%) · g: 65,187 (0.06%) · e: 1,462,303 (1.28%) · c: 89,264,168 (77.95%) (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 114,513,342 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 e7a6607b70b038467b1b503bdf1e10eba2a5b015437028a08f7719c104d4aea5
the corpus checksum ledger names this file with the same digest
joined 114,519,063 to merged 114,513,342, minus 5,721 (minus 0.0050%)
boundary drops 5,721 · 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-11T15:01:45Z 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,684,950 123,557,127 0-40 087fe8a2bd66fbc4965c405d6008cb2493e0de9efc38cb0d2b5f67664b2843c8 book 1,940,557 96,784,643 41-48 944885cb3b2dba6821bc1a91b20d783dd6df4a82ac8ae32e8d85645b0ed1a28c last_trade_price 65,316 3,719,431 49-49 aa005b373d2b0c9ea588f3b00a2dd2f76ca33d4ec92dd92157667d3992353c4b market_resolved 817 98,189 50-50 24b46b37050bbc35751a6980e4bf303cecdfb3b153d22e575ffba84c87990546 new_market 1,352 130,740 51-51 292f3deff00cff905009922564b56c1c601380536ed54619f7c35fa9a1b95180 price_change 101,816,898 1,005,703,294 52-440 0f1b4ff6fe6dd5b4d06ab8504af4bce4163f94285298a5982eda58fbb3032ad7 tick_size_change 3,452 127,689 441-441 53a9c695b6b26836c114285451745118b1a5036dba2e826b2a83f68e63968e18 EVENT MIX count share price_change 101,816,898 88.91% best_bid_ask 10,684,950 9.33% book 1,940,557 1.69% last_trade_price 65,316 0.06% tick_size_change 3,452 <0.01% new_market 1,352 <0.01% market_resolved 817 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,685,203 10,684,950 253 5,471 FULL book 1,941,075 1,940,557 518 201,669 FULL last_trade_price 65,322 65,316 6 386 FULL market_resolved 817 817 0 13 FULL new_market 1,352 1,352 0 39 FULL price_change 101,821,842 101,816,898 4,944 2,386 FULL tick_size_change 3,452 3,452 0 146 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,702,662 8,290,707 5ms 13ms 140ms 20.4s 0 transport_latency_assumed best_bid_ask e 10,310,966 129,286 39ms 48ms 215ms 23.9s 0 transport_latency_assumed best_bid_ask f 10,682,008 34,348 46ms 59ms 251ms 13.4s 0 transport_latency_assumed best_bid_ask g 10,678,601 4,272 77ms 98ms 448ms 29.9s 0 transport_latency_assumed best_bid_ask h 10,681,568 2,226,337 19ms 29ms 176ms 44.9s 0 transport_latency_assumed book c 1,809,668 1,796,610 14.7min 1.3d 30.8d 104.7d 0 book_staleness book e 547,406 102,546 3.5min 22.2h 23.8d 104.6d 0 book_staleness book f 139,558 2,763 49ms 453ms 14.0min 86.1d 0 book_staleness book g 148,156 6,080 85ms 7.2s 1.1d 86.1d 0 book_staleness book h 140,787 32,558 22ms 72ms 37.8min 86.1d 0 book_staleness last_trade_price c 52,594 49,715 11ms 46ms 288ms 5.1s 0 transport_latency_assumed last_trade_price e 63,086 837 50ms 278ms 6.5s 24.0s 0 transport_latency_assumed last_trade_price f 64,959 371 58ms 295ms 4.3s 13.5s 0 transport_latency_assumed last_trade_price g 64,039 105 93ms 670ms 12.1s 29.9s 0 transport_latency_assumed last_trade_price h 65,055 14,288 25ms 73ms 546ms 11.5s 0 transport_latency_assumed market_resolved c 687 664 8ms 6.0min 11.5min 11.6min 0 transport_latency_assumed market_resolved e 616 15 40ms 272ms 7.1min 7.2min 0 transport_latency_assumed market_resolved f 581 2 48ms 187ms 546ms 53.4s 0 transport_latency_assumed market_resolved g 581 1 84ms 255ms 664ms 934ms 0 transport_latency_assumed market_resolved h 581 135 20ms 62ms 277ms 53.1s 0 transport_latency_assumed new_market c 883 535 179ms 1.8min 6.6min 6.6min 0 transport_latency_assumed new_market e 842 252 215ms 24.8s 1.6h 1.6h 0 transport_latency_assumed new_market f 803 181 232ms 18.2s 27.5s 54.8s 0 transport_latency_assumed new_market g 806 91 354ms 15.8s 27.3s 1.1min 0 transport_latency_assumed new_market h 806 293 174ms 13.5s 26.5s 1.3min 0 transport_latency_assumed price_change c 83,177,595 79,123,209 5ms 14ms 159ms 21.0s 0 transport_latency_assumed price_change e 98,092,797 1,229,348 39ms 57ms 519ms 23.9s 0 transport_latency_assumed price_change f 101,733,757 372,733 46ms 68ms 524ms 13.8s 0 transport_latency_assumed price_change g 101,551,859 54,638 78ms 119ms 1.5s 29.9s 0 transport_latency_assumed price_change h 101,748,272 21,036,970 19ms 32ms 225ms 47.6s 0 transport_latency_assumed tick_size_change c 2,888 2,728 5ms 12ms 61ms 310ms 0 transport_latency_assumed tick_size_change e 3,408 19 39ms 46ms 117ms 238ms 0 transport_latency_assumed tick_size_change f 3,452 4 46ms 54ms 118ms 152ms 0 transport_latency_assumed tick_size_change g 3,452 not meas. 77ms 92ms 266ms 555ms 0 transport_latency_assumed tick_size_change h 3,452 701 19ms 26ms 68ms 3.7s 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/13/2026-09-11T13.parquet sha256sum 2026-09-11T13.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.