Follow a current TEMIRIN alert through delivery history, authenticated in-app review, the price-move guard, and an explicitly created paper order.
August 3, 2026 · 4 min read
An eligible watchlist-derived opportunity can create an in-app alert event. Evidence appears beside the market only through an explicit supported market identifier. The alert does not discover a market or decide that the source is true.
Show market identity, trigger and current price context, safe evidence context, policy status, and a link to the workspace record. Keep private wallet details and provider credentials out of the message.
Provider-configured Telegram, Slack, email, or webhook destinations can receive external notifications according to current deployment and workspace setup. Every send has its own delivery attempt and status.
Provider acceptance means transport progressed. It does not prove a person read the message, does not update approval state, and cannot create a paper or venue order.
Approve or reject is recorded through the authenticated in-app endpoint with workspace record identity, reviewer context, actor, and timestamp.
The endpoint enforces the configured price-move guard. When price exceeds the threshold, it rejects the stale decision conditions. The approval record keeps the decision timestamp; users initiate any fresh review manually.
A user can create a separate paper order after review. The server checks plan-scoped per-order and rolling twenty-four-hour notional, per-market exposure, and portfolio concentration. A blocked request returns a reason.
The paper order is simulated. It does not advance automatically from approval, reserve wallet funds, receive a venue fill, or create an external position.
Test an in-app event, failed external send, successful external send, signed-out link, price-move rejection, in-app approve or reject record, blocked paper request, and accepted paper record. Verify that each state remains separate.
Retain event and record IDs, safe timestamps, policy versions, snapshot references, and decision notes. Troubleshoot transport without changing decision history, and troubleshoot paper checks without describing a venue transaction.
The result is a reviewable current workflow: alert, optional external notification, authenticated decision, and optional paper record. The workspace preserves alert, decision, and paper records as separate states.
Use a shared identity trail to make the workflow reconstructable. The alert event should reference the watchlist-derived opportunity, each external attempt should reference the alert, the in-app decision should reference the opportunity, and any paper order should carry its own ID plus the opportunity reference. Shared links help navigation, while separate records prevent transport or review status from being mistaken for a simulation.
Test role and workspace isolation explicitly. A signed-out link should reveal no protected detail, a member from another workspace should not open the record, and a user without the required review role should not submit approve or reject. These authorization results belong to the authenticated app; external channels must not bypass them.
After a price-move rejection, refresh current market context and ask the user to review again. Preserve the original trigger price and earlier decision attempt instead of updating them in place. If the user later creates a paper order, save it under the new observed conditions and retain the server’s pass or block reasons. This sequence documents what changed with the original and refreshed review states kept separately.
Make support diagnostics follow the same boundaries. Ask first whether the in-app event exists, then whether an external delivery attempt exists, then whether an authenticated decision exists, and finally whether a separate paper order was created. This sequence identifies the failing record without assuming that one successful step caused the next.
External message copy should lead to the authenticated workspace record with clear open, review, and inspect actions. A user creates any paper order separately in the workspace.
Use a safe test destination to create one failed delivery attempt, inspect its sanitized reason, correct the configuration, and retry the eligible attempt. Then open the authenticated review record, record a decision, and create a separate user-entered paper request. The final audit should show transport recovery, decision identity, price context, and paper checks as distinct events tied to the same workspace record.
The workflow keeps the alert event and delivery attempts, the authenticated in-app review and decision, and the separately created paper order as distinct records linked to one opportunity.
It is evaluated in the authenticated review against the stored trigger price and current observation. The result belongs to the decision record, not to the external delivery message.
No. The paper order stores its simulated side, price, notional, policy result, and timestamp in the paper ledger for analysis.
