A practical guide to manual no-trade decision review in TEMIRIN using configured records, explicit market identity, current controls, and human review.
August 3, 2026 · 4 min read
A no-trade decision means the reviewer chose not to create even a simulated paper order after examining a Polymarket market record. It differs from a missed alert, an unreviewed queue item, a rejected approval request, and a paper order blocked by policy. Keeping these states distinct shows whether the team exercised judgment, lacked information, encountered an operational problem, or requested something the implemented controls did not allow.
The decision note should identify the exact market and outcome, evidence consulted, observation time, trigger and current prices, and the primary reason for stopping. Common reasons include ambiguous resolution criteria, insufficient provenance, stale market data, wide spread, shallow visible depth, price movement, existing exposure, or simple lack of conviction. TEMIRIN organizes these facts so the reviewer can record the reason and preserve it for later analysis.
Good no-trade analysis begins with provenance. Retain the configured source record, canonical reference, observed and available publication times, and any explicit market-ID link. Read the venue's question, outcomes, deadline, and resolution source directly. If evidence is unlinked or a page is unavailable, say so. Do not infer that thematically similar material supports the market or reconstruct a deterministic brief from facts learned after the decision.
Price context deserves the same discipline. The trigger price is the first stored observation for the watchlist-derived record, while current price is a later value with its own timestamp. Neither is a guaranteed executable price. Add bid, ask, spread, and visible depth only when available from read-only market data. If the reviewer stops because liquidity context is incomplete, preserve that as uncertainty rather than estimating a fill.
A reviewer may choose no trade even when current policy fields do not block the record. That is human judgment. Conversely, a proposed paper order may fail a per-order limit, rolling twenty-four-hour total, per-market exposure check, concentration rule, or price-move guard. That is an implemented control result. Record both plainly rather than turning every cautious choice into a policy failure or every policy block into a bearish thesis.
Public-wallet snapshots add exposure context but not spending authority. A visible balance does not tell the workspace how much the user should risk, and incomplete external holdings may change the full picture. Current paper controls evaluate a user-entered notional against the per-order limit, rolling twenty-four-hour total, per-market exposure, and portfolio concentration. If size uncertainty drives no trade, the reviewer should describe that uncertainty directly in the decision note.
After the market moves or resolves, append a dated review note rather than editing the original explanation. Compare what the reviewer knew with what happened next, and state which later facts were unavailable at decision time. A favorable move after no trade does not automatically reveal a process error; uncertainty, concentration, or poor execution context may have justified stopping. An unfavorable move does not prove that the reasoning was sound for the right reasons.
Never assign realized or simulated PnL to a no-trade record that created no paper position. A later price can illustrate opportunity cost, but it is not a captured return and may not have been executable at the desired size. Report sample counts, categories, and missing data beside any aggregate. Include no-trade decisions in journal exports so the performance narrative does not become a selection of only entered simulations.
Group recent decisions by reason only after reading a representative sample. Repeated provenance gaps may indicate a source-list problem; recurring ambiguity may suggest the watchlist includes markets the team cannot interpret reliably; many stale-price decisions may point to data operations; and frequent concentration concerns may justify reviewing exposure before alerts are configured. These operating questions guide source-list, watchlist, and review-checklist improvements.
Choose one prospective change at a time, such as retiring a broken source, adding a clearer note prompt, or narrowing a watchlist. Preserve earlier records under the configuration that existed then. Revisit the sample after enough new decisions accumulate and compare explanation quality, not just the number of trades. A useful no-trade practice makes disciplined inactivity visible while every real capital and venue decision remains the user's responsibility.
Write the review conclusion in operational terms: which field was unclear, which source lacked ownership, which market rule caused recurring uncertainty, or which exposure view arrived stale. Avoid a universal lesson from a handful of outcomes. A bounded change with a future review date creates a testable improvement while leaving the original no-trade decisions attributable to the information and procedures that existed then.
Not necessarily. No-trade records human abstention after review. An in-app reject action and a paper-order policy block are separate states that should retain their own reasons.
No. Without a paper order there is no simulated position, and an observed market price is not proof of an executable fill. It may be reviewed only as clearly labeled context.
The user enters the paper notional. TEMIRIN then applies the implemented per-order, rolling twenty-four-hour, per-market exposure, and portfolio concentration checks.
