Hour audit: 2026-09-28T05
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-28T05 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-28T05:00:00.000043136+00:00 · last event 2026-09-28T05:59:59.999952927+00:00
VOLUME 98,788,798 rows · 998,740,870 bytes (952.47 MiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured i: 98,717,145 · k: 98,707,038 · c: 98,706,297 · h: 98,620,577 · g: 98,344,773 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 1,350,942 (1.37%) · k: 5,431,911 (5.50%) · c: 90,693,523 (91.81%) · h: 1,298,071 (1.31%) · g: 14,351 (0.01%) (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 98,788,798 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 b032b68f77eb1c47c22017cbceba9af5557f6b0e729e2aa7bb30b3d0e0b8c9bb
the corpus checksum ledger names this file with the same digest
joined 98,790,829 to merged 98,788,798, minus 2,031 (minus 0.0021%)
boundary drops 2,031 · 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-28T07:39:25Z 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,257,551 113,535,396 0-39 f6fca10c09d0fe18ef98776010aba58e6cdf0e7eabcd9d6d4ae55c22a4ed3221 book 112,824 11,583,441 40-40 b32996c2975980f7b7327d881e27bbc21ed91c33c1e67c8d28b3f4e0075fbb9f last_trade_price 42,903 2,491,467 41-41 41998d232d270ffba3d07b5256053859d68f9305e8a3c123e65d38b03952b7be market_resolved 1,233 193,508 42-42 bcfec427cb96ac27d904e4007a73c18a508106c49f55a4767955a03ffd5f8599 new_market 1,406 147,587 43-43 74cd29508aac3a9641f35c4c49fbe1ae68c3aca95a05aadfe8161f30862e052d price_change 88,370,793 869,582,835 44-381 7fb42bc53b49bcbe08884840f5b378217f0bb538534db8e32346cac945e9c9d2 tick_size_change 2,088 77,111 382-382 feda5057bebd97ecd6b7cd0ab55d7acbbf79271f8f00454101a5be54780e92a7 EVENT MIX count share price_change 88,370,793 89.45% best_bid_ask 10,257,551 10.38% book 112,824 0.11% last_trade_price 42,903 0.04% tick_size_change 2,088 <0.01% new_market 1,406 <0.01% market_resolved 1,233 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,257,772 10,257,551 221 198 FULL book 112,824 112,824 0 7,185 FULL last_trade_price 42,903 42,903 0 0 FULL market_resolved 1,237 1,233 4 4 FULL new_market 1,406 1,406 0 0 FULL price_change 88,372,599 88,370,793 1,806 404 FULL tick_size_change 2,088 2,088 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,256,101 9,523,387 5ms 11ms 96ms 3.9s 0 transport_latency_assumed best_bid_ask g 10,248,394 531 77ms 96ms 386ms 32.4s 0 transport_latency_assumed best_bid_ask h 10,254,676 107,982 18ms 24ms 149ms 31.4s 0 transport_latency_assumed best_bid_ask i 10,255,196 121,496 22ms 28ms 93ms 2.1s 0 transport_latency_assumed best_bid_ask k 10,255,394 504,155 12ms 19ms 117ms 55.8s 0 transport_latency_assumed book c 95,261 84,139 7ms 212ms 3.3d 102.8d 0 book_staleness book g 93,864 7,106 83ms 762ms 3.3d 102.7d 0 book_staleness book h 92,019 7,265 21ms 119ms 1.1d 102.6d 0 book_staleness book i 90,488 4,595 24ms 84ms 15.2h 102.7d 0 book_staleness book k 91,709 9,719 15ms 85ms 1.1d 102.7d 0 book_staleness last_trade_price c 42,819 38,331 6ms 22ms 200ms 2.3s 0 transport_latency_assumed last_trade_price g 42,196 13 81ms 202ms 1.1s 32.0s 0 transport_latency_assumed last_trade_price h 42,611 838 19ms 42ms 304ms 9.8s 0 transport_latency_assumed last_trade_price i 42,752 690 23ms 46ms 364ms 2.1s 0 transport_latency_assumed last_trade_price k 42,806 3,031 14ms 32ms 268ms 4.9s 0 transport_latency_assumed market_resolved c 1,207 1,082 5ms 21ms 51.8s 53.8s 0 transport_latency_assumed market_resolved g 1,207 3 78ms 224ms 50.9s 55.1s 0 transport_latency_assumed market_resolved h 1,203 15 18ms 69ms 51.2s 54.2s 0 transport_latency_assumed market_resolved i 1,203 81 22ms 85ms 49.2s 55.9s 0 transport_latency_assumed market_resolved k 1,207 52 13ms 40ms 43.6s 57.6s 0 transport_latency_assumed new_market c 986 497 88ms 1.0min 1.6min 1.9min 0 transport_latency_assumed new_market g 986 84 317ms 43.8s 1.5min 1.9min 0 transport_latency_assumed new_market h 986 271 148ms 38.1s 1.6min 1.9min 0 transport_latency_assumed new_market i 986 411 96ms 30.2s 1.6min 1.9min 0 transport_latency_assumed new_market k 986 143 179ms 30.6s 1.5min 1.9min 0 transport_latency_assumed price_change c 88,307,835 81,044,262 5ms 13ms 114ms 4.6s 0 transport_latency_assumed price_change g 87,956,038 6,614 78ms 104ms 616ms 32.9s 0 transport_latency_assumed price_change h 88,226,994 1,181,638 18ms 29ms 200ms 33.1s 0 transport_latency_assumed price_change i 88,324,432 1,223,608 23ms 31ms 140ms 2.1s 0 transport_latency_assumed price_change k 88,312,848 4,914,671 12ms 22ms 140ms 55.9s 0 transport_latency_assumed tick_size_change c 2,088 1,825 5ms 23ms 95ms 170ms 0 transport_latency_assumed tick_size_change g 2,088 not meas. 78ms 213ms 514ms 1.5s 0 transport_latency_assumed tick_size_change h 2,088 62 18ms 29ms 179ms 15.3s 0 transport_latency_assumed tick_size_change i 2,088 61 22ms 31ms 81ms 115ms 0 transport_latency_assumed tick_size_change k 2,088 140 13ms 24ms 118ms 5.6s 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/05/2026-09-28T05.parquet sha256sum 2026-09-28T05.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.