VCET v1.1 Chart Overlay - Usage Guide

Build date 2026-06-07 · Indicator: vcet_indicator_v1_1_chart_overlay.pine · Engine parity: matches python/vcet_engine.py v1.1 (kite_v1.1.0) · Pine version literal: pine_v1.1.0-chart-overlay · Anchor: Pull-In Research Hub

What this overlay gives you

A chart-facing rendering of the VCET v1.1 + CBO framework so you can read rotation, compression, expansion, trend, pull-in failure, and pull-in → trend conversion in real time. It plots VWAP and bands at ±0.5/±1/±2/±4 SD, the Pardo CBO channel (prior 20 bars, current bar excluded), CBO break markers, the current VCET state, a post-entry management timer at +3/+10/+15/+25 minutes, and a risk-management dashboard table at the top-right of the chart.

This is a chart layer. It does not write to the database, does not change taxonomy, does not modify the Python engine, and does not refresh Scorecards. It exists alongside the existing canonical Pine alert indicator (vcet_indicator_v1_1.pine) - they share math but serve different purposes.

1. Installation in TradingView

  1. Open TradingView. Open the Pine editor (bottom panel → Pine Editor).
  2. New blank script → paste the contents of vcet_indicator_v1_1_chart_overlay.pine (file at C:\Users\jtdom\Downloads\vcet_v1_1\pine\).
  3. Save and add to chart. Name it “VCET v1.1 Chart Overlay”.
  4. You should see VWAP, four band tiers, the CBO channel as aqua / fuchsia lines, and a dashboard table top-right.
  5. To get the management timer, toggle manual entry mode ON in indicator settings and set the entry timestamp. Optional: set trade direction (Long / Short / None).

2. What you see on the chart

2.1 VWAP and bands

VWAP (white, 2px)
RTH-anchored typical-price VWAP. Resets each new ET trading date. This is the anchor for everything else.
±0.5 SD bands (faint gray)
Inner Pull-In zone. Calm-tape entries live near these lines.
±1 SD bands (gray)
Outer Pull-In zone. Edge of "still calm" - beyond this you are usually in extension.
+2 SD band (green, 2px)
The Pull-In → Trend trigger zone. Close above this with confirmation is the "hold for trend" signal.
−2 SD band (red, 2px)
Backside / Rubberband zone. Reclaim from this level toward VWAP is the mean-reversion play.
±4 SD bands (faint green / red)
Extended-trend target / extreme backside. Rarely reached without trend.

2.2 CBO channel (the v1.1 addition)

CBO channel high (aqua line)
Highest high of the prior 20 bars (current bar EXCLUDED, per Pardo). Close above this = LONG CBO break.
CBO channel low (fuchsia line)
Lowest low of the prior 20 bars (current bar EXCLUDED). Close below this = SHORT CBO break.
CBO LONG marker (aqua triangle, below bar)
Bar closed above the prior 20-bar channel high. This is the v1.1 channel-breakout-confirmed signal.
CBO SHORT marker (fuchsia triangle, above bar)
Bar closed below the prior 20-bar channel low. v1.1 SHORT breakout signal.

2.3 State label (top-right, follows last bar)

A floating label at the right edge of the chart shows the current VCET state in real time. Color-coded:

ROTATIONFlat bands, slope near zero, no breakout recent. Trade the band edges or pass.
COMPRESSIONBands tight, price near VWAP, volatility contracting. Wait for break.
EARLY_EXPANSIONJust left compression; width starting to widen; not yet confirmed. Position carefully.
EXPANSION_CONFIRMEDv1.0 range break + expansion score above threshold. Direction tagged in label.
TREND_UPStrong upward slope past threshold AND price above +1 SD. Hold for continuation.
TREND_DOWNStrong downward slope AND price below −1 SD. Hold short / counter-trend long passes.
MEAN_REVERSIONPrice extended ≥2.5 SD; first reversal bar present. Reclaim toward VWAP.

2.4 Dashboard table (top-right of pane)

10-row table summarizing the current state and management context:

RowWhat it shows
VCET v1.1Current state + direction (color-coded by state)
Setup modeWRONG-SIDE / TREND / ROTATION-PULL-IN / UNKNOWN
Pre-trade gateGREEN / YELLOW / RED / UNKNOWN (derived from gap condition + instrument type)
ManagementWhat to DO right now (scalp / hold candidate / reduce / exit / watch only)
Risk suggestionNormal / reduced / pass / reduce-exit (derived from gate + post-entry conditions)
VWAP slope (bp/bar)Numeric slope in basis-points-per-bar
Band width %Numeric width + arrow (↑ expanding, ↓ contracting, = stable)
Dist from VWAP (SD)Signed standard deviations from VWAP
CBOLONG ↑ / SHORT ↓ with strength, or "inside channel"
Elapsed (min)Minutes since manual entry, when manual entry is on

3. How to read mechanism in real time

3.1 The mechanism signatures (encoded in the dashboard)

