Hour audit: 2026-09-25T13
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.
1 finding
- a machine expected this hour contributed nothing. Of the 5 machines expected to be capturing this hour, 1 contributed no rows: c. The hour is still whole on minutes; it simply rests on 4 machines rather than 5.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-25T13 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-25T13:00:00.000014964+00:00 · last event 2026-09-25T13:59:59.999784192+00:00
VOLUME 127,009,338 rows · 1,389,210,196 bytes (1.29 GiB) · 7 products, all holding rows
WITNESSES ghik — 4 machines contributed rows
captured k: 126,108,085 · i: 126,098,053 · g: 125,634,871 · h: 115,431,340 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 110,578,188 (87.06%) · i: 7,154,178 (5.63%) · g: 28,464 (0.02%) · h: 9,248,508 (7.28%) (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 127,009,338 rows exactly, so those pairs supplied none
5 expected (cghik), 1 contributed nothing: c
INTEGRITY sha256 5b7b39583176ee8bedb04577ac5614c4f6850dea341d35207a393cec36713bc5
the corpus checksum ledger names this file with the same digest
joined 127,011,242 to merged 127,009,338, minus 1,904 (minus 0.0015%)
boundary drops 1,904 · 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-25T18:49:39Z as ghik
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 7/8 pass, 1 finding
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
FINDING a machine expected this hour contributed nothing
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 12,346,000 142,697,027 0-47 da848d3cbe16051b0f28825da615387f433c0575f2e5d6b219d7157a4ef962e3 book 984,267 66,732,267 48-51 93bbfd043c2016598efc530ec9393e26075315936a80b79c9cea6438b22dde4a last_trade_price 60,171 3,476,372 52-52 0de527180c5f07d81514fc34a4d2ba72eaa45ba3ab7350da70017fb397c18aed market_resolved 700 107,945 53-53 cb1ece9d32a364f1d42baf079b4a0f6bc87b34b23d2da2439a9158466f35116b new_market 1,122 122,695 54-54 1161f3986ce6b35bd0e8c10c8b651d79a1e29b99991e89f30fe8be32af18536a price_change 113,614,458 1,174,532,410 55-488 9584d68e6883f09d6d59db021300088d39d2739d6b871b64037b7b1f15c1ff8f tick_size_change 2,620 96,425 489-489 0090d50190260c019fe3fcd1f3b86a21f702fa25f7b19f33a57140a56e0f330a EVENT MIX count share price_change 113,614,458 89.45% best_bid_ask 12,346,000 9.72% book 984,267 0.77% last_trade_price 60,171 0.05% tick_size_change 2,620 <0.01% new_market 1,122 <0.01% market_resolved 700 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,346,230 12,346,000 230 49,260 PARTIAL book 984,295 984,267 28 209,961 PARTIAL last_trade_price 60,171 60,171 0 3,908 PARTIAL market_resolved 700 700 0 661 PARTIAL new_market 1,122 1,122 0 799 PARTIAL price_change 113,616,104 113,614,458 1,646 84,968 PARTIAL tick_size_change 2,620 2,620 0 655 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 12,337,493 1,747 79ms 112ms 464ms 25.0s 0 transport_latency_assumed best_bid_ask h 11,218,271 787,282 19ms 41ms 144ms 29.2s 0 transport_latency_assumed best_bid_ask i 12,345,399 632,734 20ms 30ms 112ms 4.1s 0 transport_latency_assumed best_bid_ask k 12,345,208 10,924,237 13ms 24ms 137ms 8.2s 0 transport_latency_assumed book g 126,824 4,540 91ms 5.7s 2.9d 100.1d 0 book_staleness book h 967,545 864,493 1.4h 3.9d 41.0d 118.6d 0 book_staleness book i 124,009 15,394 23ms 87ms 1.7h 100.1d 0 book_staleness book k 124,349 99,840 16ms 65ms 2.4h 100.1d 0 book_staleness last_trade_price g 58,513 77 91ms 1.2s 11.8s 25.1s 0 transport_latency_assumed last_trade_price h 54,426 4,227 21ms 82ms 400ms 6.4s 0 transport_latency_assumed last_trade_price i 60,063 4,492 22ms 65ms 351ms 3.0s 0 transport_latency_assumed last_trade_price k 59,988 51,375 14ms 43ms 228ms 1.6s 0 transport_latency_assumed market_resolved g 661 4 82ms 370ms 49.1s 52.1s 0 transport_latency_assumed market_resolved h 638 71 21ms 101ms 4.1min 4.7min 0 transport_latency_assumed market_resolved i 661 108 22ms 19.5s 52.7s 52.7s 0 transport_latency_assumed market_resolved k 661 517 15ms 22.1s 55.1s 55.1s 0 transport_latency_assumed new_market g 799 64 337ms 30.8s 1.2min 1.4min 0 transport_latency_assumed new_market h 799 287 105ms 404ms 1.2min 4.8min 0 transport_latency_assumed new_market i 799 352 115ms 17.7s 59.4s 1.2min 0 transport_latency_assumed new_market k 799 419 90ms 20.4s 1.1min 1.5min 0 transport_latency_assumed price_change g 113,107,961 22,032 81ms 167ms 4.6s 25.1s 0 transport_latency_assumed price_change h 103,187,113 7,591,866 19ms 48ms 210ms 33.0s 0 transport_latency_assumed price_change i 113,564,502 6,500,962 21ms 36ms 163ms 4.2s 0 transport_latency_assumed price_change k 113,574,460 99,499,598 13ms 28ms 151ms 8.3s 0 transport_latency_assumed tick_size_change g 2,620 not meas. 80ms 141ms 427ms 768ms 0 transport_latency_assumed tick_size_change h 2,548 282 19ms 34ms 326ms 2.1s 0 transport_latency_assumed tick_size_change i 2,620 136 21ms 35ms 171ms 312ms 0 transport_latency_assumed tick_size_change k 2,620 2,202 13ms 28ms 201ms 343ms 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-25/13/2026-09-25T13.parquet sha256sum 2026-09-25T13.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.