Standalone Analysis
Kalshi Markets
Resolution analysis works with Kalshi markets via theexchange parameter:
exchange parameter:
Batch Analysis
Pipeline Guard
Theresolution_guard() blocks quoting on markets with ambiguous resolution conditions:
Injected Parameters
| Parameter | Type | Description |
|---|---|---|
resolution_analysis | ResolutionAnalysis | Full analysis object |
resolution_risk | str | Risk level: “low”, “medium”, “high” |
resolution_blocked | bool | True if ambiguity exceeds threshold |
Configuration
model field.
Risk Levels
| Level | Ambiguity | Description |
|---|---|---|
| Low | 0.0 - 0.3 | Clear, verifiable conditions |
| Medium | 0.3 - 0.6 | Some subjective elements |
| High | 0.6 - 1.0 | Significant ambiguity, committee-dependent |
Resolution Types
| Type | Description |
|---|---|
binary_event | Yes/no outcome from a specific event |
threshold | Numeric threshold (price, score, etc.) |
committee | Resolved by committee vote or subjective judgment |
oracle | Resolved by designated oracle or data source |
Types
ResolutionAnalysis
| Field | Type | Description |
|---|---|---|
market_id | str | Market identifier |
market_title | str | Market question |
resolution_source | str | Primary resolution authority |
conditions | list[ResolutionCondition] | Resolution conditions |
ambiguity_score | float | 0.0 (clear) to 1.0 (ambiguous) |
edge_cases | list[str] | Identified edge cases |
timing_risks | list[str] | Timing-related risks |
resolution_type | str | Resolution mechanism type |
estimated_resolution_date | str | Expected date or “unknown” |
risk_level | str | ”low”, “medium”, “high” |
reasoning | str | LLM reasoning |
timestamp | float | Unix timestamp |
ResolutionCondition
| Field | Type | Description |
|---|---|---|
description | str | What needs to happen |
source | str | Resolution authority |
verifiable | bool | Objectively verifiable? |
ambiguity_notes | str | Ambiguity notes |