Hour audit: 2026-09-05T05
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-05T05 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-05T05:00:00.035510779+00:00 · last event 2026-09-05T05:59:59.999999279+00:00
VOLUME 93,365,170 rows · 889,624,853 bytes (848.41 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 93,290,423 · b: 93,283,611 · h: 93,262,227 · e: 93,259,280 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 19,729 (0.02%) · b: 25,897 (0.03%) · h: 60,754 (0.07%) · e: 93,258,790 (99.89%) (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 93,365,170 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 4561f5287b8d9e3baedd06398db9b1e216106fcd69ed92e8188a76198f1c0bfe
the corpus checksum ledger names this file with the same digest
joined 93,365,862 to merged 93,365,170, minus 692 (minus 0.0007%)
boundary drops 692 · 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-05T06:52:02Z 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 9,407,446 101,354,287 0-35 d0ee13ae7d573f83401ad29c273451df849a15098dd9c191a5a36df0210f610d book 176,126 17,712,980 36-36 5d5390317c8030ad7fee3ce5dfebee49358087f7fbdb5c017ce10bc57603ce95 last_trade_price 47,019 2,704,552 37-37 1a351454e5e974c91873a00118b21ec33c8db8a27a0dbf69ad45ca5317f55991 market_resolved 1,328 207,253 38-38 5fb39b46b9e22e02c4cc42c6ca090e902cd23777a336e64e37e2fbc53dd179df new_market 1,027 117,206 39-39 9558fcdd8843af7f68a941683567098c0459f781b1542c256d5772cf0aa2282c price_change 83,729,924 766,379,671 40-359 26a6d7ec2b8c0905d728a42a7d04ac4cdd2fe1a7ea421dd1e7e98a97f6945940 tick_size_change 2,300 84,297 360-360 ca3f778fac4339654ed3c5530f891b59782aaa92033016a2376736b7b4b19869 EVENT MIX count share price_change 83,729,924 89.68% best_bid_ask 9,407,446 10.08% book 176,126 0.19% last_trade_price 47,019 0.05% tick_size_change 2,300 <0.01% market_resolved 1,328 <0.01% new_market 1,027 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,407,540 9,407,446 94 132 FULL book 176,126 176,126 0 34,858 FULL last_trade_price 47,019 47,019 0 0 FULL market_resolved 1,328 1,328 0 0 FULL new_market 1,027 1,027 0 0 FULL price_change 83,730,522 83,729,924 598 104 FULL tick_size_change 2,300 2,300 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 9,405,384 102 55ms 67ms 155ms 2.7s 0 transport_latency_assumed best_bid_ask c 9,407,194 644 4ms 6ms 50ms 3.0s 0 transport_latency_assumed best_bid_ask e 9,405,370 9,405,300 42ms 48ms 185ms 3.7s 0 transport_latency_assumed best_bid_ask h 9,404,077 1,400 17ms 20ms 93ms 41.3s 0 transport_latency_assumed book b 122,838 22,581 59ms 4.1min 10.5d 80.2d 0 book_staleness book c 110,768 11,996 5ms 15.3s 20.1h 98.3d 0 book_staleness book e 119,639 119,639 45ms 2.9min 2.5d 79.4d 0 book_staleness book h 119,695 21,910 20ms 2.8min 5.6d 90.6d 0 book_staleness last_trade_price b 46,995 10 61ms 101ms 537ms 5.0s 0 transport_latency_assumed last_trade_price c 46,995 10 9ms 34ms 203ms 5.0s 0 transport_latency_assumed last_trade_price e 46,940 46,940 48ms 81ms 553ms 5.0s 0 transport_latency_assumed last_trade_price h 46,653 59 22ms 50ms 289ms 7.8s 0 transport_latency_assumed market_resolved b 1,316 not meas. 60ms 206ms 539ms 744ms 0 transport_latency_assumed market_resolved c 1,316 12 4ms 8ms 283ms 58.9s 0 transport_latency_assumed market_resolved e 1,316 1,316 45ms 182ms 465ms 711ms 0 transport_latency_assumed market_resolved h 1,316 not meas. 19ms 58ms 259ms 1.1s 0 transport_latency_assumed new_market b 775 114 171ms 18.3s 37.0s 2.1min 0 transport_latency_assumed new_market c 775 35 55ms 274ms 42.5s 59.5s 0 transport_latency_assumed new_market e 775 775 97ms 252ms 29.6s 3.3min 0 transport_latency_assumed new_market h 775 103 103ms 11.7s 27.6s 1.1min 0 transport_latency_assumed price_change b 83,704,003 3,090 55ms 67ms 184ms 3.4s 0 transport_latency_assumed price_change c 83,721,075 7,032 4ms 6ms 57ms 5.1s 0 transport_latency_assumed price_change e 83,682,940 83,682,520 42ms 54ms 207ms 4.4s 0 transport_latency_assumed price_change h 83,687,411 37,282 17ms 21ms 102ms 42.1s 0 transport_latency_assumed tick_size_change b 2,300 not meas. 55ms 66ms 84ms 96ms 0 transport_latency_assumed tick_size_change c 2,300 not meas. 4ms 5ms 14ms 29ms 0 transport_latency_assumed tick_size_change e 2,300 2,300 42ms 48ms 124ms 325ms 0 transport_latency_assumed tick_size_change h 2,300 not meas. 17ms 20ms 35ms 158ms 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-05/05/2026-09-05T05.parquet sha256sum 2026-09-05T05.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.