Hour audit: 2026-09-11T19
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.
1 finding
- a machine expected this hour contributed nothing. Of the 5 machines expected to be capturing this hour, 1 contributed no rows: f. The hour is still whole on minutes; it simply rests on 4 machines rather than 5.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-11T19 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-11T19:00:00.000004361+00:00 · last event 2026-09-11T19:59:59.999989658+00:00
VOLUME 131,609,957 rows · 1,438,184,009 bytes (1.34 GiB) · 7 products, all holding rows
WITNESSES cegh — 4 machines contributed rows
captured e: 128,116,720 · h: 128,055,906 · g: 117,392,445 · c: 86,000,910 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 5,212,348 (3.96%) · h: 44,966,891 (34.17%) · g: 586,240 (0.45%) · c: 80,844,478 (61.43%) (rows of the merged file that came from it; these partition it)
5 expected (cefgh), 1 contributed nothing: f
INTEGRITY sha256 bb1b19d211c20f5d17028b66fd20ea0cbe9255f4a34af59008f8fb8a86d70327
the corpus checksum ledger names this file with the same digest
joined 131,612,362 to merged 131,609,957, minus 2,405 (minus 0.0018%)
boundary drops 2,405 · 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-12T01:28:56Z as cegh
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 7/8 pass, 1 finding
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
FINDING a machine expected this hour contributed nothing
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 12,285,913 142,299,232 0-46 58159e341a6ebcac16c959c1d0f5e7f00e38f034e231b98ed28a2a9b6edce8a5 book 3,527,714 123,745,828 47-60 c0b24f5bc7574984f162cb40da592bd46a73d946d26a972e6484c83c7abe28c6 last_trade_price 60,014 3,463,977 61-61 04be93f1bc3926ca94546c135e2f4acc7319ae1d5246670c516ef884d9f5c7c5 market_resolved 2,501 161,217 62-62 a52f7c1631ef5bd411e0e6ec26af89c80bb2273a02823837b34001a3492b7009 new_market 9,115 394,939 63-63 b98fdb615edca74a1091af2ec380a7982c54330c73ab9990fde67c1123ea9435 price_change 115,717,672 1,166,372,113 64-505 8c6275752253f01c614efce8cd3d17f62beb08746d9581e96513c92a82bf58dd tick_size_change 7,028 252,414 506-506 6d11759336e30b2caed165a7aa237716985b9851e281ed4ea5b36ccac85d0ff5 EVENT MIX count share price_change 115,717,672 87.92% best_bid_ask 12,285,913 9.34% book 3,527,714 2.68% last_trade_price 60,014 0.05% new_market 9,115 <0.01% tick_size_change 7,028 <0.01% market_resolved 2,501 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,286,114 12,285,913 201 83,798 PARTIAL book 3,527,812 3,527,714 98 210,362 PARTIAL last_trade_price 60,016 60,014 2 3,694 PARTIAL market_resolved 2,501 2,501 0 899 PARTIAL new_market 9,115 9,115 0 2,182 PARTIAL price_change 115,719,776 115,717,672 2,104 130,567 PARTIAL tick_size_change 7,028 7,028 0 1,755 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 7,975,869 7,499,134 5ms 17ms 205ms 5.3s 0 transport_latency_assumed best_bid_ask e 12,282,872 500,544 42ms 62ms 322ms 17.8s 0 transport_latency_assumed best_bid_ask g 11,172,752 15,547 85ms 153ms 538ms 23.3s 0 transport_latency_assumed best_bid_ask h 12,279,871 4,270,688 19ms 45ms 453ms 43.4s 0 transport_latency_assumed book c 3,280,320 3,064,627 15.4min 2.3h 31.0d 104.9d 0 book_staleness book e 131,733 9,379 46ms 566ms 38.7min 86.3d 0 book_staleness book g 976,610 407,499 6.8min 1.7h 30.0d 104.9d 0 book_staleness book h 135,029 46,209 25ms 374ms 1.7h 78.4d 0 book_staleness last_trade_price c 39,577 37,196 11ms 58ms 380ms 4.8s 0 transport_latency_assumed last_trade_price e 59,750 2,524 55ms 299ms 4.4s 18.0s 0 transport_latency_assumed last_trade_price g 55,512 313 105ms 579ms 12.5s 23.3s 0 transport_latency_assumed last_trade_price h 59,457 19,981 27ms 137ms 886ms 10.2s 0 transport_latency_assumed market_resolved c 2,091 2,018 11.5min 29.3min 39.8min 41.9min 0 transport_latency_assumed market_resolved e 899 30 43ms 124ms 371ms 659ms 0 transport_latency_assumed market_resolved g 988 59 91ms 7.1min 13.1min 14.2min 0 transport_latency_assumed market_resolved h 899 394 20ms 80ms 58.5s 1.0min 0 transport_latency_assumed new_market c 8,548 7,433 10.4min 26.4min 33.1min 35.7min 0 transport_latency_assumed new_market e 2,182 596 222ms 15.0s 1.3min 1.9min 0 transport_latency_assumed new_market g 3,043 190 624ms 8.6min 9.7min 9.8min 0 transport_latency_assumed new_market h 2,182 896 174ms 14.0s 1.3min 1.9min 0 transport_latency_assumed price_change c 74,689,693 70,229,455 6ms 18ms 215ms 8.3s 0 transport_latency_assumed price_change e 115,632,256 4,699,114 42ms 74ms 475ms 18.3s 0 transport_latency_assumed price_change g 105,176,744 162,628 86ms 171ms 1.1s 23.3s 0 transport_latency_assumed price_change h 115,571,440 40,626,475 19ms 50ms 496ms 45.4s 0 transport_latency_assumed tick_size_change c 4,812 4,615 5ms 13ms 122ms 472ms 0 transport_latency_assumed tick_size_change e 7,028 161 42ms 52ms 203ms 520ms 0 transport_latency_assumed tick_size_change g 6,796 4 86ms 163ms 518ms 3.4s 0 transport_latency_assumed tick_size_change h 7,028 2,248 19ms 34ms 166ms 6.0s 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-11/19/2026-09-11T19.parquet sha256sum 2026-09-11T19.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.