Your portfolio in TRINITY
What IRIS remembers about your book—cash, positions, settings, alerts, and performance vs the market—in plain language.
What the app remembers
When you use Portfolios in IRIS (/portfolio, /new-portfolio, /portfolio/<id>), the product keeps a single coherent record of each portfolio: positions, cash, risk settings, portfolio settings (notifications, optional automation), and data used for performance and benchmark views when they appear.
You do not need to know backend names to use the product. Engineers call the portfolio service ATLAS; in this guide we stay with what you see in IRIS.
Demo portfolios (sometimes offered in onboarding) are sample books—real-shaped data so you can learn the screens. They are labeled as demo and are not a substitute for your own investment policy. See Portfolio basics.
Cash and buying power
TRINITY tracks remaining capital (cash available for typical long adds) separately from allocated capital (dollars already in open positions). Hunt, Cash Hunt, and optimization all respect the envelope you defined.
- If the app blocks a new buy or add, a common reason is not enough available cash for the size you asked for. TRINITY does not model margin or negative cash in normal configurations—plan cash the way you would in a cash account.
- Total capital (when shown) is the model budget for the portfolio, not necessarily your real-world brokerage balance unless you aligned them on purpose.
For how deployable cash interacts with Cash Hunt and buffers, see Hunt, Cash Hunt, and optimization.
Closing vs holding
Open positions drive unrealized P/L, many alerts, and most performance rollups. Closed lines can show realized gain (profit or loss locked in at exit). The app uses explicit rules so list and detail views stay aligned—if something still looks wrong after a refresh, note portfolio id and time for support.
Closed history matters for audit and tax planning in your real life; TRINITY is a tool, not your broker of record—see Disclosures.
Risk and sizing settings
From portfolio screens you set caps such as max risk per trade, max portfolio risk, max position size, and max number of positions. You also choose allocation strategy ideas (equal weight, confidence-weighted, stage-weighted, Kelly-style paths, and half-Kelly when offered).
These settings bind what Hunt, Cash Hunt, and DIONYSUS can suggest—they are guardrails, not guarantees about future losses. Read Risk management and Allocation strategies. Nothing here is personalized investment advice.
Notifications and automation
Portfolio settings in IRIS can turn email on or off for that book—for example daily portfolio summaries, optional Symbols checker digest (weekday, market-wide), ARTEMIS daily trade picks, and (where shown) ARES trade notifications. Account-level notification preferences may also apply for some categories; both layers can matter. See Emails and alerts in TRINITY for a full map in plain language.
Automated trading (ARES) is a separate, explicit choice: when on, scheduled flows may act after recommendations and risk checks. That is not the same as running Hunt once by hand.
- If automation is available and enabled, read Automated trading with TRINITY and Reading automation decision logs; use the same guide for automation-related email expectations.
- Risk caps and available cash in your portfolio record still gate what automation may do—see logs for “risk blocked” lines.
Understanding portfolio alerts
Alerts are a heads-up tied to targets, stops, signals, or stage context—not a promise that a trade will execute. Urgent vs low priority is a severity hint for triage. Typical types you may see:
| Alert idea (plain language) | What it is hinting at | What to do |
|---|---|---|
| Approaching target | Price is within a set band of your target level. | Decide whether to take profit, raise the target, or wait—confirm on the symbol page and check staleness. |
| Target reached | Price has met or crossed the target threshold used by the alert logic. | Same as above—you decide execution unless automation is on and allowed to act. |
| Approaching stop | Price is nearing a stop you associated with the position. | Re-read risk; confirm the stop still matches your plan. |
| Stop triggered | Stop condition fired in the product’s alert sense. | Not always the same as a broker stop order—verify how you actually exit in your account. |
| Sell / hold signal | ATHENA’s five-letter signal moved into a defensive or neutral posture the alert cares about. | Open the symbol page; signals are not orders by themselves. |
| Stage 3 / Stage 4 style context | Model reads distribution or decline phase on the position. | Context for risk reduction discussions—not a timed forecast. |
If alerts flood or disagree with your thesis, tighten thresholds or turn off types you do not need—product menus vary by deployment.
Performance and comparison to the market
Vs SPY (or similar) and portfolio performance charts use saved benchmark and return slices the app updates on a schedule. They can be temporarily empty, N/A, or one session behind—usually timing, not broken math.
- Compare the date range you selected to what the chart claims.
- For delays and outages, use Status, delays, and “is it broken?” and FAQ and troubleshooting.
- Past performance ≠ future results—see Disclosures.
For the full data stack narrative, read Where the numbers come from.
Related
Progress is saved in this browser. Cloud sync requires PUBLIC_IRIS_API_BASE, IRIS CORS allowlist,
and window.__trinityIdToken.