Hour audit: 2026-09-13T04
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-13T04 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-13T04:00:00.000020874+00:00 · last event 2026-09-13T04:59:59.998433685+00:00
VOLUME 116,403,323 rows · 1,234,779,053 bytes (1.15 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 113,983,457 · e: 113,950,080 · f: 110,030,554 · g: 109,403,202 · c: 89,602,970 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 27,276,879 (23.43%) · e: 1,961,469 (1.69%) · f: 449,185 (0.39%) · g: 175,025 (0.15%) · c: 86,540,765 (74.35%) (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 116,403,323 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 d18bbe97d9f08e4a60c02e18212934ad7324621e9fa62af2ee93b059746f1632
the corpus checksum ledger names this file with the same digest
joined 116,411,005 to merged 116,403,323, minus 7,682 (minus 0.0066%)
boundary drops 7,682 · 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-13T06:35:55Z 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,614,948 125,696,965 0-44 b8e9ad38d637a7747b4c3444512cd00c1f29c706a5a534d443572096d9677f6c book 2,525,655 100,875,974 45-54 1c969e945c4a01694ef47b8b874a9d34182fc35db09345bffc45143399205a7a last_trade_price 49,196 2,798,076 55-55 fa700f124a49effaad6e1cb6560581513c7924c32bc84aa5c9483364f96400c1 market_resolved 3,565 356,278 56-56 d322c3f3081ec8e889f7b10393fdfae947161105ddd03127926bf309349dc6cf new_market 2,279 207,701 57-57 eaf17bee5b96bda3fa8d06be8bbabfc10a5a182d94f5ec4945d70c870b511199 price_change 102,203,376 1,003,359,665 58-447 67a8b527709a5645acf23e0de93c4a64871f2745d10259813c4070ff23a49a39 tick_size_change 4,304 159,717 448-448 5dc3e8ecbb12ba0f88711aff8d61f233c4888b064e4406158914227ba9fd98ae EVENT MIX count share price_change 102,203,376 87.80% best_bid_ask 11,614,948 9.98% book 2,525,655 2.17% last_trade_price 49,196 0.04% tick_size_change 4,304 <0.01% market_resolved 3,565 <0.01% new_market 2,279 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,615,101 11,614,948 153 4,491 FULL book 2,531,417 2,525,655 5,762 176,738 FULL last_trade_price 49,197 49,196 1 596 FULL market_resolved 3,565 3,565 0 308 FULL new_market 2,279 2,279 0 6 FULL price_change 102,205,142 102,203,376 1,766 2,751 FULL tick_size_change 4,304 4,304 0 401 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,987,300 8,685,463 5ms 9ms 133ms 9.6s 0 transport_latency_assumed best_bid_ask e 11,613,404 197,119 39ms 43ms 162ms 4.6s 0 transport_latency_assumed best_bid_ask f 11,170,535 29,808 46ms 52ms 188ms 6.5s 0 transport_latency_assumed best_bid_ask g 11,125,492 1,674 77ms 92ms 433ms 20.4s 0 transport_latency_assumed best_bid_ask h 11,613,496 2,700,884 18ms 22ms 185ms 47.4s 0 transport_latency_assumed book c 2,228,400 2,181,300 30.8min 1.5d 35.5d 106.3d 0 book_staleness book e 106,180 3,418 41ms 463ms 4.4s 87.7d 0 book_staleness book f 522,266 141,121 5.6min 1.3d 32.4d 106.3d 0 book_staleness book g 530,234 157,610 5.8min 1.4d 32.4d 106.3d 0 book_staleness book h 121,889 42,206 21ms 1.8min 3.8d 88.2d 0 book_staleness last_trade_price c 34,052 32,535 10ms 41ms 243ms 4.7s 0 transport_latency_assumed last_trade_price e 49,086 976 46ms 230ms 2.9s 4.9s 0 transport_latency_assumed last_trade_price f 47,885 310 53ms 119ms 2.6s 6.7s 0 transport_latency_assumed last_trade_price g 46,289 14 93ms 576ms 11.1s 20.4s 0 transport_latency_assumed last_trade_price h 49,042 15,361 23ms 57ms 332ms 11.1s 0 transport_latency_assumed market_resolved c 2,916 2,893 9ms 12.3min 16.8min 17.7min 0 transport_latency_assumed market_resolved e 2,042 35 42ms 121ms 276ms 55.5s 0 transport_latency_assumed market_resolved f 1,987 12 50ms 129ms 372ms 6.9min 0 transport_latency_assumed market_resolved g 2,051 127 90ms 337ms 4.8min 5.9min 0 transport_latency_assumed market_resolved h 2,042 498 24ms 57ms 113ms 614ms 0 transport_latency_assumed new_market c 1,670 1,014 219ms 6.1min 2.1h 5.1h 0 transport_latency_assumed new_market e 1,270 234 199ms 38.7s 1.4min 3.3h 0 transport_latency_assumed new_market f 1,275 311 173ms 33.2s 1.2min 2.1h 0 transport_latency_assumed new_market g 1,280 234 331ms 59.6s 1.7min 2.4h 0 transport_latency_assumed new_market h 1,270 486 150ms 39.7s 1.4min 8.6h 0 transport_latency_assumed price_change c 78,345,516 75,634,504 5ms 9ms 139ms 9.9s 0 transport_latency_assumed price_change e 102,173,794 1,759,642 39ms 44ms 194ms 4.6s 0 transport_latency_assumed price_change f 98,282,366 277,608 47ms 54ms 222ms 6.6s 0 transport_latency_assumed price_change g 97,693,904 15,366 77ms 95ms 493ms 20.4s 0 transport_latency_assumed price_change h 102,191,414 24,516,256 18ms 24ms 187ms 48.8s 0 transport_latency_assumed tick_size_change c 3,116 3,056 4ms 7ms 235ms 371ms 0 transport_latency_assumed tick_size_change e 4,304 45 39ms 43ms 306ms 1.1s 0 transport_latency_assumed tick_size_change f 4,240 15 46ms 50ms 223ms 660ms 0 transport_latency_assumed tick_size_change g 3,952 not meas. 77ms 91ms 479ms 1.4s 0 transport_latency_assumed tick_size_change h 4,304 1,188 18ms 21ms 129ms 554ms 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/04/2026-09-13T04.parquet sha256sum 2026-09-13T04.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.