Hour audit: 2026-09-20T04
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-20T04 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-20T04:00:00.000019048+00:00 · last event 2026-09-20T04:59:59.999962987+00:00
VOLUME 124,364,801 rows · 1,320,355,800 bytes (1.23 GiB) · 7 products, all holding rows
WITNESSES cegh — 4 machines contributed rows
captured h: 123,728,232 · e: 123,679,794 · g: 118,899,705 · c: 117,677,381 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 12,401,540 (9.97%) · e: 929,990 (0.75%) · g: 414,594 (0.33%) · c: 110,618,677 (88.95%) (rows of the merged file that came from it; these partition it)
5 expected (cefgh), 1 contributed nothing: f
INTEGRITY sha256 90fc8ded589229e1c7bdc1a02d2e69d3a98ad8ebbb1fca1d6b825d08fc2fab93
the corpus checksum ledger names this file with the same digest
joined 124,369,053 to merged 124,364,801, minus 4,252 (minus 0.0034%)
boundary drops 4,252 · 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-20T08:49:23Z 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 15,914,588 175,599,265 0-60 793228898350832ecf5c658a5038f84bef96a0bfab017a624e93a8f076aadf87 book 731,884 60,418,052 61-63 67e721190a834195f9ede3f0942769d4ccbb7bc634798ba347045588e6bc610f last_trade_price 55,955 3,215,066 64-64 adef11679a197b50328a6f08cdf5ec3229211a44865f208ef0ace3a5a323a311 market_resolved 3,332 493,908 65-65 c2fd5ffcfec6ea34654b3f92520199348a8e3a004469788a50384235512438b9 new_market 3,096 309,940 66-66 72b150e54d0cb8bcaf26c0f4a631376889f571a722cf61fcacaa7090df6d6673 price_change 107,648,410 1,078,640,532 67-477 66bfbb6a1961bb22f853b666a1672fc0bd93ab51835ddbf9e3b9ffba78774c36 tick_size_change 7,536 268,986 478-478 145fe213c7f3d6071c5eae3c42bb9dd4fbabe91bb48d08267e2ae3b28ac8ea78 EVENT MIX count share price_change 107,648,410 86.56% best_bid_ask 15,914,588 12.80% book 731,884 0.59% last_trade_price 55,955 0.04% tick_size_change 7,536 <0.01% market_resolved 3,332 <0.01% new_market 3,096 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 15,914,908 15,914,588 320 81,611 PARTIAL book 732,062 731,884 178 178,921 PARTIAL last_trade_price 55,957 55,955 2 4,048 PARTIAL market_resolved 3,332 3,332 0 3,066 PARTIAL new_market 3,096 3,096 0 2,034 PARTIAL price_change 107,652,162 107,648,410 3,752 141,199 PARTIAL tick_size_change 7,536 7,536 0 1,884 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 15,041,782 14,210,326 5ms 13ms 192ms 5.2s 0 transport_latency_assumed best_bid_ask e 15,912,318 116,892 41ms 51ms 258ms 9.9s 0 transport_latency_assumed best_bid_ask g 15,239,847 9,356 77ms 102ms 556ms 25.3s 0 transport_latency_assumed best_bid_ask h 15,912,869 1,578,014 18ms 29ms 405ms 47.8s 0 transport_latency_assumed book c 527,661 370,609 3.1min 1.5d 38.6d 113.3d 0 book_staleness book e 120,359 5,063 43ms 884ms 38.9min 94.8d 0 book_staleness book g 482,189 337,166 1.9min 1.2d 38.4d 113.2d 0 book_staleness book h 125,916 19,046 22ms 2.3s 1.5d 94.7d 0 book_staleness last_trade_price c 53,026 48,887 5ms 26ms 321ms 4.6s 0 transport_latency_assumed last_trade_price e 55,571 555 43ms 149ms 3.0s 9.9s 0 transport_latency_assumed last_trade_price g 52,487 121 81ms 332ms 12.1s 25.4s 0 transport_latency_assumed last_trade_price h 55,641 6,392 19ms 50ms 607ms 15.1s 0 transport_latency_assumed market_resolved c 3,114 3,026 5ms 20ms 6.0min 6.3min 0 transport_latency_assumed market_resolved e 3,066 13 110ms 196ms 491ms 38.0s 0 transport_latency_assumed market_resolved g 3,119 154 190ms 378ms 5.2min 5.4min 0 transport_latency_assumed market_resolved h 3,066 139 37ms 78ms 438ms 37.9s 0 transport_latency_assumed new_market c 2,035 1,556 88ms 21.5s 58.6s 5.4h 0 transport_latency_assumed new_market e 2,034 516 210ms 28.1s 1.1min 1.7h 0 transport_latency_assumed new_market g 2,034 293 333ms 21.8s 1.1min 3.8h 0 transport_latency_assumed new_market h 2,034 731 166ms 33.5s 1.2min 2.2h 0 transport_latency_assumed price_change c 102,042,283 95,977,077 5ms 16ms 208ms 5.2s 0 transport_latency_assumed price_change e 107,578,910 806,932 41ms 60ms 399ms 9.9s 0 transport_latency_assumed price_change g 103,112,585 67,496 78ms 123ms 961ms 25.4s 0 transport_latency_assumed price_change h 107,621,170 10,796,905 18ms 34ms 410ms 51.1s 0 transport_latency_assumed tick_size_change c 7,480 7,196 4ms 9ms 122ms 373ms 0 transport_latency_assumed tick_size_change e 7,536 19 41ms 47ms 270ms 466ms 0 transport_latency_assumed tick_size_change g 7,444 8 77ms 99ms 560ms 6.2s 0 transport_latency_assumed tick_size_change h 7,536 313 18ms 26ms 281ms 5.1s 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-20/04/2026-09-20T04.parquet sha256sum 2026-09-20T04.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.