Hour audit: 2026-10-08T11
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-08T11 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-08T11:00:00.000033556+00:00 · last event 2026-10-08T11:59:59.999983343+00:00
VOLUME 123,094,500 rows · 1,411,445,022 bytes (1.31 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 122,933,330 · m: 122,917,045 · h: 122,880,107 · i: 122,838,425 · n: 121,801,772 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 58,177,613 (47.26%) · m: 62,718,251 (50.95%) · h: 1,285,976 (1.04%) · i: 787,695 (0.64%) · n: 124,965 (0.10%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 123,094,500 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 37386e701126c339b54c319cd05f2f5cdf86b9ea777a905b2be278d1337c3197
the corpus checksum ledger names this file with the same digest
joined 123,096,304 to merged 123,094,500, minus 1,804 (minus 0.0015%)
boundary drops 1,804 · 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-08T13:06:28Z 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,568,592 144,976,915 0-44 276b877edc6b842fc88821867b2778b46e740808b7c3e9ca6c7a8dacca5c3bef book 304,280 32,041,468 45-46 c4dffef69adb9815d9a6a1deb571f8ea3d5818d8bfcdea23234ca537fb6092f3 last_trade_price 57,017 3,307,432 47-47 f095c627f0e7b01f25af574c3a0745eb346b8b6ccc7b56b997546b092ef46dd9 market_resolved 564 91,379 48-48 055c14291e03ab0a6e011039f4c4853c1b64ba979d1750546e93d4b2521dc60b new_market 1,323 128,807 49-49 5aff16feeb0362e8109d6c2387e558d0404a12ddcba404eb3e47e1c7eaaa1fe7 price_change 111,160,032 1,229,393,048 50-474 1d2b1c49444b0366747db78af3d7a5a948401e2907aa01b660f2852f1c9f31ea tick_size_change 2,692 100,035 475-475 be7bb9cb57ead7ab07499fb96cdfa932a038a1df2c8fa0cc94d25a3547242763 EVENT MIX count share price_change 111,160,032 90.30% best_bid_ask 11,568,592 9.40% book 304,280 0.25% last_trade_price 57,017 0.05% tick_size_change 2,692 <0.01% new_market 1,323 <0.01% market_resolved 564 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,568,719 11,568,592 127 109 FULL book 304,476 304,280 196 80,616 FULL last_trade_price 57,017 57,017 0 0 FULL market_resolved 565 564 1 2 FULL new_market 1,323 1,323 0 0 FULL price_change 111,161,512 111,160,032 1,480 74 FULL tick_size_change 2,692 2,692 0 5 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 11,567,408 107,670 18ms 33ms 246ms 1.2min 0 transport_latency_assumed best_bid_ask i 11,567,214 69,853 21ms 35ms 172ms 6.1s 0 transport_latency_assumed best_bid_ask m 11,567,628 5,863,507 6ms 17ms 119ms 6.0s 0 transport_latency_assumed best_bid_ask n 11,538,399 4,796 44ms 69ms 329ms 18.7s 0 transport_latency_assumed best_bid_ask o 11,567,597 5,522,766 6ms 18ms 133ms 8.6s 0 transport_latency_assumed book h 145,849 29,970 29ms 1.1h 29.1d 131.5d 0 book_staleness book i 118,226 3,850 26ms 567ms 3.0h 113.0d 0 book_staleness book m 173,251 112,270 13ms 4.5h 31.0d 131.5d 0 book_staleness book n 165,131 53,579 139ms 4.3h 31.0d 113.0d 0 book_staleness book o 170,259 104,611 12ms 4.3h 31.0d 131.6d 0 book_staleness last_trade_price h 56,916 662 21ms 121ms 666ms 57.5s 0 transport_latency_assumed last_trade_price i 56,776 283 27ms 361ms 2.6s 6.1s 0 transport_latency_assumed last_trade_price m 56,851 28,954 7ms 31ms 223ms 1.6s 0 transport_latency_assumed last_trade_price n 53,608 43 53ms 1.2s 10.0s 18.7s 0 transport_latency_assumed last_trade_price o 56,921 27,075 7ms 27ms 192ms 3.1s 0 transport_latency_assumed market_resolved h 550 9 21ms 25.2s 30.1s 36.8s 0 transport_latency_assumed market_resolved i 551 86 25ms 13.8s 53.9s 55.0s 0 transport_latency_assumed market_resolved m 551 241 6ms 16.8s 56.8s 57.9s 0 transport_latency_assumed market_resolved n 552 not meas. 48ms 31.5s 36.3s 43.1s 0 transport_latency_assumed market_resolved o 551 228 6ms 16.4s 50.5s 55.3s 0 transport_latency_assumed new_market h 828 219 229ms 22.4s 48.8s 1.6min 0 transport_latency_assumed new_market i 828 214 138ms 21.8s 47.8s 1.4min 0 transport_latency_assumed new_market m 828 468 68ms 24.5s 48.7s 1.7min 0 transport_latency_assumed new_market n 828 91 160ms 17.7s 42.6s 1.6min 0 transport_latency_assumed new_market o 828 331 100ms 17.9s 27.0s 1.5min 0 transport_latency_assumed price_change h 111,105,864 1,147,412 19ms 42ms 426ms 1.2min 0 transport_latency_assumed price_change i 111,092,138 713,394 22ms 50ms 668ms 6.1s 0 transport_latency_assumed price_change m 111,115,244 56,711,438 6ms 20ms 146ms 7.8s 0 transport_latency_assumed price_change n 110,040,582 66,456 45ms 99ms 3.4s 18.8s 0 transport_latency_assumed price_change o 111,134,482 52,521,332 6ms 21ms 157ms 8.6s 0 transport_latency_assumed tick_size_change h 2,692 34 19ms 33ms 80ms 846ms 0 transport_latency_assumed tick_size_change i 2,692 15 22ms 35ms 82ms 288ms 0 transport_latency_assumed tick_size_change m 2,692 1,373 6ms 18ms 69ms 138ms 0 transport_latency_assumed tick_size_change n 2,672 not meas. 45ms 69ms 226ms 521ms 0 transport_latency_assumed tick_size_change o 2,692 1,270 6ms 20ms 133ms 1.1s 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/11/2026-10-08T11.parquet sha256sum 2026-10-08T11.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.