Automated trading with TRINITY (ARES)
What happens when automated trading is on—schedules, safeguards, and how it relates to Hunt, Cash Hunt, and your portfolio settings.
What this is (in plain language)
ARES (Automated Rebalancing and Execution Service) is TRINITY’s background process for portfolios where you have turned on automated trading. When it is enabled for a portfolio, a scheduled job can:
- Find portfolios you have flagged for automation in portfolio settings.
- Pull suggestions from the same Hunt and Cash Hunt style flows you can run yourself in IRIS (backed by ARTEMIS).
- Validate proposed actions against your risk settings and the saved portfolio record (position limits, risk caps, available cash, and related controls—same facts IRIS shows you).
- Route execution through the same portfolio execution path your environment uses for manual trades—so behavior should mirror discretionary flows, not a separate “hidden broker.” Automation does not bypass an empty cash line or a cap you configured.
Nothing here is investment advice. Automated trading amplifies speed and consistency; it does not remove market risk, model error, or the need for oversight.
When it runs
In the standard product setup, automation is designed for weekdays (not weekends). Exact clock time and time zone depend on your workspace—check in IRIS if your build shows a schedule, or ask support.
If today is not an allowed trading day for your agent, the automation stands down for that run. The decision log should say so in plain language—see Reading automation decision logs.
What you should set before enabling automation
Work through these before flipping automated trading on:
- Risk management fundamentals — max risk per trade, portfolio risk, position count, and size caps you actually want enforced.
- Portfolio basics — cash level, positions you are willing to change, and whether you are in paper / simulation vs live-capable environments (see Disclosures).
- Hunt, Cash Hunt, and optimization — so you understand what “replacement” vs “deploy cash” style suggestions mean when they arrive from automation.
- Your portfolio in TRINITY — how cash, closed lines, and settings in the portfolio record gate every run, automatic or manual.
How automation differs from clicking “Hunt” yourself
| Aspect | You in IRIS | ARES (when enabled) |
|---|---|---|
| Trigger | You open the portfolio and run a flow | Scheduled job for flagged portfolios |
| Recommendations | ARTEMIS Hunt / Cash Hunt (conceptually the same family of ideas) | Same upstream idea sources, selected and validated in code |
| Execution | You confirm in supported trade UIs | Executes only after internal checks pass; still subject to risk validation and environment rules |
| Oversight | Immediate | Review the decision log or trading-agents feed in IRIS (short, human-readable lines) — Reading automation decision logs |
Caps and “why nothing traded today”
Operational configs can impose per-run limits (for example, a maximum number of replacement trades and cash purchases per day). If a cap is zero for a category, that part of the run may be skipped on purpose—not because the market is closed.
If automation seems idle, check:
- Is automated trading still enabled on the portfolio?
- Are risk settings so tight that every suggestion fails validation?
- Are daily caps set to zero for swaps or cash deployment?
- Did the run fall on a non-trading day for the agent?
Your FAQ & troubleshooting and support channel can help map symptoms to logs.
Audit trail
ARES records decision log entries with short, plain-language messages so you can see what the system considered and why it acted or skipped. Walk the feed line-by-line with Reading automation decision logs; use Help in IRIS if a line still does not match what you see in the portfolio.
Related reading
Progress is saved in this browser. Cloud sync requires PUBLIC_IRIS_API_BASE, IRIS CORS allowlist,
and window.__trinityIdToken.