Market Trust diligence packet

Iran closes its airspace by May 18?

Do not citeStale (24.1d old)
UseUse with caveatsDiscountDo not cite

One of four bands, strongest warning on the right

Too much of the trading came from wallets we cannot yet score, so participant quality is uncertain.

Monitor, but do not cite as current. The evidence is useful as an archived read until the data freshness window refreshes.

Freshness gate: Diligence packet is stale for current product claims. Treat this as archived evidence and wait for a refresh before demos or outreach.

Market quality

72 / 100

Interval 33-84

Evidence confidence

low

40 / 100

Source health

source gate passed

1 sources | dropped 0

Audit chain

bebdc4cf20...

row hash verified

Memo language, how to use this packet, and what changes the verdict

Memo language

Convexly rates this polymarket market "Iran closes its airspace by May 18?" as Do not cite. Use only as a review target. Current-card issues must clear before this price is used as evidence. Caveat to carry: Too much participant flow is unknown while participant-quality evidence is still pending. This is market diligence, not a trading instruction or proof that the market probability is correct.

Caveat to carry: Too much participant flow is unknown while participant-quality evidence is still pending.

Use this packet when

  • Use to explain why this market should stay out of a citation set for now.
  • Use as a recovery checklist for source freshness, coherence, depth, or evidence gaps.

Do not use it as

  • A trading instruction.
  • Proof that the market probability is correct.
  • A manipulation accusation or person-level identity claim.

What changes the verdict

  • Clear hard cap: Too much participant flow is unknown while participant-quality evidence is still pending.
  • Clear current blocker: Not enough pillars on this card are measured yet.
  • Clear current blocker: Some pillars on this card are still gathering evidence.

Why this verdict

How the score adds up

2 measured | 3 heuristic | 2 pending

Why this rating

Composite 72 · Do not cite

2 measured3 heuristic2 pending
  • Coherenceheuristicweight 20.0

    No full-provenance CME signal is linked to this condition in the current ledger window; absence of a signal is not proof of coherence.

    • · no_linked_cme_signal_in_window
    • · absence_of_signal_not_proof_of_coherence
    • · cme_signal_window_days:7
    • · recent_full_provenance_signals:250
    50+14.3
  • Liquidityheuristicweight 15.0

    One-sided visible ladder; direct spread unavailable, so liquidity is capped and caveated.

    • · one_sided_orderbook_boundary
    • · direct_bid_ask_spread_missing
    • · visible $1k ladder slippage 0pp
    • · scorer_version:M2
    65+13.9
  • Depthmeasuredweight 15.0

    $1k visible-ladder slippage estimate is 0pp.

    • · visible_ladder_slippage_measured
    100+21.4
  • Resolution reliabilityheuristicweight 15.0

    Resolution source and rule text are present but not independently reviewed.

    • · resolution_metadata_present_manual_review_pending
    70+15.0
  • Participant qualitypendingweight 20.0

    Participant-quality inputs exist but do not meet coverage floors.

    • · below_publishable_sample_floor
    • · high_participant_concentration
    • · high_unknown_flow_share
    • · insufficient_scored_accounts
    no contrib
  • Integrity risk screenpendingweight 10.0

    Mild concentration or coordination signals; review before citing.

    • · top-3 wallets control 100% of notional flow
    • · flow_events:4
    • · distinct_wallets:4
    • · wash_round_trips:0
    75no contrib
  • Audit completenessmeasuredweight 5.0

    3 linked artifacts; 0 missing hashes; 0 stale/failing sources.

    • · artifact_hashes_present
    • · source_watermarks_healthy
    100+7.1

How it adds up: composite = Σ(score × weight) / Σ(weight) across measured + heuristic pillars only. Pending and data-rights-blocked pillars are excluded from both numerator and denominator. Total contributing weight = 70.0.

Caveat: 2 pillars pending — the score will recompute as the substrate fills in.

What is being rated

Market identity

Venue

polymarket

condition 0xbd5922eed56186e9...

Category

unmapped

used for coverage and validation breadth

Market status

active

venue-provided lifecycle state when available

Resolution rule

