Local-first infrastructure for user-defined market systems.
OptionLab provides the machinery for repeatable research and automation: define strategy logic, validate configuration, simulate execution, journal the decision, replay the run, then connect local providers when you are ready.
Strategies, execution config, activation acknowledgements, decision snapshots, and order-plan output stay explicit and replayable.
Strategy primitives
Strategy, StrategyVersion-ready versioning concepts, rules, asset class, and user-owned configuration.
Activation gates
Execution requires an acknowledgement record before the runtime submits broker requests.
Order-plan output
The engine emits structured order intent for broker adapters instead of hidden side effects.
Plugins
Provider architecture
Broker and market data providers declare their capabilities through manifests, local refs, and fingerprints.
Capability manifests
Providers advertise paper trading, market data, replay, and adapter capabilities.
Local provider refs
User-owned credentials and provider settings are resolved locally.
Fingerprints
Journal events can record which provider implementation participated in a run.
Execution
Risk and broker boundaries
Risk limits, exposure checks, broker capability compilation, and synthetic exit interfaces are represented as explicit software boundaries.
Risk scale
Users set the risk limit; OptionLab validates and records the configuration.
SimBroker
The default path accepts paper order requests without external credentials.
Broker adapters
Live adapters are local interfaces that users connect and operate at their own risk.
Audit
Journal and replay
Every demo run writes a local JSONL event trail that can be inspected, counted, and replayed without a hosted service.
Decision snapshots
Each run records the strategy, activation, signal fixture, and order intent.
Broker receipts
Submitted paper orders are captured as journal events.
Golden runs
Replay verifies the run shape from stored events rather than memory.
Local control
What stays on your machine
The open-source path is designed for local operation. There is no required hosted OptionLab account.
Credentials
Broker and data credentials live in environment variables or ignored local files.
Journals
The default demo writes to `.optionlab/journal.jsonl` inside the cloned repo.
Provider setup
Broker/data provider refs and local configuration are user supplied.
Studio
Local research workspace
The optional Studio UI gives the platform a focused dashboard for research, strategy building, local execution status, portfolio review, and plugin visibility.
Research dashboard
Dense market, strategy, options-chain, portfolio, and plugin surfaces in one shell.
Open-source chrome
The UI stays focused on local operation, not account conversion flows.
Developer loop
Run it locally with `make studio` after installing the repo prerequisites.
Next step
Run the local demo and inspect the journal.
The fastest proof is the repo path: install, run the deterministic demo, replay the generated events, then decide which providers you want to connect locally.