Jorli Agent

Jorli Agent is a terminal-native strategy builder and guarded trading runtime for NSE/BSE cash equities. The executable is jorli. Running it without a subcommand opens a conversation where the AI may help author a strategy, but deterministic code—not the model— validates, backtests, sizes, risk-checks, and routes every order intent.

idea → validated strategy version → reproducible backtest → approval
     → broker-bound shadow deployment → monitored signals and simulated fills
     → bounded guarded-live deployment → reviewed entries/exits + automatic protection

Safety boundary

Strategy behavior is saved as immutable, schema-versioned YAML. Runtime never reinterprets prose.
Every deployment is bound to one strategy version, broker, broker account, capital limit, and risk limits.
Guarded live deployment uses broker/account/version binding, explicit deployment and per-entry/exit confirmation, partial-fill stop-market protection, coordinated exits, and reconciliation-safe ambiguous states.
Broker calls go through the installed kite or dhan CLI with --json --no-color.
AI and broker credentials stay in their respective OS credential stores.
Past backtest performance does not predict live returns.

Jorli supports candle-close strategies on 5, 15, 30, and 60-minute or daily candles. V1 is cash equity only; it does not support derivatives, tick/HFT strategies, arbitrary generated code, or unattended live trading.

Install and check

Build or install jorli, install both broker CLIs, and run the production preflight.

Strategies

Author, inspect, accept, backtest, and approve immutable strategy versions.

Execution safety

Understand guarded live confirmation, risk snapshots, protective orders, and emergency controls.

Command reference

All terminal and interactive commands, global flags, and exit behavior.

Production readiness boundary

The repository implements guarded live confirmation, protective-order monitoring, coordinated target/signal/square-off exits, partial-fill recovery, and restart reconciliation. It remains a release candidate—not broker-certified production—until controlled minimum-quantity fill/stop/ exit/restart smoke is completed separately on operator-owned Kite and Dhan accounts, Dhan static IP is verified, and public artifacts are signed. Never treat a successful build as broker certification.