Guide for the forthcoming edition. The old version 3.14 PDFs are retained as an archive, not instructions for this edition. Replacement PDFs follow completed acceptance checks.
A local workflow you control
LSCT Relay processes selected Arabic and English text signals, structured entries, stops, targets and supported management instructions. It does not supply signals or guarantee profits, interpretation or execution. Ambiguous text and conflicting emojis are held for review.
The workspace should show readable source names, timestamps and the reason for every hold or rejection. Whole-setup and total-open risk limits, exact symbols and broker checks apply before an entry.
Three advertised capacities
Core: USD 9/month,2 sources,5 symbols. Scale: USD 19/month,5 sources,25 symbols. Pro: USD 29/month,10 sources,50 symbols. Basic protection is included in all three plans. Confirm the selected plan and release availability with LSCT before paying.
A source is a channel, group or incoming personal chat within one Telegram login. Each paid file binds to one device and local customer identity. Account, source, symbol and operating settings can change while the license is valid, subject to runtime ownership and risk checks.
Monthly file or one device trial
After invoice payment, import the signed monthly file; no paid activation code or service is required. The selected billing month includes the whole first day of the next month in Dubai. New entries stop after expiry; protection of already owned positions is independent.
An available seven-day trial needs one explicit device registration and then verifies locally. Re-downloads do not restart its original window. Public trial registration is not available yet. Local identifiers cannot absolutely prevent privileged changes or Windows reinstallation.
Protection and release evidence
Choose one or two protection triggers: a supported source command, a configured favourable pip distance, or a percentage towards the profit target. Either selected trigger can protect first. Trailing waits for broker-confirmed protection and its configured start condition.
The program must remain connected with verified position ownership. Manual or foreign positions are not automatically adopted. Synthetic checks are useful evidence, but installation, reception, broker execution, protection and restart must pass controlled acceptance before publication. Read the illustrated guide for the revised setup.