Hour audit: 2026-09-01T19
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.
1 finding
- a machine expected this hour contributed nothing. Of the 4 machines expected to be capturing this hour, 1 contributed no rows: b. The hour is still whole on minutes; it simply rests on 3 machines rather than 4.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-01T19 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-01T19:00:00.033257130+00:00 · last event 2026-09-01T19:59:59.999900816+00:00
VOLUME 97,709,616 rows · 1,073,094,620 bytes (1023.38 MiB) · 7 products, all holding rows
WITNESSES ceh — 3 machines contributed rows
captured c: 97,178,835 · h: 97,150,067 · e: 95,683,794 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 262,074 (0.27%) · h: 1,764,948 (1.81%) · e: 95,682,594 (97.93%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 97,709,616 rows exactly, so those pairs supplied none
4 expected (bceh), 1 contributed nothing: b
INTEGRITY sha256 5f55afa4bf519100385a587eacbd55d539c8413aff2c22668c66bef5a3061ceb
the corpus checksum ledger names this file with the same digest
joined 97,711,050 to merged 97,709,616, minus 1,434 (minus 0.0015%)
boundary drops 1,434 · 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-01T22:40:18Z as ceh
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 7/8 pass, 1 finding
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
FINDING a machine expected this hour contributed nothing
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 7,239,298 94,827,350 0-27 bdc72666c332e080e23f6e4a497f566348d60324a8da7d4ab1d10547c5d862c3 book 966,297 80,910,319 28-31 825dcc57afc3828a19e4d30dee484f42a5d1175e3333d0163908ddfa12816282 last_trade_price 75,487 4,210,375 32-32 96547e2b930cf628ad10e3844e6796011f188753a0d7d88d5b04cfd69fa51d62 market_resolved 987 156,478 33-33 b7c8edb9dab4fd00636c551f3771168a956a57cb63ed7558d05ce84bfca77b73 new_market 5,875 641,355 34-34 89778f60ebd5514593ceb4be5b5008954564d069a8445f2aec5f22f654a7a34c price_change 89,414,316 890,967,294 35-376 f0d7733020f11ecde9803919cc7d19ea1459ea5e99b70ae860408cc32bede849 tick_size_change 7,356 267,987 377-377 f80ed7b5e6b6ee270c7f2d4f802e6d8be5fa65f0f55c1957c23f6b0b4bb49ff1 EVENT MIX count share price_change 89,414,316 91.51% best_bid_ask 7,239,298 7.41% book 966,297 0.99% last_trade_price 75,487 0.08% tick_size_change 7,356 <0.01% new_market 5,875 <0.01% market_resolved 987 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 7,239,406 7,239,298 108 125,789 PARTIAL book 966,713 966,297 416 176,629 PARTIAL last_trade_price 75,487 75,487 0 3,886 PARTIAL market_resolved 987 987 0 975 PARTIAL new_market 5,875 5,875 0 4,134 PARTIAL price_change 89,415,226 89,414,316 910 157,405 PARTIAL tick_size_change 7,356 7,356 0 1,839 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 7,237,072 2,225 5ms 15ms 359ms 6.8s 0 transport_latency_assumed best_bid_ask e 7,185,381 7,185,275 48ms 263ms 5.4s 53.1s 0 transport_latency_assumed best_bid_ask h 7,233,734 51,798 19ms 52ms 593ms 57.5s 0 transport_latency_assumed book c 462,813 214,255 31.4s 50.0min 24.4d 94.9d 0 book_staleness book e 463,621 463,435 38.0s 1.0h 24.3d 94.9d 0 book_staleness book h 493,927 288,607 37.6s 56.6min 24.8d 94.9d 0 book_staleness last_trade_price c 75,459 171 11ms 54ms 465ms 5.0s 0 transport_latency_assumed last_trade_price e 69,261 69,261 115ms 5.2s 17.5s 52.9s 0 transport_latency_assumed last_trade_price h 75,235 6,055 30ms 324ms 1.8s 45.9s 0 transport_latency_assumed market_resolved c 975 12 5ms 194ms 1.0min 1.1min 0 transport_latency_assumed market_resolved e 975 975 48ms 701ms 58.9s 58.9s 0 transport_latency_assumed market_resolved h 975 not meas. 21ms 174ms 59.3s 59.3s 0 transport_latency_assumed new_market c 4,134 589 92ms 31.5s 2.0min 2.5min 0 transport_latency_assumed new_market e 4,134 4,134 302ms 37.4s 1.9min 2.5min 0 transport_latency_assumed new_market h 4,134 1,152 175ms 37.1s 1.9min 2.5min 0 transport_latency_assumed price_change c 89,391,026 44,822 5ms 15ms 358ms 7.0s 0 transport_latency_assumed price_change e 87,953,078 87,952,170 48ms 410ms 10.3s 53.1s 0 transport_latency_assumed price_change h 89,334,710 1,417,324 19ms 60ms 721ms 58.5s 0 transport_latency_assumed tick_size_change c 7,356 not meas. 5ms 10ms 233ms 762ms 0 transport_latency_assumed tick_size_change e 7,344 7,344 48ms 179ms 2.6s 21.6s 0 transport_latency_assumed tick_size_change h 7,352 12 19ms 31ms 374ms 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-01/19/2026-09-01T19.parquet sha256sum 2026-09-01T19.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.