Hour audit: 2026-09-02T17
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-02T17 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-02T17:00:00.033773630+00:00 · last event 2026-09-02T17:59:59.999987867+00:00
VOLUME 110,198,723 rows · 1,175,816,126 bytes (1.10 GiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured h: 109,293,015 · c: 109,257,739 · e: 109,160,484 · b: 100,609,414 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 262,807 (0.24%) · c: 119,709 (0.11%) · e: 109,158,530 (99.06%) · b: 657,677 (0.60%) (rows of the merged file that came from it; these partition it)
5 product-machine pairs publish no supplied count; the figures above still sum to the file's 110,198,723 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 fabd3ae06480b06f7db91ab5ec417538a6b946cd8ac56e478acb2540cb710339
the corpus checksum ledger names this file with the same digest
joined 110,203,330 to merged 110,198,723, minus 4,607 (minus 0.0042%)
boundary drops 4,607 · 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-02T20:02:57Z 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 9,175,440 109,337,492 0-35 8eab3b5f2a97f7eb1877f2eb9d05d7cd25c4c6eb3a5c7229d9a7d2b7a013f3be book 1,242,256 78,901,636 36-40 b5608800d128fe447b78ce685641e638a81055a5bc0c814d1f55b47b848712e5 last_trade_price 78,075 4,383,496 41-41 c7b31472eb8b189014ad03fb6c32aa5efcb0f19014866d395a66fc1afde62ec5 market_resolved 1,337 181,679 42-42 2e1d3ee04bb4895ec8b2f99817b1ce18b42ff154125fbb5c32ac364a2dfb0381 new_market 1,573 157,620 43-43 9dafd75aad10e5d048060241077df551e5ac77cb0c299800c7a06eb019fcc415 price_change 99,695,414 981,430,696 44-424 071000b9f48df312011cf1dc994d131e6827f82e4a7aff3beaf1c7216c0adf9a tick_size_change 4,628 166,785 425-425 5bf1c3430b6975b675ec087d703c235c047cd6da2fcec0dd519cf0f5eed750a4 EVENT MIX count share price_change 99,695,414 90.47% best_bid_ask 9,175,440 8.33% book 1,242,256 1.13% last_trade_price 78,075 0.07% tick_size_change 4,628 <0.01% new_market 1,573 <0.01% market_resolved 1,337 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,175,565 9,175,440 125 1,102 FULL book 1,245,480 1,242,256 3,224 167,012 FULL last_trade_price 78,075 78,075 0 154 FULL market_resolved 1,337 1,337 0 26 FULL new_market 1,573 1,573 0 0 FULL price_change 99,696,672 99,695,414 1,258 361 FULL tick_size_change 4,628 4,628 0 91 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 8,374,241 22 52ms 82ms 550ms 29.0s 0 transport_latency_assumed best_bid_ask c 9,174,360 556 5ms 10ms 131ms 5.0s 0 transport_latency_assumed best_bid_ask e 9,172,134 9,172,032 44ms 91ms 709ms 18.6s 0 transport_latency_assumed best_bid_ask h 9,173,624 2,830 19ms 33ms 232ms 9.2s 0 transport_latency_assumed book b 972,468 656,899 1.9min 9.6h 31.2d 95.8d 0 book_staleness book c 314,448 113,774 131ms 2.9h 25.1d 95.8d 0 book_staleness book e 301,369 300,515 3.0s 2.6h 25.1d 95.8d 0 book_staleness book h 357,036 171,068 8.1s 4.4h 25.1d 95.8d 0 book_staleness last_trade_price b 69,987 6 80ms 2.3s 10.5s 28.9s 0 transport_latency_assumed last_trade_price c 78,043 8 11ms 43ms 227ms 4.9s 0 transport_latency_assumed last_trade_price e 77,589 77,589 73ms 2.6s 10.7s 18.6s 0 transport_latency_assumed last_trade_price h 78,033 472 28ms 230ms 1.1s 8.1s 0 transport_latency_assumed market_resolved b 1,267 224 54ms 6.0min 10.8min 10.8min 0 transport_latency_assumed market_resolved c 1,113 not meas. 5ms 9ms 236ms 57.6s 0 transport_latency_assumed market_resolved e 1,113 1,113 44ms 214ms 641ms 58.4s 0 transport_latency_assumed market_resolved h 1,113 not meas. 19ms 90ms 263ms 58.8s 0 transport_latency_assumed new_market b 1,042 134 301ms 26.9s 8.1min 8.1min 0 transport_latency_assumed new_market c 1,015 229 83ms 13.8s 40.6s 51.9s 0 transport_latency_assumed new_market e 1,015 1,015 232ms 15.4s 41.8s 1.3min 0 transport_latency_assumed new_market h 1,015 195 146ms 16.7s 31.4s 52.2s 0 transport_latency_assumed price_change b 91,186,145 392 52ms 107ms 2.1s 29.1s 0 transport_latency_assumed price_change c 99,684,132 5,142 5ms 10ms 159ms 5.2s 0 transport_latency_assumed price_change e 99,602,636 99,601,638 44ms 126ms 2.5s 18.6s 0 transport_latency_assumed price_change h 99,677,566 88,242 19ms 37ms 311ms 9.2s 0 transport_latency_assumed tick_size_change b 4,264 not meas. 51ms 71ms 183ms 351ms 0 transport_latency_assumed tick_size_change c 4,628 not meas. 5ms 8ms 28ms 258ms 0 transport_latency_assumed tick_size_change e 4,628 4,628 43ms 84ms 278ms 604ms 0 transport_latency_assumed tick_size_change h 4,628 not meas. 19ms 25ms 88ms 2.5s 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/17/2026-09-02T17.parquet sha256sum 2026-09-02T17.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.