Hour audit: 2026-10-08T12
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-08T12 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-08T12:00:00.000026510+00:00 · last event 2026-10-08T12:59:59.999972097+00:00
VOLUME 121,204,524 rows · 1,401,984,155 bytes (1.31 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 121,066,287 · h: 121,051,641 · m: 121,026,689 · i: 120,865,208 · n: 120,250,383 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 56,203,034 (46.37%) · h: 1,571,137 (1.30%) · m: 62,323,138 (51.42%) · i: 1,004,360 (0.83%) · n: 102,855 (0.08%) (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 121,204,524 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 63548cc3fc6cc899251167052fa48d00577fe4ce8bf96af0d1395fae2d2dccea
the corpus checksum ledger names this file with the same digest
joined 121,205,706 to merged 121,204,524, minus 1,182 (minus 0.0010%)
boundary drops 1,182 · 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-08T14:05:52Z 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 11,368,664 143,859,649 0-43 a6c5217e606f4c8a7a3c51a648724dd3fe40e7503d6cbd1e7ec27b61b860655c book 219,857 24,473,145 44-44 e961db96607b5dd5d176832419bde1fb7cdcbd1ae381d8a533eab548cc6d3bc8 last_trade_price 65,435 3,755,610 45-45 59cf8d8693e3c52d348002d06a72adbb7d4e36137f7ac87c4b9af910f1435709 market_resolved 571 95,658 46-46 e1f2cf1b2e1a258fe7a92516bfed051a7c0e803770880ba324e011add2d9be1a new_market 2,037 189,374 47-47 63afb8e854623fdd9fd5eb9bc757bbc57a0fe8f33867ce90653e23c8a35aca13 price_change 109,544,820 1,228,114,556 48-465 502dd7812b7ef14c04a0c343fcf93b12c1546479b3eca095fd9f8176cce45d45 tick_size_change 3,140 116,752 466-466 936c486d6dc59b11909aaf208b4a087138ddd28c7ea8aee27ebda8a07f2cc235 EVENT MIX count share price_change 109,544,820 90.38% best_bid_ask 11,368,664 9.38% book 219,857 0.18% last_trade_price 65,435 0.05% tick_size_change 3,140 <0.01% new_market 2,037 <0.01% market_resolved 571 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,368,770 11,368,664 106 132 FULL book 219,895 219,857 38 36,339 FULL last_trade_price 65,435 65,435 0 1 FULL market_resolved 571 571 0 0 FULL new_market 2,037 2,037 0 0 FULL price_change 109,545,858 109,544,820 1,038 67 FULL tick_size_change 3,140 3,140 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 11,366,038 135,867 19ms 40ms 524ms 1.0min 0 transport_latency_assumed best_bid_ask i 11,361,462 91,800 22ms 42ms 279ms 12.3s 0 transport_latency_assumed best_bid_ask m 11,365,337 5,791,988 6ms 21ms 144ms 6.4s 0 transport_latency_assumed best_bid_ask n 11,352,946 6,785 46ms 79ms 510ms 23.7s 0 transport_latency_assumed best_bid_ask o 11,367,080 5,342,224 6ms 22ms 155ms 7.9s 0 transport_latency_assumed book h 150,865 19,917 30ms 58.0s 5.0d 131.6d 0 book_staleness book i 149,086 18,378 42ms 24.1s 3.6d 113.1d 0 book_staleness book m 150,343 85,463 9ms 53.0s 15.2h 130.0d 0 book_staleness book n 144,740 17,969 73ms 1.2min 4.5d 113.1d 0 book_staleness book o 150,282 78,130 9ms 50.2s 2.7d 113.1d 0 book_staleness last_trade_price h 65,273 1,000 23ms 245ms 1.4s 43.2s 0 transport_latency_assumed last_trade_price i 64,685 465 32ms 949ms 4.2s 12.3s 0 transport_latency_assumed last_trade_price m 65,088 34,063 7ms 40ms 262ms 5.0s 0 transport_latency_assumed last_trade_price n 62,240 87 64ms 1.4s 10.5s 23.7s 0 transport_latency_assumed last_trade_price o 65,178 29,820 8ms 38ms 281ms 2.4s 0 transport_latency_assumed market_resolved h 571 2 21ms 108ms 40.8s 44.4s 0 transport_latency_assumed market_resolved i 571 41 23ms 127ms 29.2s 33.3s 0 transport_latency_assumed market_resolved m 571 275 6ms 37ms 32.2s 37.4s 0 transport_latency_assumed market_resolved n 571 1 49ms 232ms 47.4s 51.4s 0 transport_latency_assumed market_resolved o 571 252 7ms 44ms 32.3s 36.6s 0 transport_latency_assumed new_market h 1,216 207 233ms 31.9s 40.7s 1.6min 0 transport_latency_assumed new_market i 1,216 174 137ms 25.4s 40.3s 1.7min 0 transport_latency_assumed new_market m 1,216 840 61ms 28.6s 34.4s 1.7min 0 transport_latency_assumed new_market n 1,216 283 114ms 29.8s 39.9s 1.8min 0 transport_latency_assumed new_market o 1,216 533 108ms 17.3s 38.4s 1.6min 0 transport_latency_assumed price_change h 109,464,538 1,414,116 19ms 59ms 776ms 1.0min 0 transport_latency_assumed price_change i 109,285,048 893,444 22ms 78ms 1.7s 12.3s 0 transport_latency_assumed price_change m 109,440,994 56,409,016 6ms 25ms 169ms 6.5s 0 transport_latency_assumed price_change n 108,685,530 77,730 47ms 170ms 5.1s 23.7s 0 transport_latency_assumed price_change o 109,478,820 50,750,514 6ms 25ms 172ms 8.2s 0 transport_latency_assumed tick_size_change h 3,140 28 19ms 35ms 591ms 855ms 0 transport_latency_assumed tick_size_change i 3,140 58 22ms 40ms 167ms 270ms 0 transport_latency_assumed tick_size_change m 3,140 1,493 6ms 19ms 252ms 359ms 0 transport_latency_assumed tick_size_change n 3,140 not meas. 45ms 78ms 548ms 6.0s 0 transport_latency_assumed tick_size_change o 3,140 1,561 6ms 19ms 182ms 1.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-10-08/12/2026-10-08T12.parquet sha256sum 2026-10-08T12.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.