Policy explanation and constraints in plain language
How to read preset-derived constraint packs and the “policy explanation” bullets after optimization—what tightened, and why it matters to you.
Two different things
| Concept | In one sentence |
|---|---|
| Risk settings | Your numeric guardrails—max loss per trade, max position size, how many names, etc. |
| Constraint pack | Extra structural rules—sector ceilings, volatility targets, turnover budgets on rebalance—that merge with those guardrails. |
The policy explanation is a short, human-readable bullet list describing what inputs the server applied so you can audit: “We turned your Moderate preset into sector caps + a vol tilt,” for example—not legal advice or suitability.
How to use the bullets
- Compare them to what you thought you selected in onboarding or risk wizard—if they disagree, fix the preset before trusting size.
- Pair with optimizer diagnostics when shown: diagnostics say what bound the run (e.g., effective max position after sector merge).
Transparency stance
Constraint packs make the machine explainable in product terms. They do not guarantee outcomes—they narrow the feasible set of portfolios so the proposal matches your stated posture.
Further reading
Educational disclaimer
TRINITY provides tools and education, not personalized investment advice. Consult a qualified professional before making financial decisions. See Disclosures.
Progress is saved in this browser. Cloud sync requires PUBLIC_IRIS_API_BASE, IRIS CORS allowlist,
and window.__trinityIdToken.