A convincing thesis leaves hard questions open
A clearly written trading plan is only the beginning. Once it runs, another instance may reserve the funds, quotes may move, an order may fill only partly, or a network interruption may leave its outcome unknown. A trading system must keep answering what happened, which obligations are complete, and which still need attention.
Approve a version, account for shared funds
Suppose an account or a material parameter changes after approval. The old approval cannot silently cover the new plan. Checking again keeps the approved conditions aligned with the proposed run. Multiple bots sharing an account also cannot each treat the balance as fully available: reservations and existing exposure constrain their next actions together.
One concrete requirement in local simulation is to start each new instance from the reference price frozen at approval and track its own time and fees. Existing runs retain their rules. This helps explain deviations; it does not establish live matching performance or a working venue connection.
Stopping new actions leaves obligations to reconcile
Pausing new trades does not sell existing holdings. Ending a bot requires an explicit choice to retain holdings or request an exit; actual receipts establish the outcome. Partial fills, unconfirmed orders and residual holdings still need reconciliation. Query the original operation when its result is unknown rather than treating a timeout as failure and submitting again.
A partial fill is not the end of an order Filled quantity creates exposure. Remaining funds stay reserved until the result is reconciled.
A core application can strengthen the ecosystem
LensWave Trading Core aims to keep approval, rules and outcomes connected. Research can continue to propose new judgments while explicit rules and records govern an active run. With consent and independent validation, that experience could eventually strengthen Astarter’s tools, data and models.
Current evidence covers adapted grid and bounded DCA versions in local simulation. Catalog inclusion does not establish executability, and joint acceptance of two BOT flows is still pending. Simulation records cannot prove real fills or a live trading connection.