Hour audit: 2026-09-21T17
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-21T17 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-21T17:00:00.000057668+00:00 · last event 2026-09-21T17:59:59.999996026+00:00
VOLUME 110,304,478 rows · 1,169,399,647 bytes (1.09 GiB) · 7 products, all holding rows
WITNESSES cefh — 4 machines contributed rows
captured h: 108,857,763 · f: 108,673,244 · e: 108,388,525 · c: 94,153,436 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 20,530,679 (18.61%) · f: 620,273 (0.56%) · e: 1,120,091 (1.02%) · c: 88,033,435 (79.81%) (rows of the merged file that came from it; these partition it)
5 expected (cefgh), 1 contributed nothing: g
INTEGRITY sha256 1f9967c4c4c41a427eae81e81b47d31c678180b9d8184dcf87b6e745ad93c801
the corpus checksum ledger names this file with the same digest
joined 110,308,231 to merged 110,304,478, minus 3,753 (minus 0.0034%)
boundary drops 3,753 · 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-21T18:55:33Z 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 10,646,010 120,989,232 0-40 45800138dd3cb5a23f9f0abc1ad0110be4d6737e80f906814efc6e09da281f9b book 1,306,848 69,573,576 41-45 5fcd758edb526be028e950f6e0419b4c0220204523df065fb7d411f15b9d86d6 last_trade_price 60,885 3,420,503 46-46 ae4880c73ad3aa348249851a8353c1390ac7a90a4d41fa9c35d332258c7f6092 market_resolved 800 114,762 47-47 a642b1393ba52d317b13a5375ae633bf24a2199395a709c8272b10d6ac9f1cd9 new_market 2,437 237,680 48-48 6dadbddd381d1fc48152da3a769104364b7c564bb8ebfa647c5cf7dcf4f61710 price_change 98,284,122 973,687,692 49-423 5878a10fe7c90492aa587a3e73f29d663f60481280ee6651688eadd1549da2a8 tick_size_change 3,376 123,144 424-424 d4ae5853920438f42c4d2ae01a17c0af9487506ed85598d2a673965c2a3fbd0f EVENT MIX count share price_change 98,284,122 89.10% best_bid_ask 10,646,010 9.65% book 1,306,848 1.18% last_trade_price 60,885 0.06% tick_size_change 3,376 <0.01% new_market 2,437 <0.01% market_resolved 800 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,646,124 10,646,010 114 70,592 PARTIAL book 1,309,468 1,306,848 2,620 156,711 PARTIAL last_trade_price 60,886 60,885 1 3,405 PARTIAL market_resolved 800 800 0 704 PARTIAL new_market 2,437 2,437 0 1,509 PARTIAL price_change 98,285,140 98,284,122 1,018 121,840 PARTIAL tick_size_change 3,376 3,376 0 844 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,075,444 8,520,950 6ms 17ms 110ms 2.4s 0 transport_latency_assumed best_bid_ask e 10,633,644 98,521 42ms 61ms 343ms 25.9s 0 transport_latency_assumed best_bid_ask f 10,641,504 50,270 47ms 67ms 340ms 20.8s 0 transport_latency_assumed best_bid_ask h 10,644,276 1,976,269 19ms 33ms 214ms 45.0s 0 transport_latency_assumed book c 1,269,212 1,250,567 6.7min 3.1d 44.2d 114.8d 0 book_staleness book e 136,927 14,314 52ms 23.3s 8.3d 96.2d 0 book_staleness book f 135,847 10,087 59ms 10.9s 6.1d 96.3d 0 book_staleness book h 133,656 31,880 24ms 631ms 2.1d 114.8d 0 book_staleness last_trade_price c 51,040 47,361 7ms 31ms 224ms 1.7s 0 transport_latency_assumed last_trade_price e 58,835 625 49ms 987ms 7.6s 26.0s 0 transport_latency_assumed last_trade_price f 59,744 360 57ms 1.2s 14.1s 20.8s 0 transport_latency_assumed last_trade_price h 60,602 12,539 20ms 103ms 752ms 11.3s 0 transport_latency_assumed market_resolved c 631 548 6ms 52.1s 4.3min 5.3min 0 transport_latency_assumed market_resolved e 704 6 44ms 39.9s 59.6s 1.0min 0 transport_latency_assumed market_resolved f 704 4 49ms 38.8s 1.0min 1.0min 0 transport_latency_assumed market_resolved h 704 242 20ms 40.3s 1.0min 1.0min 0 transport_latency_assumed new_market c 1,537 910 2.0s 4.4min 4.8min 4.9min 0 transport_latency_assumed new_market e 1,509 330 241ms 25.7s 1.4min 1.5min 0 transport_latency_assumed new_market f 1,509 416 259ms 34.0s 1.4min 1.5min 0 transport_latency_assumed new_market h 1,509 781 168ms 29.6s 1.5min 1.7min 0 transport_latency_assumed price_change c 83,752,452 78,210,348 6ms 21ms 152ms 3.8s 0 transport_latency_assumed price_change e 97,553,530 1,006,274 42ms 92ms 2.7s 26.1s 0 transport_latency_assumed price_change f 97,830,560 559,124 48ms 99ms 2.4s 20.8s 0 transport_latency_assumed price_change h 98,013,640 18,508,376 19ms 42ms 335ms 45.2s 0 transport_latency_assumed tick_size_change c 3,120 2,751 6ms 34ms 126ms 279ms 0 transport_latency_assumed tick_size_change e 3,376 21 42ms 61ms 146ms 5.8s 0 transport_latency_assumed tick_size_change f 3,376 12 48ms 63ms 142ms 699ms 0 transport_latency_assumed tick_size_change h 3,376 592 19ms 36ms 169ms 497ms 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/17/2026-09-21T17.parquet sha256sum 2026-09-21T17.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.