Hour audit: 2026-09-14T22
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-14T22 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-14T22:00:00.000191568+00:00 · last event 2026-09-14T22:59:59.999972413+00:00
VOLUME 111,032,132 rows · 1,188,037,647 bytes (1.11 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 109,337,853 · h: 109,326,792 · e: 109,315,770 · g: 109,287,717 · c: 93,754,048 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 516,684 (0.47%) · h: 20,245,838 (18.23%) · e: 865,653 (0.78%) · g: 293,901 (0.26%) · c: 89,110,056 (80.26%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 111,032,132 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 a31abe6e2fa7dc0b564f679d5af36e940be6702ec7a3f3264ab195580196b35e
the corpus checksum ledger names this file with the same digest
joined 111,042,877 to merged 111,032,132, minus 10,745 (minus 0.0097%)
boundary drops 10,745 · 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-14T23:58:18Z 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,655,164 132,040,575 0-44 a16a7546ce940767fda36e769a4ae0a3a2e9ab59622ced9937aabc7e70eddbd2 book 2,116,316 102,804,395 45-53 80cdd027c7e13974fa9fae98c5a5fd42485389f3280285e358ed18e3990ca93f last_trade_price 42,406 2,496,151 54-54 3de230074c9d6a845db4d78cb03c578068242021cfbc1ef55082d25ec3abfbc2 market_resolved 1,705 242,361 55-55 7a25d55424120f3994133209b14794b3e0fa25fa66c18e07bcdd76d0559f9d6f new_market 1,862 182,785 56-56 bb645daccac3f16864667abb9c73c89d621a51fbacb25307da2a76fbc3583d69 price_change 97,212,347 948,918,769 57-427 35d9142928ee5112db355b43d47c3857659c33ee47e42774cf72cb321476f397 tick_size_change 2,332 87,142 428-428 5da22dbba0ce5bf590963f25e2823d78a3e36b42d2df4e520b6e024ba66e5300 EVENT MIX count share price_change 97,212,347 87.55% best_bid_ask 11,655,164 10.50% book 2,116,316 1.91% last_trade_price 42,406 0.04% tick_size_change 2,332 <0.01% new_market 1,862 <0.01% market_resolved 1,705 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,655,379 11,655,164 215 1,845 FULL book 2,123,382 2,116,316 7,066 101,538 FULL last_trade_price 42,408 42,406 2 265 FULL market_resolved 1,705 1,705 0 89 FULL new_market 1,862 1,862 0 3 FULL price_change 97,215,809 97,212,347 3,462 1,288 FULL tick_size_change 2,332 2,332 0 70 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,833,843 9,394,112 5ms 12ms 117ms 7.3s 0 transport_latency_assumed best_bid_ask e 11,649,060 68,625 46ms 62ms 213ms 7.7s 0 transport_latency_assumed best_bid_ask f 11,649,032 31,893 48ms 60ms 230ms 8.9s 0 transport_latency_assumed best_bid_ask g 11,645,148 2,750 79ms 102ms 397ms 25.3s 0 transport_latency_assumed best_bid_ask h 11,650,740 2,157,784 18ms 25ms 158ms 18.4s 0 transport_latency_assumed book c 1,569,018 1,284,525 8.5min 3.1d 37.2d 108.0d 0 book_staleness book e 513,057 193,167 3.9min 1.6d 34.1d 108.0d 0 book_staleness book f 517,291 194,798 4.0min 1.7d 34.2d 108.0d 0 book_staleness book g 585,091 253,530 4.8min 1.8d 34.2d 108.0d 0 book_staleness book h 489,527 190,296 3.8min 1.6d 34.2d 108.0d 0 book_staleness last_trade_price c 35,686 33,611 11ms 50ms 240ms 4.5s 0 transport_latency_assumed last_trade_price e 42,087 330 62ms 215ms 1.5s 4.6s 0 transport_latency_assumed last_trade_price f 42,131 282 59ms 231ms 1.9s 5.1s 0 transport_latency_assumed last_trade_price g 41,720 147 96ms 334ms 3.9s 25.3s 0 transport_latency_assumed last_trade_price h 42,231 8,036 24ms 92ms 503ms 8.9s 0 transport_latency_assumed market_resolved c 1,408 1,366 5ms 2.7min 4.8min 5.2min 0 transport_latency_assumed market_resolved e 1,486 3 49ms 189ms 488ms 1.0min 0 transport_latency_assumed market_resolved f 1,487 4 49ms 200ms 464ms 766ms 0 transport_latency_assumed market_resolved g 1,486 not meas. 87ms 267ms 799ms 1.2s 0 transport_latency_assumed market_resolved h 1,486 332 18ms 63ms 179ms 58.8s 0 transport_latency_assumed new_market c 1,139 744 89ms 17.7s 4.6min 4.6min 0 transport_latency_assumed new_market e 1,141 274 218ms 26.2s 1.1min 1.4min 0 transport_latency_assumed new_market f 1,141 198 221ms 20.8s 45.2s 4.0min 0 transport_latency_assumed new_market g 1,141 152 285ms 22.9s 46.6s 1.3min 0 transport_latency_assumed new_market h 1,141 494 132ms 22.9s 43.5s 1.4min 0 transport_latency_assumed price_change c 82,310,902 78,393,696 5ms 14ms 129ms 7.3s 0 transport_latency_assumed price_change e 97,106,607 603,240 47ms 67ms 363ms 8.7s 0 transport_latency_assumed price_change f 97,124,439 289,509 48ms 69ms 406ms 9.2s 0 transport_latency_assumed price_change g 97,010,799 37,322 80ms 119ms 646ms 25.3s 0 transport_latency_assumed price_change h 97,139,335 17,888,580 18ms 30ms 205ms 19.9s 0 transport_latency_assumed tick_size_change c 2,052 2,002 5ms 9ms 39ms 219ms 0 transport_latency_assumed tick_size_change e 2,332 14 46ms 57ms 104ms 259ms 0 transport_latency_assumed tick_size_change f 2,332 not meas. 48ms 52ms 95ms 272ms 0 transport_latency_assumed tick_size_change g 2,332 not meas. 79ms 93ms 169ms 382ms 0 transport_latency_assumed tick_size_change h 2,332 316 17ms 21ms 102ms 275ms 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-14/22/2026-09-14T22.parquet sha256sum 2026-09-14T22.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.