Hour audit: 2026-09-13T15
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-13T15 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-13T15:00:00.000026831+00:00 · last event 2026-09-13T15:59:59.999975483+00:00
VOLUME 120,366,383 rows · 1,267,793,016 bytes (1.18 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 119,592,050 · f: 119,580,863 · e: 119,576,538 · g: 119,565,763 · c: 108,814,324 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 14,789,817 (12.29%) · f: 141,967 (0.12%) · e: 699,477 (0.58%) · g: 22,420 (0.02%) · c: 104,712,702 (86.99%) (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 120,366,383 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 56d0b1fe01d5b964916190053b6506bb4de957113036a1d1bfd3e575b04c9091
the corpus checksum ledger names this file with the same digest
joined 120,368,808 to merged 120,366,383, minus 2,425 (minus 0.0020%)
boundary drops 2,425 · 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-13T17:00:45Z 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,482,338 127,771,129 0-43 021b2b99bfa015699daa689cb8558c6325b6fe9c66afe127d71780fc4a841d76 book 896,443 64,913,871 44-47 3975a0bfaff89565cc9421923970b494f1217b3a219de3cb3183ffe5db921e69 last_trade_price 63,018 3,737,551 48-48 8c30d1a2eab2ea3b2cd2784289eeb1f03237d0d05cea4d8e1bc65fe251dfaa73 market_resolved 2,938 441,353 49-49 36e09fd10d0a6031ce3c6cc6ba8019d802c4e5bb986d0575b7d3acf55bcc5060 new_market 696 73,405 50-50 e97636cf626f72bf79e6687ec74fb774d16ff27110b60ee5a315d2e822d48875 price_change 107,913,470 1,069,217,495 51-462 6738858c4a314640cb0a19d9a67a6652963331a86bfc581c5e9c2836736452f5 tick_size_change 7,480 268,786 463-463 c0fdbad0b3c97f3878f4f5fe0609d9052683328bed9eaf24838d30410b233760 EVENT MIX count share price_change 107,913,470 89.65% best_bid_ask 11,482,338 9.54% book 896,443 0.74% last_trade_price 63,018 0.05% tick_size_change 7,480 <0.01% market_resolved 2,938 <0.01% new_market 696 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,482,602 11,482,338 264 1,865 FULL book 896,459 896,443 16 174,169 FULL last_trade_price 63,018 63,018 0 207 FULL market_resolved 2,939 2,938 1 233 FULL new_market 696 696 0 0 FULL price_change 107,915,614 107,913,470 2,144 1,101 FULL tick_size_change 7,480 7,480 0 202 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,339,194 9,962,029 5ms 10ms 74ms 6.5s 0 transport_latency_assumed best_bid_ask e 11,480,966 67,990 41ms 45ms 114ms 4.2s 0 transport_latency_assumed best_bid_ask f 11,480,904 11,706 47ms 53ms 137ms 11.0s 0 transport_latency_assumed best_bid_ask g 11,478,748 672 81ms 97ms 225ms 12.0s 0 transport_latency_assumed best_bid_ask h 11,481,782 1,439,941 18ms 25ms 78ms 16.9s 0 transport_latency_assumed book c 872,325 862,939 7.4min 1.8d 32.9d 106.7d 0 book_staleness book e 129,973 1,665 42ms 78ms 1.1s 22.1d 0 book_staleness book f 132,641 1,900 49ms 103ms 38.6min 88.2d 0 book_staleness book g 150,379 11,996 87ms 1.5min 4.3d 105.1d 0 book_staleness book h 130,742 17,943 22ms 41ms 2.1s 88.2d 0 book_staleness last_trade_price c 56,314 53,794 10ms 41ms 196ms 5.0s 0 transport_latency_assumed last_trade_price e 62,968 431 47ms 100ms 667ms 5.0s 0 transport_latency_assumed last_trade_price f 62,984 116 54ms 107ms 848ms 5.0s 0 transport_latency_assumed last_trade_price g 62,897 9 91ms 171ms 547ms 5.1s 0 transport_latency_assumed last_trade_price h 62,991 8,668 24ms 56ms 232ms 5.0s 0 transport_latency_assumed market_resolved c 2,607 2,514 5ms 20ms 5.5min 5.8min 0 transport_latency_assumed market_resolved e 2,761 36 43ms 121ms 364ms 56.3s 0 transport_latency_assumed market_resolved f 2,761 not meas. 49ms 127ms 427ms 56.3s 0 transport_latency_assumed market_resolved g 2,760 5 88ms 239ms 466ms 1.0min 0 transport_latency_assumed market_resolved h 2,760 383 21ms 52ms 229ms 1.0min 0 transport_latency_assumed new_market c 551 351 70ms 1.3min 1.6min 1.7min 0 transport_latency_assumed new_market e 465 49 140ms 10.7s 27.6s 31.6s 0 transport_latency_assumed new_market f 465 95 133ms 14.4s 40.7s 8.3min 0 transport_latency_assumed new_market g 465 34 284ms 14.0s 24.9s 1.5min 0 transport_latency_assumed new_market h 465 167 81ms 11.4s 19.2s 1.6min 0 transport_latency_assumed price_change c 97,536,653 93,824,665 5ms 11ms 82ms 7.9s 0 transport_latency_assumed price_change e 107,891,925 629,294 41ms 48ms 161ms 4.3s 0 transport_latency_assumed price_change f 107,893,628 128,150 47ms 56ms 182ms 13.5s 0 transport_latency_assumed price_change g 107,863,042 9,704 81ms 100ms 281ms 12.0s 0 transport_latency_assumed price_change h 107,905,830 13,321,657 18ms 27ms 92ms 17.2s 0 transport_latency_assumed tick_size_change c 6,680 6,410 5ms 10ms 58ms 124ms 0 transport_latency_assumed tick_size_change e 7,480 12 40ms 44ms 110ms 427ms 0 transport_latency_assumed tick_size_change f 7,480 not meas. 47ms 52ms 86ms 1.7s 0 transport_latency_assumed tick_size_change g 7,472 not meas. 80ms 95ms 145ms 451ms 0 transport_latency_assumed tick_size_change h 7,480 1,058 18ms 23ms 58ms 447ms 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/15/2026-09-13T15.parquet sha256sum 2026-09-13T15.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.