Hour audit: 2026-09-07T21
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-07T21 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-07T21:00:00.000862084+00:00 · last event 2026-09-07T21:59:59.999970670+00:00
VOLUME 89,495,389 rows · 903,800,424 bytes (861.93 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 89,349,522 · h: 89,305,375 · f: 89,286,918 · g: 89,277,946 · e: 89,271,139 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 84,902,087 (94.87%) · h: 4,208,471 (4.70%) · f: 117,168 (0.13%) · g: 49,211 (0.05%) · e: 218,452 (0.24%) (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 89,495,389 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 96fde25db26179661f7bfb4008e817a72d0afe30464a447550d47d2c1fc9f52f
the corpus checksum ledger names this file with the same digest
joined 89,497,887 to merged 89,495,389, minus 2,498 (minus 0.0028%)
boundary drops 2,498 · 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-07T22:53:52Z 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,526,918 112,330,125 0-40 cad8908e0667e1798e2fe1511668aed0bdce11035cad3ab50b4c2675a83f009f book 334,893 34,291,844 41-42 049962de0fe7cc2a836a497479ed410caa49a8f7a8ce4b7037edc0c7b93238e5 last_trade_price 55,102 3,120,350 43-43 b0c353b7d20360c30d883a5273778a206f5c2eed81c99b6dc4af76405978957b market_resolved 2,669 436,944 44-44 bdbf3550abc179fb875e39653831ca611da76749ca23460e7ea1c5f54d81bea4 new_market 1,241 120,087 45-45 1f8f8a7bb59180a252f0390262a5bb9b0c496b544b4059e7a04fee7852fb6300 price_change 78,570,398 752,324,124 46-345 9dbabede9ffeddf871ad3703659f1c7a27ddea49500bf7082bd9b9bc7879a976 tick_size_change 4,168 153,203 346-346 7870f5dd9c2a38f8aaac89073459c89f7f03f90d071dfe3f2cbb2480856cca97 EVENT MIX count share price_change 78,570,398 87.79% best_bid_ask 10,526,918 11.76% book 334,893 0.37% last_trade_price 55,102 0.06% tick_size_change 4,168 <0.01% market_resolved 2,669 <0.01% new_market 1,241 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,527,137 10,526,918 219 189 FULL book 334,893 334,893 0 95,943 FULL last_trade_price 55,103 55,102 1 0 FULL market_resolved 2,669 2,669 0 0 FULL new_market 1,241 1,241 0 0 FULL price_change 78,572,676 78,570,398 2,278 172 FULL tick_size_change 4,168 4,168 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,525,914 10,038,259 5ms 8ms 81ms 7.1s 0 transport_latency_assumed best_bid_ask e 10,524,984 19,467 39ms 44ms 151ms 3.6s 0 transport_latency_assumed best_bid_ask f 10,524,896 10,064 45ms 50ms 168ms 4.7s 0 transport_latency_assumed best_bid_ask g 10,523,535 853 82ms 102ms 349ms 12.1s 0 transport_latency_assumed best_bid_ask h 10,525,396 458,275 12ms 15ms 103ms 20.2s 0 transport_latency_assumed book c 196,788 180,374 12ms 8.1h 16.3d 101.0d 0 book_staleness book e 158,807 36,214 45ms 3.4h 12.1d 101.0d 0 book_staleness book f 152,732 28,327 49ms 2.5h 5.9d 101.0d 0 book_staleness book g 163,979 40,133 118ms 4.0h 13.1d 101.0d 0 book_staleness book h 165,646 49,845 18ms 4.4h 13.2d 101.0d 0 book_staleness last_trade_price c 55,060 51,913 10ms 38ms 191ms 4.6s 0 transport_latency_assumed last_trade_price e 54,988 124 46ms 145ms 1.1s 4.6s 0 transport_latency_assumed last_trade_price f 55,072 96 51ms 161ms 1.2s 4.7s 0 transport_latency_assumed last_trade_price g 54,820 6 101ms 350ms 4.1s 9.3s 0 transport_latency_assumed last_trade_price h 54,945 2,963 17ms 52ms 288ms 7.9s 0 transport_latency_assumed market_resolved c 2,665 2,551 5ms 10ms 114ms 721ms 0 transport_latency_assumed market_resolved e 2,665 4 42ms 162ms 529ms 1.0min 0 transport_latency_assumed market_resolved f 2,665 2 48ms 182ms 519ms 1.0min 0 transport_latency_assumed market_resolved g 2,665 not meas. 94ms 322ms 855ms 2.0s 0 transport_latency_assumed market_resolved h 2,665 112 15ms 39ms 207ms 7.3s 0 transport_latency_assumed new_market c 765 469 97ms 22.8s 1.8min 24.8min 0 transport_latency_assumed new_market e 765 226 150ms 24.9s 1.7min 4.4min 0 transport_latency_assumed new_market f 765 57 193ms 23.0s 1.8min 18.6min 0 transport_latency_assumed new_market g 765 105 268ms 23.4s 1.8min 13.9min 0 transport_latency_assumed new_market h 765 384 116ms 25.0s 1.8min 19.0min 0 transport_latency_assumed price_change c 78,564,162 74,624,684 5ms 9ms 97ms 7.1s 0 transport_latency_assumed price_change e 78,524,762 162,402 40ms 47ms 235ms 5.0s 0 transport_latency_assumed price_change f 78,546,620 78,614 45ms 53ms 259ms 4.7s 0 transport_latency_assumed price_change g 78,528,014 8,114 82ms 119ms 532ms 12.1s 0 transport_latency_assumed price_change h 78,551,790 3,696,584 12ms 17ms 129ms 20.2s 0 transport_latency_assumed tick_size_change c 4,168 3,837 5ms 11ms 115ms 249ms 0 transport_latency_assumed tick_size_change e 4,168 15 40ms 48ms 162ms 273ms 0 transport_latency_assumed tick_size_change f 4,168 8 45ms 63ms 215ms 289ms 0 transport_latency_assumed tick_size_change g 4,168 not meas. 82ms 121ms 347ms 523ms 0 transport_latency_assumed tick_size_change h 4,168 308 12ms 18ms 207ms 1.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-07/21/2026-09-07T21.parquet sha256sum 2026-09-07T21.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.