Hour audit: 2026-09-13T18
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-13T18 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-13T18:00:00.000005048+00:00 · last event 2026-09-13T18:59:59.999975278+00:00
VOLUME 157,368,939 rows · 1,771,746,419 bytes (1.65 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 152,336,964 · e: 135,781,591 · g: 119,669,960 · f: 118,026,111 · c: 89,805,099 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 64,769,650 (41.16%) · e: 3,713,071 (2.36%) · g: 651,849 (0.41%) · f: 2,341,529 (1.49%) · c: 85,892,840 (54.58%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 e965637c99e061030bec23697114624026627f98788e12ce60ee97d650b1c346
the corpus checksum ledger names this file with the same digest
joined 157,410,303 to merged 157,368,939, minus 41,364 (minus 0.0263%)
boundary drops 41,364 · 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-13T20:04:53Z 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 15,222,921 170,614,413 0-58 78ea7788ce1f903f9c6c75d10ca4901953c9f75d50e032a9788d347d9fae86a2 book 5,120,439 158,958,976 59-78 1251f842f81f89b801e3e669c3c703a97a8093952338bd94b07537c7a8c6a4a8 last_trade_price 61,818 3,630,749 79-79 4f23d02caf13ac77a8b1b9368a4ad5deba355b3a3aa3a36d5a1516e89d423212 market_resolved 14,822 786,161 80-80 0defe1d081b9278eb905d9547b36f7196e4255f18f723009edcdaef6eaf09ff5 new_market 8,227 293,396 81-81 d3dbd2a0379010aaecb2e37d3a11c070cfa2420e1e3ca9405a0a8fa3417c6ff3 price_change 136,931,828 1,435,354,637 82-604 a7d69ebe873dc0d80ee91fb7e35643b023ea3f814603f7f84b4612636cc28cb3 tick_size_change 8,884 319,549 605-605 ae081a482e64cc2452645da8d4bf1d29129a0c1288c9cb8d7b755839bb225c01 EVENT MIX count share price_change 136,931,828 87.01% best_bid_ask 15,222,921 9.67% book 5,120,439 3.25% last_trade_price 61,818 0.04% market_resolved 14,822 <0.01% tick_size_change 8,884 <0.01% new_market 8,227 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 15,223,317 15,222,921 396 11,831 FULL book 5,158,365 5,120,439 37,926 172,814 FULL last_trade_price 61,819 61,818 1 1,817 FULL market_resolved 14,836 14,822 14 1,472 FULL new_market 8,350 8,227 123 616 FULL price_change 136,934,732 136,931,828 2,904 8,206 FULL tick_size_change 8,884 8,884 0 1,476 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,536,951 8,211,362 5ms 12ms 79ms 1.6s 0 transport_latency_assumed best_bid_ask e 13,386,402 336,425 43ms 53ms 206ms 6.2s 0 transport_latency_assumed best_bid_ask f 11,506,918 148,407 46ms 58ms 210ms 6.6s 0 transport_latency_assumed best_bid_ask g 11,712,598 6,834 82ms 104ms 478ms 12.6s 0 transport_latency_assumed best_bid_ask h 15,221,275 6,519,893 19ms 38ms 165ms 50.0s 0 transport_latency_assumed book c 3,956,228 3,418,501 30.8min 2.0d 36.2d 106.9d 0 book_staleness book e 1,169,940 253,553 15.3min 2.0d 35.8d 106.8d 0 book_staleness book f 2,472,735 817,029 25.6min 2.0d 36.2d 106.9d 0 book_staleness book g 2,194,329 572,807 24.2min 2.0d 36.2d 106.9d 0 book_staleness book h 130,704 58,549 23ms 69ms 17.0s 88.3d 0 book_staleness last_trade_price c 31,967 30,330 11ms 47ms 243ms 5.0s 0 transport_latency_assumed last_trade_price e 53,433 1,568 50ms 123ms 1.1s 6.3s 0 transport_latency_assumed last_trade_price f 46,523 875 54ms 127ms 987ms 6.7s 0 transport_latency_assumed last_trade_price g 46,601 91 93ms 213ms 1.6s 11.7s 0 transport_latency_assumed last_trade_price h 61,740 28,954 26ms 72ms 364ms 33.0s 0 transport_latency_assumed market_resolved c 12,797 8,116 15.5min 33.3min 43.8min 46.9min 0 transport_latency_assumed market_resolved e 4,325 162 110ms 10.9min 16.3min 16.6min 0 transport_latency_assumed market_resolved f 5,792 2,051 355ms 14.1min 20.8min 21.3min 0 transport_latency_assumed market_resolved g 7,649 3,041 7.1min 21.3min 28.9min 32.9min 0 transport_latency_assumed market_resolved h 3,592 1,452 30ms 65ms 207ms 1.0min 0 transport_latency_assumed new_market c 7,744 6,997 27.1min 55.5min 1.1h 1.4h 0 transport_latency_assumed new_market e 1,088 298 205ms 24.8s 15.2min 20.8min 0 transport_latency_assumed new_market f 1,751 335 361ms 15.3min 43.7min 53.4min 0 transport_latency_assumed new_market g 2,018 256 30.8s 15.6min 28.8min 1.1h 0 transport_latency_assumed new_market h 1,039 341 176ms 23.2s 36.4s 14.0min 0 transport_latency_assumed price_change c 77,254,724 74,212,960 5ms 13ms 90ms 1.6s 0 transport_latency_assumed price_change e 121,158,263 3,120,933 43ms 57ms 254ms 7.2s 0 transport_latency_assumed price_change f 103,985,540 1,372,740 47ms 61ms 250ms 7.6s 0 transport_latency_assumed price_change g 105,698,985 68,816 82ms 110ms 577ms 14.2s 0 transport_latency_assumed price_change h 136,909,730 58,156,379 19ms 40ms 184ms 52.7s 0 transport_latency_assumed tick_size_change c 4,688 4,574 5ms 9ms 37ms 144ms 0 transport_latency_assumed tick_size_change e 8,140 132 43ms 48ms 164ms 556ms 0 transport_latency_assumed tick_size_change f 6,852 92 46ms 55ms 168ms 385ms 0 transport_latency_assumed tick_size_change g 7,780 4 80ms 96ms 319ms 4.9s 0 transport_latency_assumed tick_size_change h 8,884 4,082 18ms 31ms 122ms 743ms 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-13/18/2026-09-13T18.parquet sha256sum 2026-09-13T18.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.