All work

Case study · TradingView indicator

My trading model, written as code so the chart finds the setup for me.

Role
Design and build
Type
TradingView indicator
Status
Live
The problem

The CISD Rejection Block model I trade and teach needs several things to line up at once: a change in state of delivery, a higher-timeframe fair value gap, and the deepest rejection wick inside that gap. Checking all of that by hand across timeframes, every session, is slow and easy to get wrong.

What I built
  • An engine that tracks every CISD level on finished candles, so nothing repaints after the fact
  • Rejection blocks that only print when a wick taps a valid CISD inside a live 15 minute, 1 hour or 4 hour fair value gap
  • One block per gap: a deeper qualifying wick replaces it, and it is removed once the gap or the CISD is broken
  • The entry marked at the 50% midpoint of the wick, with a label showing the block size and whether it is still fresh
  • Alerts for new CISDs and new rejection blocks, sent only when a candle closes
  • Works on the 3 minute through 4 hour charts, with a backtestable strategy version built on the same engine

Built in Pine Script with Claude Code over six releases, v1.0 to v1.6, and studied across about 2,000 backtested trades.

Built with

Claude Code, Pine Script v6, TradingView

Where it stands

Version 1.6 is live and offered to members of The Trading Ark as Ark Indicators.

Visit thetradingark.com
Next case study Beals Lawn Services