Hour audit: 2026-08-31T14
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-31T14 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-31T14:00:00.037394676+00:00 · last event 2026-08-31T14:59:59.999888891+00:00
VOLUME 99,095,487 rows · 968,578,504 bytes (923.71 MiB) · 7 products, all holding rows
WITNESSES ceh — 3 machines contributed rows
captured c: 99,032,958 · h: 98,983,870 · e: 98,078,943 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 47,105 (0.05%) · h: 970,838 (0.98%) · e: 98,077,544 (98.97%) (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 99,095,487 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 5814404f98c24d65bf9d18f6d00f207547be614a6ea6cc91acc5c1b397df927c
the corpus checksum ledger names this file with the same digest
joined 99,096,892 to merged 99,095,487, minus 1,405 (minus 0.0014%)
boundary drops 1,405 · 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:29:19Z 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,457,739 93,066,505 0-32 cee90b7b126b5bf920132d4d725a47bedb6c7aacef326a83cfba71897d3bc9c9 book 216,633 21,233,045 33-33 9f450299c663eb68e3f77bd3a0ac754c8adecd2cb263051edb9887c33a8edf2d last_trade_price 82,169 4,464,759 34-34 c519542e364df2c89df83224f406dc6f61b5a24c08c07b9d585c576c86bf88bb market_resolved 662 106,589 35-35 2a206589678191eb84b41458cf7a6e2677ca05c3dc5028164442980733a41537 new_market 1,281 141,086 36-36 ef6db85c0491698cbb5cc21ec11851645fcced96cd5c356e4673cbb1469d6ed9 price_change 90,333,259 848,305,886 37-381 1aa2b3230feceb763af1ad4c053a36d6b347f87998e7c612c6352517121f429e tick_size_change 3,744 133,222 382-382 deae6facb2fd6119d90d6c2eb9a1b2ae53d0ef910d93090126a332811b970ac2 EVENT MIX count share price_change 90,333,259 91.16% best_bid_ask 8,457,739 8.53% book 216,633 0.22% last_trade_price 82,169 0.08% tick_size_change 3,744 <0.01% new_market 1,281 <0.01% market_resolved 662 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,457,867 8,457,739 128 65,464 PARTIAL book 216,651 216,633 18 23,794 PARTIAL last_trade_price 82,170 82,169 1 4,041 PARTIAL market_resolved 662 662 0 648 PARTIAL new_market 1,281 1,281 0 917 PARTIAL price_change 90,334,517 90,333,259 1,258 125,729 PARTIAL tick_size_change 3,744 3,744 0 935 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,457,385 937 4ms 8ms 81ms 4.0s 0 transport_latency_assumed best_bid_ask e 8,428,693 8,428,565 45ms 99ms 1.3s 28.2s 0 transport_latency_assumed best_bid_ask h 8,456,576 28,237 12ms 21ms 141ms 23.4s 0 transport_latency_assumed book c 178,657 8,746 7ms 33ms 2.5h 93.7d 0 book_staleness book e 172,786 172,774 124ms 18.0s 6.6h 93.7d 0 book_staleness book h 188,837 35,113 19ms 1.9s 16.9h 93.7d 0 book_staleness last_trade_price c 82,094 39 9ms 35ms 163ms 5.1s 0 transport_latency_assumed last_trade_price e 74,377 74,376 76ms 6.1s 17.3s 28.2s 0 transport_latency_assumed last_trade_price h 82,116 7,754 18ms 79ms 375ms 5.5s 0 transport_latency_assumed market_resolved c 648 13 4ms 16ms 49.9s 1.1min 0 transport_latency_assumed market_resolved e 646 646 46ms 594ms 58.6s 1.0min 0 transport_latency_assumed market_resolved h 648 3 13ms 89ms 1.0min 1.0min 0 transport_latency_assumed new_market c 917 138 65ms 14.6s 21.2s 1.7min 0 transport_latency_assumed new_market e 917 917 242ms 16.5s 22.5s 1.6min 0 transport_latency_assumed new_market h 917 226 137ms 14.8s 22.9s 1.1min 0 transport_latency_assumed price_change c 90,309,513 37,232 4ms 9ms 111ms 4.9s 0 transport_latency_assumed price_change e 89,397,780 89,396,522 45ms 154ms 7.2s 28.3s 0 transport_latency_assumed price_change h 90,251,032 899,505 13ms 25ms 189ms 24.4s 0 transport_latency_assumed tick_size_change c 3,744 not meas. 4ms 8ms 100ms 262ms 0 transport_latency_assumed tick_size_change e 3,744 3,744 45ms 92ms 237ms 658ms 0 transport_latency_assumed tick_size_change h 3,744 not meas. 12ms 18ms 149ms 4.9s 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/14/2026-08-31T14.parquet sha256sum 2026-08-31T14.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.