Hour audit: 2026-09-07T15
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-07T15 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-07T15:00:00.000160798+00:00 · last event 2026-09-07T15:59:59.999988551+00:00
VOLUME 98,624,034 rows · 1,017,310,449 bytes (970.18 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 98,424,389 · f: 98,356,626 · g: 98,237,960 · e: 97,779,560 · c: 97,549,890 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 4,885,892 (4.95%) · f: 257,377 (0.26%) · g: 29,904 (0.03%) · e: 377,065 (0.38%) · c: 93,073,796 (94.37%) (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,624,034 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 5b0d6e5a725fa46bd342d5866a8010a56654325a94bd58027ab7d2b542d50956
the corpus checksum ledger names this file with the same digest
joined 98,626,705 to merged 98,624,034, minus 2,671 (minus 0.0027%)
boundary drops 2,671 · 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-07T16:56:11Z 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,172,284 110,949,558 0-38 6e1065248253670271edc97b4825e5a8b143e6d407ede479bd1967755c120f39 book 410,676 42,030,396 39-40 a61b87f210ffd600b5a5700feadfa962722a5c39e5fcc3c79e9feca106c5e8d6 last_trade_price 69,871 3,910,793 41-41 2fca9b6a09ea526cf02da41e97a370bac4af650518218ba52ed1302ab6fc0088 market_resolved 795 122,977 42-42 87ed5a335bb48e797f5abc58d46a33f4d86380816d4be128538d38a34d64dcf8 new_market 3,126 315,474 43-43 47bf45abaa2043504b028c190e43bd03e5f2b90b9b8a52d320d04104c489c760 price_change 87,964,362 858,749,641 44-379 1d92f100e8ed942a72587e7ee8459a6c0105b5e207f051f278708cd1c76d81cf tick_size_change 2,920 107,376 380-380 f951ec93415d569f082840393fb13b9a66190d606d1843226c86aa83d65cf2de EVENT MIX count share price_change 87,964,362 89.19% best_bid_ask 10,172,284 10.31% book 410,676 0.42% last_trade_price 69,871 0.07% new_market 3,126 <0.01% tick_size_change 2,920 <0.01% market_resolved 795 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,172,503 10,172,284 219 343 FULL book 411,410 410,676 734 106,671 FULL last_trade_price 69,871 69,871 0 44 FULL market_resolved 795 795 0 4 FULL new_market 3,126 3,126 0 0 FULL price_change 87,966,080 87,964,362 1,718 329 FULL tick_size_change 2,920 2,920 0 14 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,089,920 9,652,561 5ms 11ms 146ms 3.3s 0 transport_latency_assumed best_bid_ask e 10,089,608 32,510 40ms 49ms 251ms 8.4s 0 transport_latency_assumed best_bid_ask f 10,168,342 19,620 44ms 56ms 255ms 7.9s 0 transport_latency_assumed best_bid_ask g 10,166,844 1,298 84ms 116ms 613ms 25.6s 0 transport_latency_assumed best_bid_ask h 10,170,585 466,295 18ms 25ms 189ms 13.9s 0 transport_latency_assumed book c 189,798 171,833 8ms 1.5h 5.6d 100.7d 0 book_staleness book e 231,572 70,994 119ms 4.2h 16.1d 100.7d 0 book_staleness book f 230,074 67,958 101ms 3.9h 16.1d 100.7d 0 book_staleness book g 165,997 17,694 97ms 34.3s 17.7h 82.2d 0 book_staleness book h 233,279 82,197 36ms 4.0h 16.0d 100.7d 0 book_staleness last_trade_price c 69,113 65,718 10ms 44ms 282ms 5.0s 0 transport_latency_assumed last_trade_price e 69,058 187 47ms 307ms 3.4s 8.4s 0 transport_latency_assumed last_trade_price f 69,555 155 51ms 221ms 3.5s 7.9s 0 transport_latency_assumed last_trade_price g 69,034 5 100ms 874ms 11.9s 25.6s 0 transport_latency_assumed last_trade_price h 69,744 3,806 23ms 65ms 399ms 9.7s 0 transport_latency_assumed market_resolved c 758 724 5ms 14ms 24.0s 1.0min 0 transport_latency_assumed market_resolved e 754 33 42ms 361ms 1.0min 1.0min 0 transport_latency_assumed market_resolved f 758 8 46ms 397ms 1.0min 1.0min 0 transport_latency_assumed market_resolved g 758 not meas. 87ms 409ms 1.2s 4.1s 0 transport_latency_assumed market_resolved h 758 30 18ms 100ms 284ms 6.1s 0 transport_latency_assumed new_market c 2,035 1,080 91ms 1.7min 3.6min 5.7d 0 transport_latency_assumed new_market e 2,035 512 157ms 1.4min 3.5min 5.7d 0 transport_latency_assumed new_market f 2,035 259 196ms 1.3min 3.5min 5.7d 0 transport_latency_assumed new_market g 2,035 197 294ms 3.2min 3.6min 5.7d 0 transport_latency_assumed new_market h 2,035 1,078 107ms 3.3min 3.7min 5.7d 0 transport_latency_assumed price_change c 87,195,366 83,179,106 5ms 12ms 162ms 5.3s 0 transport_latency_assumed price_change e 87,383,649 272,817 41ms 62ms 446ms 8.4s 0 transport_latency_assumed price_change f 87,882,942 169,372 45ms 67ms 409ms 8.0s 0 transport_latency_assumed price_change g 87,830,372 10,710 85ms 157ms 1.3s 25.6s 0 transport_latency_assumed price_change h 87,945,068 4,332,357 18ms 28ms 216ms 25.3s 0 transport_latency_assumed tick_size_change c 2,900 2,774 5ms 9ms 206ms 427ms 0 transport_latency_assumed tick_size_change e 2,884 12 40ms 47ms 325ms 538ms 0 transport_latency_assumed tick_size_change f 2,920 5 45ms 58ms 302ms 793ms 0 transport_latency_assumed tick_size_change g 2,920 not meas. 84ms 121ms 465ms 1.6s 0 transport_latency_assumed tick_size_change h 2,920 129 18ms 37ms 297ms 994ms 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-07/15/2026-09-07T15.parquet sha256sum 2026-09-07T15.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.