RX5 Bots and Indicators
Review the planned RX5 runtime, permissions and release scope. Runnable bot and indicator examples require a published SDK and tested client build.
RX5 Runtime and Release Scope
RX5 bots and indicators are planned. A released workflow needs a named runtime build, supported client and tested permission scope.
Swipe horizontally to view all columns.
| Workflow | Scope | Build evidence |
|---|---|---|
| Indicator calculation and display | Read permitted data and produce chart calculations or signals. | Supported runtime/client build and original fixture: not yet published. |
| Bot order execution | Submit authorized trading intent within broker and account controls. | Runtime build, supported order actions and permission tests: not yet published. |
| Hosted monitoring and control | Observe an approved server instance and request start/stop actions from eligible clients. | Client/runtime support and disconnect tests: to be confirmed. |
Trade Smarter with Automation & Insights.
RX5 bots and indicators are planned. The workflow distinguishes data calculation, trading authorization and hosted controls; it does not establish available tools or promise improved returns.
Automate Strategies
Plan approved trading rules with explicit order permissions, failure handling and supervision.
Precision Indicators
Plan permitted data calculations and chart signals; an indicator does not itself authorize an order.
High-Speed Execution
Execution depends on the tested runtime, broker validation and market conditions. No latency result is established here.
Data-Driven Decisions
Review data quality and stated assumptions. AI capability and improved trading outcomes are not verified for the proposed runtime.
Trading Robots (Expert Advisors)
Planned bots would submit authorized trading intent from defined strategy rules. Runtime compatibility, risk checks and stop outcomes must be verified before use.
Fully Automated Trading
An approved hosted bot would follow configured rules within broker permissions. Availability, restarts and supervision depend on the tested plan.
Rule-Based Decisions
Declare the strategy inputs and decision rules; any model dependency needs separate compatibility and validation evidence.
High-Speed Execution
Supported order actions and measured execution times must be documented for the runtime and broker environment.
Custom Strategy Integration
Use authorized strategy source and supported SDK interfaces. No verified library or proven performance record is published here.
Risk Management Controls
Confirm supported position sizing and order controls with the broker. Stops cannot guarantee execution price or eliminate loss.
Key Benefits
Smart Trading Indicators
Planned indicators calculate or display signals within permitted data scope. Original examples and supported client versions are not yet published.
Real-Time Market Analysis
Calculate against entitled data with documented update timing and missing-data behavior for the supported runtime.
Trend & Signal Detection
Express a defined signal rule and publish original fixtures; a signal does not predict a profitable trade.
Customizable Parameters
Record supported parameters and validate their range against the named indicator and runtime versions.
Multi-Timeframe Support
Timeframe and series support depend on the documented SDK and client. Confirm warm-up and alignment behavior.
Key Benefits
Bot and Indicator Permissions
An indicator calculation does not itself authorize a trade. The broker's permitted scope determines what an algorithm instance can read and do.
Swipe horizontally to view all columns.
| Capability | Indicator | Trading bot |
|---|---|---|
| Read market data | Only entitled instruments and history. | Only entitled instruments and history. |
| Calculate or display | Produce chart values, marks or a signal within the client/runtime scope. | May use calculations to form a decision; display support is separately defined. |
| Read account state | Requires explicit access when an indicator needs account information. | Requires permission for the specific account and data scope. |
| Submit or change orders | No trading permission follows from displaying a signal. | Requires explicit trading rights plus server-side account, instrument and risk validation. |
| Files, network and dependencies | Availability must be defined by the runtime policy. | Availability must be defined by the runtime policy; external access is not assumed. |
Declare what a package may read, display and trade
The proposed package review treats an indicator, a trading strategy and its client display as separate capabilities.
Swipe horizontally to view all columns.
| Area | Proposed requirement | Release evidence |
|---|---|---|
| Package identity | Declare strategy/indicator type, source and build hashes, SDK/API version, dependency inventory and licence. | Reviewed signed artifact and compatible runtime version. |
| Indicator display | Distinguish chart-only calculations from server indicators used by strategies. Clients receive typed plots/values through a documented protocol. | Supported plot schema and tested client display; no arbitrary downloaded native or UI code. |
| Trading scope | Grant order actions only for the named tenant, account, symbols and approved risk limits. A displayed signal does not grant trading permission. | Allowed and denied operations, including broker risk rejection. |
| External access | Deny arbitrary files, network, processes and environment access by default. An approved external-data capability needs domain, size, rate and timeout limits. | Isolation, exhaustion and permission-denial results for the exact build. |
| Revocation | Block new activation of a revoked version and follow a disclosed policy for existing instances, trader notice and open positions. | A tested revocation and controlled-stop scenario. |
Manual Trading vs Automated Trading.
| Aspect | Manual Trading | RTX5 Robots & Indicators |
|---|---|---|
| Orders | Human decision | Authorized bot action |
| Rules | Human interpretation | Configured logic |
| Validation | Review decisions | Review code and fixtures |
| Limits | Account controls | Account and runtime controls |
Evaluate Your Trading Style.
Scalping
A proposed short-horizon strategy needs realistic spread, fee, latency and fill assumptions; broker support must be confirmed.
Day Trading
Define session cutoffs and explicitly test position handling; closing every position cannot be assumed from a schedule.
Swing Trading
Evaluate multi-day rules with declared rollover, data and risk assumptions rather than an implied optimal entry.
Long-Term Investing
Test position-based rules with realistic costs and exposure limits; rebalancing and returns are not guaranteed.
Planned Integration.
Confirm the published integration scope and test the chosen artifact on desktop before requesting an approved hosted instance.
Platform Compatible
Compatibility depends on the exact SDK, artifact and client/runtime versions; setup requirements must be published.
Reviewed Setup
Review source rights, dependencies, configuration and permissions before approving an artifact.
Flexible Configuration
Use only the documented parameter ranges, timeframes and entitled instruments for the supported build.
Cross-Instrument Support
Eligible instruments and account modes depend on the broker and runtime contract; universal asset support is not assumed.
Validation and Security Requirements.
Build-Level Validation
A released example needs original source, fixtures and results from a named build. Those records are not yet published.
Regular Updates
Updates need versioned compatibility notes and retesting; no update schedule or perpetual compatibility is promised.
Measured Behavior
Record behavior under data gaps, volatile conditions and resource limits. No performance guarantee is established here.
Secure Execution
Verify authorization, isolation, transport and denial outcomes for the actual runtime before enabling order actions.
Monitor Resources and Define Stop Behavior
Agree the operational limits before enabling a strategy. Numeric allowances and tested stop behavior will be documented for the available runtime.
Swipe horizontally to view all columns.
| Control | Required explanation |
|---|---|
| Resource quota | CPU allowance, memory, instance count, log/storage retention and behavior when a limit is reached. Numeric quotas: not yet published. |
| Monitoring | Active artifact/version, start time, running/stopped/error state, latest heartbeat, resource use and recent order activity. |
| Stop new strategy actions | Identify who can stop the instance, when the request takes effect and how the client confirms the resulting state. |
| Working orders and positions | State separately whether stopping the instance cancels pending orders or closes positions. Neither outcome should be assumed from the word 'stop'. |
| Failure and restart | Explain errors, disconnect behavior, restart authorization and how existing account state is reconciled before new actions. |
Upgrade Your Trading Strategy.
Ask about the planned runtime, supported examples and approval requirements before relying on an RX5 workflow.