Configuration
Separate saved strategy settings from launch choices and in-memory controls.
The saved app is the starting configuration for a run. Keep it coherent across its source editors, model settings, data inputs, and execution assumptions.
Review the saved app
| Setting | What to establish |
|---|---|
| Name and app type | Which candidate this is and which runtime family it expects |
| Instrument | Exact symbol, exchange, security type, and expiry where applicable |
| Interval and input mode | The observations and callback cadence your source expects |
| Timezone and session options | How clock-based rules and historical filtering should behave |
| Capital and sizing | Which settings the selected source and adapter actually consume |
| Historical bounds | The data window used for a historical test |
| Fill delay | Simulated execution delay where supported; not a broker fill setting |
Do not treat a familiar ticker as a complete instrument identity. Follow the instrument guide, especially for futures contracts and changing market families.
Source and configured models
SJS owns the main algorithm. Native Pine belongs in its own editor, SQX compiles declarative rules and models, and L3 provides optional advanced coordination.
Choose one owner for each action. A Pine strategy, transmitting SQX order primitive, and SJS entry can all request execution if enabled together. One layer's presence does not disable another automatically.
SQX compilation can update configured model arrays. Verify the saved result after editing source and model controls through different representations.
Settings have different lifetimes
Saved source and settings belong to the app. Broker selection, warmup, and follower choices belong to the launch workflow. Automation mode and script state belong to the running session.
Editing an app does not establish that an already running instance reloaded those changes. Use a deliberate, verified restart or new launch for a changed candidate, and reconcile account state separately.
Keep secrets in the relevant connection settings, not in source, plots, notes, or logs. The Lab authoring model connection, an L3 provider, and a broker connection are separate configurations.
Continue with importing and publishing.