Hour audit: 2026-09-04T02
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-04T02 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-04T02:00:00.000125297+00:00 · last event 2026-09-04T02:59:59.999987671+00:00
VOLUME 99,343,741 rows · 941,321,616 bytes (897.71 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 99,310,815 · h: 72,645,708 · e: 60,915,633 · b: 57,260,756 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 19,290,502 (19.42%) · h: 19,133,217 (19.26%) · e: 60,914,131 (61.32%) · b: 5,891 (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 99,343,741 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 21d6e475648034461ca31e0021c3eaabe40ee620a66c03b7a7fb581b4356f583
the corpus checksum ledger names this file with the same digest
joined 99,345,606 to merged 99,343,741, minus 1,865 (minus 0.0019%)
boundary drops 1,865 · 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-04T03:49:35Z 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,960,060 100,388,670 0-34 1c2e6f6d8a46dfab07ba389733c979a91ae8a5174415b599bda4aa4b4f38c78f book 150,492 14,771,625 35-35 7ada6ab29b1c7ed3efc5542f4530f46ed941a2c89766144d8810c1537f193395 last_trade_price 55,385 3,092,685 36-36 999af3b5f039a0a9b2ed1ad8531f5e95bc49cee50e0d4ccec687de35fff7628b market_resolved 2,143 349,733 37-37 2808a2c63f7a7abe5ef581093c474a35d757db17849ede8aae7f4e3b67fe3db5 new_market 991 108,659 38-38 07bdd2b6eb53080ae62b189c86947ed91bffb4b383f1eda634eef4563d5001cb price_change 90,170,826 821,336,445 39-382 dfd33543ae9d8f768b122c739f69dbafa801bdb03fd269cad2a75341b1f366d1 tick_size_change 3,844 140,574 383-383 c9e34960b2d4c2598a00de510a4c42640bc3876bc53eb7d13884c1b7b07b0f05 EVENT MIX count share price_change 90,170,826 90.77% best_bid_ask 8,960,060 9.02% book 150,492 0.15% last_trade_price 55,385 0.06% tick_size_change 3,844 <0.01% market_resolved 2,143 <0.01% new_market 991 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,960,217 8,960,060 157 141 FULL book 150,492 150,492 0 15,988 FULL last_trade_price 55,385 55,385 0 2 FULL market_resolved 2,143 2,143 0 0 FULL new_market 991 991 0 0 FULL price_change 90,172,534 90,170,826 1,708 109,215 FULL tick_size_change 3,844 3,844 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 8,955,522 34 53ms 75ms 535ms 21.4s 0 transport_latency_assumed best_bid_ask c 8,959,572 684 4ms 6ms 65ms 1.6s 0 transport_latency_assumed best_bid_ask e 8,953,347 8,953,229 41ms 89ms 844ms 20.5s 0 transport_latency_assumed best_bid_ask h 8,959,326 6,113 18ms 23ms 143ms 10.6s 0 transport_latency_assumed book b 118,872 5,604 114ms 6.0s 3.2h 79.1d 0 book_staleness book c 132,884 18,319 7ms 57.0s 2.1d 78.7d 0 book_staleness book e 123,963 123,963 122ms 11.0s 12.9h 78.7d 0 book_staleness book h 114,946 2,606 26ms 301ms 2.0s 78.6d 0 book_staleness last_trade_price b 54,707 2 93ms 3.7s 13.1s 21.4s 0 transport_latency_assumed last_trade_price c 55,327 2 9ms 41ms 231ms 4.9s 0 transport_latency_assumed last_trade_price e 54,426 54,426 86ms 3.6s 12.7s 20.5s 0 transport_latency_assumed last_trade_price h 55,369 955 27ms 312ms 1.4s 5.5s 0 transport_latency_assumed market_resolved b 2,135 not meas. 64ms 203ms 627ms 57.5s 0 transport_latency_assumed market_resolved c 2,135 8 4ms 7ms 38ms 284ms 0 transport_latency_assumed market_resolved e 2,135 2,135 49ms 191ms 608ms 55.9s 0 transport_latency_assumed market_resolved h 2,135 not meas. 27ms 64ms 218ms 55.9s 0 transport_latency_assumed new_market b 702 37 244ms 10.9s 42.7s 55.9s 0 transport_latency_assumed new_market c 702 107 72ms 17.4s 46.5s 58.9s 0 transport_latency_assumed new_market e 702 702 203ms 14.4s 56.0s 2.8min 0 transport_latency_assumed new_market h 702 145 130ms 12.2s 53.2s 59.3s 0 transport_latency_assumed price_change b 48,124,974 214 53ms 141ms 5.3s 21.4s 0 transport_latency_assumed price_change c 90,156,351 19,271,382 4ms 7ms 80ms 1.6s 0 transport_latency_assumed price_change e 51,777,216 51,775,832 42ms 169ms 5.5s 20.5s 0 transport_latency_assumed price_change h 63,509,386 19,123,398 18ms 29ms 327ms 10.6s 0 transport_latency_assumed tick_size_change b 3,844 not meas. 53ms 84ms 289ms 771ms 0 transport_latency_assumed tick_size_change c 3,844 not meas. 4ms 8ms 95ms 225ms 0 transport_latency_assumed tick_size_change e 3,844 3,844 42ms 107ms 459ms 5.4s 0 transport_latency_assumed tick_size_change h 3,844 not meas. 18ms 29ms 117ms 558ms 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/02/2026-09-04T02.parquet sha256sum 2026-09-04T02.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.