Hour audit: 2026-09-02T15
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-02T15 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-02T15:00:00.032715320+00:00 · last event 2026-09-02T15:59:59.999964107+00:00
VOLUME 108,129,092 rows · 1,123,791,824 bytes (1.05 GiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured h: 107,629,285 · c: 107,612,357 · e: 107,254,000 · b: 102,534,317 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 459,977 (0.43%) · c: 75,899 (0.07%) · e: 107,253,094 (99.19%) · b: 340,122 (0.31%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 108,129,092 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 b8f3214fcea4ff1dcba5738604c0c4f9c197af38d69abcb7515a5f988b933132
the corpus checksum ledger names this file with the same digest
joined 108,130,870 to merged 108,129,092, minus 1,778 (minus 0.0016%)
boundary drops 1,778 · 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-02T18:02:27Z 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,468,069 107,468,212 0-36 a9c5f407e0ece86b31036ec765ad5a41da8897bc757e5ef2de658a31693c2069 book 730,587 62,722,634 37-39 610df85df46979c39cccb36b68093e1397fb79da5c1b5ac1e3ccf9c40d0a5e52 last_trade_price 72,627 4,113,741 40-40 ee48627b35c812c8a8215c3d55ebc110bb8a891c50ede6dcb23e0e2acaf98a52 market_resolved 1,252 186,988 41-41 5591ed9f12d3db6f3c31b581d3f8143ef2cf9761fba0ffab7d30bd050a96e533 new_market 765 87,082 42-42 fa8fcb9fb4b12ed05b6d726cc43700841ff3a4cd16b7703bceb91dd3e0f886e2 price_change 97,851,728 947,833,896 43-416 1b176662c9c63eb8c1d1a979323996dd2632b42738b007f3e22513a4fb84d464 tick_size_change 4,064 146,063 417-417 95288859b78d5bc620ba0b952da9026ca99f38bcecd528ba34631bb9c75532db EVENT MIX count share price_change 97,851,728 90.50% best_bid_ask 9,468,069 8.76% book 730,587 0.68% last_trade_price 72,627 0.07% tick_size_change 4,064 <0.01% market_resolved 1,252 <0.01% new_market 765 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,468,147 9,468,069 78 481 FULL book 731,169 730,587 582 176,728 FULL last_trade_price 72,627 72,627 0 83 FULL market_resolved 1,252 1,252 0 10 FULL new_market 765 765 0 34 FULL price_change 97,852,846 97,851,728 1,118 117 FULL tick_size_change 4,064 4,064 0 45 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 9,007,172 10 52ms 72ms 336ms 16.1s 0 transport_latency_assumed best_bid_ask c 9,467,293 729 5ms 8ms 44ms 1.6s 0 transport_latency_assumed best_bid_ask e 9,453,904 9,453,844 42ms 77ms 694ms 17.7s 0 transport_latency_assumed best_bid_ask h 9,466,560 13,486 18ms 26ms 102ms 5.7s 0 transport_latency_assumed book b 578,104 339,959 1.4min 7.2h 29.8d 95.7d 0 book_staleness book c 227,349 63,120 10ms 58.9min 21.9d 95.7d 0 book_staleness book e 228,972 228,898 573ms 1.7h 21.9d 95.7d 0 book_staleness book h 253,976 98,610 73ms 2.5h 25.0d 95.7d 0 book_staleness last_trade_price b 68,554 4 84ms 2.9s 11.0s 16.3s 0 transport_latency_assumed last_trade_price c 72,488 105 13ms 45ms 207ms 5.0s 0 transport_latency_assumed last_trade_price e 70,531 70,531 76ms 3.1s 10.7s 17.7s 0 transport_latency_assumed last_trade_price h 72,488 1,987 32ms 143ms 836ms 5.0s 0 transport_latency_assumed market_resolved b 1,155 85 53ms 352ms 4.9min 4.9min 0 transport_latency_assumed market_resolved c 1,161 not meas. 5ms 13ms 57.9s 1.0min 0 transport_latency_assumed market_resolved e 1,161 1,161 42ms 288ms 1.0min 1.0min 0 transport_latency_assumed market_resolved h 1,161 6 18ms 135ms 57.9s 2.2min 0 transport_latency_assumed new_market b 536 52 197ms 24.8s 9.7h 10.4h 0 transport_latency_assumed new_market c 550 59 50ms 22.6s 1.5d 1.5d 0 transport_latency_assumed new_market e 526 526 191ms 19.5s 2.1min 4.7d 0 transport_latency_assumed new_market h 526 128 87ms 17.1s 2.5min 2.5min 0 transport_latency_assumed price_change b 92,874,912 12 52ms 91ms 3.1s 16.3s 0 transport_latency_assumed price_change c 97,839,452 11,886 5ms 9ms 51ms 2.2s 0 transport_latency_assumed price_change e 97,494,842 97,494,070 42ms 114ms 3.4s 17.7s 0 transport_latency_assumed price_change h 97,830,510 345,760 18ms 30ms 166ms 5.7s 0 transport_latency_assumed tick_size_change b 3,884 not meas. 52ms 80ms 311ms 3.0s 0 transport_latency_assumed tick_size_change c 4,064 not meas. 5ms 9ms 31ms 143ms 0 transport_latency_assumed tick_size_change e 4,064 4,064 42ms 107ms 184ms 9.5s 0 transport_latency_assumed tick_size_change h 4,064 not meas. 18ms 28ms 72ms 298ms 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/15/2026-09-02T15.parquet sha256sum 2026-09-02T15.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.