Hour audit: 2026-09-17T23
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-17T23 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-17T23:00:00.000036781+00:00 · last event 2026-09-17T23:59:59.999997379+00:00
VOLUME 104,837,183 rows · 1,042,522,007 bytes (994.23 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 104,801,292 · h: 104,738,673 · f: 104,729,012 · e: 104,723,862 · g: 104,662,839 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 100,468,646 (95.83%) · h: 3,810,711 (3.63%) · f: 158,036 (0.15%) · e: 377,631 (0.36%) · g: 22,159 (0.02%) (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 104,837,183 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 de51aa7e8b3047d4e8d7e5efcc36989a083e1e6c83f15fc157abc037c68fa3bf
the corpus checksum ledger names this file with the same digest
joined 104,839,912 to merged 104,837,183, minus 2,729 (minus 0.0026%)
boundary drops 2,729 · 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-18T01:36:21Z 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 10,469,367 117,636,565 0-39 34c9c32f7b35d0f94480bb02765bb9b3b3d4140e4d86f0ee82f1a5edc544a3bd book 108,545 11,270,596 40-40 a6ad10f3184a3db2dc47640a76da815794a422d56f32210eba25f783b2f7d4c1 last_trade_price 43,428 2,460,318 41-41 d5b9f6b6ff1960c2a058b1c62af49cc2619edee7d1bc97f57e72fa846661a87b market_resolved 902 146,077 42-42 34569b9ae8d84eff6e7f776a1522baaf2ee6e6e10e0a4ec7e0ba0255704e914a new_market 1,199 131,214 43-43 327e2609cfb84c485f166ef9a48a40059a3fb4a4a830a5ed9bd67920dfb2a344 price_change 94,211,606 909,603,621 44-403 6efcaa8561fc89978d13971f2ce0628fcd3c16361e1dfafe305a7eecdf503789 tick_size_change 2,136 79,150 404-404 9afaf5fb4ec31047290961f2962687e2543e580c73170c655cdc0acb587fe17e EVENT MIX count share price_change 94,211,606 89.86% best_bid_ask 10,469,367 9.99% book 108,545 0.10% last_trade_price 43,428 0.04% tick_size_change 2,136 <0.01% new_market 1,199 <0.01% market_resolved 902 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,469,659 10,469,367 292 188 FULL book 108,570 108,545 25 5,197 FULL last_trade_price 43,430 43,428 2 0 FULL market_resolved 902 902 0 0 FULL new_market 1,199 1,199 0 0 FULL price_change 94,214,016 94,211,606 2,410 327 FULL tick_size_change 2,136 2,136 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,468,623 10,065,917 5ms 10ms 87ms 4.1s 0 transport_latency_assumed best_bid_ask e 10,466,933 32,726 40ms 46ms 155ms 4.0s 0 transport_latency_assumed best_bid_ask f 10,466,847 13,474 48ms 55ms 172ms 7.9s 0 transport_latency_assumed best_bid_ask g 10,466,170 1,542 81ms 99ms 284ms 12.8s 0 transport_latency_assumed best_bid_ask h 10,467,454 355,708 17ms 25ms 129ms 7.2s 0 transport_latency_assumed book c 92,099 86,734 6ms 33ms 2.3min 92.5d 0 book_staleness book e 93,959 4,576 42ms 294ms 19.7min 92.4d 0 book_staleness book f 93,117 3,251 50ms 210ms 15.0min 92.5d 0 book_staleness book g 95,596 5,626 90ms 514ms 32.3min 92.5d 0 book_staleness book h 94,094 8,358 21ms 122ms 15.8min 92.5d 0 book_staleness last_trade_price c 43,334 41,121 10ms 47ms 223ms 4.8s 0 transport_latency_assumed last_trade_price e 43,282 267 48ms 174ms 1.3s 4.9s 0 transport_latency_assumed last_trade_price f 43,252 126 55ms 162ms 1.2s 4.9s 0 transport_latency_assumed last_trade_price g 43,145 11 98ms 244ms 2.4s 12.9s 0 transport_latency_assumed last_trade_price h 43,211 1,903 23ms 82ms 363ms 5.0s 0 transport_latency_assumed market_resolved c 877 826 5ms 15ms 54.9s 54.9s 0 transport_latency_assumed market_resolved e 877 1 42ms 201ms 44.1s 1.0min 0 transport_latency_assumed market_resolved f 877 1 50ms 209ms 50.6s 50.7s 0 transport_latency_assumed market_resolved g 877 20 88ms 306ms 830ms 1.1min 0 transport_latency_assumed market_resolved h 877 54 19ms 80ms 43.5s 1.0min 0 transport_latency_assumed new_market c 825 466 79ms 13.0s 59.1s 2.6min 0 transport_latency_assumed new_market e 825 127 146ms 11.8s 1.1min 4.5min 0 transport_latency_assumed new_market f 825 134 145ms 12.1s 57.7s 3.7min 0 transport_latency_assumed new_market g 825 86 277ms 13.0s 1.0min 1.1min 0 transport_latency_assumed new_market h 825 386 97ms 15.7s 1.0min 2.0min 0 transport_latency_assumed price_change c 94,193,398 90,271,520 5ms 11ms 103ms 4.1s 0 transport_latency_assumed price_change e 94,115,850 339,926 40ms 52ms 261ms 7.5s 0 transport_latency_assumed price_change f 94,121,958 141,046 48ms 60ms 259ms 9.0s 0 transport_latency_assumed price_change g 94,054,090 14,874 81ms 103ms 427ms 12.9s 0 transport_latency_assumed price_change h 94,130,076 3,444,240 17ms 29ms 174ms 7.2s 0 transport_latency_assumed tick_size_change c 2,136 2,062 5ms 9ms 43ms 141ms 0 transport_latency_assumed tick_size_change e 2,136 8 39ms 44ms 104ms 382ms 0 transport_latency_assumed tick_size_change f 2,136 4 48ms 52ms 141ms 220ms 0 transport_latency_assumed tick_size_change g 2,136 not meas. 81ms 95ms 119ms 561ms 0 transport_latency_assumed tick_size_change h 2,136 62 17ms 24ms 78ms 1.8s 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-17/23/2026-09-17T23.parquet sha256sum 2026-09-17T23.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.