Hour audit: 2026-09-28T02
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-28T02 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-28T02:00:00.000128012+00:00 · last event 2026-09-28T02:59:59.999668244+00:00
VOLUME 103,931,966 rows · 1,065,500,170 bytes (1016.14 MiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured k: 103,817,235 · g: 103,413,434 · h: 102,962,339 · c: 102,587,429 · i: 101,305,052 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 7,257,926 (6.98%) · g: 14,219 (0.01%) · h: 1,607,641 (1.55%) · c: 94,021,730 (90.46%) · i: 1,030,450 (0.99%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 103,931,966 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 f2b2db21c6c17576e956b615b4864eca3b72ce0975b4f91f68bafa5c03404cf7
the corpus checksum ledger names this file with the same digest
joined 103,936,240 to merged 103,931,966, minus 4,274 (minus 0.0041%)
boundary drops 4,274 · 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-28T04:37:39Z as cghik
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 status feed unobserved for this hour. Our incident register was last checked against the venue's feed at 2026-09-23T20:35Z, before this hour ended, so nothing has looked yet. This is a could-not-look and never an all-clear.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,380,488 115,273,588 0-39 554027bec30d23b55326f5f91ee1b91b2de8bc927479bf286568b43e63713574 book 158,741 14,795,906 40-40 af762c4212a879d71b0548dd89a7e5ee9197de28ee3169ab6943621ec2ff45c7 last_trade_price 48,959 2,759,193 41-41 699259a09d6381af80f3c12ec1c57d0c764cd738f5adf818155bfdb260b6d2a3 market_resolved 1,511 247,174 42-42 0d0704cebb8414ccb51279db2fc496318ce09cd28a51693b18cacaedc70924ef new_market 2,031 211,203 43-43 f83a754196725411d962eb5d82473cca544b3ff37b810127813dc521a1ec52cd price_change 93,337,420 930,924,770 44-400 e2c247cf2c402ef0a6b3d0fd0d3b72ccafd03c941277b508038f1bf71987e194 tick_size_change 2,816 102,194 401-401 d44c8253f3f84800372b3563b7d6cc08721a5d4a84feddd6bd7742c558d5552c EVENT MIX count share price_change 93,337,420 89.81% best_bid_ask 10,380,488 9.99% book 158,741 0.15% last_trade_price 48,959 0.05% tick_size_change 2,816 <0.01% new_market 2,031 <0.01% market_resolved 1,511 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,380,670 10,380,488 182 1,452 FULL book 158,743 158,741 2 13,044 FULL last_trade_price 48,959 48,959 0 91 FULL market_resolved 1,511 1,511 0 33 FULL new_market 2,031 2,031 0 0 FULL price_change 93,341,510 93,337,420 4,090 2,847 FULL tick_size_change 2,816 2,816 0 26 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,251,948 9,473,423 4ms 12ms 134ms 4.9s 0 transport_latency_assumed best_bid_ask g 10,371,912 453 79ms 102ms 511ms 41.2s 0 transport_latency_assumed best_bid_ask h 10,346,696 149,817 18ms 28ms 250ms 2.7min 0 transport_latency_assumed best_bid_ask i 10,197,727 90,676 27ms 33ms 110ms 9.7s 0 transport_latency_assumed best_bid_ask k 10,378,188 666,119 13ms 21ms 139ms 1.0min 0 transport_latency_assumed book c 112,641 101,686 7ms 26.2s 6.3d 102.7d 0 book_staleness book g 105,128 6,413 84ms 1.7s 22.7h 102.6d 0 book_staleness book h 126,495 31,010 23ms 1.6h 22.5h 102.7d 0 book_staleness book i 97,286 4,412 29ms 97ms 8.9h 102.5d 0 book_staleness book k 109,022 15,220 16ms 615ms 1.5d 121.2d 0 book_staleness last_trade_price c 48,666 44,175 6ms 19ms 252ms 4.9s 0 transport_latency_assumed last_trade_price g 48,099 14 82ms 249ms 5.8s 32.9s 0 transport_latency_assumed last_trade_price h 47,295 697 19ms 47ms 474ms 50.4s 0 transport_latency_assumed last_trade_price i 45,754 491 28ms 51ms 408ms 9.7s 0 transport_latency_assumed last_trade_price k 48,856 3,582 14ms 30ms 232ms 1.0min 0 transport_latency_assumed market_resolved c 1,483 1,291 5ms 87ms 49.4s 2.4min 0 transport_latency_assumed market_resolved g 1,496 not meas. 82ms 451ms 52.4s 56.6s 0 transport_latency_assumed market_resolved h 1,496 27 18ms 165ms 43.9s 48.3s 0 transport_latency_assumed market_resolved i 1,476 125 27ms 133ms 45.2s 2.0min 0 transport_latency_assumed market_resolved k 1,496 68 14ms 67ms 50.5s 54.8s 0 transport_latency_assumed new_market c 1,355 789 139ms 2.0min 3.9min 4.6min 0 transport_latency_assumed new_market g 1,355 199 353ms 1.9min 2.3min 4.7min 0 transport_latency_assumed new_market h 1,355 478 189ms 2.0min 3.8min 4.5min 0 transport_latency_assumed new_market i 1,355 318 130ms 2.0min 3.8min 4.5min 0 transport_latency_assumed new_market k 1,355 247 199ms 2.0min 2.5min 4.6min 0 transport_latency_assumed price_change c 92,168,552 84,397,892 5ms 15ms 164ms 4.9s 0 transport_latency_assumed price_change g 92,882,628 7,140 79ms 121ms 1.4s 41.4s 0 transport_latency_assumed price_change h 92,436,198 1,425,560 18ms 33ms 319ms 2.7min 0 transport_latency_assumed price_change i 90,958,698 934,376 27ms 36ms 175ms 9.8s 0 transport_latency_assumed price_change k 93,275,502 6,572,452 13ms 24ms 167ms 1.0min 0 transport_latency_assumed tick_size_change c 2,784 2,474 5ms 17ms 82ms 154ms 0 transport_latency_assumed tick_size_change g 2,816 not meas. 79ms 102ms 701ms 7.5s 0 transport_latency_assumed tick_size_change h 2,804 52 18ms 37ms 874ms 4.0s 0 transport_latency_assumed tick_size_change i 2,756 52 26ms 31ms 86ms 1.1s 0 transport_latency_assumed tick_size_change k 2,816 238 13ms 24ms 117ms 1.6s 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-28/02/2026-09-28T02.parquet sha256sum 2026-09-28T02.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.