Current Bridge decision engine

Test signals, replies and safe rejections.

See how Navigator Bridge v8 interprets a new entry, a reply-management command, a split SL/TP continuation, provider result chatter or unsupported text—without queuing anything to MT5.

Bridge v8.00TP1–TP5fail-closed
Syntax simulation only. “Reply context” tells the tester which grammar to evaluate; it cannot manufacture a Telegram message link, Bridge signal record or MT5 ticket. Live management still requires that exact proof.
Message under test
01 / Input

How did this message arrive?

Tests new entries, commentary and whether a standalone management command fails closed.

No message is sent to Bridge or MT50 / 5,000
Match Bridge settings and provider aliases

Aliases are tested as an additive provider/topic vocabulary and retain the same reply/ticket safety. A modify alias must prefix explicit SL/TP values.

Bridge interpretation
02 / Decision
>_
Ready for a message

The result will distinguish entry signals, protected commands, split follow-ups, blocked actions and harmless provider chatter.

What this tester covers

New trade entries

Direction, broker-normalized symbol, market/pending/zone type, entry, SL and TP1–TP5.

Protected reply commands

Close, partial close, breakeven, SL/TP edits, cancel pending, TP-leg close and Move TP to Entry.

Provider-specific behavior

Global/provider/topic alias grammar, bare reply opt-in and split-message provider policy.

Safe non-actions

Result chatter, stale-status wording, unsafe standalone management and ambiguous text.

Command examplesNavigator Bridge 8.00Troubleshooting

Recognition is not permission to trade. Provider policy, exact reply/ticket proof, entry age, symbol mapping, whitelist/blacklist, duplicate and cooldown state, broker rules and EA controls are evaluated elsewhere. Pasted text is processed for this response and is not intentionally stored by this tool.