A price trigger should reopen a question

Treat a price trigger as a reason to reconsider the strategy. The wake-up and the entry condition are distinct events. We would define what evidence the agent must check after the wake-up, especially when the original thesis depends on a catalyst that can change independently of price.

The public policy and execution reference describes a schedule or trigger making a turn eligible, followed by evaluation and possible action. Configured checks precede submission. This is the Hyperliquid alpha workflow inspected October 3, 2026, rather than a claim about guaranteed trigger timing.

Crossing the level after the thesis changes

Illustrative scenario: an owner watches a fictional perpetual priced near 100. They want reconsideration above 105, provided a scheduled product announcement still supports the thesis. Price reaches 106 after the announcement is postponed.

The price condition occurred. The supporting event condition failed. A well-specified mandate can therefore produce a completed review with no entry. If the owner had intended unconditional price-following behavior, that would be a different strategy and should be written explicitly.

Use the example to distinguish three statements: “The level was crossed,” “the thesis was reviewed,” and “an admissible order filled.” Each needs its own observation. Inferring the third from the first discards both reasoning and execution stages.

Write the reconsideration question

A useful instruction could ask the agent to refresh the event status, inspect current exposure, and assess whether the completed price evidence still matches the entry rule. The owner should identify which facts are essential and which are contextual. An unavailable required fact should have a specified waiting response.

A conditional wake-up can also become obsolete. Perhaps the owner changes the market scope or adopts another thesis before the level is reached. Review the current saved strategy and active trigger conditions together. A historical rationale describing why the trigger was created is insufficient to establish its current authority.

Our mandate compiler article explains how instructions become decision criteria. Our state and memory article covers the relationship between remembered context and current account state.

Judge the turn by the reopened question

After the turn, inspect whether the event status was refreshed, whether the existing position was recognized, and whether the action followed the current mandate. A no-trade result can be correct if the postponement invalidated the required evidence. A policy rejection can also prevent an otherwise supported entry, but it belongs to another part of the diagnosis.

If an order was submitted, compare the recorded outcome with Trades and Positions. The trigger tells you why review began; those records tell you what happened afterward. That distinction lets owners refine wake-up conditions without silently turning every market alert into an instruction to trade.