And when it doesn't work.
Automated systems fail. A model returns something that cannot be parsed, a data feed goes
quiet, a connection drops mid-run. The question that matters is not whether that happens,
it is what the system does about it, and the honest answer is worth more to you than a
reassurance.
A cycle that fails does not trade.
Placing an order is the last stage of the cycle, and every failure before it stops the run
there. A cycle that cannot complete leaves your portfolio exactly as it found it. There is
no partial execution, no best guess, no half-applied strategy.
A failure is a decision too.
When the model's response cannot be read, the run is written into your decision log marked
as failed, with the error attached, alongside the runs that did something. A gap in the log
would be the worst possible outcome: you would have no way to tell an unrecorded failure
from a night the system chose to do nothing.
A failure on our side cannot reach your money.
Your assets are at your broker, in your name. There is no state Coincruze can get into that
moves them, freezes them, or makes them ours. The worst outcome of an outage here is that
nothing happens to your portfolio that day.
Where this stands today
Coincruze has not yet run against a live account. Everything on this page describes what
the system is built to do, verified against the code that does it, and we would rather
say that than imply an operating history we do not have. When it has run, we will publish
what it actually did.