Hour audit: 2026-09-01T05
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-09-01T05 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-01T05:00:00.003430165+00:00 · last event 2026-09-01T05:59:59.999857093+00:00
VOLUME 88,621,105 rows · 846,038,223 bytes (806.84 MiB) · 7 products, all holding rows
WITNESSES ceh — 3 machines contributed rows
captured c: 88,569,379 · h: 88,494,842 · e: 88,043,609 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 36,439 (0.04%) · h: 541,994 (0.61%) · e: 88,042,672 (99.35%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 88,621,105 rows exactly, so those pairs supplied none
4 expected (bceh), 1 contributed nothing: b
INTEGRITY sha256 929c57ab6f330058acdad402e31f6134d11b5e86de0077092c6a68b0347bca3d
the corpus checksum ledger names this file with the same digest
joined 88,622,042 to merged 88,621,105, minus 937 (minus 0.0011%)
boundary drops 937 · 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-01T13:17:25Z 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 8,493,464 91,741,195 0-32 75d8546b7bb1ce711a91d15339b91583ffae8e4e2bf9d4ad4f400ed3a3245393 book 171,293 15,949,223 33-33 22bb7a18f94f7b54f168023caa8405da00f523a7c3312fb3299d5e09fa260f92 last_trade_price 59,380 3,303,781 34-34 982a838a2baa0e5afc62039d265612f60f14cffd22b228d2427d7278bc72bca3 market_resolved 633 103,105 35-35 82815cc63d26c83b6e691b0f39cdf56b9aa7dd7395a36de01e011a0e91a704c5 new_market 1,405 143,354 36-36 030eba2e8a93a9f139acfdbeb40bac057a2a9b7c394a1211eb30236e635e9152 price_change 79,892,830 733,710,285 37-341 fa45edf9d08966e96b58dcb68c5a820a1677d355e63613fcdc1d264a2541d64c tick_size_change 2,100 77,815 342-342 e4e3cb55587624842a8cee8211aa914e6966db772f8f617aa7b2b32062597382 EVENT MIX count share price_change 79,892,830 90.15% best_bid_ask 8,493,464 9.58% book 171,293 0.19% last_trade_price 59,380 0.07% tick_size_change 2,100 <0.01% new_market 1,405 <0.01% market_resolved 633 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,493,555 8,493,464 91 69,619 PARTIAL book 171,295 171,293 2 24,004 PARTIAL last_trade_price 59,380 59,380 0 3,071 PARTIAL market_resolved 633 633 0 633 PARTIAL new_market 1,405 1,405 0 949 PARTIAL price_change 79,893,674 79,892,830 844 125,670 PARTIAL tick_size_change 2,100 2,100 0 525 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,492,890 493 4ms 7ms 67ms 4.7s 0 transport_latency_assumed best_bid_ask e 8,473,772 8,473,681 43ms 88ms 1.5s 19.9s 0 transport_latency_assumed best_bid_ask h 8,492,515 19,290 12ms 17ms 147ms 45.7s 0 transport_latency_assumed book c 139,220 15,763 7ms 12.7s 14.0h 76.2d 0 book_staleness book e 134,519 134,517 166ms 35.9s 1.1d 94.3d 0 book_staleness book h 137,974 21,013 22ms 4.9s 14.1h 94.3d 0 book_staleness last_trade_price c 59,355 12 9ms 38ms 198ms 4.7s 0 transport_latency_assumed last_trade_price e 56,466 56,466 95ms 4.9s 11.8s 19.9s 0 transport_latency_assumed last_trade_price h 59,336 2,902 19ms 165ms 679ms 6.8s 0 transport_latency_assumed market_resolved c 633 not meas. 4ms 7ms 71ms 234ms 0 transport_latency_assumed market_resolved e 633 633 43ms 203ms 2.6s 6.0s 0 transport_latency_assumed market_resolved h 633 not meas. 12ms 48ms 202ms 351ms 0 transport_latency_assumed new_market c 949 95 84ms 18.7s 38.1s 1.3min 0 transport_latency_assumed new_market e 949 949 254ms 22.7s 33.8s 1.1min 0 transport_latency_assumed new_market h 949 361 137ms 20.2s 40.0s 1.0min 0 transport_latency_assumed price_change c 79,874,232 20,076 4ms 7ms 87ms 4.7s 0 transport_latency_assumed price_change e 79,375,170 79,374,326 43ms 130ms 4.4s 19.9s 0 transport_latency_assumed price_change h 79,801,335 498,428 12ms 20ms 218ms 46.6s 0 transport_latency_assumed tick_size_change c 2,100 not meas. 4ms 8ms 156ms 274ms 0 transport_latency_assumed tick_size_change e 2,100 2,100 44ms 120ms 847ms 6.3s 0 transport_latency_assumed tick_size_change h 2,100 not meas. 12ms 21ms 85ms 313ms 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-01/05/2026-09-01T05.parquet sha256sum 2026-09-01T05.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.