When an automated trade goes wrong, ask a simple question: what did the system actually do?
Most stacks cannot answer it.
Why the record is usually missing
Application logs are editable. That is not an accusation, it is just what a log file is — a writable file on a machine somebody controls.
Screenshots prove nothing. They are trivially fabricated and carry no verifiable ordering.
The broker's record shows the order that arrived. It does not show the chain that produced it: which signal fired, what state the system was in, what was evaluated and rejected, and whether the order that reached the exchange is the one the strategy intended.
So when the outcome is disputed — a fill at an unexpected price, an order that should never have been sent, an alleged malfunction — reconstruction depends on records held by whoever has the strongest interest in their content.
That is an unsatisfactory basis for a dispute. It is a worse basis for an audit, and a worse one still for a regulatory enquiry.
The asymmetry
This matters more for retail algorithmic traders than for institutions, and the reason is structural.
An institution has compliance infrastructure, order management systems with immutable audit trails, and lawyers. A retail trader running an automated strategy through a broker API has a Python process and a log file.
When something goes wrong, the institution can produce a record. The retail trader can produce a screenshot.
What we built
AION Order Execution Agent records the chain of custody from the originating signal through to the executed order, and it does so on the trader's own device.
Device-resident is the entire point. A record held by the counterparty to a dispute is worth very little. A record held by you, produced as events occur rather than reconstructed afterwards, is worth a great deal.
It stays under your control. It is not transmitted to us.
What it deliberately does not do
It makes no trading decision. It is not a strategy, not a signal source, not an execution algorithm.
It does not prevent a bad trade. It records what happened so the question can be settled afterwards.
It does not replace your broker's records. It sits alongside them and answers a different question — not what order arrived, but what produced it.
On the method
The capture method is the subject of a filed patent application and is deliberately not documented publicly.
We are aware that saying so is unsatisfying in a technical post. The alternative is worse: publishing the method before the application is resolved converts our own work into prior art against it.
So this describes what the component does and why it exists. It does not describe how the capture works, and it will not.
The wider point
The problem is not unique to trading. Any system that acts autonomously on your behalf and can be disputed afterwards has the same gap: the actor holds the record, and the record is editable.
Trading is where the gap is most expensive, because the disputes involve money and the counterparty is better resourced than you are. But the question generalises — who holds the evidence about what the machine did, and can they edit it? — and most autonomous systems currently answer it badly.
More at dashboard.aiondashboard.site/models/order-execution-agent.
Informational only. Not investment advice.
Top comments (0)