Hour audit: 2026-09-13T08
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-13T08 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-13T08:00:00.000038712+00:00 · last event 2026-09-13T08:59:59.999975419+00:00
VOLUME 98,152,591 rows · 974,406,087 bytes (929.27 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 98,109,224 · h: 98,106,107 · f: 98,094,415 · e: 98,079,681 · g: 98,001,849 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 93,652,316 (95.42%) · h: 3,749,330 (3.82%) · f: 267,922 (0.27%) · e: 432,194 (0.44%) · g: 50,829 (0.05%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 98,152,591 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 b3dad2cc49f6a7d847c0415250923f720a93dbae8bd1734a58a4acd826574d52
the corpus checksum ledger names this file with the same digest
joined 98,154,500 to merged 98,152,591, minus 1,909 (minus 0.0019%)
boundary drops 1,909 · 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-13T09:56:08Z 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,403,838 112,243,902 0-39 6d84c87a081ef51f80f12c231df4dc7e29a5e3b382b8134012d6125d0397c75a book 132,640 13,447,594 40-40 22560e65c2a7b8c2dd8b5766b4d4521053e9502180aff6c0545ec11805e27126 last_trade_price 48,735 2,816,248 41-41 969b93958f24a3d5056954139094e7b7276895a79f097d131b48e180ae337e16 market_resolved 594 90,750 42-42 84849cb44221fcc0c8a709ce6f4e6c0fa3e13df75f36fc89a059a6eb9545d227 new_market 2,816 278,317 43-43 15fec9124951d26e2084e85ce0b793270ddbba33e7c407c261776cd9ddeb9ea6 price_change 87,561,964 844,335,104 44-378 8741a8335f4e3731a887f2912d2a40326879c6d7b446df528d958ab3dae16cfa tick_size_change 2,004 73,748 379-379 4c3883f7f4884b279e72cd81c52b9c4cd7c81d22d79e44fe8c2210fad3e800d9 EVENT MIX count share price_change 87,561,964 89.21% best_bid_ask 10,403,838 10.60% book 132,640 0.14% last_trade_price 48,735 0.05% new_market 2,816 <0.01% tick_size_change 2,004 <0.01% market_resolved 594 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,404,055 10,403,838 217 591 FULL book 132,680 132,640 40 11,518 FULL last_trade_price 48,739 48,735 4 0 FULL market_resolved 594 594 0 0 FULL new_market 2,816 2,816 0 0 FULL price_change 87,563,612 87,561,964 1,648 164 FULL tick_size_change 2,004 2,004 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,401,700 9,955,709 4ms 10ms 200ms 10.3s 0 transport_latency_assumed best_bid_ask e 10,400,064 45,426 39ms 45ms 248ms 16.8s 0 transport_latency_assumed best_bid_ask f 10,399,996 26,602 47ms 53ms 260ms 16.1s 0 transport_latency_assumed best_bid_ask g 10,396,679 2,505 80ms 99ms 571ms 20.1s 0 transport_latency_assumed best_bid_ask h 10,400,818 373,596 18ms 22ms 289ms 42.6s 0 transport_latency_assumed book c 104,866 98,569 6ms 27ms 1.5min 87.9d 0 book_staleness book e 103,842 1,890 41ms 149ms 3.8s 40.7d 0 book_staleness book f 104,246 2,219 50ms 151ms 10.7s 44.0d 0 book_staleness book g 126,465 24,564 89ms 21.1min 5.9d 87.9d 0 book_staleness book h 103,710 5,398 21ms 53ms 2.8s 42.4d 0 book_staleness last_trade_price c 48,669 46,448 10ms 41ms 263ms 4.9s 0 transport_latency_assumed last_trade_price e 48,616 216 46ms 126ms 1.5s 16.8s 0 transport_latency_assumed last_trade_price f 48,682 126 55ms 128ms 2.5s 16.0s 0 transport_latency_assumed last_trade_price g 48,294 20 93ms 215ms 2.8s 20.2s 0 transport_latency_assumed last_trade_price h 48,654 1,925 23ms 60ms 478ms 23.4s 0 transport_latency_assumed market_resolved c 549 499 5ms 29ms 569ms 1.1s 0 transport_latency_assumed market_resolved e 549 48 43ms 464ms 47.9s 48.3s 0 transport_latency_assumed market_resolved f 549 3 50ms 523ms 47.9s 48.3s 0 transport_latency_assumed market_resolved g 549 not meas. 95ms 860ms 54.5s 54.9s 0 transport_latency_assumed market_resolved h 549 44 19ms 140ms 59.8s 1.0min 0 transport_latency_assumed new_market c 1,824 973 165ms 23.7s 51.7s 3.4h 0 transport_latency_assumed new_market e 1,824 420 205ms 23.3s 51.5s 3.4h 0 transport_latency_assumed new_market f 1,824 512 183ms 24.2s 54.9s 1.2h 0 transport_latency_assumed new_market g 1,824 190 325ms 23.7s 48.4s 6.4h 0 transport_latency_assumed new_market h 1,824 721 151ms 23.1s 46.7s 7.8h 0 transport_latency_assumed price_change c 87,549,612 83,548,296 5ms 11ms 225ms 12.0s 0 transport_latency_assumed price_change e 87,522,782 384,170 39ms 48ms 345ms 16.8s 0 transport_latency_assumed price_change f 87,537,114 238,448 47ms 57ms 349ms 16.1s 0 transport_latency_assumed price_change g 87,426,034 23,550 81ms 106ms 728ms 20.3s 0 transport_latency_assumed price_change h 87,548,548 3,367,500 18ms 25ms 319ms 45.4s 0 transport_latency_assumed tick_size_change c 2,004 1,822 5ms 26ms 311ms 991ms 0 transport_latency_assumed tick_size_change e 2,004 24 40ms 59ms 378ms 583ms 0 transport_latency_assumed tick_size_change f 2,004 12 47ms 65ms 475ms 737ms 0 transport_latency_assumed tick_size_change g 2,004 not meas. 82ms 209ms 754ms 1.3s 0 transport_latency_assumed tick_size_change h 2,004 146 18ms 28ms 364ms 5.3s 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/08/2026-09-13T08.parquet sha256sum 2026-09-13T08.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.