Test your own signal as your position

A smaller week. Every change here started with a report from you.

Your signal can be your position

If you uploaded a TradingView strategy's signal (+1 long, 0 flat, -1 short) and tested it as your own indicator, PTQ read it as a score and picked its own levels to act on. So a 0 didn't close the trade. Two longs with a flat gap between them came out as one trade, and the trade count didn't match TradingView.

Strategies on your own indicator now have a signal mode. In the builder, next to the rule type, it asks "Your signal column is" with two options:

• A score. This works exactly as before and stays the default. PTQ picks the levels and tests 7 sets of them.
• My position. PTQ trades the column as given: +1 long, 0 flat, -1 short, held until it changes. On a long-only strategy, -1 means flat.

You can also ask Claude to set it. In "My position" the column must hold only -1, 0 or 1. Any other value is refused, never rounded, and a missing value holds the position you're in. PTQ's stop and target still apply, so a stop can close a trade before your signal does.

One thing to know before you validate. PTQ didn't choose anything in this mode, so the overfitting check has nothing to compare. It says "not applicable" with the reason and counts as not passed. The luck check counts 1 attempt, so any searching you did before uploading isn't in that number.

"Both" stays "Both", and you're not charged twice to validate

A strategy Claude made to trade long and short turned into long-only when you opened it in the web app. Pressing Test there saved that change and charged 11 credits to backtest and validate a strategy you'd already validated.

"Both" is now kept, and the builder has a Both button next to Long and Short.

Validating the same backtest again within 24 hours now returns the verdict you already have and charges nothing. A second click while a validation is still running is turned away without a charge. If you do want a fresh validation of the same backtest, ask Claude to re-run it and it charges as normal.

Credits back when a run fails on our side

If a backtest or validation fails because something broke at our end, the credits it took go straight back to your balance, and the error says so. If they couldn't be returned, the message tells you to contact support. A run we turn down because of its settings still costs what it cost.

SMT divergence in the Academy course

The course's tester used to read one market at a time, so a rule comparing two markets couldn't be written. SMT divergence between EURUSD and GBPUSD is the common one: one pair takes out its swing low or high and the other doesn't.

Day 3 can now name a second market. Day 4 loads it from the same price source, or from its own CSV, and lines the two up bar by bar. If the second market has no data or its bars don't line up, it stops and says why. There's a new SMT divergence building block, bullish on lows and bearish on highs, with a lookback and a number of bars it stays valid for. It works alongside the session window, fair value gaps, swing stops and R targets. Day 5 and the Day 6 paper loop use the same numbers.

Download the new "(5 Oct)" prompt and Academy tools from the Day 1, 3, 4 and 5 lessons. Re-send the Day 3 prompt in the same chat and add the second market to your spec.

Fixes

• Validating a backtest that ran on your own uploaded data crashed with "'str' object has no attribute 'get'", and the 10 credits were still taken. It now finishes and gives you a verdict. Re-run validation on any backtest built on your own data.
• In the October competition, daily strategies lost their first trading day. The 1 October bar was stamped at midnight, before the window opened at 05:00 UTC, so it became the starting point and 7 of 22 entries showed as not measured. Each bar now counts from its close, so daily entries are measured from day one.

If something here doesn't work the way it says, or there's something you want PTQ to do next, tell us.