> ## Documentation Index
> Fetch the complete documentation index at: https://docs.trinigence.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Supported Markets & Limitations

> What Trinigence supports today, what’s limited, and how to avoid common surprises.

## Why this page matters

Trinigence is built to deliver fast, consistent strategy creation and backtesting - but your experience depends on **market coverage**, **historical data availability**, and **current platform limits**.

This page helps you set the right expectations before you spend time iterating.

<Info>
  Trinigence focuses on **strategy creation + backtesting** first. Execution support depends on your environment and enabled integrations.
</Info>

***

## What’s supported (high-level)

### Asset class focus

* **Crypto markets** (primary focus in the current phase)

### Strategy types

* Long-only, short-only, or combined long/short strategies
* Indicator-based conditions (TA-Lib style)
* Fixed risk rules (TP/SL in %)
* Filters such as trading schedule (days) and basic time logic (where supported)

<CardGroup cols={2}>
  <Card title="How Trinigence works" icon="wand-magic-sparkles" href="/getting-started/how-trinigence-works">
    See the end-to-end flow from idea to backtest.
  </Card>

  <Card title="Strategy structure overview" icon="diagram-project" href="/strategy-structure/overview">
    Learn how entries, exits, risk and schedules fit together.
  </Card>
</CardGroup>

***

## Markets & instruments

### Crypto pairs

Trinigence supports common crypto symbols such as:

* **BTC/USDT**, **ETH/USDT**, and other major pairs (availability depends on the exchange/data source).

<Info>
  If a specific pair is not available, ATI will typically suggest the closest supported symbol or ask you to pick an alternative.
</Info>

### Spot vs Futures

* Futures-style logic (**long/short**) is supported at the strategy level.
* Instrument availability depends on data coverage (spot/futures) in your current environment.

<Warning>
  If you’re testing a futures strategy, verify the symbol and data source are aligned (spot vs perpetual can behave differently).
</Warning>

***

## Timeframes

Trinigence supports multi-timeframe backtesting where data is available.

Commonly used:

* **15m**, **1h**, **4h**, **1D**

<AccordionGroup>
  <Accordion title="Why a timeframe might not work">
    Timeframe support depends on historical data coverage for that symbol and source.
    If the required timeframe is unavailable, ATI may suggest a nearby timeframe (e.g., 30m instead of 15m) or ask you to choose.
  </Accordion>
</AccordionGroup>

***

## Backtest data coverage

Backtesting requires historical candles (OHLCV). Coverage depends on:

* symbol
* timeframe
* data source (exchange/provider)
* start date you request

<Info>
  If you request a backtest range that exceeds available data, Trinigence will backtest the maximum available range and surface the effective start date in results (or ask you to adjust).
</Info>

<Card title="How backtesting works" icon="chart-line" href="/backtesting/how-backtesting-works" horizontal>
  Learn what’s included in Trinigence backtests and how results are computed.
</Card>

***

## Indicators

Trinigence supports:

* **TA-Lib indicator set** (broad coverage)
* **Custom indicators** (Trinigence-specific additions)

You can define:

* indicator parameters (e.g., MACD(12,26,9), RSI(14), Supertrend(10,3))
* indicator-based conditions (crosses, thresholds, trend changes, etc.)

<Warning>
  Indicator availability can differ by environment/version. If you use a niche indicator, ATI may propose an alternative or request a substitution.
</Warning>

<CardGroup cols={2}>
  <Card title="Indicators & Logic overview" icon="wave-square" href="/indicators-logic/overview">
    Understand supported condition types (cross, trend change, thresholds).
  </Card>

  <Card title="Writing better trading ideas" icon="pen-fancy" href="/writing-ideas/how-to-write-a-trading-idea">
    Learn how to express indicators and logic clearly.
  </Card>
</CardGroup>

***

## Execution (automation) limitations

Trinigence can generate **execution-ready logic**, but actual live trading depends on:

* enabled integrations
* your account permissions
* connection status
* execution rules supported in your environment

<Info>
  If you’re here primarily for backtesting and strategy design, you can ignore execution details and focus on iteration.
</Info>

***

## Known limitations (today)

The most common limitations in the current phase:

* **Market scope**: primarily crypto-focused during early rollout
* **Data availability**: some symbols/timeframes may have shorter historical ranges
* **Complex logic**: ultra-complex multi-layer rules may require clarification prompts
* **Indicator edge cases**: some indicators behave differently across libraries/providers
* **Execution parity**: not every backtest feature automatically maps 1:1 to live execution in all environments

<AccordionGroup>
  <Accordion title="Why Trinigence asks clarifying questions">
    Natural language can be ambiguous (e.g., “trend reversal”, “breakout confirmation”).
    ATI asks questions to ensure your strategy is deterministic and backtestable.
  </Accordion>

  <Accordion title="Why my strategy has fewer trades than expected">
    Common causes include timeframe mismatch, strict entry conditions, schedule filters, or insufficient data range.
    Check the requested backtest period, symbol, and timeframe first.
  </Accordion>
</AccordionGroup>

***

## Best practices to avoid surprises

* Start with **major pairs** (BTC/USDT, ETH/USDT) on **1h / 4h / 1D**
* Keep the first version of a strategy **simple**
* Add complexity only after you confirm baseline behavior
* Always verify:
  * symbol
  * timeframe
  * backtest start date
  * TP/SL definitions

<Card title="Your first strategy in 5 minutes" icon="rocket" href="/getting-started/first-strategy-5-minutes" horizontal>
  Follow the fastest path from idea to backtest.
</Card>

***

## Troubleshooting

If something doesn’t look right, start here:

<CardGroup cols={2}>
  <Card title="FAQ & Troubleshooting" icon="life-ring" href="/faq/common-questions">
    Common issues: missing trades, unexpected results, indicator mismatch.
  </Card>

  <Card title="Backtest pitfalls" icon="triangle-exclamation" href="/backtesting/common-pitfalls">
    The most common reasons strategies behave differently than expected.
  </Card>
</CardGroup>

***

## Need help?

If you’re blocked by a missing market, timeframe, or indicator, contact support and include:

* the exact strategy text you used
* symbol + timeframe
* requested backtest range
* what you expected vs what happened

<Card title="Contact support" icon="life-ring" href="mailto:info@trinigence.com" horizontal>
  Email us and we’ll help you validate the setup.
</Card>