Hour audit: 2026-08-29T23
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 5 machines expected to be capturing this hour, 1 contributed no rows: b. The hour is still whole on minutes; it simply rests on 4 machines rather than 5.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-08-29T23 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-29T23:00:00.002540935+00:00 · last event 2026-08-29T23:59:59.999941351+00:00
VOLUME 112,964,053 rows · 1,179,157,477 bytes (1.10 GiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured h: 112,564,151 · c: 112,445,326 · e: 111,831,781 · a: 107,808,170 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 752,146 (0.67%) · c: 34,200 (0.03%) · e: 111,830,310 (99.00%) · a: 347,397 (0.31%) (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 112,964,053 rows exactly, so those pairs supplied none
5 expected (abceh), 1 contributed nothing: b
INTEGRITY sha256 c130b7addeb21bece0f0cfb0d1abc7495c2e186989f10c48eaa30a1b9709af99
the corpus checksum ledger names this file with the same digest
joined 112,965,641 to merged 112,964,053, minus 1,588 (minus 0.0014%)
boundary drops 1,588 · 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-08-30T14:27:03Z as aceh
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 10,123,190 113,354,471 0-38 55e03efdc8bafebe686e9c04d5a2af5ffb8d617c7f9739392972d8c026520e17 book 494,509 51,154,971 39-40 7d1fd103e04d61d286c9e0ca214604d695b75e9a8800d29fbb218f38cbd558ce last_trade_price 61,426 3,439,449 41-41 aad56dd47f9158825cb1d37a9649f7c2a185eb8fdb727b10d3813db91b0dde33 market_resolved 2,054 319,426 42-42 0d1768a176af1027d283331f9dfacecb876a07ff96a93c121090f617e96940ca new_market 2,094 213,034 43-43 d7f2e26c59c7dc3b393725ae292ae0d50fd445075ff006a80515a17e61958abd price_change 102,276,588 1,009,236,314 44-434 1973a4b828026850848bd803a48167e658b4be89dd0256e2542ee002b600507c tick_size_change 4,192 154,312 435-435 e4c767eddf217d31475960961b7291f1d2b80c605739559a39b4f23beecc7cd8 EVENT MIX count share price_change 102,276,588 90.54% best_bid_ask 10,123,190 8.96% book 494,509 0.44% last_trade_price 61,426 0.05% tick_size_change 4,192 <0.01% new_market 2,094 <0.01% market_resolved 2,054 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,123,337 10,123,190 147 70,072 PARTIAL book 494,515 494,509 6 174,793 PARTIAL last_trade_price 61,426 61,426 0 3,164 PARTIAL market_resolved 2,055 2,054 1 2,007 PARTIAL new_market 2,094 2,094 0 1,334 PARTIAL price_change 102,278,022 102,276,588 1,434 131,382 PARTIAL tick_size_change 4,192 4,192 0 1,048 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 9,685,397 70 39ms 52ms 446ms 14.3s 0 transport_latency_assumed best_bid_ask c 10,106,292 338 1ms 5ms 147ms 3.0s 0 transport_latency_assumed best_bid_ask e 10,075,633 10,075,495 44ms 117ms 1.4s 31.0s 0 transport_latency_assumed best_bid_ask h 10,122,750 47,287 12ms 18ms 230ms 35.2s 0 transport_latency_assumed book a 475,945 346,433 57.0s 3.5h 27.1d 92.0d 0 book_staleness book c 133,357 5,241 4ms 46ms 50.8min 73.5d 0 book_staleness book e 136,880 136,880 97ms 9.9s 7.4d 73.5d 0 book_staleness book h 130,599 5,955 18ms 206ms 2.1min 35.1d 0 book_staleness last_trade_price a 58,088 not meas. 57ms 2.1s 9.1s 14.4s 0 transport_latency_assumed last_trade_price c 61,359 9 6ms 34ms 221ms 5.0s 0 transport_latency_assumed last_trade_price e 59,963 59,963 69ms 2.8s 14.7s 30.1s 0 transport_latency_assumed last_trade_price h 61,402 1,454 17ms 105ms 1.3s 8.8s 0 transport_latency_assumed market_resolved a 1,968 37 43ms 202ms 4.5min 4.6min 0 transport_latency_assumed market_resolved c 2,004 3 1ms 6ms 263ms 1.4min 0 transport_latency_assumed market_resolved e 2,003 2,002 45ms 230ms 1.0s 1.3min 0 transport_latency_assumed market_resolved h 2,006 12 13ms 51ms 388ms 47.7s 0 transport_latency_assumed new_market a 1,335 245 266ms 25.7s 1.9min 36.2min 0 transport_latency_assumed new_market c 1,334 157 87ms 17.5s 1.9min 56.7min 0 transport_latency_assumed new_market e 1,334 1,334 311ms 25.2s 1.9min 28.8min 0 transport_latency_assumed new_market h 1,334 358 157ms 26.5s 1.9min 1.9min 0 transport_latency_assumed price_change a 97,581,465 612 40ms 69ms 725ms 14.4s 0 transport_latency_assumed price_change c 102,136,808 28,452 1ms 5ms 160ms 3.4s 0 transport_latency_assumed price_change e 101,551,792 101,550,460 45ms 156ms 3.0s 31.0s 0 transport_latency_assumed price_change h 102,241,868 697,064 12ms 19ms 248ms 35.6s 0 transport_latency_assumed tick_size_change a 3,972 not meas. 39ms 47ms 497ms 717ms 0 transport_latency_assumed tick_size_change c 4,172 not meas. 2ms 5ms 296ms 1.5s 0 transport_latency_assumed tick_size_change e 4,176 4,176 44ms 114ms 976ms 2.2s 0 transport_latency_assumed tick_size_change h 4,192 16 12ms 20ms 227ms 472ms 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-08-29/23/2026-08-29T23.parquet sha256sum 2026-08-29T23.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.