Skip to main content

HX107 Rion AI Automation

HX107 teaches HyperionX's AI layer as a permissioned platform workflow. Rion can inspect chart context, help with Code Lab, control research windows, create chart drawings, and prepare or execute Hyperion Sim actions when the user enables the required settings.

AI is powerful, but it must be taught with strict boundaries.

Lesson 1: Chart-Aware Context​

Rion can work from the active chart context.

Teach users that chart context can include:

  • Symbol and timeframe.
  • Recent and visible candles.
  • Indicator metadata and parameters.
  • Strategy metadata and state.
  • Chart Trader state.
  • Selected account and connection context.
  • Open research window state where available.

The active chart matters. In multi-chart mode, users should select the chart they want Rion to inspect before asking chart-specific questions.

Lesson 2: Provider And Model Settings​

Rion AI settings include provider/model configuration and local action policy.

Teach:

  • Choose an AI provider.
  • Configure the model and endpoint only when the provider requires it.
  • Store API keys through the settings flow, not in scripts or public docs.
  • Validate license/entitlements before using desktop tools.
  • Keep model failures separate from local platform actions.

Rion should still explain local platform state when model access is unavailable, but model-generated advice should not be confused with local execution.

Lesson 3: Local Action Tools​

Rion's local action tools can support platform tasks such as:

  • Open Validator.
  • Create a Validator setup from the active chart.
  • Run Validator.
  • Cancel Validator.
  • Report Validator status.
  • Open Optimizer.
  • Create an Optimizer setup from the active chart.
  • Run Optimizer.
  • Stop Optimizer.
  • Report Optimizer status.
  • Open Code Lab.
  • List local custom scripts.
  • Compile custom scripts.
  • Report Code Lab/custom compile status.
  • Report active chart and open-window state.

Teach one running research job at a time unless the UI clearly supports parallel job tracking.

Lesson 4: Chart Drawing Automation​

Rion can create chart drawings through the chart drawing manager.

Supported training examples:

  • List drawings.
  • Clear Rion-created drawings.
  • Draw visible high and low.
  • Draw London session high and low.
  • Draw support and resistance levels.
  • Draw requested horizontal levels.

Rules:

  • Rion-created drawings should be tagged separately from manual drawings.
  • Clearing Rion drawings should not delete user-created drawings.
  • Clearing all drawings requires an explicit destructive confirmation path.
  • Drawing commands should use the active chart and visible/loaded candles.

Lesson 5: Trading Actions​

Rion trading actions are for Hyperion Sim unless the platform explicitly adds a separate live-trading permission model.

Teach the safe flow:

  1. Open a chart.
  2. Select a Hyperion Sim account.
  3. Confirm the instrument and Chart Trader state.
  4. Enable Rion order actions in Rion AI settings.
  5. Leave auto-execute off by default.
  6. Use a confirmation card for order actions.
  7. Review the local action result before claiming an order was sent.

Supported examples can include:

  • Buy market.
  • Sell market.
  • Buy bid.
  • Sell ask.
  • Cancel working orders.
  • Flatten.
  • Close position.
  • Move a stop order.
  • Change order quantity.

Rion must not say an order was placed unless the local action result confirms it.

Lesson 6: Auto-Execute Policy​

Auto-execute is an advanced setting and should be off by default.

Teach:

  • Confirmation-gated mode is the normal default.
  • Auto-execute applies only after local validation.
  • Broker/live accounts require a stronger permission model than Hyperion Sim.
  • Risk limits and audit logging must be in place before any live automation.
  • Users should be able to turn order actions off without changing AI chat provider settings.

Lesson 7: Agent Builder​

Agent Builder is for specialized assistants, not just a generic chat window.

Teach agent configuration around:

  • Name and role.
  • System instructions.
  • Allowed tools.
  • Allowed data sources.
  • Memory policy.
  • Workspace root.
  • Provider/model.
  • Trading permissions.
  • Audit log.
  • Enabled/disabled state.

Begin with read-only agents. Add script drafting, compile diagnostics, research-window control, simulation actions, and live actions in that order.

Lesson 8: Audit And Safety​

Every AI action should be explainable after the fact.

Track:

  • User command.
  • Tool selected.
  • Tool result.
  • Account and instrument context.
  • Confirmation state.
  • Error message or blocked reason.
  • Timestamp.

Completion check:

  • Rion can answer from active chart context.
  • Rion can open and report Validator/Optimizer state.
  • Rion can list and compile custom scripts when entitled.
  • Rion drawings can be cleared without touching manual drawings.
  • Hyperion Sim order actions require settings and confirmation unless auto-execute is explicitly enabled.
  • Live broker execution is not implied by chat text.