Hour audit: 2026-09-27T09
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-27T09 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-27T09:00:00.000017488+00:00 · last event 2026-09-27T09:59:59.999979245+00:00
VOLUME 105,314,665 rows · 1,138,194,896 bytes (1.06 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured k: 104,072,936 · h: 104,042,565 · i: 104,017,199 · g: 103,858,182 · c: 91,849,885 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 16,960,657 (16.10%) · h: 1,837,533 (1.74%) · i: 2,077,061 (1.97%) · g: 28,252 (0.03%) · c: 84,411,162 (80.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 105,314,665 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 ab805c800734f4296e24e34a74d6aaba4fdf10974e7810b210cbf2b99d294d22
the corpus checksum ledger names this file with the same digest
joined 105,316,585 to merged 105,314,665, minus 1,920 (minus 0.0018%)
boundary drops 1,920 · 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-27T15:40:20Z 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,700,956 121,716,338 0-40 2606f8d3b703a90479982fed150d65154807ebd719967dddd0268a2ad213e0b2 book 1,330,370 73,899,763 41-46 368473962b2275eddb9ad0223d7a3920b9307f636ba0e336e6e0d544df659a7b last_trade_price 61,342 3,442,817 47-47 262408bd7eed4ed381c582564c75b6a2ecacd416fcec067ce5cd33edeaf9264e market_resolved 812 100,717 48-48 32ddfe5b5f8ab9c03e6fe5461ddd0d86d601446feec58857c091b04a13214938 new_market 4,905 416,168 49-49 bd2671107c665f20c7cd6f532294bdbe8444f294410c8ac658b2da55decdf6aa price_change 93,213,328 937,309,806 50-405 1d1869119a152cabab3dd7a9b0abef55391c08663fff728b0da7b836babe861a tick_size_change 2,952 108,550 406-406 4146d2aded11d6cb568209593b244f3a852d1ca0796ec3334464e8ea6be46244 EVENT MIX count share price_change 93,213,328 88.51% best_bid_ask 10,700,956 10.16% book 1,330,370 1.26% last_trade_price 61,342 0.06% new_market 4,905 <0.01% tick_size_change 2,952 <0.01% market_resolved 812 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,701,226 10,700,956 270 3,512 FULL book 1,330,380 1,330,370 10 194,100 FULL last_trade_price 61,342 61,342 0 351 FULL market_resolved 812 812 0 26 FULL new_market 4,905 4,905 0 8 FULL price_change 93,214,968 93,213,328 1,640 2,457 FULL tick_size_change 2,952 2,952 0 108 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,326,619 8,606,729 4ms 11ms 230ms 7.7s 0 transport_latency_assumed best_bid_ask g 10,690,709 1,683 77ms 111ms 970ms 35.9s 0 transport_latency_assumed best_bid_ask h 10,696,805 175,065 18ms 24ms 445ms 1.0min 0 transport_latency_assumed best_bid_ask i 10,696,944 199,021 20ms 25ms 159ms 3.2s 0 transport_latency_assumed best_bid_ask k 10,697,419 1,718,458 12ms 17ms 234ms 57.0s 0 transport_latency_assumed book c 1,306,104 1,289,134 1.1h 4.6d 45.6d 120.5d 0 book_staleness book g 134,089 5,493 85ms 5.1s 19.0h 101.9d 0 book_staleness book h 129,566 4,803 22ms 187ms 46.0min 112.7d 0 book_staleness book i 128,327 5,542 22ms 143ms 7.7s 101.9d 0 book_staleness book k 132,205 25,398 15ms 145ms 5.1h 101.9d 0 book_staleness last_trade_price c 53,323 47,758 6ms 22ms 394ms 2.5s 0 transport_latency_assumed last_trade_price g 59,616 5 83ms 661ms 12.6s 36.0s 0 transport_latency_assumed last_trade_price h 61,175 1,242 19ms 76ms 1.2s 45.3s 0 transport_latency_assumed last_trade_price i 61,124 1,221 21ms 77ms 959ms 3.2s 0 transport_latency_assumed last_trade_price k 61,172 11,116 13ms 34ms 346ms 10.7s 0 transport_latency_assumed market_resolved c 666 599 6ms 6.5min 11.0min 11.0min 0 transport_latency_assumed market_resolved g 593 28 80ms 363ms 53.9s 53.9s 0 transport_latency_assumed market_resolved h 593 9 19ms 409ms 43.7s 44.4s 0 transport_latency_assumed market_resolved i 593 36 22ms 156ms 38.5s 38.6s 0 transport_latency_assumed market_resolved k 593 140 13ms 288ms 38.5s 39.0s 0 transport_latency_assumed new_market c 3,649 1,922 13.4s 5.9min 7.3min 7.4min 0 transport_latency_assumed new_market g 2,617 525 364ms 38.3s 1.1min 1.7min 0 transport_latency_assumed new_market h 2,617 572 186ms 25.7s 57.8s 1.5min 0 transport_latency_assumed new_market i 2,617 1,013 135ms 25.0s 59.3s 1.7min 0 transport_latency_assumed new_market k 2,617 873 174ms 28.1s 1.1min 1.7min 0 transport_latency_assumed price_change c 81,157,004 74,462,596 5ms 12ms 277ms 9.3s 0 transport_latency_assumed price_change g 92,967,606 20,518 78ms 156ms 2.3s 39.2s 0 transport_latency_assumed price_change h 93,148,857 1,655,810 18ms 28ms 549ms 1.5min 0 transport_latency_assumed price_change i 93,124,642 1,870,178 20ms 28ms 226ms 3.3s 0 transport_latency_assumed price_change k 93,175,978 15,204,226 12ms 19ms 272ms 1.0min 0 transport_latency_assumed tick_size_change c 2,520 2,424 4ms 8ms 55ms 873ms 0 transport_latency_assumed tick_size_change g 2,952 not meas. 77ms 150ms 1.0s 9.4s 0 transport_latency_assumed tick_size_change h 2,952 32 18ms 28ms 8.1s 25.1s 0 transport_latency_assumed tick_size_change i 2,952 50 20ms 24ms 52ms 254ms 0 transport_latency_assumed tick_size_change k 2,952 446 12ms 16ms 103ms 717ms 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/09/2026-09-27T09.parquet sha256sum 2026-09-27T09.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.