Hour audit: 2026-09-08T17
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-08T17 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-08T17:00:00.001573663+00:00 · last event 2026-09-08T17:59:59.999973865+00:00
VOLUME 102,979,645 rows · 1,095,099,882 bytes (1.02 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 102,169,663 · h: 102,162,764 · f: 102,161,649 · g: 102,122,210 · c: 94,267,953 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 971,230 (0.94%) · h: 11,676,350 (11.34%) · f: 309,990 (0.30%) · g: 51,559 (0.05%) · c: 89,970,516 (87.37%) (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,979,645 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 b432744fdb28a71783272fcb65f6097b9d1df45c6d87ec502165a5fcfba34f07
the corpus checksum ledger names this file with the same digest
joined 102,981,679 to merged 102,979,645, minus 2,034 (minus 0.0020%)
boundary drops 2,034 · 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-08T18:57:12Z 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,299,195 113,390,665 0-39 8ce9b7af9cd0a25252855d6c4abc00af773e1510f05f45c7733c5cf27cb179fb book 890,354 65,806,981 40-43 592835cd3d4011e228eac1af1e7c8163d96ff1178e3c9c630819665d0cd0afcd last_trade_price 65,560 3,745,184 44-44 740e5a35841aeb9cfb56274b8d236a55a71a7ebdcaa56e3b39554af9371cded7 market_resolved 1,008 131,893 45-45 bf4fce512e38f2f006f3248d99d071dfba99612de2197cec2ee2322a0d641b70 new_market 2,940 286,080 46-46 5e1b99140356a0ffbf5a15e2482e8c981cde07bf45f97999b3083b8ea557fc23 price_change 91,716,924 910,430,945 47-396 635c941c75fdd20555c874df19029876e5e1ab7597943cc7a5529d819e6b2619 tick_size_change 3,664 134,306 397-397 78afc085664d8cfa4c6779a81bbde418f5ee2fa2493433f5a4f913c8e700c012 EVENT MIX count share price_change 91,716,924 89.06% best_bid_ask 10,299,195 10.00% book 890,354 0.86% last_trade_price 65,560 0.06% tick_size_change 3,664 <0.01% new_market 2,940 <0.01% market_resolved 1,008 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,299,373 10,299,195 178 1,702 FULL book 890,386 890,354 32 181,181 FULL last_trade_price 65,560 65,560 0 170 FULL market_resolved 1,008 1,008 0 30 FULL new_market 2,940 2,940 0 0 FULL price_change 91,718,748 91,716,924 1,824 1,270 FULL tick_size_change 3,664 3,664 0 67 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,434,558 9,013,230 5ms 11ms 178ms 4.7s 0 transport_latency_assumed best_bid_ask e 10,295,976 94,307 39ms 49ms 250ms 11.7s 0 transport_latency_assumed best_bid_ask f 10,295,959 29,855 46ms 59ms 296ms 12.0s 0 transport_latency_assumed best_bid_ask g 10,293,441 3,034 84ms 114ms 529ms 17.8s 0 transport_latency_assumed best_bid_ask h 10,296,530 1,158,769 18ms 28ms 261ms 44.0s 0 transport_latency_assumed book c 866,522 856,102 9.8min 22.3h 30.8d 101.8d 0 book_staleness book e 137,725 3,723 42ms 254ms 4.3s 83.2d 0 book_staleness book f 138,063 1,996 49ms 313ms 5.8s 71.9d 0 book_staleness book g 152,190 9,784 95ms 7.3s 1.2d 83.3d 0 book_staleness book h 139,181 18,749 23ms 123ms 6.4min 83.2d 0 book_staleness last_trade_price c 59,248 56,298 10ms 46ms 284ms 4.9s 0 transport_latency_assumed last_trade_price e 65,454 772 47ms 206ms 2.1s 11.8s 0 transport_latency_assumed last_trade_price f 65,495 279 53ms 240ms 3.0s 12.0s 0 transport_latency_assumed last_trade_price g 65,213 171 99ms 383ms 4.5s 18.0s 0 transport_latency_assumed last_trade_price h 65,347 8,040 24ms 91ms 549ms 8.3s 0 transport_latency_assumed market_resolved c 908 875 6ms 6.0min 10.3min 11.7min 0 transport_latency_assumed market_resolved e 799 22 40ms 295ms 59.8s 59.9s 0 transport_latency_assumed market_resolved f 799 18 47ms 301ms 59.8s 59.9s 0 transport_latency_assumed market_resolved g 799 not meas. 87ms 409ms 1.3s 2.7s 0 transport_latency_assumed market_resolved h 799 93 19ms 110ms 369ms 1.1min 0 transport_latency_assumed new_market c 1,965 1,141 155ms 2.3min 7.5min 7.7min 0 transport_latency_assumed new_market e 1,811 486 212ms 43.4s 2.4min 2.5min 0 transport_latency_assumed new_market f 1,811 254 244ms 34.5s 2.3min 2.4min 0 transport_latency_assumed new_market g 1,811 344 334ms 28.9s 2.4min 2.5min 0 transport_latency_assumed new_market h 1,811 715 176ms 44.2s 2.4min 2.5min 0 transport_latency_assumed price_change c 83,901,356 80,039,560 5ms 13ms 189ms 5.2s 0 transport_latency_assumed price_change e 91,664,234 871,920 40ms 59ms 378ms 11.8s 0 transport_latency_assumed price_change f 91,655,858 277,588 46ms 70ms 451ms 12.1s 0 transport_latency_assumed price_change g 91,605,092 38,224 85ms 143ms 783ms 18.7s 0 transport_latency_assumed price_change h 91,655,432 10,489,632 18ms 33ms 284ms 51.7s 0 transport_latency_assumed tick_size_change c 3,396 3,310 5ms 10ms 46ms 245ms 0 transport_latency_assumed tick_size_change e 3,664 not meas. 40ms 51ms 182ms 444ms 0 transport_latency_assumed tick_size_change f 3,664 not meas. 46ms 62ms 232ms 472ms 0 transport_latency_assumed tick_size_change g 3,664 2 83ms 102ms 438ms 635ms 0 transport_latency_assumed tick_size_change h 3,664 352 18ms 34ms 108ms 817ms 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-08/17/2026-09-08T17.parquet sha256sum 2026-09-08T17.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.