Hour audit: 2026-09-02T18
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-02T18 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-02T18:00:00.016189899+00:00 · last event 2026-09-02T18:59:59.999968598+00:00
VOLUME 116,290,234 rows · 1,247,480,289 bytes (1.16 GiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured h: 115,432,590 · c: 115,417,745 · e: 115,128,859 · b: 106,721,604 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 429,602 (0.37%) · c: 68,575 (0.06%) · e: 115,127,831 (99.00%) · b: 664,226 (0.57%) (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 116,290,234 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 24225ad291e5eccf569759af2c5e3b77e6406596a7dc205cdf345c0eb28540f0
the corpus checksum ledger names this file with the same digest
joined 116,291,780 to merged 116,290,234, minus 1,546 (minus 0.0013%)
boundary drops 1,546 · 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-02T21:05:04Z 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,336,785 124,466,998 0-39 bc8bb221070670140585762f580345b44eb6cb0471173886668712887c6a9637 book 1,100,878 75,154,627 40-44 5e4419a97ebc13db4f93ee388e787268b35f9fc6169a11d887a8ecd95715720a last_trade_price 83,006 4,669,523 45-45 9c0016e4708108c036a63ce8134675c58c1f7217c4dfa3d11d500a05caf0fe16 market_resolved 1,182 150,716 46-46 300756de9b0377375f8369551bcd6d936dfdf528b139a5685b60f76ff4cd9082 new_market 3,667 368,730 47-47 c71a17b61e8f89d9a38c6826c792df4475ce1d385c2df95efbb2d810644ad9b8 price_change 104,757,250 1,041,073,117 48-447 55b7a4047ddc0a9a25bbb1e34e78d45342bff56d0973ac7b9f6884ba3e6c44f5 tick_size_change 7,466 272,426 448-448 301585be26094583575c4c9cb939b85693f3016e6acb09e93045ad3fd6dcaa6b EVENT MIX count share price_change 104,757,250 90.08% best_bid_ask 10,336,785 8.89% book 1,100,878 0.95% last_trade_price 83,006 0.07% tick_size_change 7,466 <0.01% new_market 3,667 <0.01% market_resolved 1,182 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,336,891 10,336,785 106 1,128 FULL book 1,101,232 1,100,878 354 175,221 FULL last_trade_price 83,006 83,006 0 150 FULL market_resolved 1,182 1,182 0 0 FULL new_market 3,667 3,667 0 3 FULL price_change 104,758,336 104,757,250 1,086 431 FULL tick_size_change 7,466 7,466 0 72 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 9,508,545 312 54ms 121ms 792ms 23.2s 0 transport_latency_assumed best_bid_ask c 10,335,075 1,598 5ms 12ms 249ms 3.5s 0 transport_latency_assumed best_bid_ask e 10,320,362 10,320,280 42ms 131ms 1.3s 29.7s 0 transport_latency_assumed best_bid_ask h 10,332,297 14,595 20ms 43ms 539ms 47.4s 0 transport_latency_assumed book b 922,958 662,907 1.7min 8.0h 31.1d 95.8d 0 book_staleness book c 245,418 59,689 11ms 12.9min 17.8d 95.8d 0 book_staleness book e 274,917 274,851 1.1s 29.0min 18.2d 95.8d 0 book_staleness book h 282,020 103,431 137ms 39.4min 24.8d 95.8d 0 book_staleness last_trade_price b 74,514 5 92ms 3.0s 12.0s 23.2s 0 transport_latency_assumed last_trade_price c 82,973 7 11ms 47ms 275ms 4.9s 0 transport_latency_assumed last_trade_price e 81,262 81,262 81ms 3.4s 12.3s 29.8s 0 transport_latency_assumed last_trade_price h 82,809 1,732 31ms 381ms 2.2s 42.9s 0 transport_latency_assumed market_resolved b 1,071 258 61ms 8.8min 11.9min 12.1min 0 transport_latency_assumed market_resolved c 924 not meas. 5ms 31ms 59.6s 1.0min 0 transport_latency_assumed market_resolved e 924 924 42ms 448ms 1.0min 1.0min 0 transport_latency_assumed market_resolved h 924 not meas. 20ms 157ms 1.0min 1.0min 0 transport_latency_assumed new_market b 2,377 320 331ms 23.0s 4.7min 16.8min 0 transport_latency_assumed new_market c 2,361 189 91ms 20.8s 4.8min 15.0min 0 transport_latency_assumed new_market e 2,361 2,361 233ms 22.1s 47.7s 10.0min 0 transport_latency_assumed new_market h 2,364 797 172ms 18.3s 3.3min 15.0min 0 transport_latency_assumed price_change b 96,204,963 424 54ms 158ms 2.2s 23.2s 0 transport_latency_assumed price_change c 104,743,528 7,092 5ms 13ms 260ms 3.6s 0 transport_latency_assumed price_change e 104,441,567 104,440,687 42ms 185ms 3.3s 29.8s 0 transport_latency_assumed price_change h 104,724,710 309,047 20ms 49ms 609ms 48.4s 0 transport_latency_assumed tick_size_change b 7,176 not meas. 53ms 84ms 270ms 2.3s 0 transport_latency_assumed tick_size_change c 7,466 not meas. 5ms 11ms 72ms 510ms 0 transport_latency_assumed tick_size_change e 7,466 7,466 42ms 119ms 288ms 3.7s 0 transport_latency_assumed tick_size_change h 7,466 not meas. 20ms 38ms 129ms 4.2s 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/18/2026-09-02T18.parquet sha256sum 2026-09-02T18.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.