Review market identity, side, price, public-wallet exposure, paper-order limits, evidence, and audit context before saving a simulated Polymarket order.
July 7, 2026 · 4 min read
A TEMIRIN paper order is a simulated workspace record, not a Polymarket order. The form requires explicit confirmation of paper-only mode, no venue placement, and risk review. This language matters because a market price, opportunity status, or in-app approval should never be mistaken for a fill.
Before saving, identify the exact market, outcome side, requested notional, assumed price, and observation time. If any of those fields is uncertain, return to research. A precise-looking paper result built on the wrong outcome token or a stale mark is not useful evidence.
Compare the preserved trigger price with the latest current price, then inspect public spread, visible depth, liquidity, and market status. TEMIRIN exposes this context for review; it does not guarantee that a paper price could have filled at the requested size. Document the assumption used for the simulated entry.
Resolution wording remains more important than a favorable chart. Check the named resolution source, close time, outcome definition, and any ambiguity that could change interpretation. Link the relevant evidence or write the missing question in a decision note.
The server enforces the plan per-order notional cap and rolling twenty-four-hour notional cap. It also compares the request with per-market exposure and portfolio-concentration limits using the latest stored public-wallet snapshot. The response should make the binding reason visible when a request is blocked.
Investment-policy settings such as maximum stake, source or category overrides, confidence bands, free-capital percentage, price-move guard, and kill switch can add review context. Paper-order enforcement uses the per-order and rolling twenty-four-hour notional checks recorded in the paper ledger.
Portfolio snapshots provide read-only balance, open and closed positions, PnL, concentration, liquidity, drawdown flags, and largest-position context. They do not prove wallet ownership or grant signing authority. TEMIRIN does not need a private key, seed phrase, or mnemonic for this review.
Confirm snapshot freshness before relying on exposure. If data is stale or missing, stop the paper review or record the limitation explicitly. Do not treat unavailable portfolio context as zero exposure.
Attach a decision note with thesis, invalidation, conviction, evidence IDs, and review date. Later, compare the paper-order mark with the preserved trigger-price reference and current market mark. The result is a hypothetical mark-to-market view, not actual profit or proof that the simulated size was available.
A useful review asks whether the market identity, evidence, price convention, risk limits, and portfolio context were clear at the time. It does not reward a weak process solely because the market later moved in the same direction. Users remain responsible for all real venue decisions.
Test the review with adverse cases as well as an accepted paper order. Try a notional above the plan cap, repeated orders that breach the rolling window, a market already near its exposure limit, a concentrated portfolio snapshot, and missing or stale portfolio context. The expected response is an explicit block with a useful reason, not a silent adjustment. Retain these rejected attempts in the audit trail so the team can verify that the implemented controls behave consistently and can distinguish an enforced paper-order limit from a policy field that is stored only for review context.
Keep one rejected example beside every accepted paper order during team review. The paired records should show the requested notional, current price observation, saved portfolio snapshot, applicable plan limit, binding reason, and audit time. Reperform the calculation from those stored inputs and confirm that a later portfolio refresh does not rewrite the historical decision. Also verify that the ticket carries its explicit paper-only and no-venue-order confirmations. This small sample catches stale snapshots, unit mistakes, and confusing explanations before they become routine. It reinforces the product boundary as well: the record is a simulation for review, not evidence of a venue submission, fill, custody event, or realized return.
Verify market and outcome identity, side, simulated price and notional, current price context, evidence, public-wallet exposure, applicable paper limits, policy state, and the audit note.
It provides read-only balance, position, and exposure context with an observation time. It does not authorize wallet activity and should not be treated as proof that the portfolio stayed unchanged.
Do not save the simulated order as accepted. Show the failed check, applicable value, observation time, and a safe audit reason so the reviewer can correct the record or stop the workflow.
