Choose a focused Polymarket watchlist manually and review market identity, resolution wording, current price, spread, visible depth, category, and notes.
August 3, 2026 · 3 min read
TEMIRIN opportunity records come from markets already configured in the workspace watchlist. Users decide which markets belong there, making the product’s coverage visible, deliberate, and auditable.
Start with a manageable set whose questions, categories, and resolution sources the user understands. Add or remove a market intentionally and retain the workspace audit context for material changes.
For every watchlist entry, confirm the market ID, outcome, question, close time, resolution source, and current status. Similar titles can refer to different deadlines or conditions, so the market identity must be more than a headline.
Evidence links require an explicit market identifier. A watchlist entry does not automatically receive every source item that mentions the same topic, and users should leave unrelated evidence unlinked.
Current price, best bid and ask, spread, visible depth, and observation time can help a reviewer understand the public market state. These values are read-only context, not an execution instruction or a guarantee of available quantity.
TEMIRIN preserves the first recorded trigger price for a watchlist-derived opportunity and updates current price separately. Keep the two timestamps visible so later movement is not confused with what was known initially.
Show the workspace stake cap, source and category enabled or blocked state and max-stake overrides, confidence settings, free-capital percentage, price-move guard, and kill switch where applicable. Keep each field tied to its stored role and reason.
Paper orders have separate per-order, rolling twenty-four-hour, per-market, and portfolio-concentration checks. Passing a watchlist review does not create a paper order and never creates a venue order.
At a regular cadence, inspect inactive or resolved markets, unclear categories, duplicate coverage, stale descriptions, and watchlist entries whose rules the user no longer follows. Clean the list deliberately without erasing earlier opportunity records.
Measure whether the current watchlist remains understandable, not whether an algorithm found every later winner. Keep notes about why a market was added or removed and verify that public metadata still describes manual selection.
A focused manual watchlist is useful because it bounds attention and makes trigger-price context persistent. It is not proof of completeness, suitability, or profitable selection.
Use a short admission checklist for every market added manually. Confirm that the question is open, the outcome is understood, the resolution source is accessible, the category is appropriate, and the user has a reason to monitor it. Record the market ID and addition time. A checklist reduces accidental duplicates and unclear entries without pretending that the software ranked the market or recommended it.
When removing a market, preserve prior opportunity, note, approval, and paper records that already refer to it. The watchlist change affects later coverage; it should not erase history. If the market was added with the wrong ID, correct the configuration and record the reason. This makes explicit-link mistakes diagnosable and keeps provenance intact.
Teams can review watchlist ownership alongside source ownership. Decide who checks resolved entries, broken resolution links, category labels, and unusually stale market data. A named owner and user-chosen review cadence are operating practices. The system shows stored state, and the user chooses when to perform the review.
For each review cycle, count markets added, removed, resolved, and left unchanged, then inspect a sample rather than optimizing for a larger list. A smaller watchlist with understood rules and clean identifiers is often easier to review than broad coverage that no one owns. Record the operating reason, not a performance promise.
Review the same checklist during onboarding so new workspace members understand that coverage is user-chosen. They should know where market IDs come from, how evidence links are supplied, and why a missing market remains outside the opportunity queue until someone adds it deliberately.
Verify the market identifier, outcome identity, resolution wording, status, current price, spread, visible depth, category, and the reason the market belongs in the workspace.
A configured RSS or web record must contain a supported explicit market identifier. The workspace displays that link and provenance rather than inferring a relationship from similar wording.
Assign an owner, review market status and rules, inspect stale price context, remove obsolete entries from active review, and preserve notes explaining important additions or changes.
