Hour audit: 2026-09-01T06
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-01T06 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-01T06:00:00.020914096+00:00 · last event 2026-09-01T06:59:59.999905159+00:00
VOLUME 80,704,036 rows · 804,025,042 bytes (766.78 MiB) · 7 products, all holding rows
WITNESSES ceh — 3 machines contributed rows
captured h: 80,575,005 · c: 80,234,999 · e: 79,533,181 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 1,149,966 (1.42%) · c: 21,837 (0.03%) · e: 79,532,233 (98.55%) (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 80,704,036 rows exactly, so those pairs supplied none
4 expected (bceh), 1 contributed nothing: b
INTEGRITY sha256 7c37a8f78310710af0854516cf34fa5707e97e9adb79e8e539a44c2ed5367efa
the corpus checksum ledger names this file with the same digest
joined 80,705,170 to merged 80,704,036, minus 1,134 (minus 0.0014%)
boundary drops 1,134 · 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-01T13:30:14Z 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 6,969,190 78,120,043 0-26 be9e58af16e5582c7c8a8d291c090f88b22b6df2b7871d893a72374e5303ce30 book 565,386 51,478,358 27-29 aaa5a5b5e84d30f5cb8d1fd127c4edf16b40287b9676f75e4374c518e8c212e6 last_trade_price 48,936 2,774,434 30-30 375afadd59a048530a79273c5b82b62f2c4652f7a0a45363130ffeb1480bd527 market_resolved 905 148,578 31-31 3917e5a68ec7570ee117b0767c82febdce04b63a63ec5e25b8ddadd54611847a new_market 1,681 172,249 32-32 055b165066c005599b71f31525b845a00eade706b90a46707fe7469d74a9bb87 price_change 73,116,012 670,338,183 33-311 ff1b7aa15eeadb12cc698581dcd6d87ff74141cffd0654acfeee491fb4272444 tick_size_change 1,926 71,147 312-312 3ae1a9e2c36704b00c7422f6faf2bef067db75a47876c40a48482a421a2294c6 EVENT MIX count share price_change 73,116,012 90.60% best_bid_ask 6,969,190 8.64% book 565,386 0.70% last_trade_price 48,936 0.06% tick_size_change 1,926 <0.01% new_market 1,681 <0.01% market_resolved 905 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 6,969,266 6,969,190 76 73,234 PARTIAL book 565,576 565,386 190 177,030 PARTIAL last_trade_price 48,936 48,936 0 3,182 PARTIAL market_resolved 905 905 0 902 PARTIAL new_market 1,681 1,681 0 1,152 PARTIAL price_change 73,116,880 73,116,012 868 131,166 PARTIAL tick_size_change 1,926 1,926 0 481 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 6,968,538 1,034 4ms 7ms 95ms 2.7s 0 transport_latency_assumed best_bid_ask e 6,946,638 6,946,562 41ms 94ms 1.5s 35.0s 0 transport_latency_assumed best_bid_ask h 6,959,735 21,594 18ms 24ms 253ms 43.5s 0 transport_latency_assumed book c 128,361 16,093 8ms 4.6min 9.7d 75.9d 0 book_staleness book e 122,755 122,751 402ms 5.1min 9.7d 94.3d 0 book_staleness book h 528,617 426,542 1.9min 7.8h 29.8d 94.3d 0 book_staleness last_trade_price c 48,896 6 9ms 42ms 235ms 4.4s 0 transport_latency_assumed last_trade_price e 45,339 45,339 102ms 6.6s 15.2s 34.2s 0 transport_latency_assumed last_trade_price h 48,841 3,591 28ms 467ms 2.3s 9.4s 0 transport_latency_assumed market_resolved c 902 1 4ms 9ms 48.2s 1.8min 0 transport_latency_assumed market_resolved e 902 902 43ms 364ms 48.6s 1.0min 0 transport_latency_assumed market_resolved h 902 2 19ms 103ms 53.2s 53.3s 0 transport_latency_assumed new_market c 1,152 51 55ms 17.3s 25.3s 1.3min 0 transport_latency_assumed new_market e 1,152 1,152 299ms 17.6s 25.0s 1.2min 0 transport_latency_assumed new_market h 1,152 478 157ms 18.2s 24.0s 57.7s 0 transport_latency_assumed price_change c 73,085,224 4,652 4ms 7ms 160ms 3.6s 0 transport_latency_assumed price_change e 72,414,469 72,413,601 42ms 137ms 5.6s 35.4s 0 transport_latency_assumed price_change h 73,033,832 697,759 18ms 29ms 418ms 44.0s 0 transport_latency_assumed tick_size_change c 1,926 not meas. 4ms 7ms 361ms 687ms 0 transport_latency_assumed tick_size_change e 1,926 1,926 42ms 111ms 824ms 1.0s 0 transport_latency_assumed tick_size_change h 1,926 not meas. 18ms 22ms 301ms 447ms 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/06/2026-09-01T06.parquet sha256sum 2026-09-01T06.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.