Trading Engines
An engine (strategy type) is how a book decides when to enter, exit, and manage risk. Chatito has several families across markets.
This page is a public catalog: what each family is for, not secret recipes. We do not publish exact thresholds, timers, or templates that would hand away research edge.
Origin vs Engine
| Concept | Meaning |
|---|---|
| Origin | Where the idea came from (manual, AI Lab, wizard, Factory, starter catalog) |
| Engine | How the book actually trades |
UI may show both: for example AI Lab origin with a buy-over-time engine underneath.
CEX / DEX Families
Everyday automation families on crypto terminals:
| Family | In plain English |
|---|---|
| DCA in | Build a position over time with rules (size, spacing, conditions) |
| DCA out | Reduce or exit over time with rules |
| Limit | Limit-style entries/exits under constraints |
| Lab / builder graph | Advanced design tools; Accept → practice prefers a concrete runnable type (DCA/limit style), not an empty design shell |
Invent and Factory should land working practice strategies you can leave on, not decorative drafts.
Other Venue Families (When Open)
When prediction-market and liquidity-pool terminals open for users, their engine families will be listed here. Until then we only document the CEX / DEX families above so Docs match what people can actually run.
Shared Controls (All Engines)
Whatever the engine, books share platform ideas:
- Practice and live ledgers (which numbers you look at)
- Pause / kill / attention lifecycle
- Capacity (how many books your plan allows)
- Human live arming (never “scientist auto-live”)
- Ownership isolation (you see your books)
What We Will Not Document Publicly
- Exact entry/exit numeric bands from research arms
- Force timers, fee tables, or internal A/B arm IDs
- Protected mining template identifiers
- Anything that is a copy-paste “print money” playbook
To use the UI: CEX / DEX and in-app Help.
For research process: Edge and Research.