Hour audit: 2026-09-02T16
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-02T16 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-02T16:00:00.022781973+00:00 · last event 2026-09-02T16:59:59.999999711+00:00
VOLUME 114,710,820 rows · 1,208,088,103 bytes (1.13 GiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured h: 113,636,488 · c: 113,635,608 · e: 112,905,420 · b: 104,666,721 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 937,215 (0.82%) · c: 138,035 (0.12%) · e: 112,904,526 (98.43%) · b: 731,044 (0.64%) (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 114,710,820 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 3098e0d174275003044070e800c018794b663e3f0a6febeeb38e504f8f41e077
the corpus checksum ledger names this file with the same digest
joined 114,711,968 to merged 114,710,820, minus 1,148 (minus 0.0010%)
boundary drops 1,148 · 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-02T19:04:09Z 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 10,270,988 115,558,199 0-39 a129e42e02ff1cce1b13594d1b1da433f6ff0508f3f3ed422376fd3cde232fd7 book 1,418,346 85,020,534 40-45 b1d2266dc173b4b368e3075bd4d5e61bc8e11659ead165355f184266f621a289 last_trade_price 80,308 4,536,325 46-46 ee1a960a1f99d710413445372b553c84bf90d21f6cf42589f4fefded213e7917 market_resolved 1,693 233,087 47-47 9e597298c19f4aa164efc6b942f97af622ba6b1b14af0b9012b0303315c871e5 new_market 1,877 189,002 48-48 9eb36869d8ed3a7232f8bb2f75dc52e44dd86a4b59157ea6ed31d93936377b06 price_change 102,934,052 1,001,116,409 49-441 e4646e7f451a534096eeec653b5ed9a416bb776ca7a215044bd6a6e04db2b80f tick_size_change 3,556 127,974 442-442 df8a4c07d001546bae838eb785b340fdb8fc9dc42b3cc4900dec7c51b942bdc1 EVENT MIX count share price_change 102,934,052 89.73% best_bid_ask 10,270,988 8.95% book 1,418,346 1.24% last_trade_price 80,308 0.07% tick_size_change 3,556 <0.01% new_market 1,877 <0.01% market_resolved 1,693 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,271,090 10,270,988 102 1,018 FULL book 1,418,362 1,418,346 16 154,793 FULL last_trade_price 80,308 80,308 0 179 FULL market_resolved 1,693 1,693 0 25 FULL new_market 1,877 1,877 0 5 FULL price_change 102,935,082 102,934,052 1,030 224 FULL tick_size_change 3,556 3,556 0 46 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 9,379,976 32 52ms 77ms 421ms 16.9s 0 transport_latency_assumed best_bid_ask c 10,269,390 682 5ms 10ms 102ms 5.1s 0 transport_latency_assumed best_bid_ask e 10,253,767 10,253,691 42ms 87ms 775ms 25.3s 0 transport_latency_assumed best_bid_ask h 10,268,411 16,583 18ms 35ms 213ms 49.3s 0 transport_latency_assumed book b 1,041,647 730,366 2.2min 9.3h 31.2d 95.8d 0 book_staleness book c 361,194 128,431 6.7s 4.4h 25.1d 95.8d 0 book_staleness book e 388,608 388,604 18.3s 5.1h 25.1d 95.8d 0 book_staleness book h 378,276 170,945 11.6s 4.7h 25.1d 95.8d 0 book_staleness last_trade_price b 71,577 6 79ms 2.7s 12.5s 16.9s 0 transport_latency_assumed last_trade_price c 80,244 8 11ms 42ms 228ms 4.9s 0 transport_latency_assumed last_trade_price e 77,421 77,421 71ms 3.5s 12.3s 25.4s 0 transport_latency_assumed last_trade_price h 80,257 2,873 27ms 200ms 992ms 38.4s 0 transport_latency_assumed market_resolved b 1,613 261 60ms 5.9min 8.6min 9.9min 0 transport_latency_assumed market_resolved c 1,430 1 5ms 11ms 53.5s 56.3s 0 transport_latency_assumed market_resolved e 1,430 1,430 43ms 291ms 53.8s 1.5min 0 transport_latency_assumed market_resolved h 1,430 1 19ms 102ms 54.3s 57.1s 0 transport_latency_assumed new_market b 1,270 159 347ms 3.9min 7.3min 7.4min 0 transport_latency_assumed new_market c 1,208 265 92ms 18.3s 48.6s 2.2min 0 transport_latency_assumed new_market e 1,208 1,208 234ms 23.5s 54.8s 1.8min 0 transport_latency_assumed new_market h 1,208 245 152ms 23.1s 44.5s 1.7min 0 transport_latency_assumed price_change b 94,167,262 220 52ms 102ms 2.2s 16.9s 0 transport_latency_assumed price_change c 102,918,586 8,648 5ms 10ms 114ms 7.8s 0 transport_latency_assumed price_change e 102,179,430 102,178,616 42ms 130ms 4.5s 25.5s 0 transport_latency_assumed price_change h 102,903,354 746,568 19ms 40ms 303ms 49.4s 0 transport_latency_assumed tick_size_change b 3,376 not meas. 52ms 94ms 502ms 793ms 0 transport_latency_assumed tick_size_change c 3,556 not meas. 5ms 12ms 111ms 319ms 0 transport_latency_assumed tick_size_change e 3,556 3,556 42ms 109ms 377ms 2.0s 0 transport_latency_assumed tick_size_change h 3,552 not meas. 19ms 39ms 104ms 200ms 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/16/2026-09-02T16.parquet sha256sum 2026-09-02T16.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.