T4T Macro IFVG — Execution Log

Every trade the strategy produced

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.

1 trade, -517.09 in total. Best -517.09, worst -517.09. Far too few trades to mean anything about the strategy — they are here because execution accuracy is only worth reading next to what it cost.

Every leg, trade by trade

⭐ 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.

What the market did around each trade

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.

Which macro window is producing this

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 1 closed trade 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.

⚠ 4 of 5 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.

Every message, in order

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.

Configuration history

When the setup itself changed — a chart, a symbol, a window set, one configuration replacing another. ⭐ Read from the epoch record, so it cannot claim a change that did not happen. ⛔ The trade milestones that used to sit here were removed: they restated the leg table above, and the partial line was hardcoded to the word tp1 while matching the earliest partial of any level, so a tp2 fill was folded into the tp1 row and read as a tp2 that never happened.

The settings behind every number here

⚠⚠ 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.

⭐ Every one of the 66 inputs in your strategy, with the 10 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.

What this data does and does not support

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.

How a signal becomes an order

Four hops. Your script owns the first and nothing after it.

Running it without us

⭐ The relay is yours to own, not ours to rent you. Everything on this page runs on infrastructure you would control.

⭐ None of this is hypothetical — the pack is built and waiting: the compiled executor (143 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.

What this run has and hasn't shown