This market will resolve to “Yes” if Iran initiates a major closure of its airspace, that is not solely due to weather conditions, by the listed date, 11:59 PM ET. Otherwise, this market will resolve to “No”. A “major closure” is defined as a broad closure, cancellation, or suspension of commercial flights transiting, arriving in, and departing from Iranian airspace or a major Iranian Airspace region. A qualifying closure must apply generally to flights across Iran or a major Iranian airspace region. Limited cancellations, delays, or other partial closures will not qualify. Limited exceptions to a broad closure, however, will not disqualify such a closure from counting (e.g. exceptions for certain flights pre-approved by the Iranian Civil Aviation Authority may be permitted). Any non-weather complete suspension of commercial arrivals and departures affecting at least two of the following airports will qualify: Imam Khomeini International Airport (IKA), Mehrabad Airport (THR), Mashhad International Airport (MHD), Shiraz International Airport (SYZ), or Isfahan International Airport (IFN). Qualifying previous examples include the January 2026 total closure of Iranian airspace except to international flights with express governmental permission (https://www.reuters.com/world/middle-east/iran-shuts-airspace-most-flights-flightradar24-says-2026-01-14/) and the April 2024 closure of Iran’s western airspace (https://www.reuters.com/world/middle-east/iranian-airports-cancel-flights-until-monday-morning-2024-04-14/). Non-qualifying examples include the January 27, 2026 partial closure of Iranian airspace around the Strait of Hormuz (https://www.aa.com.tr/en/middle-east/iran-issues-airspace-notice-for-military-drills-near-strait-of-hormuz/3812508) and the January 25 - April 25, 2026 VFR (Visual Flight Rules) flights suspension which did not broadly close commercial aviation in a qualifying region (https://www.intellinews.com/iran-suspends-general-aviation-and-vfr-flights-in-new-airspace-directive-421997/). Warnings, No-Fly-Zones, or other flight restrictions imposed by airlines or countries other than Iran will not be sufficient for a “Yes” resolution. Airspace closures which occur solely due to weather conditions will not qualify. The primary resolution sources for this market will be official information from Iranian aviation authorities and a consensus of credible reporting.

card_id: mt-v02:polymarket:0xbd5922eed56186e904c4f327658e8c0cbd88cd854114d0906208f8b65cce6718:2026-05-19

market_id: 1b40fa51-3d00-489f-b6d6-6f29ed625286

venue_market_id: 0xbd5922eed56186e904c4f327658e8c0cbd88cd854114d0906208f8b65cce6718

resolution_source: 0x65070BE91477460D8A7AeEb94ef92fe056C2f2A7

Receipt and export

Audit chain

Convexly stores the card payload, removes the row_hash field, canonicalizes the remaining JSON, and recomputes the SHA-256 hash. This is the bridge from a readable verdict to a buyer-reviewable audit chain.

Export MarkdownPacket PDFPacket JSONAudit-chain JSON
market-trust-v02:2026-05-19T06-16-13-019Z

method: market_trust_card_v0_2

row_hash: bebdc4cf207faa51515208499bab1d0cc2387f7c70abe60d683c94fa45f05ec8

previous_row_hash: 94a8d5a79a2c766f24c970043eff3f7d2b915c5fd8f939ea08276e7f6f616ddc

source_artifact_hashes: 7002b390a2541e99d7731da4581fac0eaa08e44835e005404ba96c26a6148a59, 7ed2390954d064fbdc99b6c8531c1b895b87a094c7bb90454cb3882d2aa80350

Immutable verdict archive

Verdict hash

This verdict is archived as a canonical JSON object with a SHA-256 content hash. The hashed payload carries the methodology version (market_trust_card_v0_2), the canary_preview label, and a fixed boundary statement; none of them can be removed without changing the digest.

verdict archive sha256: 13677c6796f6bc8416768da984784b09099099f6653a655b9d12e527c5389fc2

How to verify this hash
  1. Fetch the canonical archive bytes: https://www.convexly.app/api/market-trust/v0.2/0xbd5922eed56186e904c4f327658e8c0cbd88cd854114d0906208f8b65cce6718/archive?venue=polymarket&format=canonical
  2. Recompute the digest locally, for example: curl -s "https://www.convexly.app/api/market-trust/v0.2/0xbd5922eed56186e904c4f327658e8c0cbd88cd854114d0906208f8b65cce6718/archive?venue=polymarket&format=canonical" | shasum -a 256
  3. Compare your digest to archive_sha256 in the JSON response at https://www.convexly.app/api/market-trust/v0.2/0xbd5922eed56186e904c4f327658e8c0cbd88cd854114d0906208f8b65cce6718/archive?venue=polymarket. Matching digests mean the archived verdict content is byte-for-byte unchanged.
  4. Cross-check card_row_hash against the stored full-card receipt at https://www.convexly.app/api/market-trust/v0.2/0xbd5922eed56186e904c4f327658e8c0cbd88cd854114d0906208f8b65cce6718/verify?venue=polymarket.

Stored v0.2 cards are frozen scorecards: a re-score inserts a new row with a new card_id and records the prior receipt in previous_row_hash, and the filed calibration design binds Convexly to never mutate frozen card-time rows. The archive is a deterministic serialization of one stored row, so the same row always reproduces the same archive_sha256.

Who shaped the price

Participant and integrity screen

Participant-flow screens flagged concentration, unknown-flow, or low-edge-flow conditions for review. This is an integrity-risk screen, not a manipulation accusation and not person-level identity resolution.

Scored flow

0%

0 scored accounts

Unknown flow

100%

higher unknown flow lowers confidence

Participants

4

public accounts observed

Top flow share

60%

concentration diagnostic

high participant concentrationhigh unknown flow sharethin participant countunknown or low sample flow present

Not claiming: wash-trading detection; sybil detection; manipulation-free market.

Instrument fitness diagnostics (experimental)

2 of 6 diagnostics have a derivable observable on this stored card; 4 are insufficient_data. An insufficient_data row means the card lacks that input, not that the check passed.

Depth durability

insufficient data

insufficient_data

No executability pillar is present on this card.

Observable: Executability pillar: worse-of(top-of-book spread, modeled price impact) from the latest inspected orderbook snapshot at 2026-05-19T06:13:22.864+00:00

Missing input: The stored card has no measured or heuristic executability pillar value (no current orderbook spread or depth input).

Spread and price impact

insufficient data

insufficient_data

No executability pillar is present on this card.

Observable: Top-of-book spread (price points) and modeled price impact for a fixed notional, from the latest inspected orderbook snapshot

Missing input: The stored card has no current orderbook spread or modeled price-impact input.

Time to resolution

insufficient data

insufficient_data

Venue lifecycle status on the card: active. No end date is stored.

Observable: Venue-supplied market end date or close time stored on the card

Missing input: The v0.2 card schema does not store an end date or close time, so time to resolution cannot be derived from this card.

Resolution reliability

heuristic

70 / 100 (descriptive)

Resolution source and rule text are present but not independently reviewed. Resolution rule text is stored on the card.

Observable: Resolution reliability pillar: review of the resolution source (0x65070BE91477460D8A7AeEb94ef92fe056C2f2A7) and stored resolution rule text

Caveats: resolved-outcome dispute history is not joined on this card; the read covers resolution source and rule text only; descriptive diagnostic from operator-set scoring that is not calibrated; no interval exists for this value, so none is shown rather than fabricated

Concentration exposure

insufficient data

insufficient_data

Participant-flow screens flagged concentration, unknown-flow, or low-edge-flow conditions for review.

Observable: Participant-flow concentration from the card's integrity screen: top account flow share, unknown flow share, scored notional share

Missing input: Participant-flow concentration is not measured on this card (no scored participant rollup or no top-account flow share).

Basis-risk note

descriptive

structural note

This market settles as a binary event contract: it pays a fixed amount on one discrete resolution. Offsetting a continuous exposure with a binary payoff leaves residual basis risk by construction, and binary payoffs will generally fail the ASC 815 80-125% dollar-offset band used for hedge-accounting treatment, so a position that works as an economic offset can still be carried as mark-to-market P&L. This is a structural description of the contract type, not a statement about any party's exposure.

Observable: Contract payoff structure (binary event contract) and the resolution rule text stored on the card

Caveats: structural description of the contract type, not accounting or legal advice

Published deliberately as a component table with no single combined number. Read each component against the observable it derives from; an insufficient_data row means the stored card lacks that input, not that the check passed.

These diagnostics describe observable market-quality measurements for one market. They are not investment advice, not a trading instruction, not a recommendation to take or offset any exposure with this or any market, and not a statement about any person or their positions.

instrument_fitness_diagnostics_v0_1

Ingest status

Source freshness window

The current ingest window is clean enough for review. This is freshness reporting, not an uptime SLA.

Latest orderbook

2026-05-19T06:13:22.864Z

most recent orderbook evidence attached to this card

Sources

1

1 healthy | 0 degraded | 0 stale | 0 failing

Dropped events

0

nonzero dropped events block current-language claims

Observed age

49s

oldest observed source watermark

Ingested age

47s

oldest ingest watermark

Canary vs v1

Validation state

Canary pipeline

blocked

Current card has source, evidence, or robustness issues to clear.

Public v1 promotion

4 public v1 validation gates still open.

Canary readiness says the current batch can be reviewed. Public v1 promotion waits for coverage, clean source-health windows, resolved outcomes, and formula-freeze evidence.

Read the promotion evidence contract
  • Not enough pillars on this card are measured yet.
  • Some pillars on this card are still gathering evidence.
  • 14 consecutive clean source-health days have not yet been observed.
  • 30 current cards across 3 market categories are not yet reached.
  • The scoring formula must be frozen before validation runs.
  • At least one resolved-outcome row is still needed in the validation ledger.

What travels with the score

Top caveats

  • Hard cap: Too much participant flow is unknown while participant-quality evidence is still pending.
  • Current card issue: Not enough pillars on this card are measured yet.
  • Current card issue: Some pillars on this card are still gathering evidence.
  • absence_of_signal_not_proof_of_coherence
  • artifact_hashes_present
  • below_publishable_sample_floor

Validation requirements

Before stable v1

  • 14 consecutive clean source-health days have not yet been observed.
  • 30 current cards across 3 market categories are not yet reached.
  • The scoring formula must be frozen before validation runs.
  • At least one resolved-outcome row is still needed in the validation ledger.

Non-scoring provenance

External context

No external baseline family is mapped for this market yet.

No external baseline family is mapped for this market yet.

External context is non-scoring in v0.2. Market Trust still measures market-quality substrate, not absolute truth against outside forecasts.

Full seven-pillar evidence grid

Coherence

weight 20 · heuristic

50 / 100

No full-provenance CME signal is linked to this condition in the current ledger window; absence of a signal is not proof of coherence.

no linked cme signal in windowabsence of signal not proof of coherencecme signal window days:7

Liquidity

weight 15 · heuristic

65 / 100

One-sided visible ladder; direct spread unavailable, so liquidity is capped and caveated.

one sided orderbook boundarydirect bid ask spread missingvisible $1k ladder slippage 0pp

Depth

weight 15 · measured

100 / 100

$1k visible-ladder slippage estimate is 0pp.

visible ladder slippage measured

Resolution reliability

weight 15 · heuristic

70 / 100

Resolution source and rule text are present but not independently reviewed.

resolution metadata present manual review pending

Participant quality

weight 20 · pending

pending

Participant-quality inputs exist but do not meet coverage floors.

below publishable sample floorhigh participant concentrationhigh unknown flow share

Integrity risk screen

weight 10 · pending

75 / 100

Mild concentration or coordination signals; review before citing.

top-3 wallets control 100% of notional flowflow events:4distinct wallets:4

Audit completeness

weight 5 · measured

100 / 100

3 linked artifacts; 0 missing hashes; 0 stale/failing sources.

artifact hashes presentsource watermarks healthy

Linked-market consistency

Coherence block

No full-provenance CME signal is linked to this condition in the current ledger window; absence of a signal is not proof of coherence.

Score

50

heuristic evidence

Source refs

0

linked-market or CME artifacts

no linked cme signal in window absence of signal not proof of coherence cme signal window days:7 recent full provenance signals:250

Sensitivity and drivers

Robustness block

Sensitivity verdict

stable

leave-one-out and weight perturbation

Leave-one-out

66-80

score range

Weight perturbation

71-73

score range

Drivers

3

largest weighted contributors

  • Coherence is heuristic, not fully measured.
  • Coherence scores below 60 and needs stronger evidence before the verdict can improve.
  • Liquidity is heuristic, not fully measured.
  • Resolution reliability is heuristic, not fully measured.
  • Participant quality is pending, not fully measured.
  • Integrity screen is pending, not fully measured.

Boundary of the packet

This packet is market diligence, not investment advice, not a claim of absolute truth, and not proof that any trader should buy or sell. It answers whether the market price has enough substrate to cite, monitor, discount, or ignore with receipts attached.