Hour audit: 2026-09-29T10
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-29T10 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-29T10:00:00.000126665+00:00 · last event 2026-09-29T10:59:59.999968903+00:00
VOLUME 104,604,060 rows · 1,138,687,780 bytes (1.06 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured c: 104,438,332 · k: 104,428,782 · h: 104,417,217 · i: 104,406,862 · g: 103,591,107 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 91,844,067 (87.80%) · k: 7,208,743 (6.89%) · h: 2,137,313 (2.04%) · i: 3,356,427 (3.21%) · g: 57,510 (0.05%) (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 104,604,060 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 fac0c096ceaa0ce7280be03b565f1ee88a8c4b26c5ece92f5df51e40efacfdc3
the corpus checksum ledger names this file with the same digest
joined 104,606,111 to merged 104,604,060, minus 2,051 (minus 0.0020%)
boundary drops 2,051 · 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-29T13:17:53Z 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,327,713 121,661,864 0-39 41cabfca2672ac310878f74bd8be40d2196995db56e211d3f633735b72ee1140 book 198,620 19,905,684 40-40 6031f72dab25c138a5fdf24a8a17d908b38ec38ba210cf231660758881d857f7 last_trade_price 53,442 3,061,560 41-41 3c06fa29abd9c43486720915e5ea748127965828ebe08491e62ef0225ffba22a market_resolved 808 132,399 42-42 8d7d0d3507b3545d464a84ae24b360ae275ff63916bbfdfc95ca40747e746dc1 new_market 1,229 130,795 43-43 ccb146ac767cfd43a6b307504727f279d60c68b68a0559e2b53a59188b4ab9c9 price_change 94,019,068 992,485,759 44-402 037bff4025103aa2c0e6d70c9b2d7ce58a6da22814ddb382e141dfee577f904c tick_size_change 3,180 116,941 403-403 000aaa5e15c5326157acbaeb973529f7dc46201e3f8874b4e29a28c15e95b7cf EVENT MIX count share price_change 94,019,068 89.88% best_bid_ask 10,327,713 9.87% book 198,620 0.19% last_trade_price 53,442 0.05% tick_size_change 3,180 <0.01% new_market 1,229 <0.01% market_resolved 808 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,327,994 10,327,713 281 192 FULL book 198,654 198,620 34 34,722 FULL last_trade_price 53,442 53,442 0 0 FULL market_resolved 808 808 0 0 FULL new_market 1,229 1,229 0 0 FULL price_change 94,020,804 94,019,068 1,736 284 FULL tick_size_change 3,180 3,180 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,326,239 9,147,009 5ms 17ms 159ms 15.5s 0 transport_latency_assumed best_bid_ask g 10,306,397 1,296 77ms 104ms 529ms 29.0s 0 transport_latency_assumed best_bid_ask h 10,323,642 189,896 18ms 26ms 178ms 57.2s 0 transport_latency_assumed best_bid_ask i 10,325,806 321,137 19ms 30ms 144ms 1.0min 0 transport_latency_assumed best_bid_ask k 10,325,519 668,375 13ms 23ms 126ms 46.1s 0 transport_latency_assumed book c 119,344 101,943 8ms 1.0s 2.3d 104.0d 0 book_staleness book g 141,809 36,736 129ms 7.7h 22.0d 122.5d 0 book_staleness book h 137,409 31,844 25ms 3.6h 20.6d 122.5d 0 book_staleness book i 111,720 7,422 23ms 211ms 14.7h 103.9d 0 book_staleness book k 120,758 20,675 17ms 7.1s 2.4d 104.0d 0 book_staleness last_trade_price c 53,207 45,733 6ms 33ms 286ms 2.3s 0 transport_latency_assumed last_trade_price g 51,073 16 89ms 1.3s 11.3s 29.0s 0 transport_latency_assumed last_trade_price h 53,098 1,170 19ms 79ms 843ms 46.1s 0 transport_latency_assumed last_trade_price i 53,130 1,721 21ms 111ms 772ms 5.7s 0 transport_latency_assumed last_trade_price k 53,113 4,802 14ms 44ms 314ms 42.3s 0 transport_latency_assumed market_resolved c 789 604 6ms 36.8s 47.0s 49.4s 0 transport_latency_assumed market_resolved g 789 not meas. 80ms 28.4s 41.5s 43.4s 0 transport_latency_assumed market_resolved h 789 20 19ms 27.5s 38.7s 40.9s 0 transport_latency_assumed market_resolved i 789 125 22ms 29.2s 54.4s 54.4s 0 transport_latency_assumed market_resolved k 789 59 15ms 37.7s 48.3s 51.1s 0 transport_latency_assumed new_market c 853 304 114ms 23.2s 1.0min 1.6min 0 transport_latency_assumed new_market g 853 118 326ms 24.8s 55.0s 1.5min 0 transport_latency_assumed new_market h 853 229 136ms 23.7s 56.1s 1.5min 0 transport_latency_assumed new_market i 853 329 130ms 22.5s 57.5s 1.6min 0 transport_latency_assumed new_market k 853 249 116ms 22.9s 58.8s 1.5min 0 transport_latency_assumed price_change c 93,934,720 82,545,616 5ms 20ms 194ms 15.5s 0 transport_latency_assumed price_change g 93,087,006 19,344 78ms 163ms 3.7s 29.0s 0 transport_latency_assumed price_change h 93,898,246 1,914,102 18ms 33ms 305ms 57.2s 0 transport_latency_assumed price_change i 93,911,384 3,025,626 19ms 37ms 323ms 1.1min 0 transport_latency_assumed price_change k 93,924,570 6,514,380 13ms 26ms 177ms 46.3s 0 transport_latency_assumed tick_size_change c 3,180 2,858 5ms 16ms 134ms 238ms 0 transport_latency_assumed tick_size_change g 3,180 not meas. 77ms 92ms 309ms 629ms 0 transport_latency_assumed tick_size_change h 3,180 52 18ms 30ms 73ms 138ms 0 transport_latency_assumed tick_size_change i 3,180 67 19ms 34ms 111ms 259ms 0 transport_latency_assumed tick_size_change k 3,180 203 13ms 22ms 68ms 116ms 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-29/10/2026-09-29T10.parquet sha256sum 2026-09-29T10.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.