Hour audit: 2026-09-01T23
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-01T23 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-01T23:00:01.372393680+00:00 · last event 2026-09-01T23:59:59.999926966+00:00
VOLUME 26,833,332 rows · 327,935,074 bytes (312.74 MiB) · 7 products, all holding rows
WITNESSES ceh — 3 machines contributed rows
captured h: 26,499,395 · e: 25,899,738 · c: 4,087,817 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 702,198 (2.62%) · e: 25,899,692 (96.52%) · c: 231,442 (0.86%) (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 26,833,332 rows exactly, so those pairs supplied none
4 expected (bceh), 1 contributed nothing: b
INTEGRITY sha256 9c084d98e0f013919f21f626402995d9819cf722169cbee696518a1e63974760
the corpus checksum ledger names this file with the same digest
joined 26,833,430 to merged 26,833,332, minus 98 (minus 0.0004%)
boundary drops 98 · 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-02T08:24:55Z 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 an incident recorded by the venue intersects this hour: Venue restart, then a paused database migration, 2026-09-01T22:30Z to 2026-09-02T04:58ZThe 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 3,324,456 47,097,087 0-12 1952515acc655f54ceee92eebd7be696f6bc9a826a7707d1514ab4ec80a33cf3 book 549,103 50,141,953 13-15 0094ac477a6eeff4380975a9a749137a2d25d8a8c41e75ec5d9ce636db609767 last_trade_price 19,605 1,159,295 16-16 44552ee15af29cdc1ad3ecc2b72fc1d7b8b07f92c7efca846c238c757bb74578 market_resolved 1,036 156,568 17-17 6028cae86c054f03bf95735d464a03d8a22c3126998343374be0b2e0539422b2 new_market 2,360 275,446 18-18 7b50c70a9ae1b0274c72a9414841040ec09fc0562e77886500980d036c89f128 price_change 22,934,920 228,717,139 19-106 0fe86e4b768e9f67a4c1a9eb2f5b0b7b568e02d4d3f6aee92c0b4be3509d9705 tick_size_change 1,852 68,532 107-107 dd3a2a95dc802437b1844a148dd3d80f2aff8700441479717ae03fd6d10fe235 EVENT MIX count share price_change 22,934,920 85.47% best_bid_ask 3,324,456 12.39% book 549,103 2.05% last_trade_price 19,605 0.07% new_market 2,360 <0.01% tick_size_change 1,852 <0.01% market_resolved 1,036 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 3,324,456 3,324,456 0 107,052 PARTIAL book 549,201 549,103 98 184,059 PARTIAL last_trade_price 19,605 19,605 0 1,802 PARTIAL market_resolved 1,036 1,036 0 979 PARTIAL new_market 2,360 2,360 0 1,892 PARTIAL price_change 22,934,920 22,934,920 0 153,859 PARTIAL tick_size_change 1,852 1,852 0 463 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 490,088 8 2ms 4ms 39ms 1.5s 0 transport_latency_assumed best_bid_ask e 3,258,506 3,258,506 42ms 118ms 811ms 33.1s 0 transport_latency_assumed best_bid_ask h 3,324,254 65,942 17ms 27ms 333ms 7.8s 0 transport_latency_assumed book c 465,672 231,254 39.1min 5.2h 30.5d 95.0d 0 book_staleness book e 193,434 193,388 22.2min 1.6h 30.5d 95.1d 0 book_staleness book h 217,793 124,461 26.2min 2.3h 30.3d 95.0d 0 book_staleness last_trade_price c 1,604 not meas. 8ms 59ms 251ms 4.9s 0 transport_latency_assumed last_trade_price e 18,721 18,721 92ms 5.9s 14.1s 33.3s 0 transport_latency_assumed last_trade_price h 19,603 884 29ms 474ms 3.0s 5.0s 0 transport_latency_assumed market_resolved c 815 37 4ms 7ms 7.9min 9.7min 0 transport_latency_assumed market_resolved e 978 978 41ms 90ms 48.5s 1.4min 0 transport_latency_assumed market_resolved h 979 21 19ms 24ms 287ms 48.6s 0 transport_latency_assumed new_market c 534 61 52ms 16.8s 10.5min 33.1min 0 transport_latency_assumed new_market e 1,892 1,892 217ms 38.8s 1.7min 3.5min 0 transport_latency_assumed new_market h 1,892 407 117ms 38.4s 1.7min 8.4min 0 transport_latency_assumed price_change c 3,128,808 82 2ms 6ms 145ms 3.1s 0 transport_latency_assumed price_change e 22,424,359 22,424,359 42ms 188ms 6.0s 33.3s 0 transport_latency_assumed price_change h 22,933,022 510,479 17ms 37ms 423ms 7.9s 0 transport_latency_assumed tick_size_change c 296 not meas. 2ms 3ms 7ms 7ms 0 transport_latency_assumed tick_size_change e 1,848 1,848 42ms 175ms 749ms 1.0s 0 transport_latency_assumed tick_size_change h 1,852 4 17ms 37ms 249ms 361ms 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/23/2026-09-01T23.parquet sha256sum 2026-09-01T23.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.