Hour audit: 2026-09-04T14
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-04T14 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-04T14:00:00.019873946+00:00 · last event 2026-09-04T14:59:59.999995047+00:00
VOLUME 110,440,839 rows · 1,132,559,936 bytes (1.05 GiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured h: 110,039,606 · c: 109,154,502 · e: 108,686,577 · b: 105,485,096 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 1,361,361 (1.23%) · c: 15,518 (0.01%) · e: 108,685,675 (98.41%) · b: 378,285 (0.34%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 110,440,839 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 3b2aa803c6a8e975b12f295f8ad5bf8676a3309a59df866e680c94b18289c253
the corpus checksum ledger names this file with the same digest
joined 110,441,953 to merged 110,440,839, minus 1,114 (minus 0.0010%)
boundary drops 1,114 · 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-04T17:04:20Z 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,385,434 115,623,770 0-39 0e7a7e12c681466a8a236887c81b2d15093a846f6af0ef1baee3eff5b7ccfa26 book 552,158 59,898,916 40-42 7429b0b83337d980a7df5c433314f5c44f2cecf017de291d9f4f8951744ca3c9 last_trade_price 81,051 4,501,290 43-43 3632b7c3f4bf1a4a27d9c6879727d3ac72d56d257dd5854e59c70b8003d9b5a3 market_resolved 930 145,775 44-44 c21c14c499c57a8baaa00b80046958897388052e62510f88c9ea6fce3aa31e9e new_market 1,986 204,939 45-45 0f219dc4cdc70a36479c4962e4763a269735072034a8fc72fa1870ef1f2b6917 price_change 99,415,544 950,789,455 46-425 0f662fea46fb9c0c70ddd499852f6094de48722b512fd8188e9c4c4b07ac0c3e tick_size_change 3,736 136,515 426-426 6f90539caafa296d1c9540fe356d11d1be81ea350dc22f574fe88e9999c2ebe5 EVENT MIX count share price_change 99,415,544 90.02% best_bid_ask 10,385,434 9.40% book 552,158 0.50% last_trade_price 81,051 0.07% tick_size_change 3,736 <0.01% new_market 1,986 <0.01% market_resolved 930 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,385,532 10,385,434 98 2,079 FULL book 552,196 552,158 38 185,043 FULL last_trade_price 81,051 81,051 0 181 FULL market_resolved 930 930 0 6 FULL new_market 1,986 1,986 0 0 FULL price_change 99,416,522 99,415,544 978 2,805 FULL tick_size_change 3,736 3,736 0 63 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 9,942,335 60 48ms 66ms 320ms 10.3s 0 transport_latency_assumed best_bid_ask c 10,283,430 685 5ms 9ms 112ms 6.1s 0 transport_latency_assumed best_bid_ask e 10,261,754 10,261,672 40ms 59ms 339ms 11.8s 0 transport_latency_assumed best_bid_ask h 10,384,521 123,017 19ms 29ms 262ms 43.8s 0 transport_latency_assumed book b 539,735 376,964 1.0min 11.2h 27.0d 97.7d 0 book_staleness book c 170,011 2,121 6ms 20ms 3.7s 79.1d 0 book_staleness book e 171,293 171,293 44ms 304ms 8.8min 11.0d 0 book_staleness book h 169,003 1,780 23ms 59ms 2.2s 27.2d 0 book_staleness last_trade_price b 77,069 6 62ms 231ms 3.5s 10.5s 0 transport_latency_assumed last_trade_price c 80,779 6 10ms 39ms 253ms 5.0s 0 transport_latency_assumed last_trade_price e 80,559 80,559 49ms 228ms 2.8s 11.9s 0 transport_latency_assumed last_trade_price h 81,019 480 24ms 66ms 460ms 30.8s 0 transport_latency_assumed market_resolved b 906 25 49ms 211ms 4.7min 5.4min 0 transport_latency_assumed market_resolved c 894 3 5ms 9ms 56ms 2.4min 0 transport_latency_assumed market_resolved e 899 899 41ms 181ms 631ms 2.3min 0 transport_latency_assumed market_resolved h 899 3 19ms 87ms 204ms 678ms 0 transport_latency_assumed new_market b 1,330 136 172ms 14.0s 3.9min 4.7min 0 transport_latency_assumed new_market c 1,326 149 100ms 12.6s 48.7s 2.3min 0 transport_latency_assumed new_market e 1,326 1,326 217ms 18.7s 53.7s 1.6min 0 transport_latency_assumed new_market h 1,326 375 152ms 15.3s 44.6s 1.0min 0 transport_latency_assumed price_change b 94,920,173 1,094 48ms 77ms 461ms 10.7s 0 transport_latency_assumed price_change c 98,614,362 12,554 5ms 10ms 122ms 6.3s 0 transport_latency_assumed price_change e 98,167,042 98,166,222 41ms 79ms 490ms 11.8s 0 transport_latency_assumed price_change h 99,399,102 1,235,674 19ms 32ms 271ms 43.8s 0 transport_latency_assumed tick_size_change b 3,548 not meas. 48ms 61ms 183ms 698ms 0 transport_latency_assumed tick_size_change c 3,700 not meas. 5ms 8ms 69ms 422ms 0 transport_latency_assumed tick_size_change e 3,704 3,704 41ms 103ms 208ms 500ms 0 transport_latency_assumed tick_size_change h 3,736 32 19ms 26ms 107ms 2.3s 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/14/2026-09-04T14.parquet sha256sum 2026-09-04T14.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.