Hour audit: 2026-09-13T00
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-13T00 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-13T00:00:00.000016800+00:00 · last event 2026-09-13T00:59:59.997885608+00:00
VOLUME 124,678,136 rows · 1,331,056,585 bytes (1.24 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 122,745,472 · h: 122,740,189 · f: 117,740,313 · g: 117,693,979 · c: 98,774,798 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 2,047,964 (1.64%) · h: 25,934,283 (20.80%) · f: 380,041 (0.30%) · g: 58,373 (0.05%) · c: 96,257,475 (77.20%) (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 124,678,136 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 6b7e77920945a29f56135ca968e313746a821adf9aebe01dd49aba5b27e11872
the corpus checksum ledger names this file with the same digest
joined 124,681,919 to merged 124,678,136, minus 3,783 (minus 0.0030%)
boundary drops 3,783 · 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-13T02:05:09Z 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 12,530,143 138,660,567 0-47 0b1cc1d8a8eb1d300f2aa2548dd221acdaf3aeb088b296b051e5811ea9100536 book 2,012,204 87,672,665 48-55 5c7b76eb118d3df00dafda4c28733b77ced8e4bac586488129878f71b7423fc6 last_trade_price 48,755 2,871,374 56-56 04e3e18978a828ab0d30f5982260a92fa203c4cde095c874e99ec66c2e28ba13 market_resolved 3,490 430,416 57-57 6ffec03659a154af71e89563c8839331b94448893fa5a905806302c6cfb6d6e0 new_market 692 62,365 58-58 9eafa7b270a67e4b7971ac82ab70e189deeae3d0a89b5a9a2718999007d4bd9e price_change 110,076,096 1,099,697,211 59-478 ce135c922a4a7a8a372629a1474c6fa8fb666b9085147862eb036fbcca831123 tick_size_change 6,756 245,931 479-479 a178120cc54197926d81d629ec4fa7a27165fd9546933b53ce5570ae2ebc4605 EVENT MIX count share price_change 110,076,096 88.29% best_bid_ask 12,530,143 10.05% book 2,012,204 1.61% last_trade_price 48,755 0.04% tick_size_change 6,756 <0.01% market_resolved 3,490 <0.01% new_market 692 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,530,461 12,530,143 318 3,433 FULL book 2,012,290 2,012,204 86 186,691 FULL last_trade_price 48,756 48,755 1 501 FULL market_resolved 3,490 3,490 0 23 FULL new_market 692 692 0 0 FULL price_change 110,079,474 110,076,096 3,378 3,120 FULL tick_size_change 6,756 6,756 0 234 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,932,078 9,696,557 4ms 8ms 48ms 3.6s 0 transport_latency_assumed best_bid_ask e 12,529,177 204,007 41ms 46ms 102ms 2.3s 0 transport_latency_assumed best_bid_ask f 11,973,104 27,034 46ms 51ms 121ms 1.6s 0 transport_latency_assumed best_bid_ask g 11,964,128 1,633 77ms 91ms 202ms 12.7s 0 transport_latency_assumed best_bid_ask h 12,529,639 2,600,912 17ms 23ms 76ms 14.2s 0 transport_latency_assumed book c 1,889,511 1,864,354 25.5min 1.3d 34.5d 106.1d 0 book_staleness book e 101,242 3,331 43ms 70ms 655ms 87.6d 0 book_staleness book f 475,281 84,187 5.1min 1.1d 31.2d 106.1d 0 book_staleness book g 496,818 38,476 5.7min 1.1d 31.4d 106.1d 0 book_staleness book h 100,820 21,856 20ms 42ms 246ms 17.5s 0 book_staleness last_trade_price c 37,652 36,575 9ms 37ms 151ms 4.9s 0 transport_latency_assumed last_trade_price e 48,710 1,129 47ms 96ms 342ms 5.0s 0 transport_latency_assumed last_trade_price f 46,273 239 52ms 99ms 295ms 4.9s 0 transport_latency_assumed last_trade_price g 46,121 17 88ms 176ms 574ms 5.0s 0 transport_latency_assumed last_trade_price h 48,726 10,795 22ms 58ms 207ms 4.9s 0 transport_latency_assumed market_resolved c 2,858 2,647 5ms 12.3min 16.2min 16.5min 0 transport_latency_assumed market_resolved e 2,618 62 43ms 121ms 282ms 1.0min 0 transport_latency_assumed market_resolved f 2,640 159 48ms 139ms 5.0min 5.3min 0 transport_latency_assumed market_resolved g 2,667 34 86ms 253ms 5.5min 5.8min 0 transport_latency_assumed market_resolved h 2,618 588 21ms 53ms 149ms 1.0min 0 transport_latency_assumed new_market c 571 431 114ms 8.0min 2.5h 3.9h 0 transport_latency_assumed new_market e 379 49 132ms 11.8s 25.2s 4.3h 0 transport_latency_assumed new_market f 379 65 112ms 15.7s 22.9s 13.0min 0 transport_latency_assumed new_market g 380 31 197ms 17.5s 23.1s 2.0h 0 transport_latency_assumed new_market h 379 116 67ms 13.8s 24.1s 2.1h 0 transport_latency_assumed price_change c 86,906,296 84,651,147 4ms 9ms 63ms 3.6s 0 transport_latency_assumed price_change e 110,056,590 1,839,313 41ms 47ms 125ms 2.3s 0 transport_latency_assumed price_change f 105,235,908 268,321 46ms 52ms 144ms 2.1s 0 transport_latency_assumed price_change g 105,177,145 18,182 78ms 92ms 235ms 13.9s 0 transport_latency_assumed price_change h 110,051,251 23,299,133 17ms 25ms 90ms 18.1s 0 transport_latency_assumed tick_size_change c 5,832 5,764 4ms 6ms 20ms 54ms 0 transport_latency_assumed tick_size_change e 6,756 73 42ms 45ms 122ms 323ms 0 transport_latency_assumed tick_size_change f 6,728 36 45ms 50ms 158ms 378ms 0 transport_latency_assumed tick_size_change g 6,720 not meas. 77ms 91ms 305ms 603ms 0 transport_latency_assumed tick_size_change h 6,756 883 17ms 20ms 94ms 608ms 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/00/2026-09-13T00.parquet sha256sum 2026-09-13T00.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.