> ## 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.

# Optional vs Required Components

> Which parts of a Trinigence strategy are mandatory, which are optional, and why that matters.

## Why this distinction matters

Not every part of a strategy is equal.

Some components are **required** for a strategy to exist.\
Others are **optional**, but can dramatically change behavior and results.

Understanding this distinction helps you:

* write clearer trading ideas
* avoid invalid strategies
* know when ATI will ask questions vs infer safely

***

## Required components

A strategy **cannot be created or backtested** without these components.

### 1. Market

Every strategy must specify **what is being traded**.

Example:

```text theme={null}
Trade BTC/USDT.
```

Without a market:

* price data cannot be loaded
* indicators cannot be calculated
* strategy is invalid

***

### 2. Timeframe

Every strategy must specify **when logic is evaluated**.

Example:

```text theme={null}
Use the 1h timeframe.
```

Without a timeframe:

* candle resolution is unknown
* signals cannot be evaluated

***

### 3. Entry logic

A strategy must define **at least one entry condition**.

Example:

```text theme={null}
Go long when RSI(14) crosses above 50.
```

Without entry logic:

* no trades can ever open
* backtesting is impossible

***

### 4. Exit logic

Every entry must have a corresponding exit.

Example:

```text theme={null}
Exit with a 5% take profit and a 1% stop loss.
```

<Warning>
  A strategy without exit logic is considered invalid.
</Warning>

***

## Optional components

Optional components are **not required**, but strongly recommended.

They refine behavior rather than define existence.

***

### Direction (long / short)

If not explicitly stated:

* ATI may infer direction
* or default to long-only

Explicit direction is always safer.

***

### Risk management extensions

Beyond basic stop loss:

* position sizing
* exposure limits
* trade limits

These improve robustness but are not strictly required.

***

### Filters & schedules

Examples:

* trading days
* sessions
* volatility filters
* higher timeframe filters

If omitted:

* strategy trades continuously
* entry logic is always eligible

***

### Multi-timeframe logic

Higher timeframe filters or confirmations are optional.

They:

* reduce noise
* add context
* increase complexity

***

## What ATI fills automatically

ATI can safely infer some missing details.

Typical examples:

* reasonable default timeframe
* implied direction
* conservative risk assumptions

However, ATI will **never guess**:

* exits
* market symbol
* contradictory logic

<Card title="What Trinigence fills automatically" icon="robot" href="/writing-ideas/what-trinigence-fills-automatically" horizontal>
  See exactly what can and cannot be inferred.
</Card>

***

## When ATI asks for clarification

ATI will stop and ask when:

* required components are missing
* logic is ambiguous
* multiple interpretations exist
* exits are undefined

This prevents silent failures and misleading results.

***

## Common misunderstandings

<AccordionGroup>
  <Accordion title="I thought filters were required">
    Filters refine behavior but are not mandatory for a valid strategy.
  </Accordion>

  <Accordion title="I assumed risk management was optional">
    Basic risk control is mandatory. Advanced risk rules are optional.
  </Accordion>

  <Accordion title="ATI should guess missing exits">
    Exits define outcomes and are never guessed.
  </Accordion>
</AccordionGroup>

***

## Best practices

* Always define required components explicitly
* Add optional components gradually
* Treat exits and risk as first-class logic
* Use ATI questions as guidance, not friction

<Card title="Strategy structure overview" icon="diagram-project" href="/strategy-structure/overview" horizontal>
  See how all components fit together.
</Card>

***

## What to read next

<CardGroup cols={2}>
  <Card title="Writing trading ideas" icon="pen-fancy" href="/writing-ideas/how-to-write-a-trading-idea">
    Write clearer ideas with fewer assumptions.
  </Card>

  <Card title="Common missing details" icon="triangle-exclamation" href="/writing-ideas/common-missing-details">
    See what users forget most often.
  </Card>

  <Card title="Strategy overview" icon="diagram-project" href="/strategy-structure/overview">
    Return to the big picture.
  </Card>

  <Card title="Backtesting metrics" icon="chart-line" href="/backtesting/metrics-overview">
    See how structure affects results.
  </Card>
</CardGroup>

<Note>
  Required components define *existence*.\
  Optional components define *quality*.
</Note>
