Build in Public: When the Market Changes Its Mind Mid-Trade

Here's a situation that used to have no answer in LiquidMind.

The morning bias comes in bearish on BTC. Two hours later, price taps a 1H order block, the lower-timeframe structure confirms, and the engine opens a short. Textbook. The trade is working.

The next morning, the bias agent runs again — and this time it's bullish. Conviction 70. The higher-timeframe lean just reversed.

But the short is still open.

So: what should happen?

Why Isn't a Flipped Bias Just an Exit Signal?

The naive answer is "close the short, the thesis is dead." That answer is wrong, and it's wrong in a way that costs money.

A daily bias is a strategic higher-timeframe lean. The short wasn't opened because of the daily bias in isolation — it was opened on a specific lower-timeframe setup, often targeting a pool of liquidity below current price. A bullish daily bias flipping doesn't invalidate that. In fact, a daily bias turning up frequently means the sell-side liquidity the short was hunting has just been swept — which is the short reaching its target, not failing.

There are three distinct realities hiding behind one event:

1. The move down completed, liquidity was taken, and higher-timeframe now wants up — the short is now counter-trend and its job may be done. De-risk.
2. The flip is premature or low-conviction noise, and the short's own structure is intact. Hold.
3. The short was always a counter-bias intraday play, and nothing about its thesis changed. Hold.

An automated "flip the position" would get all three wrong two-thirds of the time. Whatever we built had to weigh the flip, not obey it.

What Does the bias_flip Trigger Actually Do?

LiquidMind's position management is event-driven. Positions aren't monitored continuously — specific trigger events say "something worth reviewing happened." A Market Cipher B momentum dot prints (mcb_momentum_signal). An opposing zone appears (opposite_poi). Structure breaks in your favor (favorable_event_detected). Each one wakes the AI Sentinel to re-evaluate.

The daily bias reversal is now one of those events: bias_flip_{direction}_1D.

When the bias agent finishes its morning run and detects that today's BTC direction is the opposite of yesterday's — and only long↔short; a fade to neutral is not a flip — it fans a review out across the book:

One dispatch → the Triad's two layers (Sentinel stance, Guard action) → executed on the terms you set.

The Sentinel does its normal job — pulls fresh structure, momentum, liquidity — but now with an extra instruction in its prompt. It reads, in part:

### ⚠️ BIAS SHIFT (HTF CONTEXT)
The DAILY market bias (BTC-driven) just flipped LONG → SHORT (conviction 72/100).
This is a whole-market HTF context change, not a standalone signal. Weigh it against:
- Whether THIS position's own thesis still holds on its entry timeframe.
- Scale mismatch: an intraday move toward liquidity can stay valid despite an opposing daily bias.
- Time since entry: a fresh position may have this shift already priced in.
Only lean DEFEND/REDUCE_RISK if the position's OWN structure is also weakening.
The flip alone is never grounds for EXIT. Whatever you decide is executed or sent
for approval according to the user's management mode — so keep the bar for action high.

That last line matters. The agent knows its verdict has teeth: on a HOLD it does nothing, but a DEFEND or REDUCE_RISK will be carried out — automatically for Autonomous users, or after a tap for Approval users. So the prompt pushes it to earn any action, not hand out reflexive de-risks on a number that changed overnight.

Why Does Only BTC Fire the Review?

The bias agent runs on a watchlist — BTC, ETH, and more. So why does an ETH flip do nothing?

Because in crypto, BTC is the market regime. The directional lean of the entire book — including the alts — tracks Bitcoin. An ETH daily flip is a symbol-level event; a BTC daily flip is a whole-market event. When BTC's daily bias reverses, we don't just review BTC positions — we review every open crypto position, on every symbol, for every user, because the context change applies to all of them.

An ETH flip, by contrast, stays informational. It updates the journal and the briefing, but it doesn't wake the Sentinel across the book. One driver, one dispatch. It keeps the signal clean and the LLM bill honest.

Does It Execute, or Just Suggest?

It executes — gated by the autonomy setting you already chose. bias_flip is a normal trigger, not a special case, and it runs the exact same path as opposite_poi or an MCB momentum dot:

• Autonomous → a DEFEND or REDUCE_RISK is executed — SL to breakeven, a trailing stop behind structure, a partial. HOLD does nothing.
• Approval → the same verdict becomes an approval request in Telegram; nothing touches the exchange until you confirm.

The safeguard isn't a block on execution — it's where the conservatism lives. It lives in the prompt, in the agent's bar for action, not in a hard-coded veto. The engine is told, in no uncertain terms, that a flipped number is not a reason to close a working trade. If it still concludes the position is genuinely deteriorating — the flip and the position's own structure breaking — then acting on that is exactly what an autonomous user signed up for.

Threading this properly surfaced a bug worth mentioning in public: the "Analyze" button in the terminal passed allow_execution=False, but that argument was being silently ignored downstream. In Autonomous mode, a manual "just analyze this" could actually place a trade. Making execution explicitly mode-driven fixed that path too — "Analyze" now truly only analyzes.

What Does the User Actually See?

Whatever the mode dictates. For an Autonomous user whose position is genuinely rolling over, it's the normal action notification — "SL moved to breakeven," "partial taken" — with the flip named as the trigger. For an Approval user, it's a confirmation prompt. And when the verdict is HOLD, which on a healthy position it usually should be, it's quiet — because a trade that's still working doesn't need an alert every time BTC's daily bias wobbles.

That restraint is deliberate. The worst version of this feature is one that pings you at 6am every time a number flips and then does nothing useful. The bar for both action and noise is high on purpose.

One Contract, Not Two

If you read the POI state machine post, you know I'm allergic to behavior that changes depending on how it got there. Every trigger feeds the same Triad, and every decision answers to the same autonomy setting — a reversed daily bias included. One notion of what the agent decided, one setting that governs whether it acts.

So the discipline lives in exactly one place: the agent's judgment, shaped by the prompt. A flipped daily bias is context, and the engine is taught to treat it as context — to demand that a position's own structure confirm the danger before it acts. Never a loophole around the autonomy contract you set.

The aggregate outcome of all these decisions is tracked, in full, in the public trade ledger. This trigger is new enough that its fingerprints won't show there yet — but when the market changes its mind mid-trade, the engine now has something to say about it, on exactly the terms you asked it to.