Paste one prompt. Dare your strategy to survive.

Build this idea as a Pine v6 strategy: [describe your idea in plain English]. Compile-check it. Then backtest it honestly on [OANDA:XAUUSD] [1h] — full history, per-year windows, and an in-sample/out-of-sample split — on my real TradingView Strategy Tester. Give me the verdict with every gate that failed, and the ONE mutation worth trying next. If nothing honest is worth trying, say so plainly. End with a summary card: VERDICT / trades / OOS PF / max DD / next move.

My strategy just failed the kill-gates. Here is the verdict card: [paste the verdict]. Tell me what is legal to try next under an honest research playbook. If the answer is a different strategy family — not a parameter tweak — say so plainly, scaffold that candidate, and run it through the same honest multi-window backtest. End with the new summary card: VERDICT / trades / OOS PF / max DD / next move.

Here is my existing Pine strategy: [paste the code or file path]. Audit it, compile-check it, then run it through the same honest multi-window backtest and kill-gates — full history, per-year windows, in-sample/out-of-sample split — on my real TradingView Strategy Tester. I want the verdict a fund would give me, not encouragement. End with a summary card: VERDICT / trades / OOS PF / max DD / next move.

This strategy is from a video: [paste the rules exactly as taught]. Build it faithfully in Pine v6 — no improvements, no fixes — and test whether it survives real out-of-sample windows on my own TradingView Strategy Tester. Don't be polite. If it only works in one year, name the year and explain why that matters. End with a summary card: VERDICT / years survived / OOS PF / the one honest conclusion.

Take these five ideas: [list them in plain English]. Build, compile-check, and kill-gate test each one on [symbol] [timeframe] on my real TradingView Strategy Tester. Give me a leaderboard: KILLED / WEAK / PASS for every idea, one line on why each died, and which single candidate deserves a forward test. The leaderboard IS the summary card — end with it.

Import my trade history from [file]. Find where I'm actually bleeding: by session, by day of week, by symbol, and by behavior after a loss. Then show me the ONE change with the biggest net improvement, with the exact numbers before and after. No motivational talk — just the leak and the patch. End with a summary card: THE LEAK / what it costs / THE PATCH / net improvement.

Take this strategy: [paste or describe it]. Before viewing results or tuning, establish which data has already influenced it and reserve a later chronological holdout that has not. If no untouched history is available, say so and use a fresh forward window; do not relabel previously seen data as out-of-sample. On my TradingView Strategy Tester, deliberately overfit ONLY the development window and log every tried variant. Freeze the chosen rules, parameters, costs and evaluation gates, then evaluate the reserved window once without retuning. Report the dates, trial count and selection history. Any further changes consume that holdout and require fresh data. Teach me the difference on my own chart. End with a summary card: SELECTED DEVELOPMENT result / UNTOUCHED EVALUATION result or unavailable / trades / costs / trial count / limitations.

Here is a strategy: [paste the Pine code or the rules]. Run it twice on my real TradingView Strategy Tester on [BINANCE:BTCUSDT] [1D], same date range both times, including at least one bear-market year; if the chart cannot load a range that long, say so on the card instead of quietly using a shorter one. Run 1: no costs — commission 0 and slippage 0, overriding anything the script sets. Run 2: realistic costs — commission [0.15]% per order ([0.1]% fee plus [0.05]% for slippage) and slippage 0. Do not change the rules between runs. End with a summary card: GROSS = Run 1 net profit / NET = Run 2 net profit (not TradingView's "Gross profit" row) / fees paid = Run 2 commission paid / max DD (Run 2) / Buy & Hold same period / VERDICT: SURVIVED COSTS if Run 2's net profit is above zero, WIPED BY COSTS if not.

Check Bitcoin against one line, using my rule:
1. Get https://data-api.binance.vision/api/v3/klines?symbol=BTCUSDT&interval=1d&limit=202 (Binance's free public daily candles: in each row, the 1st value is the day's start time and the 5th is its close). The last row is today, not finished yet: drop it. That leaves 201 finished days.
2. The line = the average of the last 200 daily closes. Latest close above the line = HOLD BITCOIN. Below = HOLD CASH.
3. Do the same for the day before the latest close: its own close against the average of the 200 closes ending on that day. If the answer changed, start with "ACTION: BUY" (cash to Bitcoin) or "ACTION: SELL" (Bitcoin to cash). If not, start with "NO ACTION".
4. Then, on the same line: HOLD BITCOIN or HOLD CASH, the date of the latest close (UTC), the close, the line, and how far the close is above or below the line, as (close − line) ÷ line in %.
If you can, fetch and compute in code, and check you have 201 finished days in a row. If you can't get these rows from this link, reply only "NO DATA: could not reach Binance": use no other source, and never a remembered or guessed price. Never place a trade: you only report my rule, I decide.