Hour audit: 2026-09-21T15
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: g. 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-21T15 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-21T15:00:00.000171752+00:00 · last event 2026-09-21T15:59:59.999983155+00:00
VOLUME 118,923,433 rows · 1,285,075,384 bytes (1.20 GiB) · 7 products, all holding rows
WITNESSES cefh — 4 machines contributed rows
captured h: 117,022,512 · e: 116,519,598 · f: 111,927,704 · c: 96,363,104 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 26,318,798 (22.13%) · e: 1,725,662 (1.45%) · f: 654,653 (0.55%) · c: 90,224,320 (75.87%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 118,923,433 rows exactly, so those pairs supplied none
5 expected (cefgh), 1 contributed nothing: g
INTEGRITY sha256 0cc58e3e7f29e0d4bdb6425c8c43adead310ee0afb0bd16cced791c686f88c0b
the corpus checksum ledger names this file with the same digest
joined 118,925,323 to merged 118,923,433, minus 1,890 (minus 0.0016%)
boundary drops 1,890 · 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-21T16:56:05Z as cefh
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 11,503,118 133,591,073 0-43 614a32354060ce8cb776a9b94ca65411954837107c42eab37251447fb5cfffa2 book 1,814,639 82,887,086 44-50 becd98f2960a4f2d20e21f05415969c99b4fae24859139c3a02b14f71b72f908 last_trade_price 69,346 3,934,240 51-51 fe21e3ab7d861a2a4e80bc537424fb9b5f7670e58f8ffa191c23038e2340524b market_resolved 999 136,378 52-52 52073ac92b51b88eb4244a40b665dd7b91fff7aebe2a60a95683fdafdc47ff31 new_market 2,879 274,160 53-53 3b3ddad83de938ebb20712d779ad3cc63827f226c9df507ede63fed929cb1a2d price_change 105,528,352 1,062,750,895 54-456 2cf9c128013af59c7ce3c22cd6f29f4a592b06f9115773d2c6871975ab45b983 tick_size_change 4,100 151,104 457-457 45cd2f95a652d0e3f7a3e8b73ebbe3e3b8c673ec1fb4ca90d60a9fba41c59f37 EVENT MIX count share price_change 105,528,352 88.74% best_bid_ask 11,503,118 9.67% book 1,814,639 1.53% last_trade_price 69,346 0.06% tick_size_change 4,100 <0.01% new_market 2,879 <0.01% market_resolved 999 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,503,312 11,503,118 194 73,096 PARTIAL book 1,814,887 1,814,639 248 156,450 PARTIAL last_trade_price 69,346 69,346 0 3,878 PARTIAL market_resolved 999 999 0 842 PARTIAL new_market 2,879 2,879 0 1,799 PARTIAL price_change 105,529,800 105,528,352 1,448 122,015 PARTIAL tick_size_change 4,100 4,100 0 1,025 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,317,509 8,746,356 6ms 18ms 140ms 3.2s 0 transport_latency_assumed best_bid_ask e 11,496,886 157,644 42ms 60ms 305ms 22.2s 0 transport_latency_assumed best_bid_ask f 11,033,728 40,754 48ms 72ms 368ms 20.1s 0 transport_latency_assumed best_bid_ask h 11,502,370 2,558,364 19ms 37ms 174ms 48.7s 0 transport_latency_assumed book c 1,668,841 1,639,191 7.3min 3.0d 44.2d 114.7d 0 book_staleness book e 154,638 12,256 51ms 13.2s 4.5d 96.2d 0 book_staleness book f 455,760 126,428 1.5min 2.1d 40.0d 114.7d 0 book_staleness book h 147,948 36,764 24ms 179ms 34.4min 96.2d 0 book_staleness last_trade_price c 55,606 51,729 7ms 28ms 226ms 2.4s 0 transport_latency_assumed last_trade_price e 67,451 931 47ms 1.4s 13.1s 22.3s 0 transport_latency_assumed last_trade_price f 63,720 414 55ms 1.6s 10.9s 20.1s 0 transport_latency_assumed last_trade_price h 69,205 16,272 21ms 78ms 452ms 8.5s 0 transport_latency_assumed market_resolved c 779 657 7ms 51.0s 4.6min 5.0min 0 transport_latency_assumed market_resolved e 842 125 45ms 33.3s 50.8s 52.8s 0 transport_latency_assumed market_resolved f 862 63 51ms 36.7s 5.4min 5.4min 0 transport_latency_assumed market_resolved h 842 154 22ms 34.8s 1.0min 1.0min 0 transport_latency_assumed new_market c 1,788 1,114 98ms 3.3min 3.7min 261.8d 0 transport_latency_assumed new_market e 1,799 589 289ms 3.5min 3.7min 261.8d 0 transport_latency_assumed new_market f 1,907 416 336ms 3.6min 4.9min 261.8d 0 transport_latency_assumed new_market h 1,799 760 163ms 3.5min 3.7min 261.8d 0 transport_latency_assumed price_change c 85,315,281 79,782,107 6ms 21ms 167ms 3.5s 0 transport_latency_assumed price_change e 104,793,882 1,554,074 43ms 96ms 4.5s 22.6s 0 transport_latency_assumed price_change f 100,367,683 486,578 49ms 113ms 4.0s 20.1s 0 transport_latency_assumed price_change h 105,296,248 23,705,593 19ms 44ms 281ms 50.0s 0 transport_latency_assumed tick_size_change c 3,300 3,166 6ms 13ms 59ms 125ms 0 transport_latency_assumed tick_size_change e 4,100 43 42ms 51ms 180ms 817ms 0 transport_latency_assumed tick_size_change f 4,044 not meas. 48ms 56ms 199ms 777ms 0 transport_latency_assumed tick_size_change h 4,100 891 19ms 27ms 93ms 378ms 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-21/15/2026-09-21T15.parquet sha256sum 2026-09-21T15.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.