A practical guide to manual review of configured official resolution pages in TEMIRIN using configured records, explicit market identity, current controls, and human review.
August 3, 2026 · 4 min read
The market question and rules define what resolves a Polymarket contract, not the loudest headline. Before monitoring any page, open the exact market and copy its outcome wording, cutoff time, jurisdiction, measurement threshold, and named resolution source into a reviewer note. Then configure the official public page that is expected to publish the decisive fact when technically suitable. This preparation prevents a plausible news report from being treated as equivalent to the authority specified by the contract.
Official pages vary widely. An election board may publish certified tables, a statistics agency may release a dated series, a sports body may post a final result, and a court may update a docket. Identify the precise field or document the reviewer expects to inspect. TEMIRIN can store configured RSS or HTTPS web evidence and provenance; it does not interpret every resolution clause, resolve a contract, or guarantee that an authority will publish on a predictable schedule.
For each stored update, retain the canonical URL, publisher identity, observed time, supplied publication time when available, and source configuration. A screenshot alone can hide navigation context or later corrections, while a bare link can change. The stored record and canonical reference together give the reviewer a traceable starting point. If the page is unavailable or collection fails, expose that operational state rather than assuming that the absence of a new record confirms the prior value.
Official sources sometimes revise preliminary data, issue corrections, or publish multiple documents with different legal status. Keep each relevant record attributable and note which version the human reviewer used. Deduplication can reduce repeated web evidence, but it should not erase a genuinely changed publication. The reviewer must still compare the update with the contract terms. TEMIRIN’s deterministic evidence organization does not create an automated hierarchy that declares one conflicting record authoritative.
Resolution evidence belongs beside a market only through a supported explicit market identifier. Opportunity records come from markets already configured in the workspace watchlist. This boundary is especially important when one authority publishes many similar series or contests. A user should verify that the stored page, exact market ID, outcome side, period, and measurement all refer to the same question before making a decision note.
Show the preserved trigger price and a current price observation as market context, with timestamps for each. A repricing before certification may reflect rumors, preliminary releases, liquidity conditions, or information outside the monitored page. Do not label the price move as proof that the official result is known. Public spread and visible depth can help a reviewer understand the displayed market state, but neither replaces the resolution rules or demonstrates an executable fill for a particular order.
A configured alert rule may deliver the stored update through email, Telegram, Slack, or outbound webhook. The delivery ledger and manual retry controls make transport reviewable, but a successful attempt only shows that the message reached the destination. It cannot resolve the market, approve a decision, create a paper order, or act at the venue. In-app approve or reject remains a distinct authenticated record and may be blocked by the configured price-move guard.
Use a concise resolution checklist after an alert: reopen the contract, inspect the official record, note any revision status, compare the publication time with the cutoff, and record the reviewer’s conclusion. If the wording is ambiguous, keep the status unresolved and seek appropriate venue guidance rather than forcing certainty. TEMIRIN provides provenance, watchlist context, price observations, alerts, and journal history; users remain responsible for interpreting the contract and every external transaction.
After resolution, compare the evidence record used by the team with the venue’s final resolution history and retain any difference as a process note. This is not an automated correctness score. It can reveal that a source was preliminary, a document arrived after the cutoff, or a reviewer relied on the wrong field. Keeping the original note and the later lesson separate makes the record useful for training without pretending the final outcome was known earlier.
No. It can store configured evidence and market context, while the user must interpret the exact contract and the venue’s resolution process.
No. The relevant document, status, cutoff, jurisdiction, threshold, and authority must match the market’s wording and rules.
No. Evidence is shown beside a configured watchlist market only through a supported explicit market identifier.
