Hour audit: 2026-09-13T12
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-13T12 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-13T12:00:00.002006690+00:00 · last event 2026-09-13T12:59:59.999792463+00:00
VOLUME 114,876,554 rows · 1,226,257,168 bytes (1.14 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 112,415,603 · f: 112,411,680 · e: 112,394,788 · g: 112,384,385 · c: 81,900,995 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 34,452,899 (29.99%) · f: 225,749 (0.20%) · e: 953,813 (0.83%) · g: 31,258 (0.03%) · c: 79,212,835 (68.95%) (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 114,876,554 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 0457cf6b715acc4fd314dd4e97db399b3903bc9a44d4f569270036ac0b774175
the corpus checksum ledger names this file with the same digest
joined 114,878,252 to merged 114,876,554, minus 1,698 (minus 0.0015%)
boundary drops 1,698 · 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-13T14:35:44Z 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,802,408 128,563,781 0-45 70e6579945a1b00ee82e34e8922a45f35578217561b63c8e6e9d67e00f334a33 book 2,556,684 91,107,870 46-55 443d44ca40820fb1a173b96a93fb295a4e267abc26879b72476b6f1ebdc7ab58 last_trade_price 54,876 3,190,605 56-56 e33341baa73bf4e22a163a39f88c9c3c5542ce1c24a7f96a0769813448992215 market_resolved 1,842 182,548 57-57 18fbd89c71a16a9be69b4def679265f8b39311a451c2bfdccbf1207b6fb4cf9d new_market 1,050 73,049 58-58 37c33675b24aca42d458abd0d647e9b45736cea1838d1800b9ce1081f66a831a price_change 100,454,030 1,001,623,025 59-442 7c51b2c059df21d414792307897bda381b44699994e8496f95667dab293ec15c tick_size_change 5,664 206,782 443-443 f73c0d79153242fcf6cac1f0bba68529fc593a083288d08352c5a1714cee4c2c EVENT MIX count share price_change 100,454,030 87.45% best_bid_ask 11,802,408 10.27% book 2,556,684 2.23% last_trade_price 54,876 0.05% tick_size_change 5,664 <0.01% market_resolved 1,842 <0.01% new_market 1,050 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,802,638 11,802,408 230 4,440 FULL book 2,556,704 2,556,684 20 176,870 FULL last_trade_price 54,876 54,876 0 655 FULL market_resolved 1,842 1,842 0 17 FULL new_market 1,050 1,050 0 0 FULL price_change 100,455,478 100,454,030 1,448 2,854 FULL tick_size_change 5,664 5,664 0 338 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,279,796 8,020,993 5ms 10ms 57ms 1.9s 0 transport_latency_assumed best_bid_ask e 11,800,656 93,181 40ms 46ms 114ms 2.7s 0 transport_latency_assumed best_bid_ask f 11,800,846 20,345 47ms 52ms 132ms 2.1s 0 transport_latency_assumed best_bid_ask g 11,799,088 1,479 80ms 96ms 238ms 14.4s 0 transport_latency_assumed best_bid_ask h 11,801,626 3,666,410 18ms 23ms 76ms 9.9s 0 transport_latency_assumed book c 2,513,970 2,506,273 30.9min 1.8d 35.8d 106.6d 0 book_staleness book e 114,939 2,997 42ms 95ms 1.5min 88.1d 0 book_staleness book f 114,425 1,054 50ms 107ms 2.4s 87.9d 0 book_staleness book g 135,730 9,408 86ms 6.7min 6.1d 106.6d 0 book_staleness book h 114,029 36,952 21ms 41ms 457ms 36.1d 0 book_staleness last_trade_price c 37,788 36,003 11ms 42ms 187ms 5.0s 0 transport_latency_assumed last_trade_price e 54,758 621 48ms 101ms 568ms 5.0s 0 transport_latency_assumed last_trade_price f 54,776 150 54ms 113ms 705ms 5.0s 0 transport_latency_assumed last_trade_price g 54,676 45 90ms 195ms 826ms 5.0s 0 transport_latency_assumed last_trade_price h 54,819 18,057 23ms 57ms 227ms 6.1s 0 transport_latency_assumed market_resolved c 1,542 1,520 12ms 16.5min 21.7min 22.7min 0 transport_latency_assumed market_resolved e 1,098 32 41ms 121ms 59.2s 1.0min 0 transport_latency_assumed market_resolved f 1,098 2 48ms 127ms 59.2s 1.0min 0 transport_latency_assumed market_resolved g 1,098 1 85ms 235ms 547ms 1.5s 0 transport_latency_assumed market_resolved h 1,098 287 19ms 45ms 125ms 1.0min 0 transport_latency_assumed new_market c 876 683 1.7min 12.3min 16.8min 16.9min 0 transport_latency_assumed new_market e 443 72 148ms 15.6s 26.0s 1.6min 0 transport_latency_assumed new_market f 443 56 168ms 17.3s 28.2s 58.2s 0 transport_latency_assumed new_market g 443 61 256ms 18.7s 28.1s 58.7s 0 transport_latency_assumed new_market h 443 178 86ms 11.3s 23.1s 55.9s 0 transport_latency_assumed price_change c 71,062,711 68,643,151 5ms 11ms 72ms 2.4s 0 transport_latency_assumed price_change e 100,417,230 856,834 41ms 47ms 161ms 4.9s 0 transport_latency_assumed price_change f 100,434,428 204,138 47ms 55ms 184ms 4.9s 0 transport_latency_assumed price_change g 100,387,686 20,264 81ms 100ms 317ms 14.4s 0 transport_latency_assumed price_change h 100,437,924 30,729,643 18ms 24ms 96ms 10.3s 0 transport_latency_assumed tick_size_change c 4,312 4,212 5ms 9ms 38ms 350ms 0 transport_latency_assumed tick_size_change e 5,664 76 40ms 46ms 83ms 343ms 0 transport_latency_assumed tick_size_change f 5,664 4 47ms 51ms 97ms 261ms 0 transport_latency_assumed tick_size_change g 5,664 not meas. 81ms 95ms 146ms 408ms 0 transport_latency_assumed tick_size_change h 5,664 1,372 18ms 22ms 64ms 249ms 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/12/2026-09-13T12.parquet sha256sum 2026-09-13T12.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.