Hour audit: 2026-09-30T11
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-30T11 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-30T11:00:00.000373971+00:00 · last event 2026-09-30T11:59:59.999936898+00:00
VOLUME 113,697,421 rows · 1,196,779,702 bytes (1.11 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured k: 113,478,115 · h: 113,458,511 · i: 113,436,246 · m: 113,351,709 · g: 113,327,738 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 4,467,863 (3.93%) · h: 1,013,422 (0.89%) · i: 578,158 (0.51%) · m: 107,558,293 (94.60%) · g: 79,685 (0.07%) (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 113,697,421 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 90aacfd8db85cad900584d5ff18af2638816cac9ccc44911f7a920409fb65518
the corpus checksum ledger names this file with the same digest
joined 113,702,584 to merged 113,697,421, minus 5,163 (minus 0.0045%)
boundary drops 5,163 · 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-30T18:46:41Z as ghikm
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 9,913,928 117,014,838 0-37 fe0fc6c02f10bb676f67c9c7c6ec574210ae7df6dea29c2430258b7ad42e231e book 351,874 35,741,433 38-39 4eeeb0b52e1b19a3feea57cc992f060287d6e22f96fdf4c4beed5736e0bf6cbc last_trade_price 58,178 3,302,910 40-40 9761a0c49d630e69a36af5d9cc7b716dc5ad51ff0b3246cd6bee9587f0b967e0 market_resolved 997 147,062 41-41 20d6f1e866dfc03e18238758d3c6dc9c69dacd5c41816fe5575eea3f00a8f840 new_market 1,446 141,150 42-42 a96c29f03158409f6a8562805e07c2f773a1bc012224fc4f2336ab5dd6ad1fe2 price_change 103,367,786 1,039,017,447 43-437 d3c572b905ec20aeae99d445428ff3a5d3624d3210b1de78f2b90acfa52112a7 tick_size_change 3,212 117,649 438-438 94d1e252844edff10406bbac41c2165395a05567123c48a9ac0faf9634ce2c9d EVENT MIX count share price_change 103,367,786 90.91% best_bid_ask 9,913,928 8.72% book 351,874 0.31% last_trade_price 58,178 0.05% tick_size_change 3,212 <0.01% new_market 1,446 <0.01% market_resolved 997 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,914,097 9,913,928 169 241 FULL book 351,884 351,874 10 100,616 FULL last_trade_price 58,182 58,178 4 4 FULL market_resolved 997 997 0 0 FULL new_market 1,446 1,446 0 0 FULL price_change 103,372,766 103,367,786 4,980 70 FULL tick_size_change 3,212 3,212 0 2 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,908,083 1,797 77ms 97ms 496ms 27.8s 0 transport_latency_assumed best_bid_ask h 9,911,994 81,220 18ms 24ms 218ms 44.0s 0 transport_latency_assumed best_bid_ask i 9,909,926 38,960 22ms 29ms 125ms 16.5s 0 transport_latency_assumed best_bid_ask k 9,911,680 376,049 13ms 22ms 156ms 42.6s 0 transport_latency_assumed best_bid_ask m 9,906,554 9,415,902 5ms 10ms 60ms 3.4s 0 transport_latency_assumed book g 187,112 63,296 213ms 16.5h 24.9d 123.5d 0 book_staleness book h 145,447 26,206 23ms 1.5h 21.7d 105.1d 0 book_staleness book i 173,099 49,240 32ms 10.8h 24.9d 123.6d 0 book_staleness book k 183,070 60,267 26ms 14.5h 24.9d 123.6d 0 book_staleness book m 166,025 152,865 8ms 7.5h 23.0d 123.6d 0 book_staleness last_trade_price g 57,181 9 89ms 559ms 8.3s 26.6s 0 transport_latency_assumed last_trade_price h 58,114 783 19ms 53ms 643ms 11.2s 0 transport_latency_assumed last_trade_price i 57,857 657 23ms 43ms 284ms 10.6s 0 transport_latency_assumed last_trade_price k 58,047 2,678 15ms 35ms 322ms 12.6s 0 transport_latency_assumed last_trade_price m 57,566 54,051 6ms 14ms 136ms 1.5s 0 transport_latency_assumed market_resolved g 914 1 80ms 39.7s 49.9s 56.5s 0 transport_latency_assumed market_resolved h 914 6 20ms 33.0s 54.9s 55.0s 0 transport_latency_assumed market_resolved i 914 66 22ms 32.5s 54.6s 54.7s 0 transport_latency_assumed market_resolved k 914 42 15ms 36.2s 54.1s 54.2s 0 transport_latency_assumed market_resolved m 914 882 6ms 30.5s 50.0s 50.0s 0 transport_latency_assumed new_market g 914 108 361ms 17.4s 58.6s 1.4min 0 transport_latency_assumed new_market h 914 197 187ms 21.4s 1.0min 1.7min 0 transport_latency_assumed new_market i 914 223 150ms 18.5s 1.1min 1.6min 0 transport_latency_assumed new_market k 914 193 139ms 18.5s 1.0min 1.6min 0 transport_latency_assumed new_market m 914 725 55ms 21.5s 1.0min 1.7min 0 transport_latency_assumed price_change g 103,170,322 14,474 77ms 122ms 1.7s 27.9s 0 transport_latency_assumed price_change h 103,337,916 904,986 18ms 26ms 283ms 51.3s 0 transport_latency_assumed price_change i 103,290,324 489,004 22ms 30ms 155ms 18.8s 0 transport_latency_assumed price_change k 103,320,286 4,028,538 14ms 24ms 171ms 42.8s 0 transport_latency_assumed price_change m 103,216,524 97,930,784 5ms 11ms 71ms 6.4s 0 transport_latency_assumed tick_size_change g 3,212 not meas. 77ms 92ms 283ms 609ms 0 transport_latency_assumed tick_size_change h 3,212 24 18ms 30ms 84ms 451ms 0 transport_latency_assumed tick_size_change i 3,212 8 22ms 29ms 94ms 469ms 0 transport_latency_assumed tick_size_change k 3,204 96 14ms 22ms 161ms 2.7s 0 transport_latency_assumed tick_size_change m 3,212 3,084 5ms 9ms 38ms 182ms 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-30/11/2026-09-30T11.parquet sha256sum 2026-09-30T11.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.