Hour audit: 2026-10-03T11
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-03T11 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-03T11:00:00.000074324+00:00 · last event 2026-10-03T11:59:59.999984359+00:00
VOLUME 111,005,258 rows · 1,147,145,758 bytes (1.07 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured k: 110,941,091 · h: 110,902,512 · i: 110,901,022 · m: 110,898,269 · g: 110,856,216 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 3,810,500 (3.43%) · h: 953,112 (0.86%) · i: 547,977 (0.49%) · m: 105,652,715 (95.18%) · g: 40,954 (0.04%) (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 111,005,258 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 f294bbec023d357ff69dd20708d540247443f2e491dd62e97de6496ef1dfc598
the corpus checksum ledger names this file with the same digest
joined 111,007,182 to merged 111,005,258, minus 1,924 (minus 0.0017%)
boundary drops 1,924 · 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-03T13:46:15Z 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,649,909 115,858,997 0-36 3e050a768c1623771c7a4ee59db8c6c858e006df26f2674b5500f53dc7ad5af9 book 115,717 12,436,853 37-37 bd92298e39ff9d7f96d30328ded688aa54e0ae0241cf585277139c8e7a7012f7 last_trade_price 47,822 2,789,805 38-38 e67e4f678183524125dc8e1698d2660b485f9e4d119839239309bde00f88fa54 market_resolved 820 121,191 39-39 af9d566f66b04ab718089c86bc889b63540c8396747fa4550f5c99d2ea4281f3 new_market 2,312 221,097 40-40 ac56889ebe5189be9ce23250432a6725cf44b75ae3e68359170635c98e102549 price_change 101,184,750 1,014,309,020 41-426 ffe3bf8fabe22754f4003c5059dfee7b7e73ced85005a699bd5fa32470720c8e tick_size_change 3,928 144,128 427-427 a821d792566690ee5bb51352784eefcdfdddc1587efa79b904d5d266344cd24b EVENT MIX count share price_change 101,184,750 91.15% best_bid_ask 9,649,909 8.69% book 115,717 0.10% last_trade_price 47,822 0.04% tick_size_change 3,928 <0.01% new_market 2,312 <0.01% market_resolved 820 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,650,136 9,649,909 227 112 FULL book 115,719 115,717 2 7,038 FULL last_trade_price 47,823 47,822 1 0 FULL market_resolved 820 820 0 0 FULL new_market 2,312 2,312 0 0 FULL price_change 101,186,444 101,184,750 1,694 381 FULL tick_size_change 3,928 3,928 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,647,091 968 78ms 99ms 498ms 40.3s 0 transport_latency_assumed best_bid_ask h 9,649,194 79,266 18ms 25ms 268ms 52.4s 0 transport_latency_assumed best_bid_ask i 9,649,033 44,827 20ms 26ms 146ms 29.9s 0 transport_latency_assumed best_bid_ask k 9,648,987 323,548 13ms 23ms 218ms 51.1s 0 transport_latency_assumed best_bid_ask m 9,649,353 9,201,300 4ms 10ms 67ms 7.2s 0 transport_latency_assumed book g 108,678 11,715 88ms 10.6s 4.0d 108.0d 0 book_staleness book h 99,147 2,398 22ms 65ms 9.0s 107.9d 0 book_staleness book i 100,095 3,196 23ms 80ms 28.0min 107.9d 0 book_staleness book k 99,079 5,010 17ms 49ms 8.4s 107.9d 0 book_staleness book m 99,859 93,398 6ms 23ms 3.9min 1.7d 0 book_staleness last_trade_price g 47,418 5 84ms 244ms 5.6s 40.3s 0 transport_latency_assumed last_trade_price h 47,773 539 19ms 40ms 523ms 13.1s 0 transport_latency_assumed last_trade_price i 47,708 266 22ms 45ms 414ms 3.6s 0 transport_latency_assumed last_trade_price k 47,736 2,220 14ms 31ms 325ms 13.6s 0 transport_latency_assumed last_trade_price m 47,735 44,792 6ms 14ms 129ms 2.4s 0 transport_latency_assumed market_resolved g 743 not meas. 81ms 323ms 50.7s 50.8s 0 transport_latency_assumed market_resolved h 743 20 20ms 69ms 45.1s 45.2s 0 transport_latency_assumed market_resolved i 743 10 22ms 37.5s 56.9s 57.9s 0 transport_latency_assumed market_resolved k 743 85 15ms 48ms 50.7s 50.8s 0 transport_latency_assumed market_resolved m 743 705 6ms 37.1s 57.3s 58.0s 0 transport_latency_assumed new_market g 1,400 216 300ms 30.4s 43.0s 1.4min 0 transport_latency_assumed new_market h 1,400 245 172ms 25.2s 42.9s 1.7min 0 transport_latency_assumed new_market i 1,400 612 101ms 27.8s 42.5s 1.6min 0 transport_latency_assumed new_market k 1,400 236 227ms 27.3s 42.8s 1.7min 0 transport_latency_assumed new_market m 1,400 1,003 75ms 30.4s 40.4s 1.8min 0 transport_latency_assumed price_change g 101,046,958 28,050 79ms 112ms 1.1s 40.3s 0 transport_latency_assumed price_change h 101,100,327 870,608 18ms 27ms 331ms 55.9s 0 transport_latency_assumed price_change i 101,098,115 499,050 20ms 29ms 240ms 30.7s 0 transport_latency_assumed price_change k 101,139,218 3,479,161 13ms 24ms 246ms 54.7s 0 transport_latency_assumed price_change m 101,095,251 96,307,881 5ms 10ms 73ms 7.2s 0 transport_latency_assumed tick_size_change g 3,928 not meas. 79ms 110ms 487ms 1.1s 0 transport_latency_assumed tick_size_change h 3,928 36 18ms 32ms 183ms 3.4s 0 transport_latency_assumed tick_size_change i 3,928 16 20ms 34ms 80ms 267ms 0 transport_latency_assumed tick_size_change k 3,928 240 13ms 24ms 119ms 3.6s 0 transport_latency_assumed tick_size_change m 3,928 3,636 5ms 12ms 50ms 190ms 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/11/2026-10-03T11.parquet sha256sum 2026-10-03T11.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.