Hour audit: 2026-09-05T01
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-05T01 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-05T01:00:00.030753934+00:00 · last event 2026-09-05T01:59:59.999968441+00:00
VOLUME 121,107,099 rows · 1,255,954,058 bytes (1.17 GiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured h: 119,410,910 · e: 119,363,917 · c: 119,338,933 · b: 88,681,291 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 104,758 (0.09%) · e: 119,362,545 (98.56%) · c: 37,331 (0.03%) · b: 1,602,465 (1.32%) (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 121,107,099 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 b787f059d38702c8dc7aa9ae44835b97e85609d66ac3a7dbe7ea6ecc86d21515
the corpus checksum ledger names this file with the same digest
joined 121,122,674 to merged 121,107,099, minus 15,575 (minus 0.0129%)
boundary drops 15,575 · 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-05T03:33:57Z 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 12,336,498 133,324,574 0-47 28caac91908f207e4c3cec9bc3c98a0831ff1daa019582fabe3e8a9cb1eff908 book 1,867,654 83,858,486 48-55 3d7e1fdd233ab2a1ff20f64232d6b4bc2fb6a73884717e29dd9041a4e1d96503 last_trade_price 47,493 2,697,840 56-56 aeb7b99f6319de9b2c415b4ef0ce0f87d303b408af1b37f903c74643fe3aae4c market_resolved 1,654 231,432 57-57 462a9a4240938403ec20a60eb689b58c7a55d06ce340f457d38da8e4e4d66a1a new_market 942 84,054 58-58 ee156920c95bea158730a52c7107f4035473495680ed3f5e620a53221b27b41c price_change 106,849,414 1,034,251,920 59-466 f1f1b37123f7f5a20d8f18578eb43517a14b9ba01cb3c3fa26242766c02022c2 tick_size_change 3,444 125,798 467-467 fd5528744a6df43ab5bccac0297b45b97a39cb473bea865993d00f460f3d12ba EVENT MIX count share price_change 106,849,414 88.23% best_bid_ask 12,336,498 10.19% book 1,867,654 1.54% last_trade_price 47,493 0.04% tick_size_change 3,444 <0.01% market_resolved 1,654 <0.01% new_market 942 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,337,314 12,336,498 816 4,995 FULL book 1,868,332 1,867,654 678 191,631 FULL last_trade_price 47,494 47,493 1 547 FULL market_resolved 1,654 1,654 0 380 FULL new_market 942 942 0 106 FULL price_change 106,863,494 106,849,414 14,080 2,499 FULL tick_size_change 3,444 3,444 0 200 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 9,022,863 2 56ms 68ms 149ms 1.4s 0 transport_latency_assumed best_bid_ask c 12,334,435 640 4ms 8ms 50ms 4.9s 0 transport_latency_assumed best_bid_ask e 12,334,166 12,334,036 40ms 48ms 172ms 3.2s 0 transport_latency_assumed best_bid_ask h 12,335,021 1,820 18ms 24ms 85ms 53.1s 0 transport_latency_assumed book b 1,780,554 1,601,031 3.3min 9.6h 33.6d 98.1d 0 book_staleness book c 135,900 32,543 8ms 17.5min 13.5d 98.1d 0 book_staleness book e 157,559 157,459 48ms 1.2h 13.5d 98.1d 0 book_staleness book h 180,129 76,621 49ms 2.2h 24.3d 98.1d 0 book_staleness last_trade_price b 33,891 2 63ms 108ms 442ms 5.1s 0 transport_latency_assumed last_trade_price c 47,321 8 10ms 38ms 226ms 5.0s 0 transport_latency_assumed last_trade_price e 47,405 47,405 46ms 85ms 545ms 5.0s 0 transport_latency_assumed last_trade_price h 47,467 78 23ms 56ms 289ms 7.5s 0 transport_latency_assumed market_resolved b 1,163 187 64ms 8.6min 15.3min 19.1min 0 transport_latency_assumed market_resolved c 1,449 7 4ms 9ms 46.7s 53.1s 0 transport_latency_assumed market_resolved e 1,449 1,449 41ms 121ms 1.1s 1.0min 0 transport_latency_assumed market_resolved h 1,449 11 19ms 61ms 51.5s 57.2s 0 transport_latency_assumed new_market b 653 223 245ms 10.8min 16.0min 16.0min 0 transport_latency_assumed new_market c 514 83 63ms 14.5s 20.5s 1.8min 0 transport_latency_assumed new_market e 514 514 122ms 13.0s 19.1s 1.2min 0 transport_latency_assumed new_market h 514 122 85ms 13.1s 19.3s 1.9min 0 transport_latency_assumed price_change b 77,839,523 1,020 56ms 69ms 169ms 2.1s 0 transport_latency_assumed price_change c 106,815,870 4,050 4ms 9ms 57ms 5.2s 0 transport_latency_assumed price_change e 106,819,380 106,818,238 41ms 53ms 185ms 4.3s 0 transport_latency_assumed price_change h 106,842,886 26,106 18ms 26ms 97ms 53.2s 0 transport_latency_assumed tick_size_change b 2,644 not meas. 56ms 70ms 199ms 424ms 0 transport_latency_assumed tick_size_change c 3,444 not meas. 4ms 8ms 31ms 136ms 0 transport_latency_assumed tick_size_change e 3,444 3,444 41ms 59ms 157ms 196ms 0 transport_latency_assumed tick_size_change h 3,444 not meas. 18ms 28ms 115ms 657ms 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-05/01/2026-09-05T01.parquet sha256sum 2026-09-05T01.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.