Hour audit: 2026-09-07T22
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-07T22 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-07T22:00:00.000020085+00:00 · last event 2026-09-07T22:59:59.999890332+00:00
VOLUME 92,327,976 rows · 919,914,241 bytes (877.30 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 92,308,714 · h: 92,306,699 · f: 92,275,758 · g: 92,257,413 · e: 92,219,436 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 86,110,593 (93.27%) · h: 5,771,565 (6.25%) · f: 127,596 (0.14%) · g: 19,960 (0.02%) · e: 298,262 (0.32%) (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 92,327,976 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 4b8d51a8984a812c931feb5f4cf439ebcc659c5e7467aa69c8e2cac4f33ebe15
the corpus checksum ledger names this file with the same digest
joined 92,330,632 to merged 92,327,976, minus 2,656 (minus 0.0029%)
boundary drops 2,656 · 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-07T23:54:21Z 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 11,034,490 118,686,525 0-42 bb0e5190536835c0e07b0bc7bc03722d3f6102c18b7ba778574016c797d845d3 book 127,044 12,454,709 43-43 517f212e4bb1103bec24d5ebf86c0cc76d6649b3ad67f95b8cd3651fa3cc95ce last_trade_price 53,987 3,062,380 44-44 3af98cbe2a6f447028a396e32fe3d16b7088471ccd0e936865e7fb51ba1711d6 market_resolved 1,602 252,961 45-45 56fedf366ff5a52a101f6c9d542ae0d4167553139d62d864e7a787554ecd6ece new_market 1,887 192,891 46-46 b7155ebe427c1b417cecf076907cd32818fb1fdf59484b5d78f77364de5cd459 price_change 81,106,634 784,122,152 47-356 0a10c9607630fe919dcb551f504555ba7962b6d854a4a9d224c10e547fff5406 tick_size_change 2,332 86,546 357-357 cecdb2af3eab788d0f41360aa1b34dcdfd9daa73abacd7b661c381d55390b0d0 EVENT MIX count share price_change 81,106,634 87.85% best_bid_ask 11,034,490 11.95% book 127,044 0.14% last_trade_price 53,987 0.06% tick_size_change 2,332 <0.01% new_market 1,887 <0.01% market_resolved 1,602 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,034,681 11,034,490 191 202 FULL book 127,048 127,044 4 5,707 FULL last_trade_price 53,990 53,987 3 1 FULL market_resolved 1,602 1,602 0 0 FULL new_market 1,887 1,887 0 0 FULL price_change 81,109,092 81,106,634 2,458 210 FULL tick_size_change 2,332 2,332 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,033,828 10,329,322 5ms 10ms 138ms 14.7s 0 transport_latency_assumed best_bid_ask e 11,032,458 35,563 39ms 44ms 195ms 8.3s 0 transport_latency_assumed best_bid_ask f 11,032,058 15,455 45ms 53ms 235ms 6.1s 0 transport_latency_assumed best_bid_ask g 11,030,905 1,409 83ms 105ms 499ms 13.0s 0 transport_latency_assumed best_bid_ask h 11,033,651 652,741 11ms 16ms 194ms 49.2s 0 transport_latency_assumed book c 112,924 103,070 7ms 26ms 2.2s 82.4d 0 book_staleness book e 113,920 2,637 40ms 178ms 4.9s 82.3d 0 book_staleness book f 113,752 2,145 48ms 269ms 5.0s 82.5d 0 book_staleness book g 122,213 10,199 98ms 3.0s 12.2h 82.5d 0 book_staleness book h 112,924 8,993 15ms 58ms 2.7s 11.3h 0 book_staleness last_trade_price c 53,960 49,459 10ms 42ms 255ms 5.0s 0 transport_latency_assumed last_trade_price e 53,958 292 45ms 141ms 1.7s 8.3s 0 transport_latency_assumed last_trade_price f 53,880 130 53ms 202ms 1.9s 5.0s 0 transport_latency_assumed last_trade_price g 53,849 7 103ms 488ms 5.5s 13.0s 0 transport_latency_assumed last_trade_price h 53,940 4,099 17ms 60ms 483ms 7.9s 0 transport_latency_assumed market_resolved c 1,566 1,486 5ms 13ms 88ms 482ms 0 transport_latency_assumed market_resolved e 1,566 36 43ms 196ms 48.6s 1.0min 0 transport_latency_assumed market_resolved f 1,566 1 48ms 208ms 48.7s 51.9s 0 transport_latency_assumed market_resolved g 1,566 not meas. 97ms 367ms 840ms 1.7s 0 transport_latency_assumed market_resolved h 1,566 79 14ms 42ms 137ms 29.0s 0 transport_latency_assumed new_market c 1,206 623 109ms 19.5s 34.9s 42.7min 0 transport_latency_assumed new_market e 1,206 318 131ms 18.4s 34.8s 8.8min 0 transport_latency_assumed new_market f 1,206 209 192ms 16.7s 42.1s 16.7min 0 transport_latency_assumed new_market g 1,206 151 303ms 19.0s 35.8s 4.5min 0 transport_latency_assumed new_market h 1,206 586 125ms 19.6s 34.8s 15.2min 0 transport_latency_assumed price_change c 81,102,898 75,624,448 5ms 11ms 150ms 15.3s 0 transport_latency_assumed price_change e 81,013,996 259,404 39ms 51ms 304ms 8.3s 0 transport_latency_assumed price_change f 81,070,964 109,656 46ms 61ms 394ms 6.4s 0 transport_latency_assumed price_change g 81,045,342 8,194 84ms 133ms 846ms 13.0s 0 transport_latency_assumed price_change h 81,101,080 5,104,932 12ms 18ms 207ms 49.3s 0 transport_latency_assumed tick_size_change c 2,332 2,185 5ms 10ms 141ms 251ms 0 transport_latency_assumed tick_size_change e 2,332 12 39ms 46ms 280ms 566ms 0 transport_latency_assumed tick_size_change f 2,332 not meas. 45ms 53ms 426ms 2.0s 0 transport_latency_assumed tick_size_change g 2,332 not meas. 83ms 102ms 579ms 2.8s 0 transport_latency_assumed tick_size_change h 2,332 135 12ms 16ms 151ms 3.4s 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-07/22/2026-09-07T22.parquet sha256sum 2026-09-07T22.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.