Hour audit: 2026-09-03T02
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-03T02 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-03T02:00:00.013074550+00:00 · last event 2026-09-03T02:59:59.999987472+00:00
VOLUME 104,834,667 rows · 1,069,564,411 bytes (1020.02 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 104,431,347 · e: 104,039,842 · h: 102,610,639 · b: 98,624,367 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 53,681 (0.05%) · e: 104,038,403 (99.24%) · h: 371,103 (0.35%) · b: 371,480 (0.35%) (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 104,834,667 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 7e0425871fb277670788fbb6f3e658fce3e309a25bd73db521e0184ae282cb33
the corpus checksum ledger names this file with the same digest
joined 104,836,460 to merged 104,834,667, minus 1,793 (minus 0.0017%)
boundary drops 1,793 · 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-03T04:00:45Z 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,791,290 119,965,157 0-41 31be6b783dfa348e334e3714bf65cb8c4939d97c1a07b15f1b0e192059eb4e1d book 543,928 55,575,200 42-44 09df4cd79fa4c6617591893e1ce765609f3885b36d10fab2ccee37c651c92242 last_trade_price 59,026 3,288,269 45-45 eca872e22c4b171e2a50574c8cbe00dfa11f699c05222da5a11994a51e6e8a5b market_resolved 901 133,411 46-46 9555a8677e16e7dba3b0f734e8768cfd4b045eedcb351b57323647226c28ab76 new_market 1,104 119,526 47-47 1cacdbc2254716553cd99fc8a15522dc736be160781c12fcda44f2c251457886 price_change 93,435,002 889,160,753 48-404 475ee7233245521e88528f6dd0b206c0b0bfa9b4eeaa47351edc879f83648cea tick_size_change 3,416 125,315 405-405 7e05b2850624820e4708ee318dc124afdbbaed6f39db0b86d6508d1a59f29e4e EVENT MIX count share price_change 93,435,002 89.13% best_bid_ask 10,791,290 10.29% book 543,928 0.52% last_trade_price 59,026 0.06% tick_size_change 3,416 <0.01% new_market 1,104 <0.01% market_resolved 901 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,791,452 10,791,290 162 1,507 FULL book 543,964 543,928 36 188,739 FULL last_trade_price 59,027 59,026 1 134 FULL market_resolved 901 901 0 28 FULL new_market 1,104 1,104 0 0 FULL price_change 93,436,596 93,435,002 1,594 828 FULL tick_size_change 3,416 3,416 0 36 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 10,178,180 58 55ms 93ms 837ms 29.0s 0 transport_latency_assumed best_bid_ask c 10,789,196 1,392 4ms 9ms 78ms 6.7s 0 transport_latency_assumed best_bid_ask e 10,774,847 10,774,713 42ms 119ms 1.2s 23.3s 0 transport_latency_assumed best_bid_ask h 10,613,787 15,127 18ms 30ms 190ms 24.6s 0 transport_latency_assumed book b 501,847 368,610 1.8min 7.2h 28.6d 96.2d 0 book_staleness book c 160,561 38,404 8ms 34.5min 11.5d 96.2d 0 book_staleness book e 125,599 125,589 124ms 10.6s 3.4h 25.4d 0 book_staleness book h 127,174 11,325 30ms 588ms 5.9h 77.6d 0 book_staleness last_trade_price b 54,706 4 104ms 5.2s 15.5s 29.0s 0 transport_latency_assumed last_trade_price c 58,926 10 10ms 41ms 205ms 4.8s 0 transport_latency_assumed last_trade_price e 56,407 56,406 93ms 5.2s 17.7s 23.3s 0 transport_latency_assumed last_trade_price h 58,774 2,606 29ms 344ms 1.3s 9.4s 0 transport_latency_assumed market_resolved b 791 85 56ms 839ms 5.0min 5.0min 0 transport_latency_assumed market_resolved c 816 not meas. 4ms 8ms 14.6s 58.0s 0 transport_latency_assumed market_resolved e 816 816 42ms 251ms 16.8s 1.0min 0 transport_latency_assumed market_resolved h 813 not meas. 18ms 72ms 14.4s 57.8s 0 transport_latency_assumed new_market b 770 67 259ms 18.1s 1.1min 1.1min 0 transport_latency_assumed new_market c 770 162 89ms 17.6s 1.2min 1.3min 0 transport_latency_assumed new_market e 770 770 234ms 16.9s 1.1min 1.2min 0 transport_latency_assumed new_market h 770 105 146ms 18.6s 1.1min 1.1min 0 transport_latency_assumed price_change b 87,884,765 2,656 55ms 121ms 4.5s 29.0s 0 transport_latency_assumed price_change c 93,417,662 13,713 4ms 8ms 102ms 6.7s 0 transport_latency_assumed price_change e 93,077,987 93,076,693 42ms 141ms 5.2s 23.3s 0 transport_latency_assumed price_change h 91,805,945 341,940 18ms 32ms 310ms 25.3s 0 transport_latency_assumed tick_size_change b 3,308 not meas. 55ms 69ms 168ms 466ms 0 transport_latency_assumed tick_size_change c 3,416 not meas. 4ms 7ms 29ms 244ms 0 transport_latency_assumed tick_size_change e 3,416 3,416 43ms 114ms 327ms 19.6s 0 transport_latency_assumed tick_size_change h 3,376 not meas. 18ms 35ms 113ms 300ms 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-03/02/2026-09-03T02.parquet sha256sum 2026-09-03T02.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.