true_pull_in_to_trend (the conversion)

  • Entry state: ROTATION or COMPRESSION near VWAP
  • Within 5-15 min: width EXPANDS (arrow ↑)
  • Slope ACCELERATES in trade direction past flat threshold
  • CBO break fires in trade direction (aqua ↑ for LONG, fuchsia ↓ for SHORT)
  • State transitions to EARLY_EXPANSION → EXPANSION_CONFIRMED → TREND_*
Management: trail wide, hold the core, do not auto-scratch at +1 SD. Target +2 SD close then hold for trend continuation.

vwap_rotation_scalp

  • Entry state: ROTATION (often near VWAP)
  • Width stays FLAT (arrow = stable)
  • Slope stays near zero (slope cell < flat threshold)
  • CBO never fires (channel cell shows "inside channel")
  • State remains ROTATION at +15 / +25 min
Management: target the opposite band, take the rotation. Don't extend stops hoping for a breakout that isn't coming.

wrong_side_escape

  • CBO fires OPPOSITE trade direction (fuchsia when you're LONG; aqua when you're SHORT)
  • Slope accelerates AGAINST direction
  • State transitions to TREND opposite trade direction within 5-15 min
  • Dashboard "Setup mode" cell turns WRONG-SIDE red
Management: exit or reduce quickly. The outcome will be lucky scratch or ugly loss. Do NOT let P&L validate the setup.

trend_continuation_entry

  • State at -5 / 0 (entry) was ALREADY TREND_UP / TREND_DOWN in trade direction
  • CBO had ALREADY fired before entry (timer ran from a previous bar)
  • No fresh compression precursor
  • Slope sign matches direction, often decelerating
Management: different play than a Pull-In conversion. Manage as continuation - tighter stop, smaller R, accept lower hit rate.

range_break / hitchhiker

  • State: COMPRESSION at entry-5
  • CBO fires within +/-2 bars of entry
  • Band width expands within 10 min
  • State transitions to TREND_* matching break direction
Management: hitchhike the break. Trail behind structure. Tighter than Pull-In conversion because the breakout is concentrated, not extended.

rubberband / backside

  • "Dist from VWAP (SD)" cell ≥ +/-2.5 AGAINST trade direction
  • State: MEAN_REVERSION near entry
  • Price reclaims toward VWAP within 25 min
  • Slope at entry against direction but DECELERATING
Management: band-anchored stop at ±2 SD opposite, exit at VWAP, no trailing.

4. Post-entry management timer

When you flip on manual entry mode in the inputs and set manual entry timestamp, the overlay draws checkpoint labels on the chart at the specified offsets from entry. The dashboard "Elapsed (min)" cell ticks alongside.

CheckpointWhat it checksWhat the label says
+3 min FADE detection (close moved against direction past entry price) If fading: red label "3 min: FADE - reduce / exit" above bar · If holding: green label "3 min: no early failure" below bar
+10 min Expansion confirmation: width expanding AND slope in direction AND CBO in direction If yes: green label "10 min: trend conversion candidate" · If no: yellow label "10 min: manage as rotation scalp"
+15 min Same expansion confirmation re-evaluated If yes: green "15 min: confirmation HOLDS" · If no: yellow "15 min: no confirmation → rotation"
+25 min Final mechanism call: expansion confirmation AND state in {TREND_UP, TREND_DOWN, EXPANSION_CONFIRMED} If trend: green "25 min: TREND CONVERSION" · If not: yellow "25 min: NOT a trend; manage as rotation/exit"
anytime > 0 Wrong-side CBO fired (opposite trade direction) Red label "Wrong-side CBO - reduce / exit" above bar (can fire any bar after entry)

5. The pre-trade gate (dashboard "Pre-trade gate" cell)

Encoded directly from the research conclusions. Drives the "Risk suggestion" cell:

Gap conditionInstrument typeGateRisk suggestion
controlledmegacap-tech / energy-commodity / other-acceptableGREENNormal planned risk
controlledother (uncategorized)YELLOWReduced risk only
extended(any)REDPass or reclassify
(any)crypto-proxy-ETF / small-cap-high-betaREDPass or reclassify - this is the leak-instrument class
unknown(any)UNKNOWNDefine gap + instrument first

5.1 Why no RVOL gate?

Per the research conclusions, RVOL is secondary context, not the primary gate. Gap condition and instrument type predict outcomes more reliably than RVOL. The Quality Gate doc lists RVOL as a numeric reference, but the chart-overlay gate uses gap + instrument as the primary inputs. RVOL still appears in the chart math (used for v1.0 range break detection) but does not drive the dashboard's pre-trade-gate cell.

6. Inputs reference

