@jay.gori
Thank you for the clarification.
However, the main concern remains unanswered. We already understand that the current system requires funds equal to the total allocation of all deployed algos.
Our question is why full cumulative capital is required during deployment or allocation changes when:
-
Actual simultaneous capital utilisation is much lower.
-
Margin is checked again by RMS when each order is placed.
-
Funds can be withdrawn after deployment, following which orders may simply fail if margin is insufficient.
We are not asking Stratzy to decide when we should pause or restart an algo. We have developed our own rebalancing framework for that.
We are asking for the ability to implement it efficiently without maintaining approximately ₹54 lakh when historical peak utilisation is only around ₹20 lakh.
Please escalate this to the product and risk teams and clarify whether order-level margin validation, flexible reactivation, or portfolio-level capital allocation can be considered.