Hour audit: 2026-09-27T14
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-27T14 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-27T14:00:00.000804703+00:00 · last event 2026-09-27T14:59:59.999973756+00:00
VOLUME 108,091,993 rows · 1,189,361,153 bytes (1.11 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured k: 106,424,487 · i: 106,418,637 · h: 106,357,345 · g: 105,885,476 · c: 88,788,270 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 24,137,816 (22.33%) · i: 2,434,823 (2.25%) · h: 3,506,965 (3.24%) · g: 19,820 (0.02%) · c: 77,992,569 (72.15%) (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 108,091,993 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 08f45bc3e543a1b5b42d77df162c041c099bd47af8994f8b787ee5da3e32143e
the corpus checksum ledger names this file with the same digest
joined 108,094,561 to merged 108,091,993, minus 2,568 (minus 0.0024%)
boundary drops 2,568 · 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-27T17:52:59Z 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,245,361 119,558,701 0-39 30de2fe72c27296b90c27a658a81f40e3736dbbb1c5a2f18b25d139e5540948e book 1,760,666 80,432,767 40-46 55e48fde615a6a6cd613b5aab6de63265f43fb3ad60e6f850afe0f0976435b65 last_trade_price 64,754 3,719,357 47-47 56b8e27e582b030339fd42e317c6c6ffa0e2ce7d390ccfebe6dc66b9f4612635 market_resolved 1,225 151,930 48-48 80c5088b491922cbc345e38d4759adfbd84e80b3e43b58b5a01a6e0e03b7219f new_market 4,885 470,966 49-49 0b8a05984223308a628e0fb2f3b83a4c2d40a381083d3f8bec03c40091f3609b price_change 96,011,502 983,660,163 50-416 39640b01082ffdc2502c95bf637f202c00af137bdcfddd0c6a68c09861cd5be1 tick_size_change 3,600 133,437 417-417 ebac20630697011db3e37c9c7ec1471322c63dfe40e7364c24221644b7da379d EVENT MIX count share price_change 96,011,502 88.82% best_bid_ask 10,245,361 9.48% book 1,760,666 1.63% last_trade_price 64,754 0.06% new_market 4,885 <0.01% tick_size_change 3,600 <0.01% market_resolved 1,225 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,245,601 10,245,361 240 2,214 FULL book 1,760,686 1,760,666 20 200,121 FULL last_trade_price 64,754 64,754 0 414 FULL market_resolved 1,225 1,225 0 138 FULL new_market 4,885 4,885 0 0 FULL price_change 96,013,810 96,011,502 2,308 1,522 FULL tick_size_change 3,600 3,600 0 160 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,322,206 7,364,636 5ms 21ms 377ms 20.5s 0 transport_latency_assumed best_bid_ask g 10,231,755 1,373 80ms 134ms 1.2s 58.1s 0 transport_latency_assumed best_bid_ask h 10,240,490 305,060 18ms 31ms 558ms 1.5min 0 transport_latency_assumed best_bid_ask i 10,242,508 217,091 26ms 35ms 187ms 7.1s 0 transport_latency_assumed best_bid_ask k 10,242,270 2,357,201 13ms 23ms 274ms 1.1min 0 transport_latency_assumed book c 1,723,352 1,701,587 1.5h 4.7d 45.8d 120.7d 0 book_staleness book g 140,244 4,798 92ms 6.9s 11.1h 102.2d 0 book_staleness book h 143,735 11,652 24ms 1.9s 10.7h 102.2d 0 book_staleness book i 137,427 7,288 30ms 305ms 52.0min 102.1d 0 book_staleness book k 139,320 35,341 17ms 177ms 9.0h 102.1d 0 book_staleness last_trade_price c 50,537 43,521 6ms 43ms 565ms 8.4s 0 transport_latency_assumed last_trade_price g 62,646 15 91ms 1.6s 12.5s 47.4s 0 transport_latency_assumed last_trade_price h 64,260 2,684 20ms 74ms 2.1s 1.1min 0 transport_latency_assumed last_trade_price i 64,548 1,711 29ms 122ms 1.5s 7.1s 0 transport_latency_assumed last_trade_price k 64,525 16,823 14ms 46ms 460ms 12.8s 0 transport_latency_assumed market_resolved c 973 871 7ms 7.1min 8.1min 8.1min 0 transport_latency_assumed market_resolved g 936 25 81ms 280ms 43.9s 44.0s 0 transport_latency_assumed market_resolved h 936 94 19ms 126ms 35.4s 49.0s 0 transport_latency_assumed market_resolved i 936 16 28ms 101ms 43.2s 43.3s 0 transport_latency_assumed market_resolved k 936 219 14ms 74ms 37.6s 51.5s 0 transport_latency_assumed new_market c 3,432 1,392 418ms 6.2min 7.4min 8.6min 0 transport_latency_assumed new_market g 2,964 645 552ms 1.9min 2.2min 2.6min 0 transport_latency_assumed new_market h 2,964 1,163 247ms 1.8min 2.2min 2.6min 0 transport_latency_assumed new_market i 2,964 855 231ms 1.8min 2.2min 2.6min 0 transport_latency_assumed new_market k 2,964 830 283ms 1.9min 2.2min 2.6min 0 transport_latency_assumed price_change c 78,684,810 68,878,146 5ms 27ms 420ms 21.1s 0 transport_latency_assumed price_change g 95,443,331 12,964 80ms 203ms 5.2s 58.1s 0 transport_latency_assumed price_change h 95,901,360 3,186,120 19ms 38ms 691ms 1.6min 0 transport_latency_assumed price_change i 95,966,654 2,207,618 27ms 43ms 299ms 7.2s 0 transport_latency_assumed price_change k 95,970,872 21,726,654 13ms 28ms 308ms 1.1min 0 transport_latency_assumed tick_size_change c 2,960 2,416 5ms 67ms 461ms 1.6s 0 transport_latency_assumed tick_size_change g 3,600 not meas. 79ms 147ms 975ms 1.6s 0 transport_latency_assumed tick_size_change h 3,600 192 19ms 48ms 549ms 7.1s 0 transport_latency_assumed tick_size_change i 3,600 244 25ms 45ms 273ms 438ms 0 transport_latency_assumed tick_size_change k 3,600 748 13ms 44ms 419ms 4.3s 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-27/14/2026-09-27T14.parquet sha256sum 2026-09-27T14.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.