Hour audit: 2026-10-04T08
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-10-04T08 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-04T08:00:00.000076041+00:00 · last event 2026-10-04T08:59:59.999424481+00:00
VOLUME 94,969,400 rows · 1,043,768,025 bytes (995.41 MiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured i: 94,907,113 · h: 94,898,276 · m: 94,879,698 · o: 94,858,929 · n: 94,803,706 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 410,572 (0.43%) · h: 459,149 (0.48%) · m: 46,243,265 (48.69%) · o: 47,785,431 (50.32%) · n: 70,983 (0.07%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 94,969,400 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 640a555e53317614290cf98a1169f9336a59b2b76335bcf1cec1f9be570928b9
the corpus checksum ledger names this file with the same digest
joined 94,970,350 to merged 94,969,400, minus 950 (minus 0.0010%)
boundary drops 950 · 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-10-04T10:07:51Z as himno
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 8,490,032 108,013,204 0-32 f236c9b58934df8b9e8138791db8cec763f4a8ea5b70fdadd6f11ef5872b5bb5 book 128,199 13,125,569 33-33 4175a252cb9952dde462c9b46e2aaaa4e564092b4da20726889251f8eb4a4d4b last_trade_price 49,797 2,880,520 34-34 de87cf07dc83d1a0ceac4f9de95636ed5524bc9a1e96b7f062ba8ed419bbd7e1 market_resolved 683 102,937 35-35 0761d2eb992e82daf356f496438565bb296e0e1550366a1cee12df93d12f0c35 new_market 3,931 378,286 36-36 e27fff5143179acc29bf1f248cd6f0e806b97cf33ebbcdf58b1e9423f4567f0d price_change 86,294,170 918,083,725 37-366 0e29320e2dea19ae7bdf9f5fdc9a9f953dabcbf426acd606748dd997b8353597 tick_size_change 2,588 96,477 367-367 20202fc5d4467242a98f618a9e91410b1b21dd74d3fed8b1cd1c1ae6385e4832 EVENT MIX count share price_change 86,294,170 90.87% best_bid_ask 8,490,032 8.94% book 128,199 0.13% last_trade_price 49,797 0.05% new_market 3,931 <0.01% tick_size_change 2,588 <0.01% market_resolved 683 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,490,106 8,490,032 74 396 FULL book 128,199 128,199 0 10,266 FULL last_trade_price 49,797 49,797 0 0 FULL market_resolved 683 683 0 0 FULL new_market 3,931 3,931 0 0 FULL price_change 86,295,046 86,294,170 876 805 FULL tick_size_change 2,588 2,588 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 8,486,626 36,451 18ms 26ms 690ms 2.3min 0 transport_latency_assumed best_bid_ask i 8,487,804 33,735 19ms 28ms 314ms 50.6s 0 transport_latency_assumed best_bid_ask m 8,488,298 4,087,641 4ms 10ms 187ms 14.4s 0 transport_latency_assumed best_bid_ask n 8,485,492 4,986 45ms 61ms 436ms 29.7s 0 transport_latency_assumed best_bid_ask o 8,488,593 4,327,219 4ms 10ms 189ms 11.3s 0 transport_latency_assumed book h 112,077 9,438 22ms 1.5s 1.5d 108.9d 0 book_staleness book i 106,007 4,084 23ms 219ms 20.5min 108.9d 0 book_staleness book m 105,173 51,304 6ms 36ms 9.2s 108.8d 0 book_staleness book n 113,587 11,313 50ms 6.8s 2.3d 127.4d 0 book_staleness book o 105,049 52,060 6ms 36ms 8.6s 56.9d 0 book_staleness last_trade_price h 49,672 321 20ms 47ms 679ms 50.7s 0 transport_latency_assumed last_trade_price i 49,775 195 23ms 73ms 1.2s 9.8s 0 transport_latency_assumed last_trade_price m 49,696 23,702 6ms 15ms 236ms 7.0s 0 transport_latency_assumed last_trade_price n 49,107 30 49ms 215ms 4.7s 30.2s 0 transport_latency_assumed last_trade_price o 49,730 25,549 5ms 14ms 215ms 6.7s 0 transport_latency_assumed market_resolved h 638 43 20ms 76ms 54.3s 54.4s 0 transport_latency_assumed market_resolved i 638 5 23ms 93ms 54.2s 54.2s 0 transport_latency_assumed market_resolved m 638 288 5ms 12.9s 52.2s 1.1min 0 transport_latency_assumed market_resolved n 638 not meas. 48ms 198ms 49.8s 53.8s 0 transport_latency_assumed market_resolved o 638 347 5ms 12.4s 52.0s 56.6s 0 transport_latency_assumed new_market h 2,451 508 338ms 35.6s 43.3s 1.7min 0 transport_latency_assumed new_market i 2,451 1,001 275ms 33.8s 48.6s 1.0min 0 transport_latency_assumed new_market m 2,451 946 156ms 34.8s 53.4s 1.7min 0 transport_latency_assumed new_market n 2,451 340 300ms 36.5s 43.1s 1.6min 0 transport_latency_assumed new_market o 2,451 1,136 206ms 35.6s 53.0s 1.8min 0 transport_latency_assumed price_change h 86,244,224 412,388 18ms 30ms 739ms 2.3min 0 transport_latency_assumed price_change i 86,257,850 371,548 19ms 33ms 443ms 57.7s 0 transport_latency_assumed price_change m 86,230,854 42,078,206 5ms 11ms 196ms 14.5s 0 transport_latency_assumed price_change n 86,149,843 54,314 46ms 79ms 1.1s 30.4s 0 transport_latency_assumed price_change o 86,209,880 43,377,714 5ms 11ms 198ms 12.0s 0 transport_latency_assumed tick_size_change h 2,588 not meas. 18ms 30ms 420ms 51.9s 0 transport_latency_assumed tick_size_change i 2,588 4 20ms 31ms 246ms 1.4s 0 transport_latency_assumed tick_size_change m 2,588 1,178 5ms 10ms 119ms 857ms 0 transport_latency_assumed tick_size_change n 2,588 not meas. 46ms 60ms 217ms 748ms 0 transport_latency_assumed tick_size_change o 2,588 1,406 5ms 10ms 69ms 214ms 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-10-04/08/2026-10-04T08.parquet sha256sum 2026-10-04T08.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.