Hour audit: 2026-09-11T05
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-11T05 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-11T05:00:00.000032532+00:00 · last event 2026-09-11T05:59:59.999974716+00:00
VOLUME 102,963,109 rows · 1,051,121,724 bytes (1002.43 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 102,456,272 · h: 102,436,653 · g: 102,433,772 · e: 102,414,658 · c: 98,641,930 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 158,278 (0.15%) · h: 7,546,936 (7.33%) · g: 39,478 (0.04%) · e: 432,963 (0.42%) · c: 94,785,454 (92.06%) (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 102,963,109 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 6c45a02a3dc50fa524d356dc3dfbcef8fdfe1cbc8ceba19caf230c95ec8ab153
the corpus checksum ledger names this file with the same digest
joined 102,965,788 to merged 102,963,109, minus 2,679 (minus 0.0026%)
boundary drops 2,679 · 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-11T06:58:39Z 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 9,786,778 108,044,518 0-37 fa136dcdad31b341616f34b84fe84609f7273d71014fc04f0cdb0be70dc8b326 book 604,652 61,894,858 38-40 8954c81a96926931574e61135983d81f0f90dc3486e483911737165d76846e0b last_trade_price 45,343 2,603,622 41-41 c9d6f9580aadfb0bc34a9bcd2be8a6fb1d587df2bec4be847e08c1fafaf9e961 market_resolved 572 93,651 42-42 99d6e391c48c9ac4f3e8a1daff5ae69e1e8020293aaca3c21012dee8a7c785b9 new_market 1,606 165,963 43-43 1eb8cfd53d8498f9b00f47cfe345043cc3063560cf0b12dfac6caebcbd3dba8e price_change 92,522,382 877,079,152 44-396 0598c223a8522b75a7b4407eb5ec11a390ccbf2a55e706f4538ed0bcbe7f09ec tick_size_change 1,776 65,550 397-397 b2d9dd92f5ec16cd80005a89158947ef462dba1ef2545b4fc9ad13dc281f72c7 EVENT MIX count share price_change 92,522,382 89.86% best_bid_ask 9,786,778 9.51% book 604,652 0.59% last_trade_price 45,343 0.04% tick_size_change 1,776 <0.01% new_market 1,606 <0.01% market_resolved 572 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,786,969 9,786,778 191 466 FULL book 605,046 604,652 394 202,654 FULL last_trade_price 45,343 45,343 0 44 FULL market_resolved 572 572 0 7 FULL new_market 1,606 1,606 0 0 FULL price_change 92,524,476 92,522,382 2,094 268 FULL tick_size_change 1,776 1,776 0 4 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,371,849 9,015,167 4ms 9ms 112ms 8.2s 0 transport_latency_assumed best_bid_ask e 9,785,172 39,703 38ms 43ms 151ms 2.8s 0 transport_latency_assumed best_bid_ask f 9,785,152 12,976 44ms 52ms 173ms 2.3s 0 transport_latency_assumed best_bid_ask g 9,784,790 1,227 75ms 93ms 330ms 26.6s 0 transport_latency_assumed best_bid_ask h 9,785,982 717,705 17ms 23ms 154ms 36.3s 0 transport_latency_assumed book c 533,321 509,761 7.5min 23.1h 29.4d 104.3d 0 book_staleness book e 123,795 22,800 42ms 1.2h 3.8d 104.3d 0 book_staleness book f 133,583 20,182 51ms 2.4h 5.7d 104.3d 0 book_staleness book g 144,606 27,758 99ms 2.9h 12.4d 104.3d 0 book_staleness book h 125,069 24,151 22ms 1.4h 5.6d 85.8d 0 book_staleness last_trade_price c 43,334 41,222 10ms 43ms 212ms 4.9s 0 transport_latency_assumed last_trade_price e 45,228 241 45ms 113ms 1.2s 4.9s 0 transport_latency_assumed last_trade_price f 45,210 89 53ms 121ms 515ms 4.9s 0 transport_latency_assumed last_trade_price g 45,179 12 91ms 220ms 5.8s 24.5s 0 transport_latency_assumed last_trade_price h 45,247 3,779 22ms 65ms 311ms 6.9s 0 transport_latency_assumed market_resolved c 550 524 5ms 22ms 4.9min 6.2min 0 transport_latency_assumed market_resolved e 555 6 39ms 140ms 431ms 1.0min 0 transport_latency_assumed market_resolved f 555 not meas. 47ms 188ms 566ms 1.0s 0 transport_latency_assumed market_resolved g 555 not meas. 83ms 336ms 918ms 1.9s 0 transport_latency_assumed market_resolved h 555 42 18ms 69ms 597ms 1.6min 0 transport_latency_assumed new_market c 1,092 638 96ms 35.4s 2.1min 5.9min 0 transport_latency_assumed new_market e 1,084 216 160ms 48.4s 1.7min 2.2min 0 transport_latency_assumed new_market f 1,084 167 175ms 39.3s 1.9min 2.4min 0 transport_latency_assumed new_market g 1,084 143 263ms 39.1s 1.5min 2.2min 0 transport_latency_assumed new_market h 1,084 442 141ms 45.4s 1.6min 2.2min 0 transport_latency_assumed price_change c 88,690,024 85,216,512 5ms 10ms 118ms 8.2s 0 transport_latency_assumed price_change e 92,457,048 369,977 38ms 45ms 196ms 2.8s 0 transport_latency_assumed price_change f 92,488,912 124,860 45ms 55ms 211ms 2.9s 0 transport_latency_assumed price_change g 92,455,782 10,338 76ms 99ms 428ms 26.7s 0 transport_latency_assumed price_change h 92,476,940 6,800,695 17ms 25ms 166ms 38.4s 0 transport_latency_assumed tick_size_change c 1,760 1,630 5ms 17ms 160ms 204ms 0 transport_latency_assumed tick_size_change e 1,776 20 38ms 44ms 194ms 349ms 0 transport_latency_assumed tick_size_change f 1,776 4 45ms 52ms 192ms 353ms 0 transport_latency_assumed tick_size_change g 1,776 not meas. 76ms 92ms 504ms 867ms 0 transport_latency_assumed tick_size_change h 1,776 122 17ms 31ms 193ms 2.1s 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-11/05/2026-09-11T05.parquet sha256sum 2026-09-11T05.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.