Hour audit: 2026-08-29T02
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-08-29T02 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-08-29T02:00:00.024069596+00:00 · last event 2026-08-29T02:59:59.999995342+00:00
VOLUME 110,054,740 rows · 1,164,084,589 bytes (1.08 GiB) · 7 products, all holding rows
WITNESSES abceh — 5 machines contributed rows
captured c: 109,659,441 · h: 109,646,285 · e: 109,352,862 · a: 105,514,163 · b: 707 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 30,219 (0.03%) · h: 310,682 (0.28%) · e: 109,351,123 (99.36%) · a: 362,246 (0.33%) · b: 470 (0.00%) (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 110,054,740 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 696c6356892a1825450f59cc77e6b82fa49da295bd047c67a67e4fc653a6bce8
the corpus checksum ledger names this file with the same digest
joined 110,056,539 to merged 110,054,740, minus 1,799 (minus 0.0016%)
boundary drops 1,799 · 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-01T01:43:49Z as abceh
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,346,296 96,792,216 0-31 79733eb1a045fcd54352b384ca071b63c508f5a35c08e85ca30ec8c61e46e49d book 520,085 54,793,598 32-33 b717ecd7e1b99de4d90504cf819897c10fd8fb5fef3f21380715ce64b7c8e2be last_trade_price 54,743 3,092,355 34-34 c30eddd340ee9f3e4ddf2ce2b40f34d8cbbfb901493952468b16a6ae3f8f2bc8 market_resolved 1,264 193,871 35-35 a2f6d3e05faf60fe33d848b45a0c91ea0ff1c72754f9dd666c81778f425247ce new_market 914 105,196 36-36 8993106cf7851063f3ba2fe36003a1ee48a3b9dd10b65be1e938e45fdda55f40 price_change 101,127,718 1,007,720,401 37-422 82f42a465baa06487524ea27f17f8169064a5624db57195e4687f25f8c341e51 tick_size_change 3,720 135,819 423-423 d8b831c5bd799139a2ea429e28cc968261c62510c4ceba4611d77f23c1061a05 EVENT MIX count share price_change 101,127,718 91.89% best_bid_ask 8,346,296 7.58% book 520,085 0.47% last_trade_price 54,743 0.05% tick_size_change 3,720 <0.01% market_resolved 1,264 <0.01% new_market 914 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,346,407 8,346,296 111 72,007 FULL book 520,097 520,085 12 183,974 FULL last_trade_price 54,743 54,743 0 3,305 PARTIAL market_resolved 1,264 1,264 0 1,198 PARTIAL new_market 930 914 16 624 FULL price_change 101,129,378 101,127,718 1,660 128,179 FULL tick_size_change 3,720 3,720 0 930 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 8,006,354 42 38ms 52ms 225ms 13.4s 0 transport_latency_assumed best_bid_ask b 10 not meas. 61ms 89ms 89ms 89ms 0 transport_latency_assumed best_bid_ask c 8,345,868 437 4ms 7ms 58ms 4.5s 0 transport_latency_assumed best_bid_ask e 8,331,024 8,330,915 45ms 129ms 3.0s 19.5s 0 transport_latency_assumed best_bid_ask h 8,345,322 14,902 12ms 19ms 81ms 7.4s 0 transport_latency_assumed book a 485,657 361,660 1.4min 5.7h 25.5d 91.2d 0 book_staleness book b 284 204 3.0min 6.6min 15.5min 21.3min 0 book_staleness book c 130,606 17,922 7ms 43.9s 3.3d 72.7d 0 book_staleness book e 114,637 114,637 78ms 6.7s 58.6min 48.4d 0 book_staleness book h 133,275 25,662 21ms 1.2min 6.5d 91.2d 0 book_staleness last_trade_price a 52,219 4 56ms 1.7s 8.6s 13.5s 0 transport_latency_assumed last_trade_price c 54,672 40 9ms 37ms 177ms 4.9s 0 transport_latency_assumed last_trade_price e 52,526 52,526 73ms 4.1s 11.8s 19.4s 0 transport_latency_assumed last_trade_price h 54,607 2,173 17ms 88ms 615ms 5.0s 0 transport_latency_assumed market_resolved a 1,118 36 39ms 293ms 54.0s 2.2min 0 transport_latency_assumed market_resolved c 1,198 17 4ms 8ms 190ms 595ms 0 transport_latency_assumed market_resolved e 1,198 1,198 45ms 236ms 43.5s 55.3s 0 transport_latency_assumed market_resolved h 1,198 13 12ms 64ms 50.7s 53.7s 0 transport_latency_assumed new_market a 489 46 146ms 11.5s 45.0s 24.4min 0 transport_latency_assumed new_market b 315 266 30.7min 38.4min 38.5min 38.5min 0 transport_latency_assumed new_market c 489 33 35ms 387ms 1.2min 1.8h 0 transport_latency_assumed new_market e 489 489 163ms 8.9s 20.9s 1.3h 0 transport_latency_assumed new_market h 489 80 43ms 375ms 24.1s 3.0h 0 transport_latency_assumed price_change a 96,964,718 458 38ms 63ms 536ms 13.5s 0 transport_latency_assumed price_change b 98 not meas. 61ms 70ms 89ms 89ms 0 transport_latency_assumed price_change c 101,122,888 11,770 4ms 7ms 58ms 5.1s 0 transport_latency_assumed price_change e 100,849,268 100,847,638 45ms 158ms 4.3s 19.5s 0 transport_latency_assumed price_change h 101,107,674 267,852 12ms 18ms 93ms 7.4s 0 transport_latency_assumed tick_size_change a 3,608 not meas. 38ms 44ms 145ms 1.0s 0 transport_latency_assumed tick_size_change c 3,720 not meas. 4ms 6ms 22ms 187ms 0 transport_latency_assumed tick_size_change e 3,720 3,720 45ms 121ms 5.4s 12.1s 0 transport_latency_assumed tick_size_change h 3,720 not meas. 12ms 16ms 49ms 269ms 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/02/2026-08-29T02.parquet sha256sum 2026-08-29T02.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.