Hour audit: 2026-09-18T02
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-18T02 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-18T02:00:00.000040543+00:00 · last event 2026-09-18T02:59:59.999918078+00:00
VOLUME 117,737,649 rows · 1,245,778,615 bytes (1.16 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 116,506,741 · e: 116,391,779 · c: 111,934,141 · g: 111,619,603 · f: 106,871,164 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 9,160,534 (7.78%) · e: 461,432 (0.39%) · c: 107,221,389 (91.07%) · g: 151,112 (0.13%) · f: 743,182 (0.63%) (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 117,737,649 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 bef4ceaf59625c19fb2beca30bdd8b6f643a47723309ad154df1880fa0a54d80
the corpus checksum ledger names this file with the same digest
joined 117,740,514 to merged 117,737,649, minus 2,865 (minus 0.0024%)
boundary drops 2,865 · 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-18T04:00:34Z 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,821,360 121,215,963 0-41 dcbfe7711d5d4308d8fd02fbe2287dd5e62f0ba5519365947e53938b86abbd9d book 1,283,618 79,661,009 42-46 9eedb49c2f0c7dcc3aed2faaa8c87173a3a2ea6f86bb8dea3c9e796c0985e30a last_trade_price 50,495 2,875,711 47-47 ec6f27b2ad774f438e541bbe72985259262753026066e0b127faebcbf0887a16 market_resolved 1,826 222,971 48-48 c674614f68d1f00687c34e972e654dcff7a0b0f62528733c384d18cbed125cdb new_market 574 61,511 49-49 6ced3873c98c984c646c98bfbf7ce75347dab0d1abc0b82fc52b3ef617a3483e price_change 105,575,856 1,040,259,252 50-452 e8fc8a651ac0ae494c5bf57f8051319a315ab316b43796302a6ec414e9f18628 tick_size_change 3,920 142,520 453-453 e670e9dce608392f070deb6d1108c8d7b419ca60924d16712899637f7c90c32f EVENT MIX count share price_change 105,575,856 89.67% best_bid_ask 10,821,360 9.19% book 1,283,618 1.09% last_trade_price 50,495 0.04% tick_size_change 3,920 <0.01% market_resolved 1,826 <0.01% new_market 574 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,821,624 10,821,360 264 1,119 FULL book 1,283,658 1,283,618 40 186,861 FULL last_trade_price 50,499 50,495 4 174 FULL market_resolved 1,827 1,826 1 186 FULL new_market 574 574 0 1 FULL price_change 105,578,412 105,575,856 2,556 603 FULL tick_size_change 3,920 3,920 0 146 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,325,098 9,935,414 5ms 9ms 76ms 1.8s 0 transport_latency_assumed best_bid_ask e 10,816,554 36,537 41ms 47ms 124ms 7.5s 0 transport_latency_assumed best_bid_ask f 9,836,400 11,894 48ms 55ms 146ms 7.1s 0 transport_latency_assumed best_bid_ask g 10,326,159 1,030 82ms 100ms 208ms 13.7s 0 transport_latency_assumed best_bid_ask h 10,820,628 836,485 18ms 26ms 90ms 8.9s 0 transport_latency_assumed book c 735,040 557,365 3.4min 8.3h 37.3d 111.2d 0 book_staleness book e 109,901 6,610 43ms 158ms 21.8min 45.4d 0 book_staleness book f 874,400 573,796 3.2min 10.3h 37.3d 111.2d 0 book_staleness book g 501,538 134,171 2.4min 7.1h 36.3d 111.2d 0 book_staleness book h 106,826 11,676 21ms 60ms 4.3min 92.6d 0 book_staleness last_trade_price c 47,479 44,713 10ms 44ms 249ms 5.0s 0 transport_latency_assumed last_trade_price e 50,048 470 47ms 105ms 1.0s 7.7s 0 transport_latency_assumed last_trade_price f 44,611 221 54ms 109ms 367ms 7.1s 0 transport_latency_assumed last_trade_price g 46,961 29 91ms 174ms 488ms 4.9s 0 transport_latency_assumed last_trade_price h 50,394 5,062 23ms 67ms 314ms 8.9s 0 transport_latency_assumed market_resolved c 1,214 1,175 5ms 33ms 5.5min 5.6min 0 transport_latency_assumed market_resolved e 1,350 4 44ms 121ms 316ms 49.3s 0 transport_latency_assumed market_resolved f 1,699 208 119ms 6.8min 9.1min 11.1min 0 transport_latency_assumed market_resolved g 1,376 182 142ms 4.0min 5.2min 6.5min 0 transport_latency_assumed market_resolved h 1,350 257 28ms 54ms 152ms 47.2s 0 transport_latency_assumed new_market c 394 228 50ms 247ms 24.2s 1.4min 0 transport_latency_assumed new_market e 394 91 77ms 13.2s 36.5s 1.0min 0 transport_latency_assumed new_market f 420 71 111ms 17.7s 6.5min 6.6min 0 transport_latency_assumed new_market g 395 38 136ms 13.1s 4.5min 42.2min 0 transport_latency_assumed new_market h 394 146 64ms 14.0s 39.9s 1.6min 0 transport_latency_assumed price_change c 100,821,184 96,678,866 5ms 11ms 89ms 1.9s 0 transport_latency_assumed price_change e 105,409,612 417,720 41ms 50ms 175ms 7.7s 0 transport_latency_assumed price_change f 96,110,150 156,988 48ms 58ms 190ms 7.2s 0 transport_latency_assumed price_change g 100,739,354 15,662 82ms 102ms 254ms 14.5s 0 transport_latency_assumed price_change h 105,523,229 8,306,620 18ms 29ms 115ms 9.0s 0 transport_latency_assumed tick_size_change c 3,732 3,628 5ms 8ms 52ms 322ms 0 transport_latency_assumed tick_size_change e 3,920 not meas. 41ms 45ms 105ms 331ms 0 transport_latency_assumed tick_size_change f 3,484 4 48ms 53ms 122ms 376ms 0 transport_latency_assumed tick_size_change g 3,820 not meas. 82ms 97ms 167ms 404ms 0 transport_latency_assumed tick_size_change h 3,920 288 18ms 27ms 108ms 752ms 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-18/02/2026-09-18T02.parquet sha256sum 2026-09-18T02.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.