Hour audit: 2026-09-01T22
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-01T22 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-01T22:00:00.014106098+00:00 · last event 2026-09-01T22:59:57.107818858+00:00
VOLUME 53,564,796 rows · 595,930,005 bytes (568.32 MiB) · 7 products, all holding rows
WITNESSES ceh — 3 machines contributed rows
captured h: 53,205,479 · c: 53,201,613 · e: 52,639,107 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 771,690 (1.44%) · c: 160,054 (0.30%) · e: 52,633,052 (98.26%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 53,564,796 rows exactly, so those pairs supplied none
4 expected (bceh), 1 contributed nothing: b
INTEGRITY sha256 5cd4e6b10bba51f9d54d6ac16637a1009b7ef824c4ed21b4fdaadf8787925dd9
the corpus checksum ledger names this file with the same digest
joined 53,574,223 to merged 53,564,796, minus 9,427 (minus 0.0176%)
boundary drops 9,427 · 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-02T00:21:52Z 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,813,232 58,448,098 0-14 c6107caac297c8886de9332af78c2a596f4bf5c82179f25819878f8c3f2f8470 book 620,479 56,642,524 15-17 3310154a6514793e43c1561fa32db93b6664d20e9e23138eb28f665a10e4d608 last_trade_price 38,245 2,190,507 18-18 2b46c1fb6b40e4e138c54ba867c198c415dd6a61883ffa74f5c9845efa263d88 market_resolved 2,694 428,076 19-19 c39d8b9b9fed4a3ad5821c7ebfbaf428db9f34405ff885aa62bbcaf28e94b195 new_market 1,606 189,631 20-20 a7b2735db5fe3feffb63c5fe5cbf25bc1c6607180e1f65419a44ca5916801527 price_change 49,086,404 477,334,227 21-208 edb0f5f685ba7e40e095f506ee1f0aa2c76257d5bd4f786b9fa0b36cc4471570 tick_size_change 2,136 77,272 209-209 487df28ab84a3451cda3ec4d8dd6aecc870eb75f8b21accfd7dbbc1da9c7f16c EVENT MIX count share price_change 49,086,404 91.64% best_bid_ask 3,813,232 7.12% book 620,479 1.16% last_trade_price 38,245 0.07% market_resolved 2,694 <0.01% tick_size_change 2,136 <0.01% new_market 1,606 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 3,813,637 3,813,232 405 127,724 PARTIAL book 624,225 620,479 3,746 160,001 PARTIAL last_trade_price 38,245 38,245 0 2,407 PARTIAL market_resolved 2,694 2,694 0 2,677 PARTIAL new_market 1,606 1,606 0 1,250 PARTIAL price_change 49,091,680 49,086,404 5,276 159,033 PARTIAL tick_size_change 2,136 2,136 0 534 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 3,812,774 424 5ms 11ms 182ms 6.4s 0 transport_latency_assumed best_bid_ask e 3,797,447 3,797,110 42ms 169ms 2.6s 21.0s 0 transport_latency_assumed best_bid_ask h 3,812,186 15,698 18ms 38ms 328ms 22.6s 0 transport_latency_assumed book c 265,636 132,650 1.7min 50.2min 26.9d 95.0d 0 book_staleness book e 292,508 291,352 2.1min 1.3h 28.2d 95.0d 0 book_staleness book h 308,583 196,477 1.9min 1.2h 28.3d 95.0d 0 book_staleness last_trade_price c 38,219 4 10ms 48ms 265ms 5.0s 0 transport_latency_assumed last_trade_price e 36,488 36,488 94ms 5.1s 12.8s 21.0s 0 transport_latency_assumed last_trade_price h 38,227 1,753 33ms 670ms 2.8s 6.1s 0 transport_latency_assumed market_resolved c 2,676 not meas. 5ms 10ms 52.8s 58.9s 0 transport_latency_assumed market_resolved e 2,675 2,675 42ms 285ms 54.7s 1.0min 0 transport_latency_assumed market_resolved h 2,677 19 19ms 80ms 55.7s 1.2min 0 transport_latency_assumed new_market c 1,250 62 36ms 14.4s 52.6s 6.7min 0 transport_latency_assumed new_market e 1,250 1,250 180ms 15.8s 53.8s 2.1min 0 transport_latency_assumed new_market h 1,250 294 104ms 25.8s 55.0s 8.8min 0 transport_latency_assumed price_change c 49,078,922 26,914 5ms 11ms 233ms 7.0s 0 transport_latency_assumed price_change e 48,506,603 48,502,041 43ms 230ms 5.3s 21.0s 0 transport_latency_assumed price_change h 49,040,420 557,449 19ms 46ms 624ms 23.0s 0 transport_latency_assumed tick_size_change c 2,136 not meas. 5ms 8ms 243ms 496ms 0 transport_latency_assumed tick_size_change e 2,136 2,136 42ms 218ms 1.3s 10.4s 0 transport_latency_assumed tick_size_change h 2,136 not meas. 18ms 31ms 121ms 792ms 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/22/2026-09-01T22.parquet sha256sum 2026-09-01T22.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.