1. Define the instrument and question
Write the question before opening an indicator. For example: 'What changed in the completed hourly observations for this spot pair?' Name the venue, base asset, quote asset and timeframe. A spot pair and a perpetual futures contract are different instruments even when they share a familiar ticker.
For a hypothetical BTC/USDT study, USDT is the quote unit; a displayed amount is not automatically US dollars. Record whether you are examining a price change, volume activity or available positioning data. This prevents unrelated outputs from being treated as answers to the same question.
2. Check the observations before the chart
OHLCV means open, high, low, close and volume. Binance's official market-data documentation distinguishes candle intervals and timestamps. AIONEX checks completed candles, positive finite prices and usable history before interpreting calculations. A still-forming candle can change; it should not be compared with a frozen historical close as if both were final.
Inspect the provider, observation time and any gaps. Missing volume does not mean no trading occurred. If required observations are unavailable, narrow the question or record that the study cannot answer it. An attractive chart is not a substitute for usable inputs.
3. Give each indicator a specific role
Use separate questions for trend, momentum, volatility and volume. In the AIONEX methodology, EMA calculations describe smoothed price history; RSI describes recent relative gains and losses; ATR describes historical range. Their lookback and warm-up requirements matter. Compare compatible instruments and timeframes, and record the calculation settings.
Several indicators agreeing does not automatically provide several independent sources of evidence: they may reuse the same prices. Describe what each calculation adds. Increased volume activity alone does not establish the direction of the next price move, and a descriptive setup score is not a measured probability.
4. Compare evidence without hiding disagreement
Available external observations can add context, but their identity and freshness still matter. Distinguish a public trade-tape observation from on-chain activity, and a source-specific sentiment reading from a fact about the whole market. Do not combine different observation times into a single 'live' statement.
If price observations and another source conflict, preserve that conflict in the research record. If a source is stale, unsupported or blocked by data rights, treat it as unavailable for the relevant conclusion. In AIONEX, missing evidence must remain explicit rather than receiving a convenient neutral score.
5. Write a conclusion someone can challenge
A hypothetical note might say: 'The completed hourly price series rose over the chosen window; the momentum calculation uses the recorded settings; volume is missing, so volume confirmation is unavailable.' This statement separates observation, method and uncertainty without claiming the next candle will rise.
Add the conditions that would change the interpretation: a corrected source record, a different timeframe or new completed observations. When reviewing saved research later, compare the original question and timestamps before assuming a different score means the method improved.
A checklist for the next review
Keep this short record beside the analysis. It makes the result easier to reproduce and makes a missing input easier to spot.
- Instrument: venue, product type, base/quote identity and timeframe.
- Evidence: source, observation time, completed candles and known gaps.
- Method: indicator settings, warm-up and the question each output answers.
- Limits: missing or stale inputs, conflicting observations and untested assumptions.
- Conclusion: a bounded explanation and conditions for the next review.
Using the AIONEX Trade workspace
The Data Analyst workflow organizes this review around a selected instrument and available evidence. Source access, quality checks and plan limits apply. The current signed-in workspace is English. Read the backtesting guide next if you want to investigate historical strategy behavior; an analysis snapshot alone is not a strategy evaluation.