Hour audit: 2026-09-13T16
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-13T16 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-13T16:00:00.000033211+00:00 · last event 2026-09-13T16:59:59.999930574+00:00
VOLUME 117,756,789 rows · 1,277,894,306 bytes (1.19 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 116,334,435 · e: 116,327,951 · f: 116,318,308 · g: 116,236,540 · c: 100,874,706 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 20,306,342 (17.24%) · e: 1,602,193 (1.36%) · f: 646,476 (0.55%) · g: 65,989 (0.06%) · c: 95,135,789 (80.79%) (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 117,756,789 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 b080794bf529b50027833f7d1b8c99e253e45356c8e8ab6be3512e22e6134996
the corpus checksum ledger names this file with the same digest
joined 117,760,107 to merged 117,756,789, minus 3,318 (minus 0.0028%)
boundary drops 3,318 · 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-13T18:00:13Z as cefgh
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 our incident register was checked against the venue's own status feed at 2026-09-23T20:35Z and names no event in this hour. That is a statement about what they published, not a check that every message they sent reached us.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,237,450 127,340,379 0-42 ae039573a63c70162ea8119c2c7d49e5e61e14c4fa88f19b9c4386bf3713d66f book 1,520,946 80,983,462 43-48 40623df71252a4685d1d60d8dba7adda23808a504d64f63d400ca517c322b2af last_trade_price 63,538 3,775,532 49-49 6058e331ae27b11f86084decc859816365e2be44e060bc106d0308aaa3aac960 market_resolved 2,875 434,698 50-50 2d8e0608edf1cef5e05244c12dbcf50bd0186f0b589352fb94aca253fda87652 new_market 4,308 416,128 51-51 b8fcf14cdf6716aa42d91788e7ee344dea609ab4b98004a7b2996ed3e173994f price_change 104,919,328 1,063,303,250 52-452 244dd651ffa664c200673cd609c5f832f3aa6f48d35c0bb41fdef9d00fde1ba5 tick_size_change 8,344 301,699 453-453 04f34365aeff3a7a4a514d7041d6ec2efd54002c0a007fd6b2fe552327313d76 EVENT MIX count share price_change 104,919,328 89.10% best_bid_ask 11,237,450 9.54% book 1,520,946 1.29% last_trade_price 63,538 0.05% tick_size_change 8,344 <0.01% new_market 4,308 <0.01% market_resolved 2,875 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,237,656 11,237,450 206 2,833 FULL book 1,522,226 1,520,946 1,280 172,625 FULL last_trade_price 63,538 63,538 0 371 FULL market_resolved 2,875 2,875 0 276 FULL new_market 4,308 4,308 0 99 FULL price_change 104,921,160 104,919,328 1,832 1,771 FULL tick_size_change 8,344 8,344 0 95 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,660,936 9,124,483 5ms 14ms 246ms 6.0s 0 transport_latency_assumed best_bid_ask e 11,233,154 150,828 41ms 56ms 372ms 17.9s 0 transport_latency_assumed best_bid_ask f 11,232,560 58,122 47ms 67ms 395ms 15.6s 0 transport_latency_assumed best_bid_ask g 11,229,150 4,850 84ms 134ms 805ms 37.3s 0 transport_latency_assumed best_bid_ask h 11,233,826 1,899,167 19ms 33ms 514ms 51.4s 0 transport_latency_assumed book c 1,490,472 1,476,748 12.3min 1.9d 35.9d 106.8d 0 book_staleness book e 136,750 4,394 45ms 332ms 14.8s 88.1d 0 book_staleness book f 137,659 2,952 50ms 358ms 3.5min 88.2d 0 book_staleness book g 157,045 10,654 90ms 2.2min 4.9d 88.3d 0 book_staleness book h 137,120 26,198 24ms 92ms 26.5s 88.3d 0 book_staleness last_trade_price c 53,946 50,513 11ms 52ms 357ms 5.0s 0 transport_latency_assumed last_trade_price e 63,433 892 52ms 212ms 4.8s 18.0s 0 transport_latency_assumed last_trade_price f 63,333 395 58ms 206ms 3.7s 15.6s 0 transport_latency_assumed last_trade_price g 62,856 40 96ms 403ms 9.6s 37.2s 0 transport_latency_assumed last_trade_price h 63,361 11,698 25ms 76ms 756ms 40.6s 0 transport_latency_assumed market_resolved c 2,578 2,478 5ms 120ms 4.8min 5.1min 0 transport_latency_assumed market_resolved e 2,564 50 71ms 197ms 57.3s 1.0min 0 transport_latency_assumed market_resolved f 2,564 12 70ms 202ms 57.4s 1.0min 0 transport_latency_assumed market_resolved g 2,565 2 100ms 309ms 833ms 2.1min 0 transport_latency_assumed market_resolved h 2,564 333 29ms 69ms 317ms 5.7s 0 transport_latency_assumed new_market c 2,597 1,716 118ms 23.9s 1.1min 18.3min 0 transport_latency_assumed new_market e 2,696 583 235ms 23.5s 58.2s 12.4min 0 transport_latency_assumed new_market f 2,696 462 240ms 22.5s 46.6s 2.0min 0 transport_latency_assumed new_market g 2,696 377 376ms 22.9s 41.0s 2.3min 0 transport_latency_assumed new_market h 2,696 1,170 178ms 23.3s 48.0s 9.7min 0 transport_latency_assumed price_change c 89,656,213 84,472,203 5ms 16ms 260ms 7.0s 0 transport_latency_assumed price_change e 104,881,010 1,445,430 42ms 71ms 567ms 18.0s 0 transport_latency_assumed price_change f 104,871,152 584,517 47ms 83ms 574ms 15.8s 0 transport_latency_assumed price_change g 104,773,884 50,066 84ms 173ms 1.6s 37.4s 0 transport_latency_assumed price_change h 104,886,524 18,367,112 19ms 38ms 531ms 51.5s 0 transport_latency_assumed tick_size_change c 7,964 7,648 5ms 12ms 104ms 1.1s 0 transport_latency_assumed tick_size_change e 8,344 16 42ms 49ms 373ms 2.9s 0 transport_latency_assumed tick_size_change f 8,344 16 47ms 54ms 410ms 2.0s 0 transport_latency_assumed tick_size_change g 8,344 not meas. 81ms 101ms 534ms 1.4s 0 transport_latency_assumed tick_size_change h 8,344 664 18ms 26ms 309ms 37.0s 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-13/16/2026-09-13T16.parquet sha256sum 2026-09-13T16.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.