docs(concepts): add Polymarket Resolution reference#225
Merged
Conversation
New concept page documents the additive `polymarketResolution` field that surfaces the upstream UMA optimistic-oracle lifecycle. Five-value enum (settled_normal / voided / disputed / proposed / unknown) with per-value semantics, the upstream caveat that cancellation / participant_withdrawn / event_not_occurred all collapse to `voided`, and a comparison table vs Pinnacle / Kalshi / OpticOdds. Linked from the sportsbooks page Polymarket callout. Pairs with api-adapters PR #724 (the wire-side plumbing). Will be live in production once that PR lands and a followup adapter PR emits terminal closed-market rows. Customer-driven (Simon, Crisp session_9439dafc). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a new concept page documenting the additive `polymarketResolution` field that pairs with api-adapters PR #724.
Why Polymarket-prefixed name
We deliberately chose `polymarketResolution` over a generic `resolutionStatus` so it's obvious the values are Polymarket-specific. Pinnacle's parallel survey (yesterday) concluded their wire emits no equivalent. A future Kalshi version would be a separate field with its own enum.
Customer driver
Simon Olsson (Crisp `session_9439dafc-a2c8-426c-86a0-594921d6ed06`, fp `177861749673385` + `177866323193031`) asked about 50/50 cancellation + participant withdrawal scenarios. The doc explicitly addresses both — they both end up as `voided` upstream because UMA does not distinguish them.
Coordination
Test plan
🤖 Generated with Claude Code