Hour audit: 2026-10-01T15
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-10-01T15 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-01T15:00:00.000074355+00:00 · last event 2026-10-01T15:59:59.999992415+00:00
VOLUME 117,023,289 rows · 1,265,737,659 bytes (1.18 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured i: 116,079,743 · k: 116,009,902 · m: 116,008,399 · h: 116,006,757 · g: 104,935,464 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 314,047 (0.27%) · k: 2,496,310 (2.13%) · m: 112,809,484 (96.40%) · h: 493,270 (0.42%) · g: 910,178 (0.78%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 117,023,289 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 b6d5dbb7f611a4397018c0f140606efa056567cbd3c0e55e0866f13b899910ce
the corpus checksum ledger names this file with the same digest
joined 117,026,966 to merged 117,023,289, minus 3,677 (minus 0.0031%)
boundary drops 3,677 · 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-10-01T18:10:25Z as ghikm
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 status feed unobserved for this hour. Our incident register was last checked against the venue's feed at 2026-09-23T20:35Z, before this hour ended, so nothing has looked yet. This is a could-not-look and never an all-clear.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,407,750 111,869,398 0-35 0400976760928b7e2052f34600611466755729150799c04456bd455af6b69c7c book 1,143,731 75,863,494 36-40 b5f730a30a2a192bc6fe32128d6d2abff59934f105c897bc5a7ab4472c367258 last_trade_price 64,133 3,660,467 41-41 075af7e411516fbb4ed0afd5314bfb401e62d058f9b8f37c1dbb919ef36e209c market_resolved 866 116,231 42-42 6374142f7b3a2cd2bd9e9a2f16808c7ef6943278e15dd14bbc6ff1f55ff76208 new_market 1,519 133,845 43-43 2b765ba56eaa3a7f4493fc88329195de16f3756dcd828331a36f0a3395d34924 price_change 106,402,198 1,072,647,198 44-449 26c19737723e5110abf36be7c423cc4c56c6aa6574db306fc80dd09c7ac4e1f7 tick_size_change 3,092 114,192 450-450 f489b6f93aa5e95e1ea516d267dc9f7acf0e020ccec2ecef0a74c631003f8c52 EVENT MIX count share price_change 106,402,198 90.92% best_bid_ask 9,407,750 8.04% book 1,143,731 0.98% last_trade_price 64,133 0.05% tick_size_change 3,092 <0.01% new_market 1,519 <0.01% market_resolved 866 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,407,967 9,407,750 217 3,258 FULL book 1,145,449 1,143,731 1,718 226,989 FULL last_trade_price 64,133 64,133 0 197 FULL market_resolved 866 866 0 6 FULL new_market 1,519 1,519 0 0 FULL price_change 106,403,940 106,402,198 1,742 2,381 FULL tick_size_change 3,092 3,092 0 44 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 8,447,917 2,701 74ms 90ms 212ms 7.4s 0 transport_latency_assumed best_bid_ask h 9,405,676 37,624 19ms 33ms 186ms 46.4s 0 transport_latency_assumed best_bid_ask i 9,405,389 19,635 24ms 42ms 103ms 20.0s 0 transport_latency_assumed best_bid_ask k 9,406,052 187,113 14ms 22ms 123ms 7.8s 0 transport_latency_assumed best_bid_ask m 9,406,836 9,160,677 5ms 9ms 53ms 3.3s 0 transport_latency_assumed book g 1,067,257 880,306 1.0h 3.6d 40.1d 124.7d 0 book_staleness book h 172,532 28,050 28ms 7.3h 24.2d 124.7d 0 book_staleness book i 225,544 75,269 45ms 22.1h 28.9d 124.7d 0 book_staleness book k 161,004 16,698 18ms 1.7h 22.3d 106.2d 0 book_staleness book m 166,852 143,408 7ms 2.7h 12.1d 106.2d 0 book_staleness last_trade_price g 56,048 5 76ms 122ms 515ms 7.3s 0 transport_latency_assumed last_trade_price h 64,098 215 21ms 35ms 247ms 29.4s 0 transport_latency_assumed last_trade_price i 64,099 110 31ms 45ms 148ms 19.4s 0 transport_latency_assumed last_trade_price k 64,103 1,363 15ms 24ms 130ms 5.8s 0 transport_latency_assumed last_trade_price m 64,106 62,440 6ms 10ms 61ms 3.1s 0 transport_latency_assumed market_resolved g 768 129 79ms 5.8min 12.1min 13.1min 0 transport_latency_assumed market_resolved h 701 3 21ms 57ms 48.6s 52.0s 0 transport_latency_assumed market_resolved i 701 22 38ms 78ms 37.8s 41.9s 0 transport_latency_assumed market_resolved k 701 46 15ms 29ms 202ms 56.6s 0 transport_latency_assumed market_resolved m 701 666 5ms 11ms 37.7s 41.0s 0 transport_latency_assumed new_market g 1,259 257 207ms 6.6min 6.9min 8.2min 0 transport_latency_assumed new_market h 838 246 150ms 42.9s 1.9min 2.4min 0 transport_latency_assumed new_market i 838 271 140ms 46.8s 2.1min 2.4min 0 transport_latency_assumed new_market k 838 263 133ms 24.6s 2.0min 2.3min 0 transport_latency_assumed new_market m 838 482 84ms 32.0s 1.9min 2.4min 0 transport_latency_assumed price_change g 95,359,299 26,780 75ms 92ms 296ms 7.4s 0 transport_latency_assumed price_change h 106,359,820 427,120 20ms 33ms 224ms 46.4s 0 transport_latency_assumed price_change i 106,380,080 218,736 25ms 43ms 113ms 20.0s 0 transport_latency_assumed price_change k 106,374,112 2,290,762 14ms 22ms 123ms 12.8s 0 transport_latency_assumed price_change m 106,365,974 103,438,800 5ms 10ms 57ms 3.3s 0 transport_latency_assumed tick_size_change g 2,916 not meas. 76ms 97ms 202ms 398ms 0 transport_latency_assumed tick_size_change h 3,092 12 20ms 32ms 46ms 237ms 0 transport_latency_assumed tick_size_change i 3,092 4 24ms 42ms 76ms 139ms 0 transport_latency_assumed tick_size_change k 3,092 65 14ms 20ms 49ms 119ms 0 transport_latency_assumed tick_size_change m 3,092 3,011 5ms 9ms 50ms 182ms 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-10-01/15/2026-10-01T15.parquet sha256sum 2026-10-01T15.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.