Operational Methodology
Risk Management
Risk is not a feeling. It is an operating contract: limits, thresholds, and actions before an Engine opens exposure.
Limits first, then Deployment
If Risk is not written down, it does not exist. Every Mission starts only with explicit drawdown, exposure, and WARNING behavior.
Step-by-step guide
Limits · Exposure · Fleet
- 1
Define Risk before Deployment
Write hard limits: max drawdown, max exposure per Engine, and what happens when they are hit. Without this there is no Mission — only hope.
- 2
Bind Risk to the Protocol
Every Engine exposes Risk via Finversa Protocol. Command Center and Fleet read that, not operator intuition. If it is not in Protocol, it is not governable.
- 3
Separate Deployment Risk and Fleet Risk
One Engine can be inside limits while the overall Fleet is overexposed. Aggregate Capital and exposure at Portfolio level before adding another Deployment.
- 4
Treat WARNING as action, not decoration
WARNING means operational with anomaly or elevated Risk. Pre-define: cut size, pause new entries, or close the Mission. Do not “watch and see”.
- 5
Block unauthorized escalation
No mid-Mission risk increase without a written rule. If you need more exposure, close the Mission, reallocate Capital, and open a conscious Deployment.
- 6
Close with a Risk review
At Mission end record peak DD, time in WARNING, and any breach. Methodology improves only if Risk is measured after — not only before.