Hour audit: 2026-09-17T01
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-17T01 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-17T01:00:00.000072764+00:00 · last event 2026-09-17T01:59:59.999905118+00:00
VOLUME 123,632,710 rows · 1,318,947,847 bytes (1.23 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 122,375,829 · e: 122,240,076 · g: 117,817,384 · f: 116,630,212 · c: 113,060,241 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 13,863,830 (11.21%) · e: 1,069,753 (0.87%) · g: 255,337 (0.21%) · f: 560,797 (0.45%) · c: 107,882,993 (87.26%) (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 123,632,710 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 2984f1ee9da78746342d8b9165e09ecc2d967c0ffdecab12ad6338523669366a
the corpus checksum ledger names this file with the same digest
joined 123,636,024 to merged 123,632,710, minus 3,314 (minus 0.0027%)
boundary drops 3,314 · 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-17T03:01:04Z 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 14,156,102 158,170,910 0-54 ad291bde2631bb58d10409d02b0f08ce8ab2b81894ea381fd6068a8da488160b book 1,554,047 90,622,140 55-60 6575f6c4cde2595a64de8417750eaaffc42ae76a91f4bc158e1002081cc36ac9 last_trade_price 47,111 2,688,679 61-61 78dc568ed5727827933c98d0c23f5b7af5d9b573912dd1f0fe2a5093c250fccd market_resolved 938 145,603 62-62 42fa38dbb803744a1018e7b2fbf0d0521dc2ac6fe35153c19d68fca84bd716fc new_market 506 57,019 63-63 7603688ac85f02e7f8525524794836d882413f23ef4532356553e44fb59f4558 price_change 107,868,950 1,065,671,435 64-475 40e0c6a10f98767d32b82f9ae1281d8b466125d6072120245ed3c069c15524bf tick_size_change 5,056 185,852 476-476 6227d718ff9a0b7e9426f5bc6f01cbb06ad4f4785fa88482e8379e18be0c9881 EVENT MIX count share price_change 107,868,950 87.25% best_bid_ask 14,156,102 11.45% book 1,554,047 1.26% last_trade_price 47,111 0.04% tick_size_change 5,056 <0.01% market_resolved 938 <0.01% new_market 506 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 14,156,454 14,156,102 352 1,749 FULL book 1,554,209 1,554,047 162 128,416 FULL last_trade_price 47,111 47,111 0 210 FULL market_resolved 938 938 0 39 FULL new_market 506 506 0 0 FULL price_change 107,871,750 107,868,950 2,800 409 FULL tick_size_change 5,056 5,056 0 165 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 13,062,590 12,546,118 4ms 9ms 71ms 1.8s 0 transport_latency_assumed best_bid_ask e 14,152,732 100,881 41ms 48ms 121ms 4.3s 0 transport_latency_assumed best_bid_ask f 13,525,306 23,081 46ms 54ms 138ms 2.6s 0 transport_latency_assumed best_bid_ask g 13,643,737 2,051 80ms 96ms 204ms 6.0s 0 transport_latency_assumed best_bid_ask h 14,152,486 1,483,971 17ms 24ms 80ms 7.5s 0 transport_latency_assumed book c 912,472 807,694 4.0min 2.4d 36.3d 110.1d 0 book_staleness book e 268,356 86,938 46.0s 1.6h 25.5d 110.1d 0 book_staleness book f 621,817 295,633 3.4min 1.1d 36.3d 110.1d 0 book_staleness book g 624,727 222,461 3.2min 1.1d 36.3d 110.1d 0 book_staleness book h 356,605 141,321 1.6min 5.4h 32.5d 110.1d 0 book_staleness last_trade_price c 43,408 40,650 10ms 45ms 205ms 4.9s 0 transport_latency_assumed last_trade_price e 47,032 420 48ms 108ms 495ms 5.0s 0 transport_latency_assumed last_trade_price f 44,300 143 54ms 117ms 477ms 5.0s 0 transport_latency_assumed last_trade_price g 45,071 27 88ms 176ms 451ms 5.0s 0 transport_latency_assumed last_trade_price h 47,000 5,871 23ms 61ms 229ms 5.0s 0 transport_latency_assumed market_resolved c 894 879 5ms 14ms 4.3min 5.4min 0 transport_latency_assumed market_resolved e 896 2 111ms 147ms 427ms 833ms 0 transport_latency_assumed market_resolved f 867 8 114ms 150ms 751ms 5.0min 0 transport_latency_assumed market_resolved g 879 1 177ms 248ms 589ms 5.5min 0 transport_latency_assumed market_resolved h 896 48 33ms 49ms 178ms 281ms 0 transport_latency_assumed new_market c 360 278 32ms 479ms 43.3s 1.3min 0 transport_latency_assumed new_market e 360 30 84ms 385ms 21.5s 2.8min 0 transport_latency_assumed new_market f 360 32 91ms 392ms 21.7s 59.8s 0 transport_latency_assumed new_market g 360 45 143ms 16.6s 4.2min 4.2min 0 transport_latency_assumed new_market h 360 121 61ms 17.9s 29.0s 1.2min 0 transport_latency_assumed price_change c 99,035,929 94,483,011 5ms 11ms 106ms 1.9s 0 transport_latency_assumed price_change e 107,765,644 881,410 41ms 51ms 203ms 5.2s 0 transport_latency_assumed price_change f 102,432,638 241,896 46ms 58ms 230ms 5.9s 0 transport_latency_assumed price_change g 103,497,745 30,752 80ms 100ms 292ms 6.3s 0 transport_latency_assumed price_change h 107,813,430 12,231,881 18ms 27ms 120ms 7.6s 0 transport_latency_assumed tick_size_change c 4,588 4,363 5ms 11ms 85ms 384ms 0 transport_latency_assumed tick_size_change e 5,056 72 41ms 51ms 159ms 336ms 0 transport_latency_assumed tick_size_change f 4,924 4 46ms 56ms 131ms 223ms 0 transport_latency_assumed tick_size_change g 4,865 not meas. 80ms 97ms 210ms 533ms 0 transport_latency_assumed tick_size_change h 5,052 617 18ms 27ms 88ms 259ms 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-17/01/2026-09-17T01.parquet sha256sum 2026-09-17T01.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.