Hour audit: 2026-09-06T07
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-06T07 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-06T07:00:00.068094128+00:00 · last event 2026-09-06T07:59:59.999972295+00:00
VOLUME 104,077,517 rows · 989,629,287 bytes (943.78 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 104,016,990 · f: 104,015,071 · g: 104,010,518 · c: 103,986,500 · e: 103,930,506 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 10,003 (0.01%) · f: 27,645 (0.03%) · g: 104,008,534 (99.93%) · c: 20,257 (0.02%) · e: 11,078 (0.01%) (rows of the merged file that came from it; these partition it)
5 product-machine pairs publish no supplied count; the figures above still sum to the file's 104,077,517 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 0a3c5b734233552563d0afdbcf88e66a6b7c5f56c0bf6ad876f359e3f9558f64
the corpus checksum ledger names this file with the same digest
joined 104,079,517 to merged 104,077,517, minus 2,000 (minus 0.0019%)
boundary drops 2,000 · 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-06T10:01:29Z 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,787,757 121,894,042 0-44 3e3b870ca54cc3310506082bd347296e3c10a92c60f0b604f1038ea6020f3d38 book 128,830 12,416,740 45-45 8f44fb6df456aeb79b37c2d3bacc98eb6bcd40b9482a8aa2bee0690e4c8f842e last_trade_price 49,678 2,776,088 46-46 7b95fbcdadf6384566af07c0deae74c374f35894cbd7282fd132d0a1d97a02be market_resolved 915 142,762 47-47 8a01f8d491b48c8bf25b3775e967facc5b8694416a6ebc6f94411224e337c08f new_market 1,530 158,325 48-48 0082917e8da7a7f2d63101a545af1ce17e418ad4a6b2f0d809eadfb334308cd0 price_change 92,106,803 850,982,776 49-400 5d48788ca30e3db5d03d1204f4fdc2fa6db99f619c4d072167678ccc5b0a6d1c tick_size_change 2,004 73,663 401-401 805dc22e9df27693c4af4fb14afb5a006ba3656c9798f3cb9272e0e17b2f8f22 EVENT MIX count share price_change 92,106,803 88.50% best_bid_ask 11,787,757 11.33% book 128,830 0.12% last_trade_price 49,678 0.05% tick_size_change 2,004 <0.01% new_market 1,530 <0.01% market_resolved 915 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,788,082 11,787,757 325 262 FULL book 128,848 128,830 18 10,328 FULL last_trade_price 49,679 49,678 1 0 FULL market_resolved 915 915 0 0 FULL new_market 1,530 1,530 0 0 FULL price_change 92,108,459 92,106,803 1,656 396 FULL tick_size_change 2,004 2,004 0 1 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,783,704 575 4ms 8ms 81ms 4.4s 0 transport_latency_assumed best_bid_ask e 11,786,225 504 39ms 44ms 143ms 2.5s 0 transport_latency_assumed best_bid_ask f 11,785,897 933 47ms 52ms 153ms 4.3s 0 transport_latency_assumed best_bid_ask g 11,785,474 11,785,149 78ms 94ms 331ms 15.6s 0 transport_latency_assumed best_bid_ask h 11,786,496 596 17ms 21ms 134ms 16.0s 0 transport_latency_assumed book c 108,398 6,281 6ms 44ms 4.1h 25.4d 0 book_staleness book e 107,496 4,593 41ms 150ms 8.2h 99.4d 0 book_staleness book f 108,352 5,505 50ms 175ms 9.8h 99.4d 0 book_staleness book g 111,509 111,507 83ms 719ms 14.1h 81.3d 0 book_staleness book h 103,747 944 20ms 46ms 2.2s 80.8d 0 book_staleness last_trade_price c 49,282 3 9ms 35ms 228ms 5.0s 0 transport_latency_assumed last_trade_price e 49,657 3 45ms 91ms 982ms 5.3s 0 transport_latency_assumed last_trade_price f 49,660 17 53ms 98ms 639ms 5.0s 0 transport_latency_assumed last_trade_price g 49,655 49,654 89ms 178ms 2.4s 15.6s 0 transport_latency_assumed last_trade_price h 49,653 1 22ms 54ms 355ms 7.6s 0 transport_latency_assumed market_resolved c 884 not meas. 4ms 7ms 34ms 368ms 0 transport_latency_assumed market_resolved e 884 12 40ms 181ms 59.1s 59.2s 0 transport_latency_assumed market_resolved f 884 19 49ms 189ms 59.6s 1.1min 0 transport_latency_assumed market_resolved g 884 884 84ms 238ms 704ms 1.4s 0 transport_latency_assumed market_resolved h 884 not meas. 18ms 62ms 152ms 287ms 0 transport_latency_assumed new_market c 1,015 40 97ms 15.7s 25.6s 2.4h 0 transport_latency_assumed new_market e 1,015 144 156ms 18.0s 26.8s 3.3h 0 transport_latency_assumed new_market f 1,015 231 174ms 16.2s 24.1s 3.1h 0 transport_latency_assumed new_market g 1,015 1,015 305ms 17.4s 25.5s 8.8h 0 transport_latency_assumed new_market h 1,015 100 138ms 18.6s 25.4s 52.7min 0 transport_latency_assumed price_change c 92,041,213 13,358 4ms 8ms 89ms 5.4s 0 transport_latency_assumed price_change e 91,983,225 5,822 39ms 45ms 181ms 2.5s 0 transport_latency_assumed price_change f 92,067,259 20,936 48ms 53ms 186ms 4.4s 0 transport_latency_assumed price_change g 92,059,981 92,058,325 79ms 98ms 418ms 15.6s 0 transport_latency_assumed price_change h 92,073,191 8,362 17ms 23ms 148ms 19.9s 0 transport_latency_assumed tick_size_change c 2,004 not meas. 4ms 7ms 41ms 209ms 0 transport_latency_assumed tick_size_change e 2,004 not meas. 40ms 46ms 165ms 253ms 0 transport_latency_assumed tick_size_change f 2,004 4 47ms 52ms 116ms 300ms 0 transport_latency_assumed tick_size_change g 2,000 2,000 78ms 97ms 424ms 646ms 0 transport_latency_assumed tick_size_change h 2,004 not meas. 17ms 24ms 143ms 377ms 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-06/07/2026-09-06T07.parquet sha256sum 2026-09-06T07.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.