Skip to main content

Why writing matters

Trinigence doesn’t require code - but it does require clear thinking. The way you describe your trading idea directly affects how accurately ATI can translate it into:
  • structured logic
  • deterministic rules
  • meaningful backtest results
This page teaches you how to think and write, not just what to type.
You don’t need special syntax. You need clarity.

The right mental model

A good trading idea implicitly answers five questions:
  1. What market and timeframe am I trading?
  2. When do I enter a trade?
  3. When do I exit a trade?
  4. How much risk am I taking?
  5. Are there any filters or constraints?
If your idea answers these, ATI can do the rest.

A good first example

Clear and effective:
Create an ETH/USDT strategy on the 1h timeframe.
Go long when EMA(20) crosses above EMA(50).
Exit with a take profit of 6% and a stop loss of 1%.
Why this works:
  • market and timeframe are explicit
  • entry condition is objective
  • exits are deterministic
  • risk is bounded

What you don’t need to worry about

You do not need to:
  • specify every parameter perfectly
  • worry about internal structure
  • use platform-specific syntax
  • define defaults explicitly (unless you want to)
ATI is designed to:
  • normalize phrasing
  • infer standard parameters
  • ask clarifying questions only when necessary

Common patterns you can use

Indicator-based entries

Buy when RSI is below 30.
Sell when RSI crosses above 70.

Crossover logic

Go long when MACD crosses above the signal line.

Trend confirmation

Enter trades only when the higher timeframe trend is bullish.

Breakouts and momentum

Buy breakouts when volume increases and momentum confirms.

Writing long and short logic

You can define one or both directions. Both directions in one idea:
Trade BTC/USDT on 1h.
Go long when EMA(20) crosses above EMA(50).
Go short when EMA(20) crosses below EMA(50).
Use a 5% take profit and a 1% stop loss for both.
ATI treats long and short as separate logical paths inside one strategy.

Exits: be explicit

Exits define strategy behavior more than entries. Good exits are:
  • deterministic
  • unambiguous
  • always present
Examples include:
  • fixed percentage TP / SL
  • logic-based exits
  • time-based exits
If an entry exists without a valid exit, ATI will always stop and ask for clarification.

Filters and constraints

You can optionally add constraints such as:
  • trading only on specific days
  • avoiding certain sessions
  • limiting trade frequency
  • requiring confirmation indicators
Example:
Trade only on Monday, Wednesday, Thursday, and Friday.
Filters should be added after baseline behavior is understood.

What to avoid

Vague language

Bad:
Buy when the market looks strong.
Sell on weakness.
Good:
Buy when RSI(14) is above 60.
Sell when RSI(14) crosses below 50.

Overloading the first version

Bad:
Use multiple confirmations, volatility filters, dynamic exits, and session rules.
Good:
Start with one entry condition and fixed exits.

Mixing intent and outcome

Bad:
Buy when price is about to go up.
Good:
Buy when price breaks above the previous high.

How ATI handles ambiguity

When your idea is unclear, ATI will:
  • ask a clarification question
  • propose a reasonable interpretation
  • show you what assumption it made
ATI may ask whether a “trend change” refers to a specific indicator or timeframe.
Yes. Every inferred detail can be modified or rewritten.

A simple checklist before submitting

Before you submit, ask yourself:
  • Is the market and timeframe clear?
  • Is the entry condition objective?
  • Is there a defined exit?
  • Is risk limited?
  • Would another trader understand this idea?
If yes, you’re ready.
Clear ideas lead to clean strategies.
Clean strategies lead to meaningful backtests.