OrderSubmitted
The OrderSubmitted event: what it carries, which side emits it, and whether it ends an order's life.
OrderSubmitted is one of the 20 variants of the tagged union every part of Vike Trader
speaks: vike_model::Event. The core loop consumes it, the journal replays it, and fixtures pin
it — one vocabulary from a venue's socket to a strategy's callback.
The payload
It carries a OrderSubmitted. On the wire the frame is tagged OrderSubmitted, the variant name.
Who emits it
Rust, synchronously at submit. The one event the local side emits itself. vike_exec::ExecutionEngine writes it the moment an order is handed to a venue adapter, before any wire round trip, so the order exists in local state even if the venue never answers.
Where it lands
Events reach the core through one ingest channel and are folded in arrival order. It moves state without ending an order's life.
The order lifecycle walks the sequence a working order produces; the execution client seam is the contract every venue adapter implements to produce these; and the journal is what makes a session of them replayable.
Where this comes from
vike_model::Event — the variant, its payload type and its wire tag, exported as rosters.json
at every release. The wire tags are checked against the enum's own source at build time, so a
renamed variant or a changed tag reddens the product tree before it could reach this page.