Use explicit market tags and a configured Polymarket watchlist to review stored RSS or web evidence with price context, policy status, notes, and audit history.
August 3, 2026 · 3 min read
TEMIRIN ingests configured RSS and HTTPS web sources into workspace-scoped evidence records. The fetchers retain canonical URL, source identity, observed time, available publication time, baseline extracted text, and safe source metadata. Canonicalization and content deduplication reduce repeated copies without hiding where the evidence came from.
This evidence pipeline begins with sources the user has configured, together with a plan-scoped refresh cadence and user-chosen tags. A failed fetch, stale source, or incomplete page remains visible in the ingestion ledger rather than appearing as a confident summary.
The current evidence brief organizes stored fields such as source tier, reliability, relevance, direction, freshness, tags, and explicit market identifiers. The source records remain available beside the brief so users can verify every summary against its configured inputs.
Reliability and relevance are review aids, not truth certificates. A primary source can be old or irrelevant to the exact resolution condition, while a secondary source may be timely but incomplete. Keep authority, freshness, direction, and market wording separate instead of turning them into one opaque recommendation.
Stored evidence links to a Polymarket market only when the ingestion path receives a supported market ID through an explicit tag, URL, or query. TEMIRIN does not claim arbitrary source-tag and watchlist discovery. If the identifier is missing, the evidence can remain in the workspace without being forced onto a market.
This boundary improves auditability. A reviewer can see whether a link came from deliberate configuration rather than inferred similarity. When the wrong market ID is supplied, correct the configuration and preserve the source record; do not describe the error as a configuration mismatch.
TEMIRIN builds opportunity records from markets already present in the workspace watchlist and the deterministic intelligence snapshot for those markets. The first recorded market price becomes the preserved trigger price; later syncs update the current price while retaining that original reference. The record can also include confidence, status, policy result, and explicitly linked source or evidence IDs.
This watchlist-derived scope keeps coverage bounded to markets users deliberately selected. Adding a source expands evidence collection for configured inputs, while users choose watchlist coverage and check market wording and resolution sources.
The user can inspect the opportunity record, compare trigger and current prices, review public-wallet exposure, record an in-app approve or reject decision, create a risk-checked paper order, and save a decision note. Each step is persisted, but none authorizes a real venue transaction.
Review the workflow by asking whether evidence links were explicit, source data was fresh, the correct watchlist market was used, policy reasons were understandable, and later paper marks kept their assumptions. That produces useful operational learning grounded in explicit configuration, attributable records, and human judgment.
A monthly operating review should sample accepted evidence, duplicates, failed fetches, explicitly linked items, and evidence left unlinked. Confirm that canonical URLs still resolve, source tiers remain appropriate, refresh entitlements match the active plan, and market IDs point to the intended watchlist records. Track corrections prospectively and preserve the original ingestion event. This routine improves source quality without inventing a hidden discovery layer, and it gives teams a concrete explanation when an evidence brief is sparse: the product summarizes only the configured, stored, and explicitly linked inputs it actually has.
Document the boundary during onboarding: sources create evidence records, explicit market identifiers create evidence links, and configured watchlist markets create opportunity records. Those are separate operations with separate failure states. If an expected market relationship is absent, check the tag and watchlist configuration first.
The source record must include a supported explicit market tag or identifier that matches the watchlist entry. The link remains visible so the reviewer can trace the relationship directly.
TEMIRIN keeps the evidence with its provenance and timestamps but does not place it beside a market as support. A reviewer can inspect it separately or add a supported explicit link.
Keep the original source, canonical URL, observation time, explicit market link, trigger and current prices, policy state, decision note, owner, and audit history together.
