Position
flat
1 of 1 executors connected
Every signal the strategy sent, and exactly what the broker did with it.
⭐ What this measures is execution fidelity — whether the trade your broker actually took matches the trade your strategy intended. Where the fill landed against the price you sent, whether the stop ended up the distance you asked for, whether a third really came off at each target.
⛔ It is not measuring whether the strategy makes money, and at 0 closed trades it could not. Every figure below is a measurement of the plumbing; the assessment section says plainly where that stops and what a real sample would need.
Everything else on this page is current state. This is the sequence — ⭐ built from the trade record and the configuration history, so it cannot drift from what actually happened.
| When | What |
|---|---|
| 20 Sep 16:48 | Gold 2-minute started — OANDA:XAUUSD on XAUUSD, 4 windows |
| 15 Sep 19:00 | Nasdaq 3-minute started — VANTAGE:NAS100 on NAS100, 7 windows |
| 15 Sep 19:00 | Nasdaq 3-minute (retired) retired |
| 14 Sep 19:00 | Nasdaq 3-minute (retired) started — CAPITALCOM:US100 on USTEC, 4 windows |
Taken from the broker's own deal history — not from TradingView's messages, which carry one alert for both legs of an exit and so cannot tell a stop-out from a take-profit. Planned is the price your strategy sent; filled is what the broker gave.
| Time | Instrument | Window | Dir | Planned | Filled | Slip | Exit | Risk asked | Risk taken | Held | Why | R | P&L | Running |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| No strategy signals executed yet. The pilot is armed and waiting for its first macro window. | ||||||||||||||
Nothing here yet. 0 hand-fired test trades are excluded on purpose: they proved the machinery, and counting them as your strategy's results would flatter or damage the record without meaning either.
⭐ The table above is the outcome; this is the working. For a strategy that scales out in thirds, the outcome alone hides most of what happened — when a third came off, when the stop moved and to where, what the remainder closed at. Straight from the executor's own records; nothing here is derived.
Candles from your broker's own feed — the same one that filled the order, so a candle and a fill can never disagree. ⭐ Each chart is drawn hours after the trade closed and deliberately runs on past the exit, because the useful question is not where we got in. It is what price did next.
Your strategy already thinks in macro windows and your own Pine has a per-macro table, so this is the same cut taken from real fills. ⚠ At 0 closed trades none of these figures can carry weight — it is here because it starts accumulating now, and because a window that never fires is worth seeing long before its numbers mean anything.
| Window | Signals | Last | Closed | Won | Total R | Mean R | P&L | State |
|---|---|---|---|---|---|---|---|---|
| 08:50 | — | — | — | — | — | — | — | no signal yet |
| 10:50 | — | — | — | — | — | — | — | no signal yet |
| 19:50 | — | — | — | — | — | — | — | no signal yet |
| 21:50 | — | — | — | — | — | — | — | no signal yet |
⚠ 4 of 4 windows have never produced a signal: 08:50, 10:50, 19:50, 21:50. That is not yet a fault — a window is an opportunity, not a schedule — but a window still silent after a few weeks is worth questioning. ⛔ No conclusion should be drawn from the columns above until each window has a sample of its own; one trade gives a window a 100% or 0% win rate, which is arithmetic, not information.
What the relay did with each message before the executor ever saw it. Times are the relay's, which is the only clock in this chain that is both trusted and shared. ⚠ A rejected message is a missed trade, and a missed trade looks exactly like a quiet market — so each one is listed rather than counted.
| Time | From | Instance | Message | Outcome | Why |
|---|---|---|---|---|---|
| nothing received yet | |||||
Times on this page are Cayman time. ⚠ New York is 1 hour ahead of Cayman at the moment, because New York observes daylight saving and Cayman does not. So a window labelled 09:20 NY is 08:20 your time today — and the same clock in January, when the two align.
⚠⚠ A TradingView alert freezes your inputs, the chart symbol and the timeframe at the moment you create it, and keeps firing that frozen copy until it is deleted and remade. So a trade does not belong to “the settings” — it belongs to whatever was frozen into the alert that produced it. Each block below is one such configuration, with the trades that came from it.
⚠ TradingView offers no way to read an alert's settings back, so these are declared, not read. Where the messages themselves prove something, it is marked evidenced; everything else is our word for it.
⭐ ARMED 2026-09-20 18:55 UTC, owner's decision. demo_only=no, KillSwitch=false, risk 0.05%, MaxOnAccount=1, breakeven After 1:1, four macros 08:50 · 10:50 · 19:50 · 21:50 NY, cap 4. ⛔ THE CHART-TO-BROKER PRICE OFFSET IS STILL UNMEASURED. Broker's Friday close was 4377.66 bid / 4378.26 ask (spread $0.60); compare against OANDA:XAUUSD's Friday close. Under ~$0.30 is fine. ⚠ No Risk Shield watcher exists yet - MaxDailyLossPc=2.0 is a local backstop that cannot see the 6%-of-peak-equity floor.
0 trades came from this configuration.
| Setting | Your default | Running as | How we know |
|---|---|---|---|
| Chart and instrument | |||
| Chart | — | OANDA:XAUUSD | declared |
| Timeframe | — | 2m | declared |
| Broker symbol | — | XAUUSD | declared |
| Account | — | Upcomers Thunderbolt 1M, real, 1:100 | declared |
| Macro windows | |||
| 08:50 NY | off | on | no signal yet |
| 10:50 NY | off | on | no signal yet |
| 19:50 NY | off | on | no signal yet |
| 21:50 NY | off | on | no signal yet |
| Trade geometry, as the messages describe it | |||
| Reward multiples, scale-out | 1:1 · 2:1 · 3:1, thirds | declared | awaiting a real signal ⚠ hand-fired tests are deliberately not counted — their geometry is ours, not the strategy's |
| Strategy inputs changed from your defaults | |||
| Enable Webhook Alerts? | false | true | declared |
| Ticker Symbol | NQM2026 | XAUUSD | declared |
| Move SL to Breakeven | After 1:1 | After 1:1 | declared |
| SL Buffer (×ATR14) | 1.95 | 2.0 | declared |
| Max Trades Per Day | 7 | 4 | declared |
| Max Trades Per Macro Window | 1 | 1 | declared |
| Execution limits (ours, not yours) | |||
| Risk per trade | — | 0.05 % of balance | declared |
| Position cap | — | 50.0 lots | declared |
| Daily loss limit | — | 3.0 % | declared |
| Concurrent positions | — | 1 | declared |
⭐ 2026-09-17: the author revised the window set to SEVEN and the daily cap to 7, one trade per macro. These are now HIS DEFAULTS unchanged - the only deviations left are the webhook switch, the ticker, and breakeven at 2:1 which he gave by phone. First TradingView signal 2026-09-16. ⭐ 2026-09-18: gold considered and deferred - XAUUSD verified FULL on this account, but MaxConcurrent=1 would make the two instruments starve each other and the dashboard assumes a single current epoch.
0 trades came from this configuration.
| Setting | Your default | Running as | How we know |
|---|---|---|---|
| Chart and instrument | |||
| Chart | — | VANTAGE:NAS100 | declared |
| Timeframe | — | 3m | declared |
| Broker symbol | — | NAS100 | declared |
| Account | — | Vantage demo, 1:100, USD 100k | declared |
| Macro windows | |||
| 00:50 NY | off | on | no signal yet |
| 03:50 NY | off | on | no signal yet |
| 09:20 NY | off | on | no signal yet |
| 18:50 NY | off | on | no signal yet |
| 19:50 NY | off | on | no signal yet |
| 22:50 NY | off | on | no signal yet |
| 23:50 NY | off | on | no signal yet |
| Trade geometry, as the messages describe it | |||
| Reward multiples, scale-out | 1:1 · 2:1 · 3:1, thirds | declared | awaiting a real signal ⚠ hand-fired tests are deliberately not counted — their geometry is ours, not the strategy's |
| Strategy inputs changed from your defaults | |||
| Enable Webhook Alerts? | false | true | declared |
| Ticker Symbol | NQM2026 | NAS100 | declared |
| Move SL to Breakeven | After 1:1 | After 2:1 | declared |
| Execution limits (ours, not yours) | |||
| Risk per trade | — | 0.5 % of balance | declared |
| Position cap | — | 5.0 lots | declared |
| Daily loss limit | — | 3.0 % | declared |
| Concurrent positions | — | 1 | declared |
Retired: that broker refused every index order with retcode 10017. No trade ever executed on this epoch.
0 trades came from this configuration.
| Setting | Your default | Running as | How we know |
|---|---|---|---|
| Chart and instrument | |||
| Chart | — | CAPITALCOM:US100 | declared |
| Timeframe | — | 3m | declared |
| Broker symbol | — | USTEC | declared |
| Account | — | MetaQuotes demo, USD 100k | declared |
| Macro windows | |||
| 09:20 NY | off | on | no signal yet |
| 14:50 NY | off | on | no signal yet |
| 18:50 NY | off | on | no signal yet |
| 22:50 NY | off | on | no signal yet |
| Trade geometry, as the messages describe it | |||
| Reward multiples, scale-out | 1:1 · 2:1 · 3:1, thirds | declared | awaiting a real signal ⚠ hand-fired tests are deliberately not counted — their geometry is ours, not the strategy's |
| Strategy inputs changed from your defaults | |||
| Max Trades Per Day | 7 | 4 | declared |
| Enable Webhook Alerts? | false | true | declared |
| Ticker Symbol | NQM2026 | US100 | declared |
| Execution limits (ours, not yours) | |||
| Risk per trade | — | 0.5 % of balance | declared |
| Position cap | — | 5.0 lots | declared |
| Daily loss limit | — | 3.0 % | declared |
| Concurrent positions | — | 1 | declared |
⭐ Every one of the 66 inputs in your strategy, with the 13 the pilot changed marked, is on its own page: the full settings table → It is read straight out of your Pine source, so the defaults column cannot drift — and it is the proof that nothing else was touched.
Each finding recomputes from the records on every rebuild, heading included. ⚠ The reasoning behind them does not — it updates its numbers but cannot notice something nobody has looked for.
Every closed trade on record - 0 of them - was hand-fired to prove the plumbing, and all are excluded below. The link from TradingView to this system is the one part that has never been observed carrying a real signal. Until it does, this page reports on machinery, not on a strategy.
0 plans executed, 0 plans refused by the executor, 0 rejected at the relay before the executor saw them. ⭐ Each refusal was a designed stop exercised on purpose during testing — a stale plan, a stop the broker's minimum distance would not accept, a budget already spent, a bad secret. The alternative in each case was trading something other than what the strategy chose. That every one of them fired, and refused rather than adjusted, is the evidence this section can offer today.
TradingView alerts stop firing after about 60 days on Essential, with no error, no email and no trace — and this page cannot read the date, so it has to be told. ⚠ Until it is, the countdown below covers the broker account only, and the alert could lapse at any time without anything here changing. ⭐ Open TradingView's alert manager, read the expiry on the current alert, and record it in config/epochs.json.
Vantage demo account 2026-10-16 (25d). ⚠ Each of these stops the pilot with no error, no email and no trace, and a strategy that trades at most four times a day cannot be watched for silence — a lapsed account and a quiet market look identical. ⭐ That is why they are counted down from recorded dates rather than noticed after the fact. The nearest one is the one that matters.
Four hops. Your script owns the first and nothing after it.
⭐ The relay is yours to own, not ours to rent you. Everything on this page runs on infrastructure you would control.
The relay is a free Cloudflare account and four commands. Your account, your URL, your secrets. Nothing runs on our side, and nothing breaks if we disappear.
The executor is a single file. It drops into MetaTrader's Experts folder and attaches to a chart. Its risk settings are a text file it re-reads every thirty seconds, so they change without a dialog and without a restart.
The alert message is a wrapper around your own. ⭐ That is why your Pine needs no changes at all — TradingView substitutes your strategy's JSON inside it.
⭐ None of this is hypothetical — the pack is built and waiting: the compiled executor (123 KB), a settings template, a preset template and a setup guide written from what actually went wrong. ⚠ It contains no credentials of any kind; the URL, token and account number are yours to fill in. Ask and it is yours.