Hour audit: 2026-09-04T07
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-04T07 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-04T07:00:00.000899768+00:00 · last event 2026-09-04T07:59:59.999997049+00:00
VOLUME 92,388,766 rows · 876,023,340 bytes (835.44 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 92,329,718 · e: 71,334,501 · h: 69,911,509 · b: 64,063,251 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 9,933,723 (10.75%) · e: 71,333,637 (77.21%) · h: 11,105,290 (12.02%) · b: 16,116 (0.02%) (rows of the merged file that came from it; these partition it)
6 product-machine pairs publish no supplied count; the figures above still sum to the file's 92,388,766 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 1c7be4c82a7cdcee78fb199be059a681454966a71091b49b460d5edd66c787f0
the corpus checksum ledger names this file with the same digest
joined 92,389,898 to merged 92,388,766, minus 1,132 (minus 0.0012%)
boundary drops 1,132 · 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-04T08:49:24Z 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 8,660,356 93,952,157 0-33 46503cf9d557d865792dbedbdce674bf4b2bbea6d303a39a1631461d7562d98b book 181,574 18,770,619 34-34 77ff38f99917b9b478f041c68cffe92662b4f3ee9fd423ba79a413b343f01cd5 last_trade_price 54,312 3,021,283 35-35 859aa2a787884763ceda37bc18439488617f4d0db60df167241d7705b276531f market_resolved 498 82,871 36-36 ea935ffe2c1bd856e6443ba5673a6f9a1a933100bf66c66a503680ee97b2b51b new_market 748 79,015 37-37 4f37ac8e1550b0aa78c0baa103b18d8f74a8a0a7d6d6f05df2d71151b1eda292 price_change 83,489,794 759,006,977 38-356 9c87e1e306ff5a55ec9ec5f73f9f33bd712955b7d13451281f0b90c564cc2459 tick_size_change 1,484 54,333 357-357 2b7f839597f6eb5ddbeaad53dd05824972f5cf311f7ea695808abc6905feb4fc EVENT MIX count share price_change 83,489,794 90.37% best_bid_ask 8,660,356 9.37% book 181,574 0.20% last_trade_price 54,312 0.06% tick_size_change 1,484 <0.01% new_market 748 <0.01% market_resolved 498 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,660,512 8,660,356 156 93 FULL book 181,632 181,574 58 31,761 FULL last_trade_price 54,312 54,312 0 2 FULL market_resolved 498 498 0 0 FULL new_market 748 748 0 0 FULL price_change 83,490,712 83,489,794 918 92,545 FULL tick_size_change 1,484 1,484 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 8,657,779 16 49ms 61ms 160ms 5.0s 0 transport_latency_assumed best_bid_ask c 8,660,224 612 4ms 7ms 55ms 5.0s 0 transport_latency_assumed best_bid_ask e 8,657,858 8,657,724 40ms 48ms 200ms 5.0s 0 transport_latency_assumed best_bid_ask h 8,658,950 2,004 17ms 22ms 96ms 8.4s 0 transport_latency_assumed book b 127,899 14,484 53ms 26.2s 19.0h 95.8d 0 book_staleness book c 136,213 22,677 6ms 2.2min 4.6d 97.4d 0 book_staleness book e 131,118 131,108 44ms 1.3min 1.5d 95.8d 0 book_staleness book h 125,503 13,305 22ms 3.5s 16.1h 78.9d 0 book_staleness last_trade_price b 54,163 not meas. 56ms 138ms 750ms 5.0s 0 transport_latency_assumed last_trade_price c 54,285 9 9ms 38ms 206ms 5.0s 0 transport_latency_assumed last_trade_price e 54,127 54,127 48ms 134ms 1.1s 5.0s 0 transport_latency_assumed last_trade_price h 54,137 176 23ms 68ms 331ms 7.9s 0 transport_latency_assumed market_resolved b 495 not meas. 50ms 229ms 523ms 851ms 0 transport_latency_assumed market_resolved c 495 3 4ms 9ms 33ms 115ms 0 transport_latency_assumed market_resolved e 495 495 42ms 201ms 533ms 59.8s 0 transport_latency_assumed market_resolved h 495 not meas. 18ms 99ms 183ms 59.8s 0 transport_latency_assumed new_market b 523 42 167ms 19.1s 49.7s 1.3min 0 transport_latency_assumed new_market c 523 95 48ms 20.4s 36.1s 1.1min 0 transport_latency_assumed new_market e 523 523 145ms 19.3s 40.8s 59.8s 0 transport_latency_assumed new_market h 523 88 72ms 18.2s 34.1s 41.5s 0 transport_latency_assumed price_change b 55,220,908 1,574 49ms 62ms 222ms 5.0s 0 transport_latency_assumed price_change c 83,476,494 9,910,327 4ms 7ms 63ms 5.0s 0 transport_latency_assumed price_change e 62,488,896 62,488,176 40ms 58ms 259ms 5.0s 0 transport_latency_assumed price_change h 61,070,417 11,089,717 18ms 25ms 120ms 8.5s 0 transport_latency_assumed tick_size_change b 1,484 not meas. 49ms 58ms 124ms 165ms 0 transport_latency_assumed tick_size_change c 1,484 not meas. 4ms 6ms 18ms 58ms 0 transport_latency_assumed tick_size_change e 1,484 1,484 41ms 46ms 115ms 130ms 0 transport_latency_assumed tick_size_change h 1,484 not meas. 18ms 21ms 60ms 181ms 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-04/07/2026-09-04T07.parquet sha256sum 2026-09-04T07.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.