Syntalium Wiki

How to Read LONG and SHORT Setups

TL;DR

LONG SETUP and SHORT SETUP are only displayed when a real published signal exists. Check entry zone, stop, freshness, expiry, and SNAP before making any decision. Do not chase price after it leaves the entry range.

Risk notice: General market intelligence, not personalized investment advice. You remain responsible for any trading or investment decision.

What LONG and SHORT mean

On Syntalium, LONG SETUP and SHORT SETUP are recorded setup state labels. They indicate that the engine has published a real signal for the asset and timeframe, and that signal has a direction.

These labels are not predictions or recommendations. They are structured observations — a record of what the system determined at a specific point in time, based on completed market data. Whether that observation is relevant to your situation is a decision only you can make.

LONG SETUP: A real published signal exists with direction long. The entry zone, stop loss, and targets are displayed. Does not mean the trade will succeed.
SHORT SETUP: A real published signal exists with direction short. Same plan fields apply. Does not guarantee any outcome.
NO PUBLISHED SETUP: No signal currently exists for this asset and timeframe. All plan fields are withheld.

When a setup is shown

A setup is displayed only when all of the following conditions are true:

01A real signal has been published by the engine for this asset and timeframe.
02The signal has a defined direction — LONG or SHORT.
03The signals endpoint is available (not returning 404 or 503).
04The setup has not expired or been invalidated.

When the signals endpoint is unavailable, the platform shows “Signals endpoint unavailable” and displays NO PUBLISHED SETUP — not an invented direction. Entry, stop, and target fields remain withheld.

If you see NO PUBLISHED SETUP, there is genuinely no active published signal. Check back later or review the freshness status to understand why.

Reading the plan fields

When a real setup is active, the following fields are displayed in the Published Trade Plan section:

Entry zone: The price range within which the setup was published. This is where the system recorded a valid entry context — not a guaranteed fill price.
Stop loss: The price level at which the setup's risk assumption is broken. Exceeding this level means the trade scenario is no longer valid.
Targets: One or more take-profit levels recorded with the signal. These are plan fields, not guaranteed exit prices.
Leverage range: If published, the leverage band the signal was recorded under. Use this as context for your own sizing decision — not a recommendation.
Published at: When the signal was originally published. Compare this to the current time to understand how old the setup is.

These fields describe the plan as it was recorded at publication time. They are not live-updated price targets. If the market has moved significantly since publication, the setup may already be expired or invalidated.

Checking freshness and SNAP

Before relying on any published setup, check two additional things: the data freshness and the SNAP proof.

Freshness: FRESH means the underlying data is within the expected threshold. STALE means it is older than expected — the setup may not reflect current conditions.
SNAP ID: A SHA-256 hash of the canonical payload. Submit it to /verify to confirm that the archived record has not been altered since publication.

01Find the SNAP ID in the Proof & Provenance section or Decision Record.
02Navigate to /verify and paste the SNAP ID.
03Submit and check the result: VERIFIED means the payload is intact.
04MISMATCH or PAYLOAD_MISSING means the record cannot be confirmed — treat with caution.

Verification proves that the record was not altered. It does not prove that a trade at the entry zone would have been profitable.

What not to do

This section covers common errors that cause users to break otherwise structured setups.

Do not chase: If price has already moved significantly past the entry zone, the setup is no longer at the conditions it was recorded under. Chasing is entering after the conditions have changed.
Do not ignore expiry: A setup published hours or days ago may have an expired validity window. Check the published-at timestamp and any expiry field.
Do not skip the stop: Using an entry from a published setup but no stop loss removes the key risk control the plan was built around.
Do not use outdated data: A STALE freshness label means the underlying data may not reflect the current market. Do not treat a stale setup as a current instruction.
Do not treat direction as advice: LONG SETUP means the engine recorded a long-direction signal. It does not mean the market will go up, and it is not personalized advice for your account.

Never enter a trade based on a setup whose freshness is STALE, whose expiry has passed, or which shows NO PUBLISHED SETUP. These states exist to protect you from acting on outdated or unavailable information.