Hey-LiSA Docs
These docs define the Hey-LiSA system: strategy specs, validation, Strategy Lab, controlled execution, and shared strategy markets.
What is Hey-LiSA?
Hey-LiSA is a strategy operating system.
It turns trading intent into structured strategy logic: something explicit enough to inspect, validate, test, compare, refine, and execute under user control.
A strategy is not a chat message. A strategy is a machine-readable object with rules, state, data requirements, actions, limits, and a trace.
Hey-LiSA exists to make that object possible.
The core loop
idea
-> strategy spec
-> validation
-> backtest
-> review
-> controlled execution
-> discovery and sharing The loop is the product.
Each step makes the strategy less vague and more accountable.
Strategy specs
A strategy spec is the bridge between human intent and machine execution.
It describes what the strategy watches, what conditions matter, what state it remembers, what actions it can take, and what limits it must respect.
The spec is explicit by design. If something is missing, unclear, unsafe, or unsupported, the system should expose it instead of guessing.
Validation
Validation is the first gate.
Before a strategy is tested or executed, it must fit the language. The structure has to be known. The data reads have to be declared. The actions have to be allowed. The logic has to be inspectable.
No hidden code. No silent assumptions. No magic prompt behavior.
Strategy Lab
Strategy Lab is the testing surface.
It replays a strategy against market history and produces a trace: orders, skipped actions, cash deployment, portfolio path, warnings, variables, and strategy graph.
The point is not only to rank outcomes. The point is to understand behavior.
A strategy that looks good for the wrong reason is not good enough. A strategy that hides risk is not good enough. A strategy that cannot explain its own decisions is not good enough.
Controlled execution
Execution comes after language, validation, and testing.
A strategy should only touch the market through explicit user controls: identity, permissions, keys, limits, monitoring, and kill switches.
The user owns the account. The system executes only inside the boundaries the user gives it.
Strategy market
Once strategies are structured objects, they can be shared, reviewed, discovered, compared, improved, and reused.
That is the larger shape: a place where strategies are not just written once, but become living systems people can inspect and build on.
$LISA
$LISA belongs to the long-term ecosystem around Hey-LiSA.
Its exact role is intentionally left open until the product layer is strong enough to deserve mechanics.