u/Minimal_Lobster

I’ve been developing a TradingView decision-support framework designed to separate four conditions: setup, confirmed direction, weakening, and exit/wait.

One problem I wanted to address was indicators changing direction too quickly during ordinary pullbacks. In this SPY example, the framework remained in the same active long state for 40 five-minute bars while continuing to monitor the strength of the move.

The “Bars In Trade” label is simply the number of bars spent in the confirmed state. It is not a brokerage position, P&L claim, or suggestion that the entire move was captured.

From a trader’s perspective, would you rather have a framework remain stable through normal pullbacks, or react sooner even if that creates more state changes?

I’m especially interested in feedback on whether the panel communicates the current state clearly at a glance.

I built a TradingView framework to help make my trading decisions more consistent — from identifying a setup through managing the trade once it’s active.

The workflow is fairly simple.

The TCP Watchlist Scanner monitors the symbols I’m interested in. When something stands out, I select that symbol from my TradingView watchlist and it opens in the second window with the TCP Decision Panel.

The SPY screenshot attached is one of the cleaner examples from this week.

The Decision Panel remained Long Active for 71 five-minute bars through the move. By the time of this screenshot, the scanner had shifted to LONG TREND WEAKENING, while the Decision Panel still showed the underlying long state as active.

That distinction is intentional.

I wanted the system to recognize that momentum is weakening without automatically treating that as the same thing as the trend being over.

That’s really what led me to build this. I didn’t want another indicator constantly throwing buy and sell signals at me. I wanted something that could help answer three questions:

Is there actually a good setup?
Has it been confirmed?
Is there a reason to get out yet?

I’ve now started a small private beta with a few traders and I’m mainly looking for feedback on:

• Scanner / Decision Panel agreement
• State transitions — SETUP → LONG/SHORT → WAIT
• Trade-bar counting and resets
• Whether weakening states appear at sensible times
• Situations where it keeps a trader in too long or gets them out too early
• Anything confusing or inconsistent

Still testing and still finding things to improve.

The goal from the beginning has been pretty simple:

Fewer but better decisions.

For the past several months, I’ve been building The Confirmation Project for my own intraday trading.

The problem I wanted to solve wasn’t a shortage of indicators. It was inconsistency—hesitating on valid setups, reacting emotionally during trades, exiting strong moves too early, or staying with weakening trades too long.

TCP uses two views built around the same decision framework:

• A Watchlist Scanner that monitors multiple symbols and identifies developing opportunities.
• A Decision Panel on the chart that helps manage the trade after a setup appears.

Instead of simply flashing BUY or SELL, it moves through clearly defined states such as:

• Early Wait
• Setup Building
• Hold Long
• Hold Short
• Trend Weakening
• Exit

The goal is to answer two practical questions:

Is a qualified setup developing?

Once in a trade, is the trend still healthy enough to hold?

I’ve spent the last several weeks testing the Scanner and Decision Panel side by side—particularly their entries, exits, trade states, and Bars in Trade.

I’m now opening a small private beta and looking for a few active TradingView users willing to provide honest feedback.

I’m particularly interested in:

• Scanner and chart discrepancies
• States that are unclear in real time
• Genuine bugs
• Usability issues
• Anything that makes the workflow harder to understand

This is a decision-support framework—not automated trading, financial advice, or a promise of results. Trade selection and risk management remain the trader’s responsibility.

If you’re interested in testing it, reply here or send me your TradingView username.