Hour audit: 2026-09-06T03
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-06T03 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-06T03:00:00.064762323+00:00 · last event 2026-09-06T03:59:59.999999052+00:00
VOLUME 125,246,238 rows · 1,278,117,725 bytes (1.19 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 124,209,320 · e: 124,124,041 · f: 119,656,786 · c: 114,593,173 · g: 114,436,349 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 7,234 (0.01%) · e: 3,759,915 (3.00%) · f: 6,800,805 (5.43%) · c: 248,225 (0.20%) · g: 114,430,059 (91.36%) (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 125,246,238 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 f9c878276bb060f3fa9889bbedaaeda59dfab99a6e1ecd3ab875cf78bb00875a
the corpus checksum ledger names this file with the same digest
joined 125,252,845 to merged 125,246,238, minus 6,607 (minus 0.0053%)
boundary drops 6,607 · 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-06T07:12:46Z 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 12,164,892 129,470,790 0-46 7000326124185e5018cf064c73cdd155d6397ad7645924f60cee73ee9ab05458 book 1,126,347 68,504,123 47-51 b2b87af707582befc4543e3ddf3034c508ec308678d66dd16dc26cd442e20d66 last_trade_price 45,409 2,674,143 52-52 be955a7ed0e11bcabcc2582f6d75a9eee412edf73feff2a63287035a8b86f450 market_resolved 5,969 716,881 53-53 8fd07dfd55ec51f0206c5f2d0426cbb8eaf27e7c926e496121d738711b61ff10 new_market 477 56,117 54-54 489d78f2ef138a18afdf5aa6a8376e7b76c08a147e418b0bb5668e71620ac3c5 price_change 111,896,592 1,075,035,070 55-481 9a8b234d4f174345d888c408bc22edf3cd56d3622ea05ed4d49375296b79dfee tick_size_change 6,552 237,096 482-482 3cbebe8bc7f2385732c58c036c4bfdb274d21d25a21705188bcd5bc7c4aae6a9 EVENT MIX count share price_change 111,896,592 89.34% best_bid_ask 12,164,892 9.71% book 1,126,347 0.90% last_trade_price 45,409 0.04% tick_size_change 6,552 <0.01% market_resolved 5,969 <0.01% new_market 477 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,165,262 12,164,892 370 1,776 FULL book 1,129,226 1,126,347 2,879 175,205 FULL last_trade_price 45,411 45,409 2 276 FULL market_resolved 5,969 5,969 0 95 FULL new_market 477 477 0 9 FULL price_change 111,899,948 111,896,592 3,356 1,074 FULL tick_size_change 6,552 6,552 0 372 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,156,486 269 4ms 7ms 45ms 845ms 0 transport_latency_assumed best_bid_ask e 12,163,442 368,549 40ms 45ms 96ms 1.1s 0 transport_latency_assumed best_bid_ask f 11,680,410 661,077 48ms 53ms 117ms 1.1s 0 transport_latency_assumed best_bid_ask g 11,134,818 11,134,448 81ms 97ms 200ms 8.8s 0 transport_latency_assumed best_bid_ask h 12,164,575 549 17ms 37ms 85ms 7.9s 0 transport_latency_assumed book c 799,178 244,869 12.3min 13.2h 34.6d 99.2d 0 book_staleness book e 106,525 6,970 43ms 34.3s 1.1d 80.7d 0 book_staleness book f 453,749 74,599 4.2min 12.6h 34.4d 99.2d 0 book_staleness book g 801,603 799,041 12.2min 13.3h 34.6d 99.2d 0 book_staleness book h 95,161 868 21ms 67ms 9.0min 80.6d 0 book_staleness last_trade_price c 40,956 1 10ms 42ms 238ms 4.9s 0 transport_latency_assumed last_trade_price e 45,359 1,387 46ms 82ms 331ms 5.0s 0 transport_latency_assumed last_trade_price f 43,544 2,614 54ms 94ms 346ms 5.0s 0 transport_latency_assumed last_trade_price g 41,408 41,406 92ms 136ms 457ms 6.8s 0 transport_latency_assumed last_trade_price h 45,389 1 24ms 69ms 294ms 7.9s 0 transport_latency_assumed market_resolved c 4,718 468 4ms 4.6min 9.4min 10.0min 0 transport_latency_assumed market_resolved e 4,291 154 46ms 121ms 311ms 31.5s 0 transport_latency_assumed market_resolved f 4,368 344 56ms 166ms 5.5min 5.7min 0 transport_latency_assumed market_resolved g 5,003 5,003 128ms 7.2min 12.5min 13.3min 0 transport_latency_assumed market_resolved h 4,291 not meas. 32ms 66ms 130ms 29.5s 0 transport_latency_assumed new_market c 361 8 42ms 14.8s 1.3h 5.9h 0 transport_latency_assumed new_market e 362 32 92ms 21.4s 30.1s 1.0min 0 transport_latency_assumed new_market f 364 39 77ms 254ms 24.0s 3.2h 0 transport_latency_assumed new_market g 386 386 143ms 23.3s 3.3h 5.1h 0 transport_latency_assumed new_market h 362 12 54ms 292ms 25.4s 28.6s 0 transport_latency_assumed price_change c 102,585,954 2,610 4ms 8ms 50ms 1.4s 0 transport_latency_assumed price_change e 111,797,510 3,382,615 41ms 46ms 112ms 1.3s 0 transport_latency_assumed price_change f 107,468,059 6,061,768 48ms 54ms 128ms 1.4s 0 transport_latency_assumed price_change g 102,447,151 102,443,795 82ms 98ms 219ms 9.0s 0 transport_latency_assumed price_change h 111,892,990 5,804 17ms 39ms 88ms 8.7s 0 transport_latency_assumed tick_size_change c 5,520 not meas. 4ms 7ms 25ms 87ms 0 transport_latency_assumed tick_size_change e 6,552 208 41ms 46ms 115ms 226ms 0 transport_latency_assumed tick_size_change f 6,292 364 48ms 53ms 100ms 304ms 0 transport_latency_assumed tick_size_change g 5,980 5,980 81ms 96ms 158ms 390ms 0 transport_latency_assumed tick_size_change h 6,552 not meas. 18ms 49ms 88ms 524ms 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/03/2026-09-06T03.parquet sha256sum 2026-09-06T03.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.