Hour audit: 2026-09-04T05
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-04T05 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-04T05:00:00.000488238+00:00 · last event 2026-09-04T05:59:59.999995533+00:00
VOLUME 93,488,181 rows · 868,024,258 bytes (827.81 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 93,443,295 · h: 67,976,802 · e: 60,433,459 · b: 57,480,940 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 16,614,296 (17.77%) · h: 16,434,180 (17.58%) · e: 60,432,311 (64.64%) · b: 7,394 (0.01%) (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 93,488,181 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 cd60a4913a37afd1d404a808b2a166677192608b8af43c8d4791fce47048a104
the corpus checksum ledger names this file with the same digest
joined 93,489,719 to merged 93,488,181, minus 1,538 (minus 0.0016%)
boundary drops 1,538 · 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-04T06:48:48Z 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 8,463,222 92,881,419 0-32 83b87bf9e55a701a36196db7a6f6972b386961362d4a0ee32bac387cae7b54b9 book 166,985 16,411,268 33-33 4905e3d7a8af3321e817b14b60378e159d6d23e3599293a41bc2606fededff02 last_trade_price 56,145 3,078,097 34-34 ea6b223627fd36cbe5c356d392a473ac44406f76cfa297e2c4d1207bbef72128 market_resolved 1,191 193,136 35-35 390f35593ef631b6ff851df64286494dc826f05e9931325f25eeb65de611f8e9 new_market 981 107,033 36-36 b01df1e5a04162967fa0bdce6adc319a5d85757ba456efa2700200c7e6a2a39c price_change 84,797,167 754,195,439 37-360 a1be7812ae5ba552f8d0648eeb1bcd24874c8a9b977d8539cbd29a5937d3ab2a tick_size_change 2,490 89,775 361-361 623270f19802963ed89c86e3536041825e55a21c886508758fd7d2c0df03f034 EVENT MIX count share price_change 84,797,167 90.70% best_bid_ask 8,463,222 9.05% book 166,985 0.18% last_trade_price 56,145 0.06% tick_size_change 2,490 <0.01% market_resolved 1,191 <0.01% new_market 981 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,463,326 8,463,222 104 79 FULL book 166,989 166,985 4 18,547 FULL last_trade_price 56,145 56,145 0 0 FULL market_resolved 1,191 1,191 0 0 FULL new_market 981 981 0 0 FULL price_change 84,798,597 84,797,167 1,430 106,392 FULL tick_size_change 2,490 2,490 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 8,460,560 6 49ms 61ms 150ms 2.5s 0 transport_latency_assumed best_bid_ask c 8,463,050 2,395 4ms 6ms 49ms 5.1s 0 transport_latency_assumed best_bid_ask e 8,458,225 8,458,135 40ms 47ms 219ms 7.0s 0 transport_latency_assumed best_bid_ask h 8,445,281 2,686 17ms 21ms 102ms 37.2s 0 transport_latency_assumed book b 122,919 6,495 53ms 210ms 4.8h 78.8d 0 book_staleness book c 137,813 21,433 6ms 1.4min 2.3d 78.8d 0 book_staleness book e 128,553 128,553 43ms 2.9s 13.7h 28.3d 0 book_staleness book h 122,751 10,504 20ms 156ms 7.4h 78.7d 0 book_staleness last_trade_price b 55,912 8 57ms 119ms 493ms 5.0s 0 transport_latency_assumed last_trade_price c 56,118 273 9ms 39ms 200ms 4.9s 0 transport_latency_assumed last_trade_price e 55,712 55,712 47ms 112ms 891ms 7.0s 0 transport_latency_assumed last_trade_price h 54,205 152 23ms 61ms 307ms 8.0s 0 transport_latency_assumed market_resolved b 1,174 not meas. 51ms 193ms 59.7s 1.0min 0 transport_latency_assumed market_resolved c 1,174 17 4ms 6ms 44ms 351ms 0 transport_latency_assumed market_resolved e 1,174 1,174 40ms 134ms 59.2s 59.8s 0 transport_latency_assumed market_resolved h 1,174 not meas. 18ms 40ms 59.1s 59.7s 0 transport_latency_assumed new_market b 698 45 161ms 15.2s 27.5s 1.0min 0 transport_latency_assumed new_market c 698 86 61ms 12.4s 25.3s 1.5min 0 transport_latency_assumed new_market e 698 698 145ms 16.7s 29.7s 1.0min 0 transport_latency_assumed new_market h 698 152 71ms 13.2s 24.2s 54.5s 0 transport_latency_assumed price_change b 48,837,187 840 50ms 62ms 203ms 2.6s 0 transport_latency_assumed price_change c 84,781,952 16,590,092 4ms 7ms 54ms 5.2s 0 transport_latency_assumed price_change e 51,786,607 51,785,549 40ms 53ms 266ms 7.0s 0 transport_latency_assumed price_change h 59,350,203 16,420,686 17ms 22ms 119ms 37.5s 0 transport_latency_assumed tick_size_change b 2,490 not meas. 49ms 61ms 123ms 205ms 0 transport_latency_assumed tick_size_change c 2,490 not meas. 4ms 6ms 19ms 87ms 0 transport_latency_assumed tick_size_change e 2,490 2,490 40ms 46ms 117ms 163ms 0 transport_latency_assumed tick_size_change h 2,490 not meas. 17ms 20ms 67ms 124ms 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-04/05/2026-09-04T05.parquet sha256sum 2026-09-04T05.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.