Hour audit: 2026-09-02T23
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-02T23 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-02T23:00:00.033538103+00:00 · last event 2026-09-02T23:59:59.999972557+00:00
VOLUME 102,922,620 rows · 1,042,918,492 bytes (994.60 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured h: 102,467,516 · c: 102,446,232 · e: 102,159,727 · b: 97,943,427 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 335,020 (0.33%) · c: 17,284 (0.02%) · e: 102,158,526 (99.26%) · b: 411,790 (0.40%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 102,922,620 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 c22b265e71f18badff342fd91a8a92d077281a19d710b6931439cedc3bea252b
the corpus checksum ledger names this file with the same digest
joined 102,924,193 to merged 102,922,620, minus 1,573 (minus 0.0015%)
boundary drops 1,573 · 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-03T00:54:14Z as bceh
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,830,654 129,410,063 0-45 9df7df59428b2fbe3383a887ca72877bdb3933c2cafc5192eb2bd131569222b8 book 522,567 53,394,829 46-47 062ad6f7a42369fff1ca1fa6d2bcead06214d06e3a00f7019a04e24e9cbd448e last_trade_price 49,679 2,846,791 48-48 f5c8487210e1a2b444bb6d73eecb1dec75296b566e7dfcf9204d01d884aa945c market_resolved 1,436 209,047 49-49 8c3960acf08cc663fb724b1bb2bf6f100b6d3f9c27b2d8d79d585fa83ab7fb7c new_market 1,826 189,274 50-50 c1a28ab6703d194cc2ee1591fcc352afbfad8b5a24c0e83dd4f4709489bbf437 price_change 90,513,018 855,568,630 51-396 8e8ca36a54bc06db560b1e9ff4bcdf425d3e7d41edd6ea48ff5500615e64a8e6 tick_size_change 3,440 126,667 397-397 d12bc2d4435af5d9d69d5d9ce9af513a12f872bdf9ed9eee504fcdd687d5d928 EVENT MIX count share price_change 90,513,018 87.94% best_bid_ask 11,830,654 11.49% book 522,567 0.51% last_trade_price 49,679 0.05% tick_size_change 3,440 <0.01% new_market 1,826 <0.01% market_resolved 1,436 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,830,812 11,830,654 158 717 FULL book 522,569 522,567 2 188,596 FULL last_trade_price 49,680 49,679 1 74 FULL market_resolved 1,436 1,436 0 10 FULL new_market 1,826 1,826 0 0 FULL price_change 90,514,430 90,513,018 1,412 574 FULL tick_size_change 3,440 3,440 0 98 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 11,294,035 420 56ms 95ms 570ms 22.5s 0 transport_latency_assumed best_bid_ask c 11,828,131 2,184 5ms 10ms 121ms 2.9s 0 transport_latency_assumed best_bid_ask e 11,812,682 11,812,566 41ms 105ms 761ms 21.3s 0 transport_latency_assumed best_bid_ask h 11,823,710 15,484 18ms 30ms 229ms 39.0s 0 transport_latency_assumed book b 488,166 369,062 2.3min 5.3h 30.1d 96.0d 0 book_staleness book c 111,683 8,050 7ms 225ms 5.2h 77.6d 0 book_staleness book e 107,451 107,451 96ms 8.6s 4.0h 6.2d 0 book_staleness book h 137,478 38,004 45ms 43.9min 11.4d 96.0d 0 book_staleness last_trade_price b 45,523 1 88ms 3.0s 15.8s 22.7s 0 transport_latency_assumed last_trade_price c 49,648 5 10ms 39ms 223ms 4.2s 0 transport_latency_assumed last_trade_price e 47,770 47,769 81ms 4.1s 13.0s 22.6s 0 transport_latency_assumed last_trade_price h 49,660 1,904 27ms 403ms 1.8s 27.7s 0 transport_latency_assumed market_resolved b 1,303 115 62ms 627ms 4.5min 4.5min 0 transport_latency_assumed market_resolved c 1,313 4 4ms 10ms 57.6s 1.0min 0 transport_latency_assumed market_resolved e 1,313 1,313 43ms 217ms 5.0s 1.0min 0 transport_latency_assumed market_resolved h 1,313 4 19ms 82ms 49.1s 1.0min 0 transport_latency_assumed new_market b 1,227 150 228ms 31.8s 1.9min 22.1min 0 transport_latency_assumed new_market c 1,227 203 70ms 23.6s 1.9min 46.0min 0 transport_latency_assumed new_market e 1,227 1,227 177ms 21.6s 1.8min 27.5min 0 transport_latency_assumed new_market h 1,227 246 121ms 21.4s 1.8min 12.5min 0 transport_latency_assumed price_change b 86,110,125 42,042 56ms 110ms 1.9s 22.7s 0 transport_latency_assumed price_change c 90,450,790 6,838 5ms 8ms 133ms 3.3s 0 transport_latency_assumed price_change e 90,185,844 90,184,760 42ms 119ms 3.0s 22.8s 0 transport_latency_assumed price_change h 90,450,688 279,378 18ms 29ms 305ms 39.2s 0 transport_latency_assumed tick_size_change b 3,048 not meas. 56ms 82ms 271ms 1.5s 0 transport_latency_assumed tick_size_change c 3,440 not meas. 5ms 8ms 30ms 224ms 0 transport_latency_assumed tick_size_change e 3,440 3,440 42ms 111ms 204ms 2.6s 0 transport_latency_assumed tick_size_change h 3,440 not meas. 18ms 34ms 77ms 1.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-02/23/2026-09-02T23.parquet sha256sum 2026-09-02T23.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.