Hour audit: 2026-09-29T13
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-29T13 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-29T13:00:00.000122920+00:00 · last event 2026-09-29T13:59:59.999997211+00:00
VOLUME 115,935,881 rows · 1,338,595,442 bytes (1.25 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured h: 114,375,939 · k: 114,360,715 · g: 112,369,847 · i: 112,165,276 · c: 99,416,362 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 3,226,371 (2.78%) · k: 19,208,579 (16.57%) · g: 76,581 (0.07%) · i: 8,078,369 (6.97%) · c: 85,345,981 (73.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 115,935,881 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 1a18b6c71f76ea8f3586f168727a55d7e302ab64b3a26d855bd857fe53ec009c
the corpus checksum ledger names this file with the same digest
joined 115,939,736 to merged 115,935,881, minus 3,855 (minus 0.0033%)
boundary drops 3,855 · 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-29T15:53:08Z as cghik
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 status feed unobserved for this hour. Our incident register was last checked against the venue's feed at 2026-09-23T20:35Z, before this hour ended, so nothing has looked yet. This is a could-not-look and never an all-clear.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,623,899 133,034,498 0-40 7258df384aa9157c76941058671e9fd80e562ba31803c960e49e93536cdd0eef book 1,652,777 84,568,303 41-47 927f490d05f681fa09fd3fb450f719fbaf87ea48d670fd64dda9a22f7c5b3858 last_trade_price 64,880 3,693,972 48-48 daf5901d2ff8b2ec4a55ff9b1bbb4b5e0ca6197d5625c57e606da5cd713aaebd market_resolved 1,142 136,967 49-49 0e1228657b9f6d4d146aa97402a30aa1abaf41b5001d5b4ce2a82376ea94179c new_market 747 80,493 50-50 519f285da6c3bf20ceea4740d25d20f0c1e5d4c6bd9e44acf884d7a357f69d87 price_change 103,588,648 1,115,617,435 51-446 ac430aa2613c4c759b29e5a2729f250010495f1fc4b6b6d02a20ded8868745f7 tick_size_change 3,788 140,870 447-447 7239540844b6f95886909dd9e96ec0dc41575f1b5cd953225143026650e43ae5 EVENT MIX count share price_change 103,588,648 89.35% best_bid_ask 10,623,899 9.16% book 1,652,777 1.43% last_trade_price 64,880 0.06% tick_size_change 3,788 <0.01% market_resolved 1,142 <0.01% new_market 747 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,624,051 10,623,899 152 1,568 FULL book 1,654,897 1,652,777 2,120 223,866 FULL last_trade_price 64,881 64,880 1 314 FULL market_resolved 1,142 1,142 0 74 FULL new_market 747 747 0 0 FULL price_change 103,590,230 103,588,648 1,582 1,355 FULL tick_size_change 3,788 3,788 0 77 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,022,223 7,749,732 6ms 25ms 182ms 3.9s 0 transport_latency_assumed best_bid_ask g 10,574,656 1,077 79ms 122ms 1.1s 30.4s 0 transport_latency_assumed best_bid_ask h 10,614,084 298,575 20ms 41ms 258ms 50.1s 0 transport_latency_assumed best_bid_ask i 10,493,728 805,064 20ms 37ms 273ms 8.6s 0 transport_latency_assumed best_bid_ask k 10,622,626 1,769,451 14ms 30ms 159ms 3.3s 0 transport_latency_assumed book c 1,544,677 1,487,377 2.4h 2.4d 41.5d 122.6d 0 book_staleness book g 296,505 64,042 1.0min 1.3d 38.0d 122.6d 0 book_staleness book h 278,366 51,739 10.2s 1.1d 38.0d 122.6d 0 book_staleness book i 137,183 19,510 25ms 663ms 9.9h 122.6d 0 book_staleness book k 143,355 30,109 18ms 327ms 2.4d 122.6d 0 book_staleness last_trade_price c 55,274 47,349 7ms 31ms 228ms 1.6s 0 transport_latency_assumed last_trade_price g 59,246 13 95ms 3.3s 17.9s 30.4s 0 transport_latency_assumed last_trade_price h 64,556 1,932 22ms 118ms 624ms 35.7s 0 transport_latency_assumed last_trade_price i 62,361 3,816 23ms 212ms 2.2s 6.7s 0 transport_latency_assumed last_trade_price k 64,618 11,770 15ms 47ms 248ms 1.6s 0 transport_latency_assumed market_resolved c 1,035 910 11ms 9.0min 12.3min 12.3min 0 transport_latency_assumed market_resolved g 760 3 80ms 278ms 55.2s 2.0min 0 transport_latency_assumed market_resolved h 759 81 21ms 235ms 45.4s 45.5s 0 transport_latency_assumed market_resolved i 754 65 22ms 119ms 36.6s 2.1min 0 transport_latency_assumed market_resolved k 760 83 15ms 87ms 53.7s 53.8s 0 transport_latency_assumed new_market c 561 266 107ms 1.8min 7.0min 7.0min 0 transport_latency_assumed new_market g 502 30 353ms 11.2s 17.1s 1.6min 0 transport_latency_assumed new_market h 502 104 172ms 608ms 18.7s 1.4min 0 transport_latency_assumed new_market i 502 154 102ms 11.4s 31.2s 1.2min 0 transport_latency_assumed new_market k 502 193 90ms 13.7s 32.2s 1.4min 0 transport_latency_assumed price_change c 88,789,052 76,057,382 6ms 27ms 193ms 4.4s 0 transport_latency_assumed price_change g 101,434,390 11,416 80ms 227ms 8.7s 30.4s 0 transport_latency_assumed price_change h 103,413,888 2,873,824 20ms 52ms 338ms 51.3s 0 transport_latency_assumed price_change i 101,467,020 7,249,473 21ms 54ms 1.0s 8.6s 0 transport_latency_assumed price_change k 103,525,066 17,396,553 14ms 33ms 170ms 5.1s 0 transport_latency_assumed tick_size_change c 3,540 2,965 6ms 24ms 91ms 254ms 0 transport_latency_assumed tick_size_change g 3,788 not meas. 79ms 119ms 367ms 1.4s 0 transport_latency_assumed tick_size_change h 3,784 116 20ms 42ms 294ms 5.6s 0 transport_latency_assumed tick_size_change i 3,728 287 21ms 44ms 133ms 1.3s 0 transport_latency_assumed tick_size_change k 3,788 420 14ms 34ms 112ms 308ms 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-29/13/2026-09-29T13.parquet sha256sum 2026-09-29T13.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.