Hour audit: 2026-09-04T23
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-04T23 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-04T23:00:00.030557659+00:00 · last event 2026-09-04T23:59:59.999977313+00:00
VOLUME 101,934,411 rows · 1,068,104,375 bytes (1018.62 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured h: 101,395,797 · c: 101,390,936 · e: 101,373,724 · b: 101,319,665 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 263,010 (0.26%) · c: 174,022 (0.17%) · e: 101,372,711 (99.45%) · b: 124,668 (0.12%) (rows of the merged file that came from it; these partition it)
6 product-machine pairs publish no supplied count; the figures above still sum to the file's 101,934,411 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 8eaa616472b298301734e94f3e59cbf60046d3faadf301bb2ca31f7cd294950b
the corpus checksum ledger names this file with the same digest
joined 101,935,859 to merged 101,934,411, minus 1,448 (minus 0.0014%)
boundary drops 1,448 · 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-05T00:53:54Z 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,714,714 126,820,975 0-44 498c5e70e55ca10b030fb39ee5b1f86b74c5b5533e77117fc3d9daed1c4bcdd9 book 923,413 69,284,239 45-48 c6592131decbb9220f0f74aa99aa8b1953553a18f4ee94ae00e38747dd02982e last_trade_price 45,822 2,675,076 49-49 123e82cf1dcccd1f57323ff1f11174cf07f4b7ac6bca315caf1490a975863508 market_resolved 970 156,869 50-50 146eba057c3433c8401e97b0e4ebdf1a4408e90cb183d3237baa2308a9e974b3 new_market 1,866 204,370 51-51 cd597779bd07719daf8166b93d5cd44f3a14bfd932a9e530f2a700050264d9db price_change 89,244,790 867,699,775 52-392 1c6b55897c5daf6e9209bd11f6227efc74fd16429d5f47d087faeab1e5db499c tick_size_change 2,836 101,944 393-393 7d017f4e0c586c0f6ebb8fd3ab9a9a611a36dcfbfc3b6312301bcd213c45e07a EVENT MIX count share price_change 89,244,790 87.55% best_bid_ask 11,714,714 11.49% book 923,413 0.91% last_trade_price 45,822 0.04% tick_size_change 2,836 <0.01% new_market 1,866 <0.01% market_resolved 970 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,714,898 11,714,714 184 104 FULL book 923,434 923,413 21 130,049 FULL last_trade_price 45,823 45,822 1 3 FULL market_resolved 970 970 0 1 FULL new_market 1,866 1,866 0 0 FULL price_change 89,246,032 89,244,790 1,242 212 FULL tick_size_change 2,836 2,836 0 1 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 11,710,527 48 54ms 68ms 236ms 3.7s 0 transport_latency_assumed best_bid_ask c 11,713,108 428 5ms 8ms 67ms 4.5s 0 transport_latency_assumed best_bid_ask e 11,710,628 11,710,496 38ms 46ms 228ms 4.9s 0 transport_latency_assumed best_bid_ask h 11,711,890 3,742 17ms 21ms 139ms 13.7s 0 transport_latency_assumed book b 354,216 120,158 1.4min 5.2h 27.6d 98.1d 0 book_staleness book c 426,976 166,230 1.7min 5.9h 29.3d 98.1d 0 book_staleness book e 429,594 429,576 1.8min 6.4h 33.4d 98.1d 0 book_staleness book h 424,396 207,449 1.7min 5.8h 29.0d 98.1d 0 book_staleness last_trade_price b 45,776 4 62ms 150ms 1.0s 5.0s 0 transport_latency_assumed last_trade_price c 45,776 2 10ms 38ms 221ms 4.9s 0 transport_latency_assumed last_trade_price e 45,794 45,793 44ms 158ms 2.6s 5.1s 0 transport_latency_assumed last_trade_price h 45,802 23 22ms 55ms 384ms 6.8s 0 transport_latency_assumed market_resolved b 970 not meas. 55ms 223ms 638ms 798ms 0 transport_latency_assumed market_resolved c 970 not meas. 5ms 9ms 30ms 86ms 0 transport_latency_assumed market_resolved e 970 970 38ms 187ms 611ms 788ms 0 transport_latency_assumed market_resolved h 969 not meas. 18ms 64ms 179ms 295ms 0 transport_latency_assumed new_market b 1,346 72 157ms 13.3s 2.7min 26.3min 0 transport_latency_assumed new_market c 1,346 130 65ms 16.9s 2.7min 6.1min 0 transport_latency_assumed new_market e 1,346 1,346 133ms 30.4s 3.0min 8.1min 0 transport_latency_assumed new_market h 1,346 318 82ms 14.5s 2.8min 3.7min 0 transport_latency_assumed price_change b 89,203,994 4,386 55ms 73ms 285ms 3.8s 0 transport_latency_assumed price_change c 89,199,928 7,232 5ms 9ms 81ms 4.6s 0 transport_latency_assumed price_change e 89,182,556 89,181,694 38ms 53ms 295ms 4.9s 0 transport_latency_assumed price_change h 89,208,558 51,478 18ms 22ms 160ms 13.9s 0 transport_latency_assumed tick_size_change b 2,836 not meas. 54ms 65ms 82ms 135ms 0 transport_latency_assumed tick_size_change c 2,832 not meas. 5ms 7ms 17ms 58ms 0 transport_latency_assumed tick_size_change e 2,836 2,836 37ms 41ms 113ms 124ms 0 transport_latency_assumed tick_size_change h 2,836 not meas. 17ms 20ms 40ms 352ms 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-04/23/2026-09-04T23.parquet sha256sum 2026-09-04T23.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.