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

# What Trinigence Fills Automatically

> Understand which strategy details Trinigence infers for you - and when it asks for clarification.

## Why this matters

When you write a trading idea, you rarely specify everything.

That’s normal.

Trinigence is designed to:

* remove unnecessary friction
* avoid invalid or ambiguous strategies
* keep you focused on logic, not boilerplate

This page explains what ATI fills automatically, and when it won’t.

<Info>
  Nothing is silently guessed in a way that changes strategy behavior without visibility.
</Info>

***

## What Trinigence fills automatically

### 1. Missing but required components

A strategy must be deterministic to be backtested.

If your idea includes:

* an entry but no exit
* a direction but no risk rule
* logic without a timeframe

ATI ensures the strategy is complete before running a backtest.

Examples of what may be auto-filled:

* default take profit and stop loss (clearly surfaced)
* standard indicator parameters
* execution assumptions required for backtesting

***

### 2. Standard indicator parameters

If you mention an indicator without parameters, ATI applies commonly accepted defaults.

Examples:

* RSI → RSI(14)
* MACD → MACD(12, 26, 9)
* EMA → context-aware defaults

<Note>
  All inferred parameters are visible and editable.
</Note>

***

### 3. Trade direction assumptions

If direction is implied but not explicit:

```text theme={null}
Trade pullbacks using RSI oversold levels.
```

ATI may infer long-only logic if phrasing suggests buying dips.

If intent is unclear, ATI will ask before proceeding.

***

### 4. Exit symmetry

When exits are defined for one direction but not the other, ATI may:

* mirror exits for both long and short
* or ask whether exits should differ

Example:

```text theme={null}
Go long when EMA(20) crosses above EMA(50).
Use a 6% take profit and 1% stop loss.
```

ATI assumes exits apply to all directions unless specified otherwise.

***

### 5. Backtest boundaries

If you don’t specify:

* backtest start date
* trading sessions or days

ATI applies:

* the maximum available historical range
* default trade-anytime behavior

These assumptions are surfaced in backtest results.

***

## What Trinigence does NOT auto-fill

Some things are too important to guess.

ATI will always ask for clarification if:

* no exit is defined at all
* risk is unbounded
* logic is contradictory
* language is non-deterministic

Examples ATI will not guess:

* “exit when it feels overextended”
* “trade during high volatility”
* “enter on strong trend”

***

## Assumptions vs clarifications

<Columns cols={2}>
  <Card title="Assumptions" icon="check">
    Safe defaults applied when industry standards exist and behavior is predictable.
  </Card>

  <Card title="Clarifications" icon="question">
    Follow-up questions asked when behavior would materially change based on interpretation.
  </Card>
</Columns>

<AccordionGroup>
  <Accordion title="Can I override defaults later?">
    Yes. Every inferred value can be modified through iteration.
  </Accordion>

  <Accordion title="Will ATI always ask before changing behavior?">
    If a choice affects trade outcomes in a meaningful way, ATI asks instead of guessing.
  </Accordion>
</AccordionGroup>

***

## Practical examples

### Minimal idea

```text theme={null}
Trade ETH using RSI oversold conditions.
```

ATI fills:

* timeframe
* RSI parameters
* long direction
* default exits
* backtest range

### Partial structure

```text theme={null}
Trade BTC on 1h.
Go long when MACD crosses up.
```

ATI fills:

* MACD parameters
* exits
* risk limits

***

## Best practices

* Let ATI fill boilerplate on the first pass
* Review inferred details before judging results
* Make assumptions explicit only when needed
* Iterate instead of rewriting everything

<Card title="Natural language vs structured input" icon="language" href="/writing-ideas/natural-language-vs-structured" horizontal>
  Learn when to stay natural and when to be explicit.
</Card>

***

## What to read next

<CardGroup cols={2}>
  <Card title="Common missing details" icon="triangle-exclamation" href="/writing-ideas/common-missing-details">
    The most frequent gaps in trading ideas.
  </Card>

  <Card title="How to write a trading idea" icon="pen-fancy" href="/writing-ideas/how-to-write-a-trading-idea">
    Learn how to express intent clearly.
  </Card>

  <Card title="Strategy structure overview" icon="diagram-project" href="/strategy-structure/overview">
    See how filled details map to strategy components.
  </Card>

  <Card title="FAQ & troubleshooting" icon="life-ring" href="/faq/common-questions">
    Answers to common questions about AI assumptions.
  </Card>
</CardGroup>

<Note>
  ATI removes friction - not responsibility.
  You stay in control of strategy behavior.
</Note>
