Understand the record connecting a watched market, explicit evidence, trigger and current prices, confidence, policy, decision state, and journal history.
August 3, 2026 · 4 min read
In TEMIRIN, a watchlist-derived record is created from a market already configured in the workspace watchlist. It preserves that market’s first recorded price as the trigger price and can update a separate current price on later syncs. The record is designed for review and audit, not as an instruction or promise of profit.
The current product builds opportunity records only from configured watchlist markets. Evidence appears beside a market only when a supported market identifier was explicitly supplied, and that bounded scope should remain visible in every description.
The record stores market identity, category, direction, confidence, status, summary, source and evidence IDs, trigger and current prices, observed times, price movement, liquidity context, and the current policy decision. Confidence is deterministic workflow context; it is not a probability forecast or an opaque review ranking.
Price movement shows how the displayed market changed after the trigger record was created. It does not prove that a source caused the movement or that either price was available for a chosen size. Users should inspect spread, depth, market wording, and source evidence separately.
A record can remain watched, need an in-app approval, be approved, rejected, blocked, associated with an open position, or closed. The state makes queue handling auditable, but it does not authorize venue activity. Approve or reject is recorded in the authenticated app.
The in-app approval endpoint applies the configured price-move guard and preserves the request time with the decision record. Telegram can deliver a provider-configured review alert; it cannot record the approve or reject decision.
When a paper order is linked to the opportunity, TEMIRIN can calculate a mark-to-market value for the paper order and compare it with a trigger-price reference path. The calculation uses the saved notional, direction, trigger price, and current market price. It is not an actual fill, realized profit, or forecast of an available venue outcome.
Keep the calculation beside the original paper-order assumptions and decision note. Review blocked and rejected records as well as favorable simulated moves so the learning set does not become a collection of selected winners.
The practical value is continuity: a stable ID connects the configured watchlist market, trigger-price memory, current price, policy status, explicitly linked evidence, in-app approval record, paper order, and later note. A teammate or support reviewer can reconstruct the state without relying on screenshots.
That continuity does not replace primary-source verification, resolution-rule reading, eligibility checks, or user judgment. TEMIRIN organizes current review records and keeps all real venue activity outside the product.
For a quality check, sample records from several watchlist categories and trace every displayed field to its origin. Confirm that the market came from the configured watchlist, the trigger price survived later updates, current-price time is visible, evidence IDs have explicit market links, and policy reasons match the stored policy version. If a field cannot be traced, label it unavailable rather than describing the record as intelligent or predictive. This audit keeps a convenient record from acquiring capabilities that its data path does not actually provide. Repeat the check after watchlist, source-tag, or policy changes.
Use the same narrow language in metadata, alerts, exports, and support documentation so the record is not described one way in the app and another way in search results. A consistent definition also helps users understand why an untagged source item can exist without an opportunity record and why adding a market to the watchlist changes coverage.
Use the same definition when training teammates and answering support questions. A watchlist-derived record with explicit links, preserved trigger price, current context, policy status, and human review is useful without adding predictive or execution claims.
The record connects a configured source trigger, an explicitly linked watchlist market, trigger and current price context, confidence inputs, policy state, decision status, notes, and later attribution.
The evidence must carry a supported explicit market identifier that matches a configured watchlist entry. Otherwise the source record remains stored without being presented as evidence for that market.
No. The record organizes review context, the authenticated decision records approve or reject, and a paper order is a separately created simulation with its own price, notional, limits, and timestamp.
