1. Inputs are structured
Price feeds, market metrics, and other relevant signals are normalized into a form the bot can evaluate consistently.
How It Works
How It Works
AetherPro runs a visible operating loop: inputs are ingested, decisions are evaluated, risk rules shape what is allowed, and outcomes are either logged in test mode or sent through live execution.
Decision pipeline
From structured inputs to reviewable outcomes
The engine follows a constrained operating loop so users can understand not only what happened, but why it happened at that point in the lifecycle.
01Ingest price and market dataNormalize signals into a consistent frame the engine can evaluate.
02Evaluate signal qualityMeasure direction, momentum, and threshold posture before choosing an action.
03Apply portfolio and risk rulesConstrain the decision with allocations, leverage caps, and exit settings.
04Choose actionSelect open, hold, close, skip, or flip based on logic plus controls.
05Log or execute the resultWrite the outcome in test mode or route the signal through live execution.
2. Decisions are constrained
Strategy logic does not act in isolation. Risk rules, allocation assumptions, and operational checks shape what the bot is allowed to do.
3. Outcomes are reviewable
The system is built for inspection, whether that means reading docs, reviewing logs, or validating behavior in test mode.
Test mode before live mode
The platform should be understood in two layers. Test mode validates the decision path without live execution. Live mode adds execution and reconciliation realities once the user is ready to operate with real capital.
Learn the action model
See how the bot chooses open, hold, close, skip, or flip depending on the combination of logic and constraints.
Understand the safety envelope
Review allocations, leverage caps, and exit posture so bot outcomes make sense in context.
Review the live transition
Going live should be a reviewed launch step, not a casual toggle from an unvalidated configuration.
Follow the whole story
Read the docs, then validate in test mode
The public site should point users into a coherent trust path: understand the system, inspect the controls, then validate behavior before live execution.