Hour audit: 2026-09-06T05
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-06T05 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-06T05:00:00.037894831+00:00 · last event 2026-09-06T05:59:59.999989517+00:00
VOLUME 95,419,050 rows · 953,568,643 bytes (909.39 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 94,979,335 · h: 94,967,999 · g: 94,935,746 · e: 94,533,598 · c: 80,442,490 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 89,188 (0.09%) · h: 26,415 (0.03%) · g: 94,933,940 (99.49%) · e: 27,723 (0.03%) · c: 341,784 (0.36%) (rows of the merged file that came from it; these partition it)
7 product-machine pairs publish no supplied count; the figures above still sum to the file's 95,419,050 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 caa8a935be706d3314bc1ba86cc4e82993cc39497bdaca4c514659cc30bfcc14
the corpus checksum ledger names this file with the same digest
joined 95,420,888 to merged 95,419,050, minus 1,838 (minus 0.0019%)
boundary drops 1,838 · 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-06T08:50:36Z as cefgh
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 10,892,614 113,746,359 0-41 bd0fadb0c8ed2a79e6386416094671b7f75ad6c62aef0ec78920b23120f9aa40 book 541,976 52,069,619 42-44 b22a17b1940b592f5a6b97c3027599767fb7de6745a7ac84464e8ae7df08559e last_trade_price 47,968 2,736,178 45-45 69d7795a8228b407ea9353e5360312eec6cde3fed37b9f7f0ae879e4c1a76b2b market_resolved 1,919 309,158 46-46 4a2721652f742231d159ef6f95718c55ab6b21b6189ef12612bb5fc4a926e077 new_market 2,165 226,418 47-47 5da131db882ac35d8ed69a3aa79c0d158d3dc04cc0dc327b5efae160593f1698 price_change 83,928,860 783,260,691 48-368 5b5478039e18897d20ae899e95df896dfc60cfd1caec195358bd7494d55fe99c tick_size_change 3,548 129,883 369-369 f574edb5d800df0925dfae8dac9408188e6858c936d2622034b4d9a5a6d00aab EVENT MIX count share price_change 83,928,860 87.96% best_bid_ask 10,892,614 11.42% book 541,976 0.57% last_trade_price 47,968 0.05% tick_size_change 3,548 <0.01% new_market 2,165 <0.01% market_resolved 1,919 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,892,812 10,892,614 198 3,700 FULL book 542,024 541,976 48 171,265 FULL last_trade_price 47,970 47,968 2 403 FULL market_resolved 1,919 1,919 0 302 FULL new_market 2,165 2,165 0 653 FULL price_change 83,930,450 83,928,860 1,590 3,345 FULL tick_size_change 3,548 3,548 0 161 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,283,102 291 4ms 6ms 51ms 1.4s 0 transport_latency_assumed best_bid_ask e 10,875,237 504 38ms 42ms 164ms 20.3s 0 transport_latency_assumed best_bid_ask f 10,890,332 2,221 47ms 52ms 171ms 4.0s 0 transport_latency_assumed best_bid_ask g 10,889,035 10,888,837 79ms 95ms 365ms 30.1s 0 transport_latency_assumed best_bid_ask h 10,891,241 761 18ms 23ms 193ms 22.8s 0 transport_latency_assumed book c 470,434 328,499 4.9min 14.3h 34.7d 99.3d 0 book_staleness book e 122,183 22,617 41ms 18.2min 4.3d 97.7d 0 book_staleness book f 137,005 34,338 52ms 3.2h 14.6d 99.3d 0 book_staleness book g 137,900 137,884 91ms 3.8h 14.6d 99.3d 0 book_staleness book h 124,781 18,638 22ms 18.9min 14.6d 99.3d 0 book_staleness last_trade_price c 40,965 not meas. 9ms 34ms 179ms 5.0s 0 transport_latency_assumed last_trade_price e 46,588 2 44ms 88ms 2.2s 20.0s 0 transport_latency_assumed last_trade_price f 47,948 181 53ms 95ms 797ms 5.3s 0 transport_latency_assumed last_trade_price g 47,781 47,779 91ms 159ms 2.4s 30.1s 0 transport_latency_assumed last_trade_price h 47,927 6 23ms 57ms 382ms 7.2s 0 transport_latency_assumed market_resolved c 1,593 21 4ms 6ms 1.8min 2.5min 0 transport_latency_assumed market_resolved e 1,891 3 40ms 120ms 385ms 56.3s 0 transport_latency_assumed market_resolved f 1,895 not meas. 50ms 145ms 411ms 998ms 0 transport_latency_assumed market_resolved g 1,895 1,895 87ms 257ms 664ms 1.8s 0 transport_latency_assumed market_resolved h 1,895 not meas. 19ms 68ms 164ms 6.8s 0 transport_latency_assumed new_market c 818 91 71ms 23.0s 35.9min 5.1h 0 transport_latency_assumed new_market e 1,471 115 165ms 30.4s 1.3min 41.8min 0 transport_latency_assumed new_market f 1,471 324 168ms 29.4s 1.3min 5.6h 0 transport_latency_assumed new_market g 1,471 1,471 274ms 25.4s 1.3min 6.5h 0 transport_latency_assumed new_market h 1,471 164 123ms 32.0s 1.2min 3.0h 0 transport_latency_assumed price_change c 70,642,674 12,882 4ms 7ms 58ms 2.4s 0 transport_latency_assumed price_change e 83,482,700 4,482 38ms 44ms 224ms 20.3s 0 transport_latency_assumed price_change f 83,897,136 52,124 48ms 54ms 205ms 4.1s 0 transport_latency_assumed price_change g 83,854,116 83,852,526 80ms 98ms 462ms 30.7s 0 transport_latency_assumed price_change h 83,897,136 6,846 18ms 26ms 207ms 22.8s 0 transport_latency_assumed tick_size_change c 2,904 not meas. 4ms 6ms 24ms 56ms 0 transport_latency_assumed tick_size_change e 3,528 not meas. 38ms 50ms 339ms 11.8s 0 transport_latency_assumed tick_size_change f 3,548 not meas. 48ms 52ms 127ms 405ms 0 transport_latency_assumed tick_size_change g 3,548 3,548 80ms 96ms 299ms 507ms 0 transport_latency_assumed tick_size_change h 3,548 not meas. 18ms 24ms 128ms 2.6s 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-06/05/2026-09-06T05.parquet sha256sum 2026-09-06T05.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.