Hour audit: 2026-09-16T06
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-16T06 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-16T06:00:00.000008891+00:00 · last event 2026-09-16T06:59:59.999965863+00:00
VOLUME 109,912,365 rows · 1,120,382,361 bytes (1.04 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured g: 109,652,727 · h: 109,449,392 · f: 109,437,666 · c: 109,416,090 · e: 109,401,594 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 446,693 (0.41%) · h: 3,633,052 (3.31%) · f: 257,649 (0.23%) · c: 105,087,993 (95.61%) · e: 486,978 (0.44%) (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 109,912,365 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 83f8803065fd7911595fa09fcbfe1c190db278c79053c8a78fb4dea8dbb9bae9
the corpus checksum ledger names this file with the same digest
joined 109,916,519 to merged 109,912,365, minus 4,154 (minus 0.0038%)
boundary drops 4,154 · 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-16T07:57:50Z 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,753,002 132,628,874 0-44 b96415c9d1a32b9e03182837721f1ca624539ac9ccea084c30dadf69cb5e4dea book 530,402 48,756,638 45-47 d9c0f708e27b6068f3c1a5139e69d420e51d773dda8e581605f3b6dbec3f525d last_trade_price 48,593 2,745,811 48-48 b33d71d1cf0a4e526d8dec2ee2fe6b59c792e8c1ceac9271dc4bc56b38846254 market_resolved 515 85,940 49-49 5d43ff25de8debd238da2cc47f02586fd93b735601126500c55f50048675f1ec new_market 1,119 113,698 50-50 19ccad122b94c2ad5ceb53a183d1ed7ac00f4c989be91216220e83f394aafba6 price_change 97,576,254 934,706,002 51-423 900a7490101c596f22dd7ffb8f9271df0ae87be3afca94d24d2a91ba69b55575 tick_size_change 2,480 91,819 424-424 717800c7711d181c0dd8e6e4d9d9f2cb10b08d691de00cfd77a29f9d0f203e8d EVENT MIX count share price_change 97,576,254 88.78% best_bid_ask 11,753,002 10.69% book 530,402 0.48% last_trade_price 48,593 0.04% tick_size_change 2,480 <0.01% new_market 1,119 <0.01% market_resolved 515 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,753,296 11,753,002 294 99 FULL book 531,474 530,402 1,072 144,625 FULL last_trade_price 48,593 48,593 0 0 FULL market_resolved 515 515 0 0 FULL new_market 1,119 1,119 0 0 FULL price_change 97,579,042 97,576,254 2,788 147 FULL tick_size_change 2,480 2,480 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,752,284 11,352,190 4ms 9ms 114ms 3.7s 0 transport_latency_assumed best_bid_ask e 11,750,864 34,791 38ms 45ms 192ms 7.2s 0 transport_latency_assumed best_bid_ask f 11,751,284 15,766 47ms 54ms 215ms 12.7s 0 transport_latency_assumed best_bid_ask g 11,744,481 4,291 79ms 100ms 374ms 17.1s 0 transport_latency_assumed best_bid_ask h 11,751,800 345,964 18ms 23ms 155ms 13.9s 0 transport_latency_assumed book c 118,405 109,247 7ms 39.7s 5.8d 90.8d 0 book_staleness book e 119,573 15,312 42ms 58.1s 6.9d 109.3d 0 book_staleness book f 124,703 17,911 50ms 4.1min 8.8d 90.8d 0 book_staleness book g 484,518 373,806 2.2min 14.7h 35.5d 109.4d 0 book_staleness book h 115,976 14,126 22ms 7.9s 4.6d 90.9d 0 book_staleness last_trade_price c 48,409 46,079 10ms 43ms 181ms 4.7s 0 transport_latency_assumed last_trade_price e 48,387 301 46ms 143ms 3.7s 6.0s 0 transport_latency_assumed last_trade_price f 48,477 127 54ms 159ms 1.8s 4.7s 0 transport_latency_assumed last_trade_price g 47,809 92 94ms 277ms 4.6s 12.2s 0 transport_latency_assumed last_trade_price h 48,348 1,994 24ms 77ms 300ms 6.5s 0 transport_latency_assumed market_resolved c 512 497 5ms 14ms 136ms 57.0s 0 transport_latency_assumed market_resolved e 512 2 41ms 187ms 410ms 698ms 0 transport_latency_assumed market_resolved f 512 not meas. 50ms 198ms 433ms 651ms 0 transport_latency_assumed market_resolved g 512 1 90ms 321ms 768ms 2.9s 0 transport_latency_assumed market_resolved h 512 15 19ms 64ms 156ms 325ms 0 transport_latency_assumed new_market c 744 472 81ms 42.7s 1.6min 2.5min 0 transport_latency_assumed new_market e 744 112 178ms 36.1s 1.5min 2.5min 0 transport_latency_assumed new_market f 744 103 170ms 35.6s 2.2min 2.6min 0 transport_latency_assumed new_market g 744 81 289ms 40.4s 1.3min 1.5min 0 transport_latency_assumed new_market h 744 351 117ms 42.2s 2.1min 2.6min 0 transport_latency_assumed price_change c 97,493,256 93,577,144 5ms 11ms 269ms 4.0s 0 transport_latency_assumed price_change e 97,479,034 436,444 39ms 50ms 479ms 12.9s 0 transport_latency_assumed price_change f 97,509,466 223,738 47ms 61ms 500ms 13.1s 0 transport_latency_assumed price_change g 97,372,183 68,422 80ms 113ms 663ms 18.0s 0 transport_latency_assumed price_change h 97,529,532 3,270,506 18ms 28ms 402ms 15.0s 0 transport_latency_assumed tick_size_change c 2,480 2,364 5ms 11ms 153ms 325ms 0 transport_latency_assumed tick_size_change e 2,480 16 38ms 45ms 156ms 543ms 0 transport_latency_assumed tick_size_change f 2,480 4 47ms 59ms 178ms 459ms 0 transport_latency_assumed tick_size_change g 2,480 not meas. 80ms 100ms 447ms 535ms 0 transport_latency_assumed tick_size_change h 2,480 96 18ms 22ms 133ms 222ms 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-16/06/2026-09-16T06.parquet sha256sum 2026-09-16T06.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.