Getting started
Getting started: access and observation
Start with ODYSSEY Fusion, the client invite-only TradingView indicator. Check the
current access status in My Access and submit your exact
TradingView username. The owner manually grants access; a billing or account
confirmation is not proof that TradingView access is already active.
PENDING ACCESS means the grant is pending. ACTIVE ACCESS should be checked against the
actual Invite-Only Scripts list. A version label does not automatically migrate a script
grant. Begin by observing charts and learning the display before making any independent
trade decision.
Getting started
Open TradingView
Sign in to the TradingView account that matches the username submitted for access. Open
a chart and confirm the exact ticker, exchange/data feed and session. Similar symbol
names can represent different instruments.
Market data availability and TradingView plan limits depend on your account. An
indicator subscription does not include exchange data or change those limits.
Getting started
Adding ODYSSEY Fusion to TradingView
Open Indicators and find Invite-Only Scripts. Select ODYSSEY Fusion after access is
granted. If it is missing, refresh TradingView and verify your username with
Support.
Use the client Fusion version supplied to your account. Avoid stacking old copies of the
same indicator: overlapping panels and repeated markers make the chart harder to read.
Keep your other chart tools only where they add useful context.
Getting started
Fusion V1 and V2: know your version
ODYSSEY Fusion · V1
The client invite-only product: chart analysis, signals, context and readable
TradingView alerts. Private owner integrations are not part of this client offer.
ODYSSEY Fusion V2
A private owner/development version with server webhook and Telegram integration. It
is not the product purchased through the public V1 offer. No integration credentials
or private setup details are published here.
The shared chart panels are representative of the client interface. V2-branded
promotional artwork identifies the development version; it does not add V2 integrations
to V1 access. Neither version is presented as an autonomous AI trader.
Getting started
Configure a readable chart
Fusion supports chart inspection beyond 5M. Use the chart timeframe to examine price
while comparing the fixed 1D / 4H / 1H / 30M / 5M context. Current signal-event
processing uses the 5-minute host chart (5M); larger chart intervals do not turn the
host workflow into a new strategy.
Mobile Layout provides compact panels. Use Single panel for small charts when two panels
compete for space. Keep the dashboard, context panel, S/R labels and trigger candles
visible. Radar overlays can be toggled, with adjustable opacity and history. If a
distant zone compresses candles, the price-axis option Scale price chart only can keep
candles readable; that zone may then be outside the viewport.
Alerts
TradingView alerts: readable delivery
On the 5M host chart, configure the granted Fusion indicator and choose Human Readable
for human notifications. Enable Odyssey alerts and select the intended event categories
before creating the alert. Choose the indicator under Condition, then Any alert()
function call. Preserve its script-generated message.
Use a clear symbol/category name such as Odyssey Fusion — ES! — Core. For human
delivery, enable the desired app notification and leave webhook delivery off. Human
messages identify the symbol and event in readable text, without raw JSON or visible
environment-test wording. These are configuration instructions, not a claim that every
existing alert has been migrated.
In the private V2 workflow, human push and machine webhook delivery are separate. The
machine alert carries the unchanged JSON payload with push off; human alerts use push on
and webhook off. Do not add a machine alert to a client V1 setup. Avoid multiple active
alerts for the same symbol/category/delivery purpose.
Alerts
Read an event sequence
A bias or setup notification is context, not permission to enter. BUY SETUP / SELL SETUP
means an opportunity is developing; RETEST or pullback context asks you to watch the
reaction. A BUY / SELL trigger is a later event when its conditions are met.
PB BUY / PB SELL identifies the separate pullback-confirmed path. Invalidation ends the
prior setup; a model target/stop message reports a price observation. Messages are
event-driven, so silence can simply mean no eligible event occurred.
Signals
The signal lifecycle
- SETUP
- PULLBACK
- RETEST
- CONFIRMATION
- BUY / SELL
- MANAGEMENT
- TARGET / STOP
Possible sequence, not a required checklist: not every valid move includes every step.
Standard BUY / SELL does not require the separate PB confirmation sequence. A developing
setup may instead become INVALIDATED or EXPIRED.
WATCH NEXT helps you follow the current step. A setup can lose alignment or expire
before a trigger. Do not assume every example proceeds to a trade, or that a completed
sequence promises a favorable outcome.
Reading the chart
How to read the Fusion dashboard
Read direction and stage first, then Conf · LIVE and the timeframe rows. The current
compact dashboard also shows Radar, Room and VWAP / S/R. The host row identifies the
event-host timeframe; it is not a restriction on every chart view.
Conf · LIVE can change as conditions develop. The 1D / 4H and 1H / 30M / 5M rows let you
compare broader context with nearer-term alignment. Radar and Room describe the
surrounding price terrain. A supportive Radar reading can coexist with a conflicting
direction: examine both instead of treating either as a command.
Some fields are hidden by compact display choices. Entry / Stop / Target may appear as
chart levels or fuller plan details when available; missing levels do not mean a
zero-price trade.
Reading the chart
Understanding multi-timeframe analysis
1D and 4H provide broader context. 1H expresses the primary directional picture, 30M
helps assess confirmation, and 5M supports timing and event observation. Read all five
together; alignment on a single row is incomplete evidence.
The current chart timeframe controls the price view. CHART TF / TIMING and BIAS /
CONFIRM distinguish that view from the underlying multi-timeframe picture. On a larger
chart, use the context to decide which timeframe deserves inspection next; do not
interpret it as a fresh larger-timeframe BUY / SELL system.
Reading the chart
Confidence: confluence, not win probability
Timeframe strength describes directional evidence within that timeframe. Conf · LIVE
summarizes technical confluence, while the context Grade / Score adds its own view of
alignment. These displays answer related but different questions.
A confidence value of 80% does not mean an 80% probability of winning. Changing live
readings are not a guaranteed forecast. Do not use one percentage to override poor room,
unfavorable risk/reward or an invalidated setup.
Signals
Setup versus entry
BUY SETUP / SELL SETUP is a developing opportunity, not an instruction to enter
immediately. Look for alignment, the current stage, nearby S/R and enough room before
the planned objective.
The engine can show SETUP WATCH, PLAN FORMING, ACTIVE PLAN and READY alongside context
lifecycle information. A developing or active plan is not identical to a confirmed
trigger. Review the actual BUY / SELL marker and the current WATCH NEXT guidance.
Signals
Understanding pullbacks
A pullback is price moving back toward a relevant area after directional movement. Depth
and the response around that area provide context; a pullback is not automatically a
reversal or an entry.
Not every pullback creates a valid entry. A shallow, ideal or deep description is an
observation, not a promise. A move that threatens structure deserves reassessment.
Standard signals and the separate PB-confirmed path must not be conflated.
Market context
Radar zones: green support, red resistance
Green shaded areas show bullish/supportive rejection-zone context; red areas show
bearish/resistance context. Thin boundaries identify the zone area. Support and
resistance lines and price numbers provide nearby references; these are areas to
examine, not guaranteed turning points.
Show radar zone overlays controls visibility. Radar zone opacity (%) defaults to a light
10%, and Radar zone history (chart bars) defaults to 200. Individual timeframe switches
control which zones are shown; 4H and 1H are enabled by default. These presentation
choices do not alter signal calculations.
Use a wider price view to inspect a distant zone. With Scale price chart only enabled,
outlying zones can remain offscreen. A zone touch does not guarantee a bounce.
Signals
Retest versus PB confirmation
A retest is a return to an already relevant area after an earlier interaction. Inspect
the reaction and the surrounding direction rather than entering because price touched a
line.
An ordinary RETEST label or Radar retest does not, by itself, mean PB BUY / PB SELL. The
PB path follows its own ordered interaction and confirmation sequence. Wait for the
explicit PB marker when evaluating that path.
Reading the chart
How to read ODYSSEY Context
Begin with CHART TF / TIMING, then BIAS / CONFIRM. WATCH NEXT names the next relevant
observation. PLAN and GRADE / SCORE summarize the developing picture. MARKET, 5M
VOLATILITY, 5M VOLUME and SESSION - 5M provide supporting context.
Compact mode can abbreviate field names, including 5M VOL for volatility. The separate
5M VOLUME row is volume confirmation. On larger charts, the panel makes the current
chart view distinct from the 5M timing context. Use the host chart to inspect signal
lifecycle detail.
Market context
Multi-timeframe Radar and support/resistance
Radar draws context from 1D, 4H, 1H, 30M and 5M, subject to the selected display
switches. Multiple zones can overlap. A higher-timeframe zone can be far from current
price and need not force a trade on the lower timeframe.
Read named SUPPORT / RESISTANCE price labels together with the shaded regions. A green
region and a red region at different prices are normal: they describe different parts of
the price map. Keep the number of visible layers appropriate for your screen.
Getting started
Supported timeframes and observation styles
Use daily or intraday chart views for context appropriate to your own process. Fusion is
not a 5M-only chart display. Its current event workflow still uses the 5M host; changing
the visible timeframe does not change the event rules.
Do not assume the same stop distance, liquidity or session behavior across instruments
and styles. Inspect the feed, tick size, session and actual spread. The tool provides
context rather than a personalized strategy recommendation.
Risk & management
Entry, stop, target and risk/reward
Entry is a planned price reference. Stop identifies the model risk/invalidation
reference. Target is a planned objective. They are drawn when a valid plan supplies them
and are not broker orders.
R:R compares distance toward the target with distance toward the stop. A
favorable-looking ratio does not guarantee execution, account for every cost or make an
otherwise poor setup valid. Nearby resistance for a BUY, or support for a SELL, can
limit room before the target.
Review the levels on the trigger chart. Do not chase a moved price and assume the
original reference still gives the same risk/reward. Actual fills, slippage and position
size remain your responsibility.
Market context
Radar context: supportive, caution and opposing
SUPPORTIVE means the zone context supports the directional view. CAUTION asks for care
around a relevant area. OPPOSING means the nearby terrain conflicts with that view.
NEUTRAL is not a directional confirmation.
Zone interaction states such as approach, reaction, holding, retest or failed describe
what price is doing near a zone. They are observational context; none independently
overrides the signal or risk framework.
Risk & management
When NOT to trade
CHOP, conflicting multi-timeframe alignment, low confidence and poor R:R are reasons to
pause your assessment. A stale, EXPIRED or INVALIDATED setup should not be treated as a
fresh opportunity.
Avoid chasing after an extended move. Low-volume conditions can weaken confirmation, and
nearby opposing zones can reduce room. WAIT or NO TRADE context is useful information;
waiting for confirmation is a valid outcome.
These are educational considerations, not individualized financial advice. No indicator
can decide suitable risk for your circumstances.
Troubleshooting
Common mistakes
Do not confuse setup with entry, confidence with win probability, or an ordinary retest
with PB confirmation. Do not hide conflicting timeframe information or assume green
shading guarantees support will hold.
Check the exact symbol/feed, host timeframe and granted script version. Avoid duplicate
chart copies and duplicate notification purposes. On a small screen, use
compact/single-panel controls and open the chart at full size before reading precise
prices.
If messages appear stale after a script update, review the alert snapshot. If raw JSON
arrives as a human notification in V2, check that the configured human and machine
delivery paths are separated; do not change a private machine payload to fix display
text.
Troubleshooting
Why an older alert can show older behavior
TradingView saves a snapshot of the script, inputs and chart context when an alert is
created. Editing the chart or compiling a new script does not automatically update an
older running alert.
TradingView alert documentation.
Record the intended symbol, timeframe, categories, notification settings and expiry
before replacing a stale alert. Recreate it from the intended current configuration,
verify it, and avoid leaving two active copies for the same purpose. Renaming an alert
is only cosmetic.
No alert is modified by reading this guide. Private owner webhook configuration should
remain with the owner; do not paste credentials into public support messages.
Getting started
Start observing
Follow one chart without treating every label as a trade. Record the symbol/feed,
timeframe, direction, context and WATCH NEXT at the moment you observe them. Compare
later behavior without rewriting your original note.
Use the current chart walkthrough to practice. A
screenshot is a single historical view; it cannot prove that an alert arrived, an order
filled or a trade was profitable.
Getting started
Supported markets
Fusion can be inspected on TradingView instruments across futures, crypto, FX, indices
and commodities where the required price data is available. Representative chart labels
include ES!, ETHUSD, SPX, USDJPY, USOIL, GOLD and VIX. Exact tickers and feeds vary.
These are examples for chart observation, not equal-performance claims or
recommendations. Index values and volatility measures are not interchangeable with
tradeable contracts. Confirm the exchange, instrument specification, data permissions
and session before interpreting the chart.
Reading the chart
WATCH NEXT: what to observe next
WATCH NEXT is informational guidance tied to the current context. Examples include Next
1H confirmation, Next 30M close, Next 4H close, Next 1D close, 5M bullish confirmation,
5M bearish confirmation and MTF confidence / setup.
New setup means reassess for a fresh opportunity. Trade management points to the
post-trigger phase; Target / invalidation asks you to watch the model outcome
boundaries. The row does not submit a trade or force every timeframe into alignment.
Signals
BUY / SELL trigger markers
BUY and SELL are the core trigger markers, visually attached to the trigger candle
rather than an arbitrary price level. Read them with the plan, direction and current
context.
They are stronger trigger information than a developing setup label, but do not
guarantee a favorable move. A marker is not proof of an actual fill. Review entry, stop,
target and room instead of chasing a historical marker.
Signals
PB BUY / PB SELL
PB identifies the separate pullback-confirmed path. It follows a zone interaction,
retest and reaction/holding sequence with fresh confirmation. The explicit PB BUY / PB
SELL marker distinguishes it from ordinary pullback context.
Standard BUY / SELL remains a separate path; not every standard signal requires this PB
sequence. If the structure is no longer valid, do not promote an incomplete pullback
into a confirmed signal yourself.
Reading the chart
Signal grades
A+, A, B and C summarize the context score from stronger to weaker confluence. They are
assessment labels, not a broker rating or a calibrated probability of profit.
Read Grade / Score alongside Conf · LIVE, alignment and market state. The score and
confidence can differ because they summarize different aspects of context. A high grade
does not cancel the need to examine risk and conflicting information.
Market context
Market state: TREND, CHOP, WAIT, NO TRADE
TREND describes aligned directional context. CHOP warns of conflicting or unsettled
conditions. WAIT indicates that the current alignment or confidence picture is not
ready. NO TRADE flags invalid-plan context.
These labels can change with incoming data. They describe the observed conditions and
are not a promise that the next candle will behave in a particular way.
Market context
Volume confirmation
The 5M VOLUME row describes volume context, such as low volume or volume confirmed. It
supports interpretation of participation; it is not a standalone entry condition for the
reader.
Volume availability and meaning vary by feed and instrument. Do not treat a missing or
limited feed as broad-market certainty. Low volume can be a reason to wait even when a
price pattern looks appealing.
Market context
Volatility
The 5M volatility field can read LOW VOL, NORMAL VOL or HIGH VOL. In compact mode its
heading may be 5M VOL; this is distinct from the 5M VOLUME row.
Volatility describes movement scale. Use it to question whether a planned stop is tight
or wide and whether a target is stretched. It does not choose position size or guarantee
a move.
Market context
Session context
SESSION - 5M describes the configured session context, including premarket, regular or
after-hours periods where configured. Verify the indicator session timezone and the
instrument feed.
A futures, FX or crypto session may not match an equity-market schedule. A session label
is context rather than an exchange-open guarantee.
Advanced features
BOS / CHOCH
BOS means break of structure; CHOCH means change of character relative to prior
structural direction. They describe a change in the observed price structure.
These are advanced observational events, not automatic BUY / SELL instructions.
Structure markers can be hidden in the clean display while the underlying behavior
remains unchanged.
Advanced features
Liquidity sweeps
A liquidity sweep describes price reaching beyond a reference area and reclaiming it
under the observation rules. Traders use that behavior to examine rejection and failed
continuation.
A sweep does not prove who traded or that a reversal must follow. Treat it as advanced
context and compare it with direction, volume and the explicit signal framework.
Signals
Setup expiration
SETUP EXPIRED means the developing setup has reached its configured age limit without
the required trigger. It is no longer a fresh setup to act on.
Wait for a new setup. Expiration is different from a target or stop outcome after a
trigger and does not imply that an actual order was canceled.
Signals
Setup invalidation
BUY INVALIDATED / SELL INVALIDATED means the prior directional setup is no longer valid.
Stop using its old levels as if it were a fresh plan.
WATCH NEXT may return to New setup. Invalidation is a model/context event, not
confirmation that a broker has closed a position. Any actual position remains the
trader’s responsibility.
Risk & management
Target, stop and management observations
MODEL TARGET HIT and MODEL STOP HIT describe price touching the model levels.
Move-stop-to-break-even and trail-active events describe model management observations.
They do not submit, modify or close broker orders.
A bar can reach both target and stop, making intrabar ordering ambiguous. Do not infer a
profitable fill from a historical candle or notification. Costs, slippage and real
execution are outside these observations.
Alerts
Telegram in the private V2 workflow
Telegram integration belongs to the private V2 owner workflow, not the public V1
entitlement. Customer-facing messages in that workflow put the symbol first, followed by
a readable event title. They show timeframe, direction and applicable grade/confidence,
plan levels or WATCH NEXT.
Messages omit raw JSON, internal event IDs and visible test-environment wording.
Structure observations do not acquire entry/stop/target fields when no plan applies.
Delivery still depends on enabled events and notification availability.
The intended split is one readable human push, one machine webhook event and one
Telegram message per eligible logical event. Duplicate machine events are filtered by
the server. This guide does not assert that every saved alert is migrated or that every
natural event has been observed end to end.
Troubleshooting
Frequently asked questions
Does higher confidence guarantee a win? No. Does every BUY require a pullback? No; the
standard path and PB path are distinct. Can I inspect a daily chart? Yes; the current
event host remains 5M.
Does client access include private Telegram integrations? No. Can a marker place a
trade? No. Why is a zone missing? Check overlay/timeframe switches, the history limit
and the visible price range. Why is an alert old? Check its saved snapshot.
Risk & management
Risk disclaimer
Odyssey Fusion is a technical-analysis and decision-support indicator for educational
and informational use, not financial advice. Signals do not guarantee profit. Users
remain responsible for trade decisions, position sizing and risk. Model observations are
not broker fills. Historical examples do not guarantee future results. Customer
execution is manual; Odyssey does not place trades. Trading involves risk.