Hour audit: 2026-09-24T20
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-24T20 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-24T20:00:00.000058833+00:00 · last event 2026-09-24T20:59:59.999120428+00:00
VOLUME 129,415,618 rows · 1,425,277,671 bytes (1.33 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured g: 120,634,396 · i: 116,479,659 · h: 110,945,825 · k: 106,294,993 · c: 100,805,762 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 2,328,825 (1.80%) · i: 7,827,941 (6.05%) · h: 9,783,091 (7.56%) · k: 20,206,039 (15.61%) · c: 89,269,722 (68.98%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 de7565cd5e14c3acb332aa2c22c72d278795cc3118d7a8f8158f0615e29a7f57
the corpus checksum ledger names this file with the same digest
joined 129,434,866 to merged 129,415,618, minus 19,248 (minus 0.0149%)
boundary drops 19,248 · 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-24T22:35:30Z 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 13,761,809 158,148,118 0-52 d13597f792c9b758b86cc9202166a0573bf42a1e1df5c126bae43e13fcf7af64 book 3,030,090 117,870,762 53-64 d7ab23d1407c7de1400748333c4efeb7d57b43ba1413e0a54b5a5e57021a0048 last_trade_price 64,092 3,597,236 65-65 42012c4bc249cf1f00bef57ccaf5e955fcbecf25410e6097a7d72dc06bf31f59 market_resolved 1,460 130,140 66-66 427432e256abfac7d2527794d0c37c7b0999040abdb8463d037561105e192523 new_market 2,607 250,995 67-67 59a248ae1e5fd6c028b526ca9930129d423b080eed0648db13bea19bc8fb425a price_change 112,549,672 1,143,594,047 68-497 86986fe54fadde68c54be84426ba1d76e928c3ae55e00df85ccb8d5757dc2219 tick_size_change 5,888 214,039 498-498 b138045eded34ab46ebcd265f7e1ffe96cf9d64bce76e103c7e2df587c2c58c5 EVENT MIX count share price_change 112,549,672 86.97% best_bid_ask 13,761,809 10.63% book 3,030,090 2.34% last_trade_price 64,092 0.05% tick_size_change 5,888 <0.01% new_market 2,607 <0.01% market_resolved 1,460 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,762,137 13,761,809 328 4,504 FULL book 3,046,700 3,030,090 16,610 2,257 FULL last_trade_price 64,092 64,092 0 595 FULL market_resolved 1,460 1,460 0 5 FULL new_market 2,607 2,607 0 0 FULL price_change 112,551,982 112,549,672 2,310 2,485 FULL tick_size_change 5,888 5,888 0 502 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,790,908 9,655,713 5ms 17ms 197ms 10.3s 0 transport_latency_assumed best_bid_ask g 13,133,602 236,591 81ms 120ms 701ms 46.8s 0 transport_latency_assumed best_bid_ask h 11,940,999 970,071 18ms 43ms 245ms 52.6s 0 transport_latency_assumed best_bid_ask i 12,608,842 811,111 21ms 30ms 149ms 7.9s 0 transport_latency_assumed best_bid_ask k 11,462,775 2,088,323 12ms 19ms 111ms 7.8s 0 transport_latency_assumed book c 2,160,837 1,345,671 9.8min 5.3d 44.1d 117.9d 0 book_staleness book g 642,937 129,176 4.8min 3.2d 40.2d 117.9d 0 book_staleness book h 1,384,647 363,979 9.3min 4.7d 43.2d 117.9d 0 book_staleness book i 991,068 154,654 7.4min 4.1d 43.1d 117.9d 0 book_staleness book k 1,773,629 1,036,610 9.9min 5.2d 44.0d 117.9d 0 book_staleness last_trade_price c 47,879 41,961 6ms 31ms 273ms 4.8s 0 transport_latency_assumed last_trade_price g 57,674 1,890 99ms 2.7s 15.4s 46.8s 0 transport_latency_assumed last_trade_price h 54,298 6,891 21ms 91ms 539ms 28.5s 0 transport_latency_assumed last_trade_price i 56,002 4,140 24ms 262ms 5.0s 7.9s 0 transport_latency_assumed last_trade_price k 50,017 9,210 13ms 41ms 258ms 1.6s 0 transport_latency_assumed market_resolved c 815 628 6ms 7.0min 12.8min 14.0min 0 transport_latency_assumed market_resolved g 742 75 84ms 35.4s 4.9min 5.1min 0 transport_latency_assumed market_resolved h 1,062 167 113ms 10.0min 13.6min 17.6min 0 transport_latency_assumed market_resolved i 864 85 27ms 8.2min 10.1min 10.8min 0 transport_latency_assumed market_resolved k 1,193 505 52.8s 11.1min 17.1min 18.1min 0 transport_latency_assumed new_market c 1,745 543 113ms 3.2min 8.4min 10.0min 0 transport_latency_assumed new_market g 1,585 321 334ms 45.7s 1.5min 4.8min 0 transport_latency_assumed new_market h 1,682 292 142ms 49.3s 13.2min 13.3min 0 transport_latency_assumed new_market i 1,626 414 111ms 49.6s 3.6min 5.5min 0 transport_latency_assumed new_market k 1,978 1,037 131ms 8.2min 13.3min 14.2min 0 transport_latency_assumed price_change c 87,799,346 78,221,328 5ms 20ms 204ms 12.7s 0 transport_latency_assumed price_change g 106,792,068 1,960,764 82ms 169ms 3.1s 46.8s 0 transport_latency_assumed price_change h 97,557,593 8,441,450 18ms 48ms 278ms 53.0s 0 transport_latency_assumed price_change i 102,815,621 6,857,439 21ms 39ms 259ms 7.9s 0 transport_latency_assumed price_change k 92,999,869 17,068,691 12ms 22ms 134ms 7.8s 0 transport_latency_assumed tick_size_change c 4,232 3,878 5ms 11ms 78ms 259ms 0 transport_latency_assumed tick_size_change g 5,788 8 80ms 96ms 239ms 27.7s 0 transport_latency_assumed tick_size_change h 5,544 241 18ms 27ms 74ms 2.8s 0 transport_latency_assumed tick_size_change i 5,636 98 22ms 25ms 51ms 138ms 0 transport_latency_assumed tick_size_change k 5,532 1,663 12ms 17ms 50ms 141ms 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-24/20/2026-09-24T20.parquet sha256sum 2026-09-24T20.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.