GroupInputDefaultPurpose
DisplayShow VWAP bandstrueToggles all band plots
DisplayShow CBO channeltrueToggles CBO channel lines + break markers
DisplayShow state labeltrueThe floating state label at chart right edge
DisplayShow management dashboardtrueThe 10-row table
DisplayShow management timertrueThe +3/+10/+15/+25 checkpoint labels
Trade contextTrade directionNoneLong / Short / None - used for fade detection + CBO direction match
Trade contextManual entry modefalseEnables the post-entry timer + fade tracking
Trade contextManual entry timestamp(set in UI)The bar time of your entry (used as t=0)
Trade contextGap conditionunknowncontrolled / extended / unknown - feeds the pre-trade gate
Trade contextInstrument typeothermegacap-tech / crypto-proxy-ETF / small-cap-high-beta / energy-commodity / other
CBOEnable CBOtrueMaster CBO toggle (computation + display)
CBOCBO channel lookback20Number of prior bars in the channel (current bar excluded)
CBOCBO min break strength0.0Filter noise - raise to 0.05+ in choppy tape
CBONormalize strength by ATRfalseElse normalize by channel width
Engine(all VCETConfig defaults)variousMatch Python VCETConfig v1.1 defaults - leave unchanged unless you know why

7. Workflow recipes

7.1 Pre-trade scan (no manual entry yet)

  1. Open the chart. Leave manual entry mode = OFF.
  2. Set Gap condition based on the opening gap you read pre-market (controlled = within +/-0.5%, extended = past +1.5% or symbol-in-{IBIT, AMD, ETHU, RGTI}).
  3. Set Instrument type based on what you're trading.
  4. Watch the dashboard cells:
    • Pre-trade gate = GREEN: you have permission to take a Pull-In
    • Pre-trade gate = YELLOW: reduced size only, with a thesis stated
    • Pre-trade gate = RED: do not click Pull-In
  5. Cross-reference with the current state label - ideally you want to be entering when state shows ROTATION or COMPRESSION (where mechanism conversion is possible).

7.2 After clicking entry

  1. Toggle manual entry mode = ON in indicator settings.
  2. Set Manual entry timestamp to your fill bar (TradingView lets you click a date/time field).
  3. Set Trade direction to Long or Short.
  4. Watch for the +3 minute label to fire:
    • If "FADE - reduce / exit" appears, you're in trouble - reduce or scratch
    • If "no early failure" appears, you're holding fine
  5. Watch for the +10 / +15 labels:
    • "trend conversion candidate" / "confirmation HOLDS" - you can trail wide and hold
    • "manage as rotation scalp" / "no confirmation" - target the band, take the rotation
  6. If WRONG-SIDE CBO fires any time after entry - reduce/exit immediately.
  7. At +25 minutes you get the final mechanism call. Use it to decide whether you're in a Pull-In conversion or not. If the engine says it isn't, accept that even if the trade is currently green - the slug is hypothesis, not confirmed.

8. Limitations and caveats

Read these before trusting the overlay's calls

9. How this overlay relates to the canonical alert indicator

vcet_indicator_v1_1.pine (canonical)vcet_indicator_v1_1_chart_overlay.pine (this file)
PurposeProduction webhook alerts + parity auditTrader-facing chart visualization
Overlay modeNo (separate pane with histogram)YES (price-overlay)
VWAP / SD bandsComputed, not plotted as separate bandsPlotted at ±0.5 / ±1 / ±2 / ±4 SD
State machineFull v1.0 + v1.1 with all reason codesSlim: state names only, simplified priority
CBO computationYes, full Python parityYes (same math, current-bar exclusion)
CBO channel renderingNoYES (aqua / fuchsia channel lines)
Webhook JSON payloadYES (state transitions emit)NO (chart-side alertcondition only)
Dashboard tableDebug table onlyRisk-management dashboard
Manual entry timerNoYES (+3 / +10 / +15 / +25)
Database writesNone (webhook to alerts_tradingview)None

Run both on the same chart if you want webhooks AND visual rendering. They share math; they will agree on state.

10. Next steps to add it to your workflow

  1. Add it to TradingView: Pine Editor → paste → Save → Add to chart.
  2. Verify it compiles. If TradingView shows a compile error, capture the line number and message; the error will point to a syntax issue I can patch.
  3. Sanity check the bands: on a chart you know (NVDA, AAPL, SPY), confirm VWAP is at the right level, +2 SD plots green above, −2 SD plots red below. If the bands look wildly off, the session anchoring may not match your chart's session settings.
  4. Confirm CBO channel is plotted correctly: the aqua line should be the highest high of the prior 20 bars (NOT including the current bar). A new session high BAR should not be ON the aqua line - it should be ABOVE it (which is the CBO LONG break condition).
  5. Pin the dashboard: move the table to a position that doesn't cover price action.
  6. Set up alerts: right-click on the indicator name in the chart legend → Add Alert. Choose from "CBO break LONG", "CBO break SHORT", "10-15 min: trend conversion candidate", "Wrong-side CBO", etc.
  7. For each trade tomorrow: follow the §7.1 / §7.2 workflow.
  8. Track outcomes: note whether the +25 mechanism call agrees with the eventual trade outcome. After 10-15 trades, you'll have a feel for how reliable the visual mechanism call is. That sample becomes useful input for whatever the eventual Stage B reclassification looks like.

11. What this build did NOT do

Links