ResolutionRuleParser
intel.resolutionruleparser
Intelligence
planned
Spec started
frozen
flagship
Convert each market's resolution rule into a structured representation: source-of-truth, condition, ambiguity score.
What it does
Convert each market's resolution rule into a structured representation: source-of-truth, condition, ambiguity score.
Pipeline placement
runs after: —
→
ResolutionRuleParser
→
runs before: —
Applies to: —
Why it matters
| If this fails | Consequence |
|---|---|
| Free-text rule treated as if structured | Resolution rules are written in English and parsed by humans. Without a structured representation, every downstream consumer — ContradictionDetector, RuleChangeMonitor, SourceOfTruthVerifier — re-parses the same string and gets subtly different answers. Worked example Setup: Market `Will Bill X be signed by 31 Dec 2026?` has a one-paragraph rule citing 'the official White House press release'. Without bot: Three downstream bots each parse the paragraph independently. ContradictionDetector concludes the source is `whitehouse.gov`. RuleChangeMonitor sees no change when the rule is later edited to `the official White House press release or comparable announcement`. SourceOfTruthVerifier never runs because it can't extract a URL. With bot: ResolutionRuleParser produces `{source: 'whitehouse.gov', condition: 'press_release_signed', deadline: '2026-12-31T23:59Z', ambiguity: 0.3}`. All three consumers read the same structured fact and the rule edit changes `ambiguity` to 0.6, which RuleChangeMonitor flags. |
| Ambiguity score not surfaced to strategies | A resolution rule with high ambiguity carries non-trivial settlement risk. Without an explicit score, strategy bots cannot down-size or skip those markets. |
| Source-of-truth field unused | A structured 'source-of-truth' field lets SourceOfTruthVerifier check whether the cited source actually publishes the data needed to resolve. The parser is the upstream that makes that check possible. |
| Rule changes hard to diff | RuleChangeMonitor needs to detect post-listing edits. Diffing structured representations catches semantic changes; diffing raw strings flags every cosmetic edit and misses meaningful ones. |
Inputs
Polymarket inputs
| Input | Source | Required | Use |
|---|---|---|---|
| Market resolution_rules and resolution_source from Gamma API | gamma | required | Primary source for extracting and hashing resolution rules. |
| Market condition_id and question text | data | required | Cross-reference condition_id to market metadata for rule provenance. |
Internal inputs
| Input | Source | Required | Use |
|---|---|---|---|
| KillSwitch active flag | KillSwitch | required | Suppress all ResolutionRuleParser emissions when KillSwitch is active. |
Authority
What this bot is permitted to do
Read-only
State
Readiness
Spec started
Status
planned
Class
Signal Service
Default mode
shadow_only
Developer owner
Polytraders core
Capital impact
Indirect
Reason codes emitted
| Code | Severity | Meaning | Action |
|---|---|---|---|
| RESOLUTIONRULEPARSER_MISSING_RULES | WARN | Market resolution_rules field is null or empty in Gamma API response. | Skip emission; log WARN for manual review. |
| STALE_DATA | WARN | Gamma API is unresponsive or returned stale market metadata. | Suppress emission; alert on-call if condition persists > 5 min. |
| KILL_SWITCH_ACTIVE | HARD_REJECT | KillSwitch active; all ResolutionRuleParser emissions suppressed. | Continue parsing but suppress ObservationReport emissions. |
| RESOLUTIONRULEPARSER_SOURCE_CHANGE | WARN | Resolution source changed since last parse (e.g. from UMA to manual). | Emit ObservationReport with change_detected=true; flag for strategy review. |
Related bots in Intelligence
Used by
Reverse index — strategies that currently reference intel.resolutionruleparser. If you change this bot's authority or reason codes, these strategies must re-pass shadow.
| Strategy | State | Activity |
|---|---|---|
| US Elections — sentiment fade | demo-wired | last triggered 40m ago |
| BTC weekly — close-aware quotes | demo-wired | last triggered 47m ago |
| Fed Rates — surprise drift | frozen | last triggered 7m ago |
Showing 3 of 3 · demo-wired ≠ production-live
Why this matters
Intelligence bots does NOT propose, veto, sign, or execute any trade. Understanding the authority boundary prevents misuse and makes promotion-gate reviews faster and more reliable. View raw spec JSON →