What it is

A strategy in Tessera is a saved description of your trading approach - name, notes, optional TradingView script - plus policy versions: rules you built from report and simulator work. Policies let you test entry filters and stop/target changes on past trades, combine rules, and export to Pine Script.

This is separate from live automated trading products. Here, strategies support analysis, simulation, and export.

What you can do

  • Create and manage strategies linked to your reports
  • Build entry filters (skip or keep trades by market conditions at entry)
  • Build exit rules (stop-loss and take-profit distance changes) and simulate them
  • Combine multiple policy versions into one bundle
  • Publish a policy from a saved simulation (backtest) on a report
  • Export rules to TradingView via Policy Pine

How it works

Strategy

A strategy holds:

  • Your name and description of the approach
  • Optional master Pine script (your TradingView strategy or indicator source)
  • Policy versions - snapshots of rules you saved over time

You can link a strategy when generating a report so the written analysis has context.

Policy types

Entry filters

  • Remove: do not count trades that match the condition tree (as if you had skipped them)
  • Keep only: count only trades that match

Conditions use market context at entry - see Simulator conditions and parameters.

Exit management

  • Stop-loss distance override
  • Take-profit distance override

Breakeven and trailing stops are not supported in the product today.

Combined bundles

You can merge an entry filter policy with an exit management policy into one bundle for simulation and export.

Typical Workspace flow

  1. Sync your account, then open your Workspace.
  2. Generate a report on the trade cohort you want to investigate (especially Regime Analysis or Exit Placement).
  3. Explore report conditions/segments, then open the policy/simulation flow for the same scope.
  4. Run simulations and compare baseline vs filtered/simulated metrics.
  5. Save the simulations you want to keep as policy versions.
  6. Optionally combine policy versions into a combined policy.
  7. Compose/export to TradingView Pine so the policy math and conditions are available in code (as a strategy merge or indicator assist) (Policy Pine).
  8. Assign executing account context to the strategy/policy setup, then forward test and review results to decide whether to keep, adjust, or replace the setup.

Policy editor on reports

Exit Placement reports can persist your in-progress policy tree on the report so you can iterate without losing work.

Workspace

The Workspace is where you connect saved policy steps into a node sequence and run a counterfactual test on your connected setup.

In Workspace, you can keep each policy setup tied to a clear account context. This helps you keep work organized and compare outcomes by account when you test the same policy idea.

See Workspace overview and Workspace - nodes, sequence, and policy inputs for the user mental model.

Limitations

  • Policies tested on a report cohort are counterfactual on those exact trades - not a forecast after you change live rules. See Understanding when results change.
  • Entry filters alone do not change per-trade PnL - only which trades count.
  • Conflicting keep only rules from different versions may not merge.
  • Conflicting stop/target overrides on the same condition may block combining policies.
  • Policy size limits: A policy is a tree of conditions (single rules and AND/OR groups). Tessera allows up to 16 levels of nesting and up to 256 conditions and groups in total per policy. That is enough for detailed rules; if you hit the limit, split logic across separate policy versions and combine them as a bundle instead.