Hour audit: 2026-09-13T14
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-13T14 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-13T14:00:00.000003877+00:00 · last event 2026-09-13T14:59:59.999991837+00:00
VOLUME 116,274,912 rows · 1,251,140,185 bytes (1.17 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 113,394,340 · e: 113,361,493 · f: 113,360,614 · g: 113,302,489 · c: 78,449,705 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 38,169,703 (32.83%) · e: 2,395,992 (2.06%) · f: 533,147 (0.46%) · g: 90,379 (0.08%) · c: 75,085,691 (64.58%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 fcc1de4a32c2e45916519374b0c68b2fb0cacc2aa89311194709a3a6ec3c4fbe
the corpus checksum ledger names this file with the same digest
joined 116,278,180 to merged 116,274,912, minus 3,268 (minus 0.0028%)
boundary drops 3,268 · 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-13T15:58:49Z 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,868,571 133,035,278 0-45 8aa0492f8d6f7830d03a5a11b26811ede65f22761aac31dfcf793a4795691db9 book 2,988,253 98,700,738 46-57 94707de5059a4d4a5c45e80c15735444d1f74dc2a1d90c9e7cd1a0903b38de18 last_trade_price 60,983 3,591,250 58-58 6f23a47e5cf054b5620f3aeb6fe82a49144ce4f78f7dbd933d1a5bc0fee8a3d0 market_resolved 2,680 235,864 59-59 8f0e25f7498c34ec8cd48d8dad8efb575411e9a18823c340d930f76603366872 new_market 3,221 246,063 60-60 c68a06043c930022452ebb674462892c5116bc064e503b8a5d602de5d93478f7 price_change 101,343,916 1,013,739,569 61-447 59ac9ce238c307b173a0b7cafb82f78cbd0c7aa58db16151d723d79be1fb96ec tick_size_change 7,288 266,974 448-448 bb859979609c16420d6d476fb6257ccb1f82e2a71743c6aa76be7a107ed1e4f0 EVENT MIX count share price_change 101,343,916 87.16% best_bid_ask 11,868,571 10.21% book 2,988,253 2.57% last_trade_price 60,983 0.05% tick_size_change 7,288 <0.01% new_market 3,221 <0.01% market_resolved 2,680 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,868,788 11,868,571 217 5,760 FULL book 2,989,639 2,988,253 1,386 174,752 FULL last_trade_price 60,984 60,983 1 952 FULL market_resolved 2,680 2,680 0 44 FULL new_market 3,221 3,221 0 1 FULL price_change 101,345,580 101,343,916 1,664 3,682 FULL tick_size_change 7,288 7,288 0 651 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 7,905,933 7,573,731 5ms 12ms 91ms 4.8s 0 transport_latency_assumed best_bid_ask e 11,866,508 245,293 40ms 46ms 227ms 26.1s 0 transport_latency_assumed best_bid_ask f 11,866,224 48,172 47ms 56ms 270ms 14.7s 0 transport_latency_assumed best_bid_ask g 11,863,261 5,527 81ms 100ms 494ms 29.5s 0 transport_latency_assumed best_bid_ask h 11,867,451 3,995,848 18ms 28ms 247ms 52.4s 0 transport_latency_assumed book c 2,937,767 2,926,921 18.8min 1.9d 36.0d 106.7d 0 book_staleness book e 128,425 4,883 42ms 173ms 5.1s 88.0d 0 book_staleness book f 128,795 2,075 49ms 181ms 6.9s 88.1d 0 book_staleness book g 149,601 9,936 88ms 3.2min 6.1d 88.2d 0 book_staleness book h 128,535 44,438 21ms 54ms 3.5s 88.2d 0 book_staleness last_trade_price c 39,852 37,743 11ms 45ms 250ms 5.0s 0 transport_latency_assumed last_trade_price e 60,828 1,354 47ms 152ms 2.6s 26.1s 0 transport_latency_assumed last_trade_price f 60,746 330 55ms 155ms 2.1s 14.8s 0 transport_latency_assumed last_trade_price g 60,470 111 92ms 215ms 4.8s 29.6s 0 transport_latency_assumed last_trade_price h 60,952 21,445 23ms 67ms 580ms 44.0s 0 transport_latency_assumed market_resolved c 2,252 2,179 4.9min 15.1min 22.2min 23.2min 0 transport_latency_assumed market_resolved e 1,366 68 41ms 141ms 58.6s 1.0min 0 transport_latency_assumed market_resolved f 1,366 2 48ms 155ms 58.6s 1.0min 0 transport_latency_assumed market_resolved g 1,366 1 84ms 242ms 46.8s 59.0s 0 transport_latency_assumed market_resolved h 1,367 430 18ms 59ms 40.7s 53.1s 0 transport_latency_assumed new_market c 2,422 1,577 1.8min 8.8min 14.2min 16.6min 0 transport_latency_assumed new_market e 1,495 421 200ms 1.1min 1.7min 2.0min 0 transport_latency_assumed new_market f 1,495 286 216ms 1.1min 2.0min 2.1min 0 transport_latency_assumed new_market g 1,495 186 314ms 1.0min 1.8min 2.1min 0 transport_latency_assumed new_market h 1,495 751 172ms 1.1min 1.5min 1.6min 0 transport_latency_assumed price_change c 67,556,791 64,538,989 5ms 13ms 105ms 5.9s 0 transport_latency_assumed price_change e 101,295,583 2,143,892 40ms 52ms 368ms 26.1s 0 transport_latency_assumed price_change f 101,294,700 482,270 47ms 64ms 392ms 14.9s 0 transport_latency_assumed price_change g 101,219,012 74,616 82ms 110ms 709ms 30.1s 0 transport_latency_assumed price_change h 101,327,252 34,104,149 18ms 31ms 295ms 52.4s 0 transport_latency_assumed tick_size_change c 4,688 4,551 5ms 11ms 71ms 293ms 0 transport_latency_assumed tick_size_change e 7,288 81 40ms 46ms 234ms 821ms 0 transport_latency_assumed tick_size_change f 7,288 12 47ms 58ms 269ms 635ms 0 transport_latency_assumed tick_size_change g 7,284 2 80ms 99ms 430ms 1.0s 0 transport_latency_assumed tick_size_change h 7,288 2,642 18ms 27ms 148ms 26.5s 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/14/2026-09-13T14.parquet sha256sum 2026-09-13T14.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.