Hour audit: 2026-09-04T22
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-04T22 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-04T22:00:00.027243729+00:00 · last event 2026-09-04T22:59:59.999908113+00:00
VOLUME 89,556,935 rows · 885,744,675 bytes (844.71 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 89,463,620 · b: 89,454,865 · h: 89,447,175 · e: 89,320,268 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 39,389 (0.04%) · b: 10,071 (0.01%) · h: 188,314 (0.21%) · e: 89,319,161 (99.73%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 89,556,935 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 a998069cfdaf9bbd550da53a7c1369498dd5702b5f05309cfed0888e301e0f6a
the corpus checksum ledger names this file with the same digest
joined 89,558,276 to merged 89,556,935, minus 1,341 (minus 0.0015%)
boundary drops 1,341 · 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-04T23:51:10Z 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 11,257,410 121,112,307 0-42 b3902838c7d7b2d875e08e2fe776189940f9aa5e163eb00b650614239f197044 book 175,954 17,230,976 43-43 7d38da9a0564c7db5f20ca1130001cd34920e81e92d7710846c8a00ab57d2117 last_trade_price 51,150 2,935,913 44-44 6fb8f2393b784d1f33d34b8a31cf34de27e4222300ef96f81b4cf3a91aa9b5c4 market_resolved 2,338 372,823 45-45 6459a5e5ec50f70a36233a9ea32ce1df4fe5a992158b30952283f50f30d14c20 new_market 3,301 335,913 46-46 b7f740341c84dc640e4289523a7c0aaa1009d8e3e93811ecada1d30cc43498d2 price_change 78,064,130 742,639,552 47-344 9e4104fc3ad34e84f95ef33fc32c57b34ebbe819dab74356200080d6ac322967 tick_size_change 2,652 97,357 345-345 6f033801ce921a097c6804b59d883b039d4f08cafeff45709d26745d95709c47 EVENT MIX count share price_change 78,064,130 87.17% best_bid_ask 11,257,410 12.57% book 175,954 0.20% last_trade_price 51,150 0.06% new_market 3,301 <0.01% tick_size_change 2,652 <0.01% market_resolved 2,338 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,257,533 11,257,410 123 235 FULL book 175,954 175,954 0 28,349 FULL last_trade_price 51,150 51,150 0 1 FULL market_resolved 2,338 2,338 0 0 FULL new_market 3,301 3,301 0 0 FULL price_change 78,065,348 78,064,130 1,218 374 FULL tick_size_change 2,652 2,652 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 11,254,805 12 52ms 67ms 386ms 13.4s 0 transport_latency_assumed best_bid_ask c 11,257,020 590 4ms 7ms 143ms 16.9s 0 transport_latency_assumed best_bid_ask e 11,250,414 11,250,303 42ms 56ms 389ms 24.3s 0 transport_latency_assumed best_bid_ask h 11,255,968 6,505 18ms 22ms 359ms 1.1min 0 transport_latency_assumed book b 111,069 585 59ms 642ms 8.3s 79.4d 0 book_staleness book c 141,794 29,303 7ms 5.9min 13.4d 90.3d 0 book_staleness book e 142,756 142,756 50ms 6.6min 3.0d 52.2d 0 book_staleness book h 112,496 3,310 21ms 111ms 47.5s 79.5d 0 book_staleness last_trade_price b 51,092 8 66ms 384ms 6.8s 13.5s 0 transport_latency_assumed last_trade_price c 51,103 8 10ms 41ms 305ms 5.0s 0 transport_latency_assumed last_trade_price e 50,505 50,505 51ms 348ms 6.1s 24.1s 0 transport_latency_assumed last_trade_price h 51,106 629 23ms 69ms 698ms 1.0min 0 transport_latency_assumed market_resolved b 2,309 7 63ms 221ms 709ms 1.0min 0 transport_latency_assumed market_resolved c 2,309 1 4ms 10ms 50.6s 53.5s 0 transport_latency_assumed market_resolved e 2,309 2,309 45ms 204ms 687ms 1.0min 0 transport_latency_assumed market_resolved h 2,309 21 20ms 83ms 55.1s 58.0s 0 transport_latency_assumed new_market b 2,158 161 227ms 22.4s 1.7min 8.2min 0 transport_latency_assumed new_market c 2,158 549 98ms 26.2s 1.8min 34.4min 0 transport_latency_assumed new_market e 2,158 2,158 175ms 36.0s 1.7min 34.4min 0 transport_latency_assumed new_market h 2,158 433 141ms 24.9s 1.6min 17.3min 0 transport_latency_assumed price_change b 78,030,780 9,298 53ms 81ms 597ms 13.6s 0 transport_latency_assumed price_change c 78,006,584 8,938 5ms 8ms 191ms 22.7s 0 transport_latency_assumed price_change e 77,869,474 77,868,478 43ms 78ms 765ms 24.4s 0 transport_latency_assumed price_change h 78,020,486 177,416 18ms 25ms 456ms 1.1min 0 transport_latency_assumed tick_size_change b 2,652 not meas. 52ms 62ms 112ms 7.0s 0 transport_latency_assumed tick_size_change c 2,652 not meas. 4ms 6ms 26ms 114ms 0 transport_latency_assumed tick_size_change e 2,652 2,652 42ms 73ms 140ms 2.7s 0 transport_latency_assumed tick_size_change h 2,652 not meas. 18ms 20ms 52ms 1.8s 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/22/2026-09-04T22.parquet sha256sum 2026-09-04T22.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.