Hour audit: 2026-09-18T19
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-18T19 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-18T19:00:00.000704724+00:00 · last event 2026-09-18T19:59:59.999950372+00:00
VOLUME 116,598,430 rows · 1,310,385,925 bytes (1.22 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 114,482,346 · e: 114,353,349 · f: 114,284,348 · g: 113,682,075 · c: 96,056,473 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 24,382,031 (20.91%) · e: 1,874,557 (1.61%) · f: 723,271 (0.62%) · g: 84,900 (0.07%) · c: 89,533,671 (76.79%) (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,598,430 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 6468ff1c8ba913def3ad124990a541f905b1f409633e18b02c76b7e05bf1b584
the corpus checksum ledger names this file with the same digest
joined 116,600,476 to merged 116,598,430, minus 2,046 (minus 0.0018%)
boundary drops 2,046 · 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-18T22:09:14Z 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,246,952 133,185,830 0-42 2bd86e30c9e8efa4457e8ae44edc2d914967ce723e4150864051179abf6379c5 book 1,936,904 89,452,369 43-50 56a09b85d26e037a813b012c4652a8dbcb51ff9d9368539047874fd546a9d825 last_trade_price 63,927 3,736,178 51-51 b7bebbd4353ba36ed424c1028db471e647eafe9bbe1582c6aae5f5914f592632 market_resolved 1,386 175,755 52-52 cb232998ea5e63bff7ac6a3ba5cc7e22387ef66581ab8248c7db7d0b47c5fe99 new_market 2,683 278,250 53-53 0f3048863d017a4fc32872211d0cb03bad2da44a8b953c17fbdc36370ea6c7d3 price_change 103,338,418 1,081,929,648 54-448 4a2497b45f93594c71b566d66a7937c186ecdf166fc77f3a8615e104d8aef7b4 tick_size_change 8,160 300,314 449-449 e3bfffcb15d91056f75dbbbd7b6da4528fba9d291cb986e77d389ed182d2eb9f EVENT MIX count share price_change 103,338,418 88.63% best_bid_ask 11,246,952 9.65% book 1,936,904 1.66% last_trade_price 63,927 0.05% tick_size_change 8,160 <0.01% new_market 2,683 <0.01% market_resolved 1,386 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,247,166 11,246,952 214 3,958 FULL book 1,936,940 1,936,904 36 211,341 FULL last_trade_price 63,927 63,927 0 412 FULL market_resolved 1,386 1,386 0 97 FULL new_market 2,683 2,683 0 32 FULL price_change 103,340,214 103,338,418 1,796 3,103 FULL tick_size_change 8,160 8,160 0 407 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,157,783 8,542,793 6ms 18ms 214ms 10.6s 0 transport_latency_assumed best_bid_ask e 11,239,622 186,094 41ms 65ms 375ms 19.2s 0 transport_latency_assumed best_bid_ask f 11,238,438 65,543 47ms 73ms 431ms 22.7s 0 transport_latency_assumed best_bid_ask g 11,234,210 5,863 81ms 127ms 788ms 26.8s 0 transport_latency_assumed best_bid_ask h 11,236,052 2,446,659 19ms 36ms 387ms 1.6min 0 transport_latency_assumed book c 1,866,143 1,832,425 17.1min 4.3h 37.0d 111.9d 0 book_staleness book e 231,896 31,022 716ms 4.0h 24.0d 111.9d 0 book_staleness book f 231,474 29,148 780ms 4.0h 20.5d 111.9d 0 book_staleness book g 146,510 8,922 94ms 26.1s 5.6h 93.4d 0 book_staleness book h 143,459 35,387 24ms 350ms 3.5h 93.4d 0 book_staleness last_trade_price c 53,342 49,347 12ms 59ms 494ms 5.1s 0 transport_latency_assumed last_trade_price e 62,420 812 62ms 1.1s 9.7s 18.5s 0 transport_latency_assumed last_trade_price f 62,194 424 69ms 1.1s 12.1s 22.8s 0 transport_latency_assumed last_trade_price g 61,069 71 103ms 1.9s 13.8s 26.7s 0 transport_latency_assumed last_trade_price h 63,445 13,273 27ms 124ms 795ms 16.1s 0 transport_latency_assumed market_resolved c 1,190 1,128 8ms 7.0min 9.8min 12.4min 0 transport_latency_assumed market_resolved e 1,057 9 44ms 201ms 527ms 3.9s 0 transport_latency_assumed market_resolved f 1,058 1 50ms 208ms 524ms 814ms 0 transport_latency_assumed market_resolved g 1,058 1 90ms 367ms 853ms 1.1s 0 transport_latency_assumed market_resolved h 1,058 247 21ms 77ms 197ms 2.1s 0 transport_latency_assumed new_market c 1,934 1,264 108ms 4.4min 6.2min 8.0min 0 transport_latency_assumed new_market e 1,758 340 226ms 15.2s 41.8s 1.8min 0 transport_latency_assumed new_market f 1,758 279 248ms 14.8s 46.9s 1.2min 0 transport_latency_assumed new_market g 1,758 201 361ms 14.2s 47.7s 1.4min 0 transport_latency_assumed new_market h 1,758 599 177ms 14.5s 43.9s 1.2min 0 transport_latency_assumed price_change c 84,969,549 79,100,885 6ms 20ms 228ms 10.7s 0 transport_latency_assumed price_change e 102,808,436 1,656,152 41ms 106ms 3.1s 19.2s 0 transport_latency_assumed price_change f 102,741,266 627,847 48ms 117ms 3.7s 22.8s 0 transport_latency_assumed price_change g 102,229,310 69,842 82ms 218ms 6.9s 27.0s 0 transport_latency_assumed price_change h 103,028,414 21,883,692 19ms 44ms 491ms 1.6min 0 transport_latency_assumed tick_size_change c 6,532 5,829 6ms 27ms 153ms 527ms 0 transport_latency_assumed tick_size_change e 8,160 128 41ms 61ms 188ms 556ms 0 transport_latency_assumed tick_size_change f 8,160 29 47ms 62ms 208ms 1.9s 0 transport_latency_assumed tick_size_change g 8,160 not meas. 81ms 104ms 421ms 872ms 0 transport_latency_assumed tick_size_change h 8,160 2,174 19ms 36ms 239ms 5.6s 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/19/2026-09-18T19.parquet sha256sum 2026-09-18T19.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.