Hour audit: 2026-09-18T10
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-18T10 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-18T10:00:00.000016008+00:00 · last event 2026-09-18T10:59:59.999917630+00:00
VOLUME 112,281,820 rows · 1,211,446,262 bytes (1.13 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured g: 111,565,218 · h: 111,488,226 · c: 111,484,830 · e: 111,327,553 · f: 107,073,630 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 418,478 (0.37%) · h: 5,723,294 (5.10%) · c: 104,096,570 (92.71%) · e: 1,073,742 (0.96%) · f: 969,736 (0.86%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 112,281,820 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 b2476ed369f3ca6df6ff3ce2ad1b8861e2e2441f83b29dfa512edfef29915ab0
the corpus checksum ledger names this file with the same digest
joined 112,283,830 to merged 112,281,820, minus 2,010 (minus 0.0018%)
boundary drops 2,010 · 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-18T12:00:06Z 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 10,421,968 125,877,790 0-39 fe20656fddede44ccbfd66f659de4bd05bbcccd9b507dcdf35252fa95c063447 book 825,930 68,829,113 40-43 56c8764c3857d2a39d6eb4131a8a03ab0d932c7c92360858f74d06728672dfa6 last_trade_price 52,570 3,100,600 44-44 12b9389e97a2750dd40c64524e39b47e2d5aa37f6387e852ce8a85265c9d90ca market_resolved 564 83,036 45-45 7a83d24860d3ed617c4466d85b884da205989f873c7f884962c47008d6865738 new_market 5,100 513,329 46-46 8eb56a280658a343cea6f5ecb53fc1b550c26b40612afb7bd4c066c60d41f3a2 price_change 100,972,364 1,011,641,908 47-432 401d836b3cff29642971e059e64e4748f9081893f6eecaa519e1f10ae4dc1372 tick_size_change 3,324 120,332 433-433 da5d2574d8581e2577e9e90e806290231d6df97b39528ed1fc9cd5665c1c7123 EVENT MIX count share price_change 100,972,364 89.93% best_bid_ask 10,421,968 9.28% book 825,930 0.74% last_trade_price 52,570 0.05% new_market 5,100 <0.01% tick_size_change 3,324 <0.01% market_resolved 564 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,422,118 10,421,968 150 1,604 FULL book 825,988 825,930 58 192,156 FULL last_trade_price 52,570 52,570 0 82 FULL market_resolved 564 564 0 17 FULL new_market 5,100 5,100 0 0 FULL price_change 100,974,166 100,972,364 1,802 644 FULL tick_size_change 3,324 3,324 0 47 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,416,893 9,758,773 5ms 17ms 247ms 13.5s 0 transport_latency_assumed best_bid_ask e 10,412,104 97,800 41ms 57ms 342ms 34.4s 0 transport_latency_assumed best_bid_ask f 9,990,897 47,498 48ms 71ms 386ms 18.3s 0 transport_latency_assumed best_bid_ask g 10,406,958 10,811 79ms 113ms 557ms 35.4s 0 transport_latency_assumed best_bid_ask h 10,415,015 507,086 18ms 36ms 546ms 1.0min 0 transport_latency_assumed book c 115,684 105,362 8ms 101ms 22.9s 93.0d 0 book_staleness book e 117,176 6,798 44ms 595ms 12.1min 93.0d 0 book_staleness book f 580,159 404,081 2.1min 6.0h 33.9d 111.5d 0 book_staleness book g 484,517 299,438 1.7min 5.6h 32.6d 111.5d 0 book_staleness book h 117,125 10,251 23ms 270ms 4.7min 93.0d 0 book_staleness last_trade_price c 52,392 48,784 11ms 60ms 371ms 5.0s 0 transport_latency_assumed last_trade_price e 51,951 648 52ms 269ms 5.0s 33.5s 0 transport_latency_assumed last_trade_price f 49,882 327 62ms 362ms 5.5s 18.5s 0 transport_latency_assumed last_trade_price g 51,449 94 93ms 509ms 14.1s 35.2s 0 transport_latency_assumed last_trade_price h 52,430 2,717 25ms 131ms 1.1s 1.0min 0 transport_latency_assumed market_resolved c 502 475 5ms 21ms 216ms 449ms 0 transport_latency_assumed market_resolved e 502 18 42ms 466ms 1.0min 1.0min 0 transport_latency_assumed market_resolved f 516 47 49ms 819ms 6.1min 6.1min 0 transport_latency_assumed market_resolved g 502 not meas. 83ms 350ms 989ms 1.7s 0 transport_latency_assumed market_resolved h 502 24 19ms 154ms 1.0min 1.0min 0 transport_latency_assumed new_market c 3,307 2,103 102ms 24.4s 48.2s 1.4min 0 transport_latency_assumed new_market e 3,307 626 197ms 25.6s 43.0s 1.3min 0 transport_latency_assumed new_market f 3,307 885 158ms 25.1s 44.1s 4.7min 0 transport_latency_assumed new_market g 3,307 398 282ms 24.9s 41.0s 1.3min 0 transport_latency_assumed new_market h 3,307 1,088 166ms 24.2s 45.8s 1.1min 0 transport_latency_assumed price_change c 100,892,728 94,177,957 5ms 20ms 269ms 14.2s 0 transport_latency_assumed price_change e 100,739,189 967,838 41ms 79ms 827ms 34.5s 0 transport_latency_assumed price_change f 96,445,733 516,892 48ms 94ms 759ms 18.6s 0 transport_latency_assumed price_change g 100,615,161 107,737 80ms 153ms 1.7s 35.5s 0 transport_latency_assumed price_change h 100,896,523 5,201,940 18ms 44ms 631ms 1.1min 0 transport_latency_assumed tick_size_change c 3,324 3,116 5ms 12ms 122ms 318ms 0 transport_latency_assumed tick_size_change e 3,324 14 41ms 50ms 168ms 472ms 0 transport_latency_assumed tick_size_change f 3,136 6 47ms 55ms 196ms 405ms 0 transport_latency_assumed tick_size_change g 3,324 not meas. 79ms 100ms 307ms 734ms 0 transport_latency_assumed tick_size_change h 3,324 188 18ms 28ms 85ms 765ms 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-18/10/2026-09-18T10.parquet sha256sum 2026-09-18T10.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.