Hour audit: 2026-09-22T02
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.
1 finding
- a machine expected this hour contributed nothing. Of the 5 machines expected to be capturing this hour, 1 contributed no rows: g. The hour is still whole on minutes; it simply rests on 4 machines rather than 5.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-22T02 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-22T02:00:00.002983238+00:00 · last event 2026-09-22T02:59:59.999986512+00:00
VOLUME 116,144,617 rows · 1,194,676,230 bytes (1.11 GiB) · 7 products, all holding rows
WITNESSES cefh — 4 machines contributed rows
captured c: 115,691,491 · h: 115,426,395 · e: 115,158,454 · f: 111,174,436 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 109,338,889 (94.14%) · h: 5,780,298 (4.98%) · e: 447,351 (0.39%) · f: 578,079 (0.50%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 116,144,617 rows exactly, so those pairs supplied none
5 expected (cefgh), 1 contributed nothing: g
INTEGRITY sha256 aecfec6d4e86eb07cf8228fbc88583c23c583a2374ce9f2cb46a9e2f49dc9536
the corpus checksum ledger names this file with the same digest
joined 116,145,835 to merged 116,144,617, minus 1,218 (minus 0.0010%)
boundary drops 1,218 · 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-22T03:56:30Z as cefh
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 7/8 pass, 1 finding
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
FINDING a machine expected this hour contributed nothing
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,285,768 126,829,918 0-43 e751d7fd6452b946118c5d734df8785005b61f3c38597a909d51375d8dbf6025 book 575,703 51,799,349 44-46 ca671f4342190392d595865dc5adfab9b621a558a9ec340640e2796d71b8be27 last_trade_price 48,497 2,718,539 47-47 5c6c6c46e74f69bed9bff2faab08eccf15300dc8bbf12571a62ad94dcca52edb market_resolved 1,077 162,362 48-48 6d0331d877077c26cc9a0568cdcd80f732f0df2030ed33f7ae17a40c0b740cd6 new_market 1,054 115,357 49-49 deda14b5d7047824cde8fb873531716eae6717bc718c32e63be84bab496dbbf5 price_change 104,228,738 1,011,591,663 50-447 022602d9ddaaf00a1aad86aedbacbc547fc3e08ec7ea3ff579a665a4cffe19e3 tick_size_change 3,780 136,240 448-448 5dd32b5ada34e86715a026909e250e9d24bdfe61f77c6dd6beedc057d942c2f5 EVENT MIX count share price_change 104,228,738 89.74% best_bid_ask 11,285,768 9.72% book 575,703 0.50% last_trade_price 48,497 0.04% tick_size_change 3,780 <0.01% market_resolved 1,077 <0.01% new_market 1,054 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,285,891 11,285,768 123 72,062 PARTIAL book 575,747 575,703 44 176,289 PARTIAL last_trade_price 48,498 48,497 1 2,819 PARTIAL market_resolved 1,077 1,077 0 1,000 PARTIAL new_market 1,054 1,054 0 740 PARTIAL price_change 104,229,788 104,228,738 1,050 125,627 PARTIAL tick_size_change 3,780 3,780 0 945 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,284,569 10,722,517 5ms 13ms 96ms 12.3s 0 transport_latency_assumed best_bid_ask e 11,283,897 36,381 42ms 53ms 167ms 8.7s 0 transport_latency_assumed best_bid_ask f 10,851,656 15,338 47ms 59ms 177ms 9.4s 0 transport_latency_assumed best_bid_ask h 11,282,638 511,532 17ms 31ms 123ms 46.6s 0 transport_latency_assumed book c 188,355 147,069 76ms 6.2h 30.5d 115.2d 0 book_staleness book e 124,699 19,351 45ms 10.8min 14.7d 113.6d 0 book_staleness book f 485,911 386,459 3.6min 2.5d 41.1d 115.2d 0 book_staleness book h 123,371 22,824 22ms 13.1min 14.7d 115.2d 0 book_staleness last_trade_price c 48,347 45,018 5ms 23ms 167ms 1.4s 0 transport_latency_assumed last_trade_price e 48,328 232 44ms 103ms 4.3s 8.7s 0 transport_latency_assumed last_trade_price f 46,190 124 50ms 113ms 3.9s 9.3s 0 transport_latency_assumed last_trade_price h 48,302 3,123 18ms 48ms 242ms 6.4s 0 transport_latency_assumed market_resolved c 1,000 943 5ms 14ms 46.5s 55.2s 0 transport_latency_assumed market_resolved e 1,000 38 43ms 178ms 57.1s 57.1s 0 transport_latency_assumed market_resolved f 1,009 33 48ms 194ms 5.9min 6.0min 0 transport_latency_assumed market_resolved h 1,000 63 18ms 91ms 57.0s 57.1s 0 transport_latency_assumed new_market c 740 485 108ms 21.8s 54.2s 1.7min 0 transport_latency_assumed new_market e 740 80 200ms 22.2s 54.3s 1.8min 0 transport_latency_assumed new_market f 740 120 172ms 22.6s 54.7s 1.4min 0 transport_latency_assumed new_market h 740 369 130ms 14.1s 42.5s 2.0min 0 transport_latency_assumed price_change c 104,164,700 98,419,153 5ms 16ms 108ms 12.3s 0 transport_latency_assumed price_change e 103,696,010 391,269 42ms 61ms 281ms 8.7s 0 transport_latency_assumed price_change f 99,785,322 176,005 48ms 66ms 279ms 9.4s 0 transport_latency_assumed price_change h 103,966,564 5,242,311 17ms 35ms 165ms 46.6s 0 transport_latency_assumed tick_size_change c 3,780 3,704 5ms 8ms 41ms 260ms 0 transport_latency_assumed tick_size_change e 3,780 not meas. 42ms 62ms 103ms 132ms 0 transport_latency_assumed tick_size_change f 3,608 not meas. 47ms 54ms 131ms 268ms 0 transport_latency_assumed tick_size_change h 3,780 76 17ms 29ms 98ms 216ms 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-22/02/2026-09-22T02.parquet sha256sum 2026-09-22T02.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.