Hour audit: 2026-09-03T23
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-03T23 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-03T23:00:00.000582647+00:00 · last event 2026-09-03T23:59:59.999920966+00:00
VOLUME 105,572,764 rows · 1,007,834,838 bytes (961.15 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 105,522,520 · h: 73,396,693 · e: 60,799,643 · b: 57,364,451 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 24,637,551 (23.34%) · h: 20,129,761 (19.07%) · e: 60,799,145 (57.59%) · b: 6,307 (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 105,572,764 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 4d71ce074252c0c9032377c9722408327b918a3652ef4f2e841ac3469f2e2d88
the corpus checksum ledger names this file with the same digest
joined 105,573,458 to merged 105,572,764, minus 694 (minus 0.0007%)
boundary drops 694 · 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-04T00:50:53Z 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 10,170,865 114,199,785 0-38 f9b88b0b8c5ec892e3d75cbef9e163285edc2111f67bc11f07bf93afa027c45a book 159,107 15,726,130 39-39 49faa2143299df075867e992fbba15388825a44c15e79b77332ecb811b0287dd last_trade_price 56,247 3,100,216 40-40 bccc6769ec5afd226d140fd51c484d201394db953d60a15b26f62be3fa99b9f1 market_resolved 821 135,067 41-41 99d4acad93d95ebe8578cae50e124a18c9763377cd8125e35e714b6accc8752d new_market 1,808 193,952 42-42 29cf8380d56201a02bdaf9cf02312a0b27277120e85045e5c3fe9f6c8c48d0f2 price_change 95,181,264 873,179,119 43-406 97e97419447a6af1fa042bd1cddeadc48f3754e284df689a1d7bfb700e97fe07 tick_size_change 2,652 96,603 407-407 6564648a0342352bf85c9f3b97a738cd5dbed51b424a872ff21c28202d1970cd EVENT MIX count share price_change 95,181,264 90.16% best_bid_ask 10,170,865 9.63% book 159,107 0.15% last_trade_price 56,247 0.05% tick_size_change 2,652 <0.01% new_market 1,808 <0.01% market_resolved 821 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,170,947 10,170,865 82 162 FULL book 159,107 159,107 0 16,857 FULL last_trade_price 56,247 56,247 0 0 FULL market_resolved 821 821 0 0 FULL new_market 1,808 1,808 0 0 FULL price_change 95,181,876 95,181,264 612 112,723 FULL tick_size_change 2,652 2,652 0 1 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 10,161,470 50 52ms 85ms 663ms 30.4s 0 transport_latency_assumed best_bid_ask c 10,170,495 1,087 19ms 26ms 150ms 1.8s 0 transport_latency_assumed best_bid_ask e 10,160,052 10,159,984 41ms 110ms 962ms 30.4s 0 transport_latency_assumed best_bid_ask h 10,169,334 9,744 17ms 26ms 206ms 24.7s 0 transport_latency_assumed book b 119,122 6,131 135ms 7.2s 2.9h 78.5d 0 book_staleness book c 119,290 2,123 23ms 65ms 1.2min 78.5d 0 book_staleness book e 119,539 119,539 124ms 7.3s 2.9h 12.4d 0 book_staleness book h 144,689 31,314 44ms 4.2min 12.2d 97.0d 0 book_staleness last_trade_price b 54,083 4 103ms 4.2s 16.1s 30.4s 0 transport_latency_assumed last_trade_price c 56,222 26 26ms 62ms 330ms 5.0s 0 transport_latency_assumed last_trade_price e 54,448 54,448 99ms 4.2s 16.1s 29.9s 0 transport_latency_assumed last_trade_price h 56,203 1,769 29ms 425ms 1.7s 10.3s 0 transport_latency_assumed market_resolved b 821 not meas. 52ms 304ms 797ms 1.3s 0 transport_latency_assumed market_resolved c 821 not meas. 20ms 29ms 232ms 746ms 0 transport_latency_assumed market_resolved e 821 821 42ms 254ms 950ms 15.5s 0 transport_latency_assumed market_resolved h 821 not meas. 17ms 107ms 254ms 617ms 0 transport_latency_assumed new_market b 1,267 72 251ms 18.9s 1.6min 2.0min 0 transport_latency_assumed new_market c 1,267 155 84ms 20.5s 1.5min 2.7min 0 transport_latency_assumed new_market e 1,267 1,267 212ms 19.5s 1.6min 2.6min 0 transport_latency_assumed new_market h 1,267 314 117ms 19.1s 1.4min 1.8min 0 transport_latency_assumed price_change b 47,025,036 50 52ms 198ms 8.7s 30.4s 0 transport_latency_assumed price_change c 95,171,773 24,634,160 19ms 27ms 178ms 2.5s 0 transport_latency_assumed price_change e 50,460,868 50,460,438 42ms 239ms 8.4s 30.6s 0 transport_latency_assumed price_change h 63,021,727 20,086,616 17ms 35ms 480ms 25.4s 0 transport_latency_assumed tick_size_change b 2,652 not meas. 52ms 87ms 389ms 924ms 0 transport_latency_assumed tick_size_change c 2,652 not meas. 20ms 26ms 286ms 1.1s 0 transport_latency_assumed tick_size_change e 2,648 2,648 42ms 105ms 714ms 20.5s 0 transport_latency_assumed tick_size_change h 2,652 4 17ms 30ms 202ms 2.5s 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-03/23/2026-09-03T23.parquet sha256sum 2026-09-03T23.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.