Execution controls
Understand warmup, automation modes, L3 intent checks, and source-specific behavior.
Execution methods apply controls before a request reaches the simulator or broker. Use logs and decision records to locate the actual rejecting check.
Warmup and automation
The shared automation checks block execution during warmup. Manual source does not bypass that warmup check.
| Mode | Bot placement/modification | Bot cancellation |
|---|---|---|
auto | Entries and exits permitted by this control | Permitted |
entry | Entry/add requests permitted; exits blocked | Permitted |
exit | Opposite-side exit requests permitted; entries/adds blocked | Permitted |
off | Blocked | Blocked |
“Permitted” means this control does not reject the request; other checks still apply. The shared classifier uses existing position side: no position or same-side action is entry, opposite-side action is exit. It does not classify partial versus oversized reversal quantities independently.
Automation mode is session runtime state. Do not assume a changed mode has rewritten the saved app configuration or will persist across a new session.
Optional L3 intent checks
When L3 evaluation is enabled, ordinary SJS/bot requests can pass through its intent hook. The request kind distinguishes placement, modification, cancellation, and closing. A close can delegate to placement and encounter another check.
L3-originated requests bypass the L3 intent hook to avoid that same review path. Manual-source requests override its resulting decision in the normal path. Neither source label promises bypass of every runtime or broker constraint, and Lab error propagation can still fail a request.
Use source: "sjs" for SJS strategy actions. Source identifies provenance; it is not a configuration trick for escaping controls.
Eligibility after policy review
A request allowed by L3 can still fail placement eligibility, duplicate checks, capital checks, price conditions, or broker validation. Policy approval is not order acceptance, and order acceptance is not a fill.
Read policy intents for the policy framework and simulation versus broker for execution differences.