Hour audit: 2026-09-28T07
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-28T07 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-28T07:00:00.000017902+00:00 · last event 2026-09-28T07:59:59.999774258+00:00
VOLUME 103,530,946 rows · 1,084,316,198 bytes (1.01 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured k: 103,412,731 · g: 103,121,571 · h: 102,480,318 · c: 101,228,967 · i: 100,768,222 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 5,814,818 (5.62%) · g: 18,832 (0.02%) · h: 795,755 (0.77%) · c: 83,913,308 (81.05%) · i: 12,988,233 (12.55%) (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 103,530,946 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 22407b2a8cbb6f2f8c2c82fa3428c8a11e3646bf6c58643cfc5f9d58d7c554ff
the corpus checksum ledger names this file with the same digest
joined 103,532,544 to merged 103,530,946, minus 1,598 (minus 0.0015%)
boundary drops 1,598 · 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-28T09:36:38Z as cghik
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 10,203,306 116,802,935 0-38 d733b7f63b752f3319c73ee90ad9259f1573b25de5fcac0c70d74728fe114436 book 155,457 14,187,844 39-39 c2631d66227ee847401b6ff86f82196b5baf51c4ecb2f2b3ae4389067092f237 last_trade_price 49,313 2,844,135 40-40 e5a4136d944d73ca95fe1b2d7e7f757e055ae896e1d162fbb5bd4a7519085bf3 market_resolved 1,677 269,029 41-41 5460ed0588df0478ce376830b175aeecc2eefe97086de76fc55eab03bd4dc7cb new_market 1,101 116,708 42-42 4dfa24f9896eafc775e9c51f7cc3f0e3ea9249e27e6136729cb18955e6fd38a5 price_change 93,117,372 948,813,922 43-398 1d5730b42b42f3e4fbcc44db57882daf8f1c24278a866983fa962aba4188f949 tick_size_change 2,720 101,405 399-399 2e28bc81700248eb575695d467dfd82b9097843f117957dc992d98207bc6769b EVENT MIX count share price_change 93,117,372 89.94% best_bid_ask 10,203,306 9.86% book 155,457 0.15% last_trade_price 49,313 0.05% tick_size_change 2,720 <0.01% market_resolved 1,677 <0.01% new_market 1,101 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,203,480 10,203,306 174 2,214 FULL book 155,475 155,457 18 8,733 FULL last_trade_price 49,313 49,313 0 126 FULL market_resolved 1,677 1,677 0 52 FULL new_market 1,101 1,101 0 0 FULL price_change 93,118,778 93,117,372 1,406 4,249 FULL tick_size_change 2,720 2,720 0 38 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,997,091 8,344,805 5ms 12ms 113ms 7.9s 0 transport_latency_assumed best_bid_ask g 10,196,386 742 78ms 99ms 393ms 29.9s 0 transport_latency_assumed best_bid_ask h 10,166,878 66,214 19ms 34ms 256ms 1.1min 0 transport_latency_assumed best_bid_ask i 9,964,786 1,279,078 15ms 30ms 92ms 4.0s 0 transport_latency_assumed best_bid_ask k 10,201,491 512,467 12ms 19ms 105ms 9.5s 0 transport_latency_assumed book c 100,184 82,962 7ms 41ms 19.2h 102.9d 0 book_staleness book g 105,060 6,564 85ms 4.2s 3.4d 102.9d 0 book_staleness book h 134,721 39,771 35ms 3.8h 1.2d 102.9d 0 book_staleness book i 99,774 12,895 23ms 116ms 9.7h 102.9d 0 book_staleness book k 106,060 13,265 15ms 105ms 1.2d 102.9d 0 book_staleness last_trade_price c 47,606 39,909 6ms 20ms 236ms 3.3s 0 transport_latency_assumed last_trade_price g 47,978 19 84ms 556ms 11.3s 30.0s 0 transport_latency_assumed last_trade_price h 47,329 449 21ms 92ms 569ms 45.5s 0 transport_latency_assumed last_trade_price i 47,871 4,760 20ms 73ms 547ms 2.1s 0 transport_latency_assumed last_trade_price k 49,126 4,176 13ms 35ms 259ms 8.1s 0 transport_latency_assumed market_resolved c 1,582 1,330 5ms 46ms 43.2s 2.5min 0 transport_latency_assumed market_resolved g 1,596 39 78ms 216ms 49.3s 55.8s 0 transport_latency_assumed market_resolved h 1,596 12 19ms 88ms 48.3s 48.4s 0 transport_latency_assumed market_resolved i 1,562 216 26ms 10.3s 1.8min 2.5min 0 transport_latency_assumed market_resolved k 1,596 80 13ms 41ms 49.0s 49.1s 0 transport_latency_assumed new_market c 749 379 113ms 16.8s 29.9s 1.6min 0 transport_latency_assumed new_market g 749 60 302ms 12.7s 28.4s 33.9s 0 transport_latency_assumed new_market h 749 191 158ms 17.2s 38.6s 1.7min 0 transport_latency_assumed new_market i 749 311 105ms 16.8s 38.0s 1.4min 0 transport_latency_assumed new_market k 749 160 165ms 18.2s 38.6s 1.6min 0 transport_latency_assumed price_change c 91,079,099 75,441,686 5ms 14ms 132ms 8.1s 0 transport_latency_assumed price_change g 92,767,082 11,408 78ms 125ms 2.4s 31.3s 0 transport_latency_assumed price_change h 92,126,325 689,113 19ms 43ms 333ms 1.1min 0 transport_latency_assumed price_change i 90,650,848 11,690,588 16ms 31ms 173ms 5.6s 0 transport_latency_assumed price_change k 93,050,989 5,284,577 12ms 22ms 133ms 10.0s 0 transport_latency_assumed tick_size_change c 2,656 2,237 5ms 8ms 70ms 604ms 0 transport_latency_assumed tick_size_change g 2,720 not meas. 76ms 90ms 193ms 349ms 0 transport_latency_assumed tick_size_change h 2,720 5 19ms 25ms 61ms 340ms 0 transport_latency_assumed tick_size_change i 2,632 385 13ms 29ms 44ms 81ms 0 transport_latency_assumed tick_size_change k 2,720 93 12ms 16ms 40ms 105ms 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-28/07/2026-09-28T07.parquet sha256sum 2026-09-28T07.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.