Hour audit: 2026-09-14T18
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-14T18 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-14T18:00:00.000150628+00:00 · last event 2026-09-14T18:59:59.999929981+00:00
VOLUME 124,405,606 rows · 1,357,192,420 bytes (1.26 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 121,984,354 · f: 121,955,256 · e: 121,676,079 · g: 117,570,112 · c: 91,790,192 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 35,243,535 (28.33%) · f: 915,717 (0.74%) · e: 1,546,982 (1.24%) · g: 177,453 (0.14%) · c: 86,521,919 (69.55%) (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,405,606 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 9900da522d0522daf80c4f9c539f05557130c6a0e5daf1ab702aed5931016830
the corpus checksum ledger names this file with the same digest
joined 124,406,914 to merged 124,405,606, minus 1,308 (minus 0.0011%)
boundary drops 1,308 · 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-14T20:00:42Z 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,367,815 131,003,148 0-43 015dd15854a6c7eb6ad2032efeb590479ecedf1cc6f144f9ae3770933a83aac0 book 2,457,357 101,332,514 44-53 d85898b12a52911796a9fbf23ee158643f0dd634d69e5baa99a5b00c2494cdeb last_trade_price 64,209 3,713,051 54-54 d5ef13093606e3c8e48d0bc091ac9462908d25f986fa04439e7124adad0536cb market_resolved 1,771 180,248 55-55 5f9ee5690ee061d2c1e790878d43af927d2af9f430dd00d6c1bb1c63a1472c72 new_market 2,848 235,661 56-56 21238434dc1da15afc656dfa8eedc76102c1de20cb343398427f5df5c255bd89 price_change 110,506,266 1,119,117,834 57-478 870f5ea16e9d238eaf17bdbe181104fc20641a3470ede23ffaa0ae53a3fbe860 tick_size_change 5,340 193,968 479-479 bdc2decdcc225740824eaad4022fb9359cd6bfe1826a9ccfe251725b46ce7082 EVENT MIX count share price_change 110,506,266 88.83% best_bid_ask 11,367,815 9.14% book 2,457,357 1.98% last_trade_price 64,209 0.05% tick_size_change 5,340 <0.01% new_market 2,848 <0.01% market_resolved 1,771 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,367,921 11,367,815 106 4,273 FULL book 2,457,415 2,457,357 58 166,714 FULL last_trade_price 64,209 64,209 0 704 FULL market_resolved 1,771 1,771 0 133 FULL new_market 2,848 2,848 0 0 FULL price_change 110,507,410 110,506,266 1,144 3,057 FULL tick_size_change 5,340 5,340 0 415 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,292,411 7,826,311 6ms 16ms 157ms 6.0s 0 transport_latency_assumed best_bid_ask e 11,351,284 140,307 47ms 64ms 333ms 19.5s 0 transport_latency_assumed best_bid_ask f 11,363,346 80,643 49ms 68ms 302ms 13.6s 0 transport_latency_assumed best_bid_ask g 10,941,890 2,926 89ms 177ms 735ms 41.6s 0 transport_latency_assumed best_bid_ask h 11,365,318 3,317,628 19ms 35ms 253ms 37.1s 0 transport_latency_assumed book c 2,342,053 2,267,702 26.5min 3.0d 37.2d 107.9d 0 book_staleness book e 139,206 7,220 55ms 813ms 10.0h 89.3d 0 book_staleness book f 137,973 4,009 52ms 385ms 8.3h 89.3d 0 book_staleness book g 497,237 135,540 3.5min 1.4d 33.1d 107.8d 0 book_staleness book h 138,173 42,886 23ms 117ms 2.7h 89.2d 0 book_staleness last_trade_price c 45,876 43,036 12ms 55ms 295ms 4.8s 0 transport_latency_assumed last_trade_price e 63,054 858 63ms 272ms 4.9s 19.5s 0 transport_latency_assumed last_trade_price f 63,542 653 62ms 224ms 3.6s 13.5s 0 transport_latency_assumed last_trade_price g 60,465 40 112ms 507ms 6.9s 24.2s 0 transport_latency_assumed last_trade_price h 63,842 19,622 26ms 93ms 571ms 9.4s 0 transport_latency_assumed market_resolved c 1,338 1,249 57.3s 13.9min 19.7min 19.7min 0 transport_latency_assumed market_resolved e 1,057 37 56ms 329ms 58.1s 1.0min 0 transport_latency_assumed market_resolved f 1,057 38 50ms 212ms 623ms 987ms 0 transport_latency_assumed market_resolved g 1,057 34 123ms 571ms 3.9min 3.9min 0 transport_latency_assumed market_resolved h 1,057 413 22ms 115ms 58.2s 1.0min 0 transport_latency_assumed new_market c 2,000 1,463 502ms 10.5min 15.9min 16.8min 0 transport_latency_assumed new_market e 1,456 307 226ms 14.5s 29.5s 1.2min 0 transport_latency_assumed new_market f 1,456 222 244ms 14.5s 25.6s 1.2min 0 transport_latency_assumed new_market g 1,456 162 431ms 16.3s 27.0s 1.2min 0 transport_latency_assumed new_market h 1,456 694 149ms 13.8s 24.6s 1.1min 0 transport_latency_assumed price_change c 81,102,834 76,378,610 6ms 17ms 170ms 6.0s 0 transport_latency_assumed price_change e 110,114,682 1,398,232 48ms 76ms 774ms 19.6s 0 transport_latency_assumed price_change f 110,382,542 830,124 49ms 80ms 484ms 13.6s 0 transport_latency_assumed price_change g 106,063,035 38,751 89ms 212ms 1.6s 42.8s 0 transport_latency_assumed price_change h 110,409,168 31,860,549 19ms 39ms 283ms 37.2s 0 transport_latency_assumed tick_size_change c 3,680 3,548 5ms 11ms 62ms 288ms 0 transport_latency_assumed tick_size_change e 5,340 21 45ms 60ms 139ms 3.3s 0 transport_latency_assumed tick_size_change f 5,340 28 48ms 63ms 199ms 3.5s 0 transport_latency_assumed tick_size_change g 4,972 not meas. 92ms 179ms 519ms 2.3s 0 transport_latency_assumed tick_size_change h 5,340 1,743 18ms 28ms 97ms 920ms 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-14/18/2026-09-14T18.parquet sha256sum 2026-09-14T18.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.