Hour audit: 2026-09-09T19
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-09T19 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-09T19:00:00.002114708+00:00 · last event 2026-09-09T19:59:59.999687912+00:00
VOLUME 128,081,828 rows · 1,437,492,059 bytes (1.34 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 124,820,687 · e: 124,791,693 · f: 119,911,050 · g: 119,687,753 · c: 84,650,826 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 42,537,496 (33.21%) · e: 3,963,269 (3.09%) · f: 1,286,422 (1.00%) · g: 210,179 (0.16%) · c: 80,084,462 (62.53%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 2fc5f20481c30d97456a3891d42a9fb66a96ab3f557dc864442c3fe3c5c04de9
the corpus checksum ledger names this file with the same digest
joined 128,088,789 to merged 128,081,828, minus 6,961 (minus 0.0054%)
boundary drops 6,961 · 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-09T21:02:06Z 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,638,670 135,692,409 0-44 1d36a9859e51a48589845520df3d4e087a17b5c66c58f1b2fdda165aabfb8b8b book 3,733,956 131,161,796 45-59 274e080fcce474ff35f44c47b039f641ca99302d091c71f0252022cf082b6140 last_trade_price 70,630 4,044,380 60-60 ed9b1a15323f1adc8015535b2aab3b4d14d6935bc726228e887b203f37050e23 market_resolved 2,376 179,320 61-61 10ba59ed0273ae9d90749b6b20fdf6f60a2e67b912cf9156a43f5897a920911f new_market 4,412 305,175 62-62 a234160eb435128b83fdcd0873978bd8c64a515b78bb4521074bdd85c0d8667d price_change 112,627,624 1,164,496,746 63-492 75d7d66fb6a109b6c565dc89b73f70b26d730836b76fdc839acf496c536c3c37 tick_size_change 4,160 154,778 493-493 1aecb1a5ce796709c664b138bc66c30dd02206377e012ed0701b0a0bfef8db17 EVENT MIX count share price_change 112,627,624 87.93% best_bid_ask 11,638,670 9.09% book 3,733,956 2.92% last_trade_price 70,630 0.06% new_market 4,412 <0.01% tick_size_change 4,160 <0.01% market_resolved 2,376 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,638,928 11,638,670 258 8,612 FULL book 3,736,472 3,733,956 2,516 48,197 FULL last_trade_price 70,631 70,630 1 979 FULL market_resolved 2,376 2,376 0 73 FULL new_market 4,412 4,412 0 0 FULL price_change 112,631,810 112,627,624 4,186 3,582 FULL tick_size_change 4,160 4,160 0 417 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 7,557,618 7,151,569 6ms 15ms 163ms 7.2s 0 transport_latency_assumed best_bid_ask e 11,632,185 375,360 41ms 56ms 287ms 12.1s 0 transport_latency_assumed best_bid_ask f 11,134,369 97,121 46ms 68ms 311ms 10.0s 0 transport_latency_assumed best_bid_ask g 11,172,542 6,696 84ms 132ms 611ms 27.2s 0 transport_latency_assumed best_bid_ask h 11,630,027 4,007,924 18ms 42ms 288ms 23.3s 0 transport_latency_assumed book c 3,287,582 3,067,751 19.8min 22.6h 32.1d 102.9d 0 book_staleness book e 527,836 153,889 2.8min 13.8h 25.2d 102.9d 0 book_staleness book f 723,854 192,339 6.2min 17.0h 29.0d 102.9d 0 book_staleness book g 558,802 115,696 3.0min 13.9h 25.4d 102.9d 0 book_staleness book h 582,910 204,281 3.8min 14.3h 25.4d 102.9d 0 book_staleness last_trade_price c 45,452 42,635 12ms 52ms 291ms 6.3s 0 transport_latency_assumed last_trade_price e 70,418 2,158 60ms 396ms 3.5s 12.1s 0 transport_latency_assumed last_trade_price f 67,586 1,082 66ms 363ms 3.3s 10.1s 0 transport_latency_assumed last_trade_price g 67,842 226 104ms 714ms 6.9s 26.6s 0 transport_latency_assumed last_trade_price h 70,238 24,529 27ms 113ms 653ms 19.1s 0 transport_latency_assumed market_resolved c 1,911 1,868 6.5min 17.7min 23.0min 23.3min 0 transport_latency_assumed market_resolved e 1,021 31 42ms 154ms 52.3s 56.3s 0 transport_latency_assumed market_resolved f 1,006 32 47ms 128ms 1.0min 4.8min 0 transport_latency_assumed market_resolved g 1,020 13 88ms 241ms 3.7min 4.8min 0 transport_latency_assumed market_resolved h 1,021 432 19ms 69ms 54.7s 1.0min 0 transport_latency_assumed new_market c 3,409 2,460 4.6min 18.9min 20.2min 20.7min 0 transport_latency_assumed new_market e 1,791 468 173ms 15.8s 32.4s 1.6min 0 transport_latency_assumed new_market f 1,791 448 188ms 20.4s 54.1s 2.2min 0 transport_latency_assumed new_market g 1,798 273 309ms 19.5s 5.1min 5.2min 0 transport_latency_assumed new_market h 1,791 763 133ms 19.6s 47.2s 1.6min 0 transport_latency_assumed price_change c 73,752,242 69,815,684 6ms 16ms 167ms 9.5s 0 transport_latency_assumed price_change e 112,554,286 3,431,186 41ms 69ms 503ms 12.1s 0 transport_latency_assumed price_change f 107,978,368 995,336 46ms 79ms 484ms 10.1s 0 transport_latency_assumed price_change g 107,881,773 87,271 85ms 158ms 1.3s 27.2s 0 transport_latency_assumed price_change h 112,530,540 38,298,147 18ms 45ms 333ms 24.1s 0 transport_latency_assumed tick_size_change c 2,612 2,495 6ms 12ms 69ms 253ms 0 transport_latency_assumed tick_size_change e 4,156 177 41ms 52ms 176ms 593ms 0 transport_latency_assumed tick_size_change f 4,076 64 46ms 68ms 174ms 358ms 0 transport_latency_assumed tick_size_change g 3,976 4 82ms 115ms 357ms 659ms 0 transport_latency_assumed tick_size_change h 4,160 1,420 18ms 47ms 136ms 845ms 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-09/19/2026-09-09T19.parquet sha256sum 2026-09-09T19.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.