Hour audit: 2026-09-11T02
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-11T02 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-11T02:00:00.000213115+00:00 · last event 2026-09-11T02:59:59.999913127+00:00
VOLUME 113,385,581 rows · 1,169,780,940 bytes (1.09 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 112,929,713 · f: 112,906,194 · e: 112,883,208 · g: 112,854,388 · c: 108,337,606 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 8,491,519 (7.49%) · f: 213,993 (0.19%) · e: 802,779 (0.71%) · g: 27,604 (0.02%) · c: 103,849,686 (91.59%) (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 113,385,581 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 e7060db49501f288e2f27349a3c0d52dd4f9c433284adcce263cafb0b17cbe71
the corpus checksum ledger names this file with the same digest
joined 113,388,867 to merged 113,385,581, minus 3,286 (minus 0.0029%)
boundary drops 3,286 · 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-11T04:36:17Z 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,709,792 116,113,382 0-40 2b75dbdcdfe60e19cc346f2c325b133190b0562c3846b704d7b6e03155e72733 book 586,988 60,895,441 41-43 191e90547c49bd5f96eefee45d802305bcc733b6944a9889fbd2cdceea77bd48 last_trade_price 53,103 3,010,159 44-44 d0c76a8b88e66f97626bff582e623a2fa0bf33a47a241db93a306dadb7b4a599 market_resolved 1,434 206,521 45-45 67cb4dba57f7b93f7d609b40907afa96833c23500296311412c4bff9368555ef new_market 722 76,042 46-46 a37b01b2342f434392d6b297ee8b41ed94eb8947e33fead81918f01c28a4e8f5 price_change 102,030,206 988,066,353 47-436 4bc649ba7c4305472cea57adceecb9b2d8a6177bd6d3c290e07234ca91a8e244 tick_size_change 3,336 120,977 437-437 258ee09dbf7a45a02a524ac90857dc3a7e7bf407c9af105b7ac054cee432998d EVENT MIX count share price_change 102,030,206 89.99% best_bid_ask 10,709,792 9.45% book 586,988 0.52% last_trade_price 53,103 0.05% tick_size_change 3,336 <0.01% market_resolved 1,434 <0.01% new_market 722 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,710,046 10,709,792 254 435 FULL book 587,364 586,988 376 202,662 FULL last_trade_price 53,103 53,103 0 58 FULL market_resolved 1,434 1,434 0 35 FULL new_market 722 722 0 0 FULL price_change 102,032,862 102,030,206 2,656 149 FULL tick_size_change 3,336 3,336 0 9 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,189,118 9,796,030 5ms 10ms 90ms 7.4s 0 transport_latency_assumed best_bid_ask e 10,706,338 68,205 37ms 44ms 125ms 3.0s 0 transport_latency_assumed best_bid_ask f 10,708,133 14,713 45ms 54ms 147ms 2.4s 0 transport_latency_assumed best_bid_ask g 10,706,708 1,614 78ms 95ms 253ms 10.6s 0 transport_latency_assumed best_bid_ask h 10,708,074 829,230 17ms 26ms 109ms 42.1s 0 transport_latency_assumed book c 528,355 470,333 7.2min 22.1h 26.7d 104.2d 0 book_staleness book e 159,527 33,122 42ms 4.4h 5.5d 104.2d 0 book_staleness book f 144,377 22,006 50ms 2.0h 5.5d 104.2d 0 book_staleness book g 123,108 6,557 87ms 1.7s 1.3d 102.6d 0 book_staleness book h 158,519 54,970 22ms 4.2h 5.5d 104.2d 0 book_staleness last_trade_price c 48,305 45,568 10ms 43ms 209ms 5.0s 0 transport_latency_assumed last_trade_price e 52,678 681 44ms 97ms 427ms 5.0s 0 transport_latency_assumed last_trade_price f 52,985 255 54ms 112ms 368ms 5.0s 0 transport_latency_assumed last_trade_price g 52,705 29 92ms 196ms 658ms 6.9s 0 transport_latency_assumed last_trade_price h 52,903 6,570 22ms 64ms 241ms 14.6s 0 transport_latency_assumed market_resolved c 1,249 1,195 5ms 68ms 5.2min 5.2min 0 transport_latency_assumed market_resolved e 1,284 15 40ms 119ms 58.4s 1.0min 0 transport_latency_assumed market_resolved f 1,284 2 50ms 137ms 51.1s 53.1s 0 transport_latency_assumed market_resolved g 1,284 18 89ms 241ms 519ms 1.1min 0 transport_latency_assumed market_resolved h 1,284 204 24ms 64ms 57.4s 1.0min 0 transport_latency_assumed new_market c 475 276 98ms 27.7s 4.8min 4.8min 0 transport_latency_assumed new_market e 475 149 146ms 16.1s 25.2s 54.1s 0 transport_latency_assumed new_market f 475 50 206ms 16.0s 26.5s 54.5s 0 transport_latency_assumed new_market g 475 38 304ms 13.3s 28.0s 1.5min 0 transport_latency_assumed new_market h 475 209 136ms 21.4s 48.9s 55.4s 0 transport_latency_assumed price_change c 97,566,804 93,533,106 5ms 11ms 115ms 7.5s 0 transport_latency_assumed price_change e 101,959,570 700,607 38ms 46ms 172ms 3.0s 0 transport_latency_assumed price_change f 101,995,604 176,963 45ms 58ms 198ms 2.5s 0 transport_latency_assumed price_change g 101,966,772 19,348 78ms 100ms 334ms 11.7s 0 transport_latency_assumed price_change h 102,005,122 7,600,182 17ms 28ms 139ms 43.4s 0 transport_latency_assumed tick_size_change c 3,300 3,178 5ms 11ms 50ms 227ms 0 transport_latency_assumed tick_size_change e 3,336 not meas. 38ms 48ms 129ms 1.7s 0 transport_latency_assumed tick_size_change f 3,336 4 45ms 56ms 129ms 187ms 0 transport_latency_assumed tick_size_change g 3,336 not meas. 78ms 96ms 220ms 364ms 0 transport_latency_assumed tick_size_change h 3,336 154 17ms 28ms 77ms 162ms 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/02/2026-09-11T02.parquet sha256sum 2026-09-11T02.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.