Hour audit: 2026-09-21T21
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.
1 finding
- a machine expected this hour contributed nothing. Of the 5 machines expected to be capturing this hour, 1 contributed no rows: g. The hour is still whole on minutes; it simply rests on 4 machines rather than 5.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-21T21 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-21T21:00:00.000039412+00:00 · last event 2026-09-21T21:59:59.999991073+00:00
VOLUME 101,461,949 rows · 1,054,302,344 bytes (1005.46 MiB) · 7 products, all holding rows
WITNESSES cefh — 4 machines contributed rows
captured h: 100,494,084 · f: 100,239,885 · e: 100,102,108 · c: 93,493,159 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 11,856,865 (11.69%) · f: 283,513 (0.28%) · e: 434,103 (0.43%) · c: 88,887,468 (87.61%) (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 101,461,949 rows exactly, so those pairs supplied none
5 expected (cefgh), 1 contributed nothing: g
INTEGRITY sha256 a979ed478de959220047b067646bec4732028b28539d7e5033afa43fdb7ef2de
the corpus checksum ledger names this file with the same digest
joined 101,491,153 to merged 101,461,949, minus 29,204 (minus 0.0288%)
boundary drops 29,204 · 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-21T23:09:52Z as cefh
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 7/8 pass, 1 finding
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
FINDING a machine expected this hour contributed nothing
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,117,748 115,240,208 0-38 df05d488e3b099d2e1f30637ed7bded6cb27294a48a2723857f8ca2527e795d7 book 988,679 63,098,399 39-42 fb60e9e9e64378b83b9c31063347fc698e28fe1adf1e145c65edfcbbd4c5421f last_trade_price 50,087 2,856,518 43-43 e1eb00ef323a88dd196b3a1d8db56476c468e77d88cff66c4ccf52affe853da5 market_resolved 567 85,732 44-44 422e796c1d9cf2821ec492549bccd4dffd496c876fcbb8b1442602d5b3b2cc1b new_market 1,904 190,400 45-45 97077319b95d6258356078dc547be9586e0b94609968e415abc03ffcc07877f5 price_change 90,300,484 871,584,170 46-390 6044a4d99760fe801b8dfb0c12b19089219c77c194bcacc66039e42a2b2f7379 tick_size_change 2,480 91,768 391-391 e8b5fab46b5786c3a94cd35fd0b07675c85f7046a83e0eec25c92cd20aa6c285 EVENT MIX count share price_change 90,300,484 89.00% best_bid_ask 10,117,748 9.97% book 988,679 0.97% last_trade_price 50,087 0.05% tick_size_change 2,480 <0.01% new_market 1,904 <0.01% market_resolved 567 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,117,872 10,117,748 124 79,660 PARTIAL book 989,337 988,679 658 177,131 PARTIAL last_trade_price 50,087 50,087 0 3,244 PARTIAL market_resolved 567 567 0 489 PARTIAL new_market 1,904 1,904 0 1,250 PARTIAL price_change 90,328,906 90,300,484 28,422 130,539 PARTIAL tick_size_change 2,480 2,480 0 620 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,355,273 8,923,278 5ms 12ms 130ms 33.0s 0 transport_latency_assumed best_bid_ask e 10,108,098 39,511 43ms 52ms 277ms 22.0s 0 transport_latency_assumed best_bid_ask f 10,113,340 22,233 47ms 58ms 239ms 18.0s 0 transport_latency_assumed best_bid_ask h 10,112,086 1,132,726 18ms 24ms 158ms 34.5s 0 transport_latency_assumed book c 911,523 861,141 7.7min 3.2d 41.1d 115.0d 0 book_staleness book e 111,398 8,363 47ms 5.3s 3.2d 96.5d 0 book_staleness book f 111,065 7,257 51ms 3.3s 3.2d 96.5d 0 book_staleness book h 224,172 111,918 8.1s 4.7h 30.3d 115.0d 0 book_staleness last_trade_price c 46,341 43,949 6ms 19ms 198ms 1.3s 0 transport_latency_assumed last_trade_price e 49,292 254 46ms 497ms 6.2s 21.9s 0 transport_latency_assumed last_trade_price f 49,539 276 50ms 264ms 5.7s 18.0s 0 transport_latency_assumed last_trade_price h 49,655 5,608 19ms 61ms 409ms 8.8s 0 transport_latency_assumed market_resolved c 498 463 6ms 3.4min 4.8min 5.2min 0 transport_latency_assumed market_resolved e 489 22 46ms 371ms 54.1s 1.0min 0 transport_latency_assumed market_resolved f 489 1 51ms 474ms 56.5s 59.4s 0 transport_latency_assumed market_resolved h 489 81 19ms 141ms 58.1s 58.8s 0 transport_latency_assumed new_market c 1,250 631 237ms 2.2h 2.2h 2.2h 0 transport_latency_assumed new_market e 1,250 398 269ms 2.2h 2.2h 2.2h 0 transport_latency_assumed new_market f 1,250 244 280ms 2.2h 2.2h 2.2h 0 transport_latency_assumed new_market h 1,250 631 180ms 2.2h 2.2h 2.2h 0 transport_latency_assumed price_change c 83,175,978 79,055,797 5ms 14ms 150ms 34.2s 0 transport_latency_assumed price_change e 89,829,105 385,555 43ms 72ms 1.6s 22.0s 0 transport_latency_assumed price_change f 89,961,722 253,498 48ms 72ms 959ms 18.0s 0 transport_latency_assumed price_change h 90,103,956 10,605,634 18ms 30ms 262ms 35.4s 0 transport_latency_assumed tick_size_change c 2,296 2,209 5ms 11ms 60ms 164ms 0 transport_latency_assumed tick_size_change e 2,476 not meas. 43ms 54ms 194ms 934ms 0 transport_latency_assumed tick_size_change f 2,480 4 48ms 62ms 238ms 433ms 0 transport_latency_assumed tick_size_change h 2,476 267 18ms 25ms 63ms 9.1s 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-21/21/2026-09-21T21.parquet sha256sum 2026-09-21T21.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.