Hour audit: 2026-10-03T05
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-03T05 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-03T05:00:00.000092195+00:00 · last event 2026-10-03T05:59:59.999887298+00:00
VOLUME 94,255,027 rows · 961,489,223 bytes (916.95 MiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured i: 94,165,987 · k: 94,164,714 · h: 94,142,793 · m: 94,136,865 · g: 94,039,226 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 344,320 (0.37%) · k: 3,054,764 (3.24%) · h: 602,046 (0.64%) · m: 90,221,668 (95.72%) · g: 32,229 (0.03%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 94,255,027 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 d01215209c5edc0902fdfeb842213612349d6fb9947a5a0088f2c4059e1ad592
the corpus checksum ledger names this file with the same digest
joined 94,257,015 to merged 94,255,027, minus 1,988 (minus 0.0021%)
boundary drops 1,988 · 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-03T07:42:06Z 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 8,928,612 103,272,717 0-34 d168202cf50d354b810abd236c7c04b61c7ddc041c496bc27cc181e213e37883 book 138,931 14,696,230 35-35 232911fcaf60a7db0c30454ed3f06b08b5c001ddcc5486c29c739fed9db87a99 last_trade_price 39,091 2,316,938 36-36 dae5f3fc5e633d81b596126663c6ce31f395552e5a9970ea52c55cd0c6cf544f market_resolved 765 115,477 37-37 832fdc684404a2c754fb21809c702959665b7b43b9a103e0dc7ad879de5fa173 new_market 1,630 159,118 38-38 9f0734dc17893e60d3b6f5bc112947754b163493d371f35655eb9c58d125e8b3 price_change 85,143,722 839,765,932 39-363 5dba3a6f9700b9be33b8aa6eff0b65d4f145830cd6bd52c061dc9c91b1519871 tick_size_change 2,276 84,661 364-364 b1a4646e4239a74052da368f856f97aaf4c6089c8c6ff3c0d84e6c5277924664 EVENT MIX count share price_change 85,143,722 90.33% best_bid_ask 8,928,612 9.47% book 138,931 0.15% last_trade_price 39,091 0.04% tick_size_change 2,276 <0.01% new_market 1,630 <0.01% market_resolved 765 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,928,784 8,928,612 172 186 FULL book 138,941 138,931 10 25,392 FULL last_trade_price 39,091 39,091 0 0 FULL market_resolved 765 765 0 0 FULL new_market 1,630 1,630 0 0 FULL price_change 85,145,528 85,143,722 1,806 237 FULL tick_size_change 2,276 2,276 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 8,925,800 745 77ms 94ms 349ms 32.4s 0 transport_latency_assumed best_bid_ask h 8,926,742 48,804 17ms 23ms 183ms 43.6s 0 transport_latency_assumed best_bid_ask i 8,927,295 25,542 21ms 26ms 102ms 6.1s 0 transport_latency_assumed best_bid_ask k 8,927,116 279,489 12ms 18ms 139ms 54.2s 0 transport_latency_assumed best_bid_ask m 8,926,637 8,574,032 4ms 8ms 53ms 5.9s 0 transport_latency_assumed book g 104,660 25,074 91ms 3.6h 24.5d 107.8d 0 book_staleness book h 83,477 4,577 21ms 77ms 8.3h 107.8d 0 book_staleness book i 91,157 11,489 23ms 1.2min 6.7d 107.8d 0 book_staleness book k 88,039 11,754 15ms 1.6s 1.2d 126.3d 0 book_staleness book m 91,583 86,037 6ms 1.5min 14.3d 126.3d 0 book_staleness last_trade_price g 38,887 2 80ms 202ms 2.6s 32.3s 0 transport_latency_assumed last_trade_price h 39,005 414 19ms 33ms 368ms 24.5s 0 transport_latency_assumed last_trade_price i 39,074 246 22ms 40ms 437ms 1.3s 0 transport_latency_assumed last_trade_price k 39,032 2,013 13ms 24ms 235ms 53.5s 0 transport_latency_assumed last_trade_price m 38,908 36,416 5ms 12ms 128ms 3.8s 0 transport_latency_assumed market_resolved g 711 18 81ms 349ms 44.3s 55.9s 0 transport_latency_assumed market_resolved h 711 1 19ms 22.5s 50.2s 50.3s 0 transport_latency_assumed market_resolved i 711 not meas. 23ms 17.5s 45.3s 57.4s 0 transport_latency_assumed market_resolved k 711 48 13ms 397ms 52.7s 52.8s 0 transport_latency_assumed market_resolved m 711 698 5ms 16.1s 56.1s 56.2s 0 transport_latency_assumed new_market g 1,044 158 285ms 17.5s 54.2s 1.7min 0 transport_latency_assumed new_market h 1,044 160 154ms 19.0s 52.3s 1.2min 0 transport_latency_assumed new_market i 1,044 299 93ms 17.2s 52.5s 1.8min 0 transport_latency_assumed new_market k 1,044 242 177ms 17.9s 54.6s 1.6min 0 transport_latency_assumed new_market m 1,044 771 51ms 22.1s 54.5s 1.3min 0 transport_latency_assumed price_change g 84,965,848 6,232 77ms 99ms 752ms 32.4s 0 transport_latency_assumed price_change h 85,089,538 548,090 18ms 24ms 254ms 43.7s 0 transport_latency_assumed price_change i 85,104,430 306,744 21ms 27ms 204ms 7.6s 0 transport_latency_assumed price_change k 85,106,496 2,761,190 12ms 20ms 184ms 54.2s 0 transport_latency_assumed price_change m 85,075,706 81,521,466 4ms 9ms 63ms 6.1s 0 transport_latency_assumed tick_size_change g 2,276 not meas. 77ms 93ms 429ms 990ms 0 transport_latency_assumed tick_size_change h 2,276 not meas. 18ms 23ms 733ms 2.8s 0 transport_latency_assumed tick_size_change i 2,276 not meas. 21ms 25ms 265ms 782ms 0 transport_latency_assumed tick_size_change k 2,276 28 12ms 19ms 250ms 769ms 0 transport_latency_assumed tick_size_change m 2,276 2,248 4ms 8ms 34ms 47ms 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-03/05/2026-10-03T05.parquet sha256sum 2026-10-03T05.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.