Hour audit: 2026-09-02T22
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-02T22 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-02T22:00:00.028175538+00:00 · last event 2026-09-02T22:59:59.999983476+00:00
VOLUME 99,018,510 rows · 970,751,174 bytes (925.78 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 98,951,005 · h: 98,930,730 · b: 98,710,547 · e: 98,448,408 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 25,108 (0.03%) · h: 524,625 (0.53%) · b: 21,676 (0.02%) · e: 98,447,101 (99.42%) (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 99,018,510 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 76f618a0ee3d1002ebd0503582a36ccc10c1b6f8c077f99dd2f5b3ad038449f4
the corpus checksum ledger names this file with the same digest
joined 99,020,127 to merged 99,018,510, minus 1,617 (minus 0.0016%)
boundary drops 1,617 · 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-02T23:53:50Z 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 11,547,675 125,546,494 0-44 1826c9a2ed5bae7d8872d906af22b35c22d39c5bf4ed6f0368c081d3d698d6e8 book 170,158 17,130,076 45-45 03b0acd9e5844b65cfc93cb7d4b373cfa58e381b76c9f8caa8adff6043457220 last_trade_price 50,539 2,878,833 46-46 6e1a37af8d268a6ec7b5b7eb92f46c5dd381c7465325eb272eda078b3078b192 market_resolved 2,936 463,798 47-47 29a88bc4e4e27412b33e95623fddb22653a03bc8460ab6105f1af9cd4049e543 new_market 1,578 164,092 48-48 15ea7a50c8b087c676e96c278c82d58e903da4d6dd295d54e28444704a149ee8 price_change 87,241,640 823,292,784 49-381 22492855ce861f5fef5f5ba95b953bff5303d8ba129e1fbb8090b39c99d6e697 tick_size_change 3,984 145,969 382-382 7ec00fb57446f706acd12bc03f6a3239e5cf94b0f48d5970366d8e57d968fe35 EVENT MIX count share price_change 87,241,640 88.11% best_bid_ask 11,547,675 11.66% book 170,158 0.17% last_trade_price 50,539 0.05% tick_size_change 3,984 <0.01% market_resolved 2,936 <0.01% new_market 1,578 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,547,830 11,547,675 155 245 FULL book 170,236 170,158 78 27,096 FULL last_trade_price 50,539 50,539 0 0 FULL market_resolved 2,936 2,936 0 0 FULL new_market 1,578 1,578 0 0 FULL price_change 87,243,024 87,241,640 1,384 85 FULL tick_size_change 3,984 3,984 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 11,538,850 52 56ms 97ms 597ms 20.5s 0 transport_latency_assumed best_bid_ask c 11,543,945 2,081 4ms 10ms 143ms 3.1s 0 transport_latency_assumed best_bid_ask e 11,529,690 11,529,555 42ms 105ms 783ms 22.7s 0 transport_latency_assumed best_bid_ask h 11,542,508 15,987 18ms 30ms 248ms 37.3s 0 transport_latency_assumed book b 123,773 21,380 172ms 4.2min 8.1d 77.5d 0 book_staleness book c 118,664 13,458 7ms 16.9s 17.3h 77.5d 0 book_staleness book e 128,250 128,214 174ms 12.2min 23.1h 96.0d 0 book_staleness book h 107,529 7,106 28ms 620ms 6.4min 77.3d 0 book_staleness last_trade_price b 48,779 5 95ms 3.6s 13.0s 20.6s 0 transport_latency_assumed last_trade_price c 50,503 26 10ms 41ms 253ms 4.6s 0 transport_latency_assumed last_trade_price e 48,403 48,403 87ms 3.9s 13.7s 22.7s 0 transport_latency_assumed last_trade_price h 50,482 2,105 28ms 460ms 2.4s 7.5s 0 transport_latency_assumed market_resolved b 2,895 34 58ms 182ms 544ms 1.3s 0 transport_latency_assumed market_resolved c 2,895 not meas. 4ms 8ms 58.2s 1.0min 0 transport_latency_assumed market_resolved e 2,895 2,895 42ms 185ms 58.5s 2.3min 0 transport_latency_assumed market_resolved h 2,895 7 19ms 55ms 34.4s 1.0min 0 transport_latency_assumed new_market b 1,062 79 328ms 19.6s 38.4s 2.3min 0 transport_latency_assumed new_market c 1,062 113 59ms 16.9s 34.3s 45.2s 0 transport_latency_assumed new_market e 1,062 1,062 184ms 19.3s 1.3min 2.1min 0 transport_latency_assumed new_market h 1,062 324 147ms 16.4s 37.3s 45.9s 0 transport_latency_assumed price_change b 86,991,204 126 57ms 120ms 2.8s 20.6s 0 transport_latency_assumed price_change c 87,229,952 9,430 4ms 8ms 183ms 4.4s 0 transport_latency_assumed price_change e 86,734,124 86,732,988 42ms 127ms 3.7s 22.8s 0 transport_latency_assumed price_change h 87,222,270 499,096 18ms 31ms 411ms 37.4s 0 transport_latency_assumed tick_size_change b 3,984 not meas. 56ms 79ms 308ms 574ms 0 transport_latency_assumed tick_size_change c 3,984 not meas. 4ms 7ms 127ms 249ms 0 transport_latency_assumed tick_size_change e 3,984 3,984 42ms 119ms 409ms 6.1s 0 transport_latency_assumed tick_size_change h 3,984 not meas. 18ms 37ms 256ms 6.4s 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/22/2026-09-02T22.parquet sha256sum 2026-09-02T22.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.