Hour audit: 2026-09-16T09
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-16T09 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-16T09:00:00.000014706+00:00 · last event 2026-09-16T09:59:59.999976831+00:00
VOLUME 117,378,458 rows · 1,243,426,445 bytes (1.16 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 116,602,596 · f: 116,544,299 · e: 116,481,352 · g: 111,595,372 · c: 110,890,178 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 9,997,503 (8.52%) · f: 363,176 (0.31%) · e: 753,996 (0.64%) · g: 157,481 (0.13%) · c: 106,106,302 (90.40%) (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 117,378,458 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 55cfc2272e0458e374d18a8add7886ba001f395ec956f689dc47a19bb5bf40b3
the corpus checksum ledger names this file with the same digest
joined 117,387,562 to merged 117,378,458, minus 9,104 (minus 0.0078%)
boundary drops 9,104 · 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-16T11:04:26Z as cefgh
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 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,837,574 135,224,467 0-45 c6badb9749e7d3d063f52eec243ec4ad336a54add833785279338e74ae329738 book 1,097,547 76,538,103 46-50 1871905b42e3a608b8ce96d70f7185bc02f69ecabb282bd48d1e2a6e6dd04772 last_trade_price 48,432 2,773,396 51-51 2a19aac5007cdcf5e770839c47f5869efbf88c35026d5be0ccd5b778296d7677 market_resolved 706 99,948 52-52 b43e8725e3c12b80070a7a829e8cd9b383053cf8b09d0edf2a946f91cd501463 new_market 475 52,720 53-53 54a35465100881651f991c8a0e25b4fc5a7aac2233878082580ea4609daafd66 price_change 104,391,140 1,027,303,430 54-452 909fd6e3f85448a0c034d1e4f902fbac77c6965ddd76a4f75f70cfa541f4286d tick_size_change 2,584 95,320 453-453 6e703d6d19a93c2f41ab5342b9da674e04d3286e1e1bebd2a478f31a1460fec3 EVENT MIX count share price_change 104,391,140 88.94% best_bid_ask 11,837,574 10.08% book 1,097,547 0.94% last_trade_price 48,432 0.04% tick_size_change 2,584 <0.01% market_resolved 706 <0.01% new_market 475 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,837,769 11,837,574 195 561 FULL book 1,103,862 1,097,547 6,315 141,154 FULL last_trade_price 48,432 48,432 0 88 FULL market_resolved 706 706 0 0 FULL new_market 475 475 0 0 FULL price_change 104,393,734 104,391,140 2,594 158 FULL tick_size_change 2,584 2,584 0 47 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,238,374 10,794,365 5ms 11ms 69ms 1.4s 0 transport_latency_assumed best_bid_ask e 11,834,196 51,243 38ms 44ms 121ms 5.1s 0 transport_latency_assumed best_bid_ask f 11,833,922 12,872 45ms 54ms 147ms 5.1s 0 transport_latency_assumed best_bid_ask g 11,325,205 659 79ms 97ms 261ms 10.3s 0 transport_latency_assumed best_bid_ask h 11,833,349 978,435 17ms 26ms 91ms 6.3s 0 transport_latency_assumed book c 554,411 397,095 3.4min 1.3d 35.6d 109.5d 0 book_staleness book e 330,795 147,473 1.2min 7.9h 31.8d 109.5d 0 book_staleness book f 338,405 158,913 1.3min 9.5h 32.0d 109.5d 0 book_staleness book g 526,023 145,285 3.1min 1.0d 35.6d 109.5d 0 book_staleness book h 420,278 248,781 2.0min 14.1h 35.6d 109.5d 0 book_staleness last_trade_price c 45,318 43,026 11ms 45ms 211ms 4.8s 0 transport_latency_assumed last_trade_price e 48,263 621 45ms 143ms 1.3s 5.0s 0 transport_latency_assumed last_trade_price f 48,130 304 54ms 167ms 1.1s 5.0s 0 transport_latency_assumed last_trade_price g 45,348 20 95ms 489ms 5.3s 10.3s 0 transport_latency_assumed last_trade_price h 47,977 4,461 24ms 89ms 415ms 4.9s 0 transport_latency_assumed market_resolved c 641 619 5ms 3.8min 5.5min 7.1min 0 transport_latency_assumed market_resolved e 618 11 39ms 123ms 59.3s 59.3s 0 transport_latency_assumed market_resolved f 618 1 47ms 131ms 1.0min 1.0min 0 transport_latency_assumed market_resolved g 634 3 84ms 393ms 4.9min 4.9min 0 transport_latency_assumed market_resolved h 618 72 18ms 56ms 156ms 234ms 0 transport_latency_assumed new_market c 340 229 41ms 12.8s 59.5s 2.7min 0 transport_latency_assumed new_market e 338 60 113ms 15.6s 39.5s 1.1min 0 transport_latency_assumed new_market f 338 32 106ms 16.5s 40.7s 1.0min 0 transport_latency_assumed new_market g 338 24 125ms 4.0s 48.7s 59.7s 0 transport_latency_assumed new_market h 338 130 51ms 14.8s 46.6s 1.3min 0 transport_latency_assumed price_change c 99,048,686 94,868,634 5ms 12ms 85ms 1.7s 0 transport_latency_assumed price_change e 104,264,558 554,576 38ms 48ms 210ms 5.2s 0 transport_latency_assumed price_change f 104,320,302 191,054 46ms 61ms 259ms 5.1s 0 transport_latency_assumed price_change g 99,695,388 11,490 80ms 107ms 676ms 10.3s 0 transport_latency_assumed price_change h 104,297,452 8,765,386 18ms 30ms 141ms 6.3s 0 transport_latency_assumed tick_size_change c 2,408 2,334 5ms 11ms 68ms 165ms 0 transport_latency_assumed tick_size_change e 2,584 12 38ms 44ms 152ms 264ms 0 transport_latency_assumed tick_size_change f 2,584 not meas. 45ms 71ms 285ms 507ms 0 transport_latency_assumed tick_size_change g 2,436 not meas. 78ms 95ms 335ms 710ms 0 transport_latency_assumed tick_size_change h 2,584 238 18ms 34ms 160ms 296ms 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-16/09/2026-09-16T09.parquet sha256sum 2026-09-16T09.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.