Hour audit: 2026-08-31T15
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-08-31T15 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-31T15:00:00.040911475+00:00 · last event 2026-08-31T15:59:59.999952704+00:00
VOLUME 94,847,162 rows · 977,564,812 bytes (932.28 MiB) · 7 products, all holding rows
WITNESSES ceh — 3 machines contributed rows
captured h: 94,412,042 · e: 93,176,485 · c: 66,548,325 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 1,291,553 (1.36%) · e: 93,174,929 (98.24%) · c: 380,680 (0.40%) (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 94,847,162 rows exactly, so those pairs supplied none
4 expected (bceh), 1 contributed nothing: b
the listing string reads "bche"; the letters above are the machines whose rows are in the file
INTEGRITY sha256 14f5af8a02f3541d071f9da67c38e3eb8de141aa467e659950b84488a3441bf1
the corpus checksum ledger names this file with the same digest
joined 94,848,720 to merged 94,847,162, minus 1,558 (minus 0.0016%)
boundary drops 1,558 · 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-02T02:43:30Z 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,512,298 76,364,517 0-24 6b1402f4baa0d2f2e9a192750f196793435c7aeac8a841e80140604d052427ad book 558,351 55,934,610 25-27 a6174500263730f8cc71b38e1928a9fc547c1d20ef8e3a9f081b04f2558d3c25 last_trade_price 79,537 4,389,264 28-28 c16ae9245f57556a3d46ef44e21db3fd14c056425f2f5e0fe7b4d44494236626 market_resolved 680 90,012 29-29 575d159a76870ba121f7a97a1163f52e464e75efe5b2a1f1cf722b902f9747df new_market 6,027 606,463 30-30 74f5746ec4b383ffb0f88912ee1ae6875b25205589c62228e767a347ad19a02e price_change 87,685,881 838,940,100 31-365 864d24737cfc2dd64a06832c48df106575305620b0316563347899e76f7e8d4a tick_size_change 4,388 158,072 366-366 417f41c7938fe1d0772c8fddbbf26576879c05aafba6d4df4c8ac6ff48ccd662 EVENT MIX count share price_change 87,685,881 92.45% best_bid_ask 6,512,298 6.87% book 558,351 0.59% last_trade_price 79,537 0.08% new_market 6,027 <0.01% tick_size_change 4,388 <0.01% market_resolved 680 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 6,512,349 6,512,298 51 66,973 PARTIAL book 558,353 558,351 2 175,087 PARTIAL last_trade_price 79,538 79,537 1 4,042 PARTIAL market_resolved 680 680 0 543 PARTIAL new_market 6,027 6,027 0 3,893 PARTIAL price_change 87,687,385 87,685,881 1,504 125,998 PARTIAL tick_size_change 4,388 4,388 0 1,097 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 4,732,782 542 4ms 11ms 257ms 14.2s 0 transport_latency_assumed best_bid_ask e 6,471,245 6,471,194 46ms 188ms 3.5s 43.1s 0 transport_latency_assumed best_bid_ask h 6,511,382 40,562 14ms 32ms 507ms 1.0min 0 transport_latency_assumed book c 489,145 365,571 1.3min 5.1h 29.0d 93.7d 0 book_staleness book e 174,620 174,618 161ms 25.6s 5.0h 93.7d 0 book_staleness book h 171,050 18,162 20ms 203ms 6.5s 75.1d 0 book_staleness last_trade_price c 54,850 9 9ms 41ms 284ms 13.9s 0 transport_latency_assumed last_trade_price e 71,638 71,637 90ms 5.5s 16.9s 43.1s 0 transport_latency_assumed last_trade_price h 79,517 7,891 20ms 128ms 823ms 44.7s 0 transport_latency_assumed market_resolved c 563 133 5ms 17.2min 20.8min 20.8min 0 transport_latency_assumed market_resolved e 543 543 47ms 612ms 54.1s 59.3s 0 transport_latency_assumed market_resolved h 543 4 15ms 100ms 57.5s 58.8s 0 transport_latency_assumed new_market c 3,895 638 89ms 3.5min 9.8min 17.5min 0 transport_latency_assumed new_market e 3,893 3,893 368ms 3.3min 3.8min 4.0min 0 transport_latency_assumed new_market h 3,893 1,496 198ms 3.2min 3.7min 4.2min 0 transport_latency_assumed price_change c 61,263,894 13,787 4ms 11ms 262ms 15.4s 0 transport_latency_assumed price_change e 86,450,158 86,448,656 46ms 282ms 8.2s 43.3s 0 transport_latency_assumed price_change h 87,641,269 1,223,438 14ms 36ms 538ms 1.0min 0 transport_latency_assumed tick_size_change c 3,196 not meas. 4ms 7ms 46ms 173ms 0 transport_latency_assumed tick_size_change e 4,388 4,388 45ms 114ms 1.8s 14.8s 0 transport_latency_assumed tick_size_change h 4,388 not meas. 14ms 22ms 198ms 1.2s 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-31/15/2026-08-31T15.parquet sha256sum 2026-08-31T15.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.