01
Run a report
Generate it with the strategy attached, so the cohort and the written analysis belong to that approach.
Every report, simulation and rule,tied to the strategy it belongs to.
Say you trade an opening range breakout. Add it as a strategy, with a description or the Pine script you already use. From then on, every report you run against it, every simulation from those reports, and every rule you save stays attached to that one approach, on the account you trade it in.
Analysis that stays attached to something
Without a strategy, findings float free. You run a report, spot something, test it, and the result sits on its own with no record of which approach it came from or which account you were trading at the time. Three months later you have a folder of results and no idea what they were about.
A strategy is the anchor. Reports attach to it. Simulations hang off those reports. Rules that hold up get saved back onto it.
You can run the same approach on more than one account, and keep the records separate.
What a strategy holds
A name and a description of the approach. The accounts you trade it on. Every policy you have saved from a simulation. And, if you use TradingView, your master Pine script.
That is the whole object. Open it and you can see what the approach is, what you have proven about it, and what is currently running on your chart.
You do not need Pine for that to be complete. Without it, a strategy is still an organiser and a reference: policies stay readable so you can check what your rules are, and everything stays attached to the right approach.
ORB Strategy
Policy versionsCurrentMaster PinescriptTradingView PinescriptCreatedUpdatedID
Description
Setup, rules, and constraints for this strategy. Edit via Edit strategy.
Opening range is the first 15 minutes of the New York cash open (09:30–09:45 ET). Long on a close above the range high; short on a close below the range low. One attempt per direction per session. Relative volume on the breakout bar must be above 1.0. Skip if the opening range is already wider than 0.35% of price. Stop sits on the opposite side of the range. The trade is invalid if price closes back inside. Target is 1.5× the opening-range height, or flatten at 11:30 ET, whichever comes first. No new entries after 10:15 ET. Skip sessions where the overnight gap already exceeded the prior day's range.
How a rule gets onto a strategy
Run a report with the strategy attached. Find something in it worth testing. Simulate the change on that same set of trades, keeping or removing what the finding points at. Save the run. Publish it onto the strategy as a policy version.
Each version is numbered and fixed once it is saved. The next one goes on top.
- 02
Find something to test
A session, a regime, an exit distance: whatever in the report is worth checking against the same trades.
- 03
Simulate, then save
Keep or remove what the finding points at. Compare baseline to the filtered set, then save the run.
- 04
Publish a policy version
The saved run becomes a numbered version on the strategy. It stays fixed. The next one goes on top.
What builds up over time
A policy version is a saved set of rules. It can keep only certain trades, remove trades that match a condition, adjust stops and targets, or do more than one of those at once.
Every version stays on the strategy with the simulation it came from. One of them is current. The rest stay there, so you can see what you tried and go back to something if you need to.
Combining
Two versions that both held up can be merged into one and tested together. Keep rules can require all conditions or any of them. Remove rules work the same way. If the combination cannot work, Tessera says so rather than saving something that will not run.
ORB Strategy
Policy versionsCurrentMaster PinescriptTradingView PinescriptCreatedUpdatedID
| Version | Policy | Simulation | Current |
|---|---|---|---|
| v4 | Remove low-ATR longs Remove | Regime Analysis · all time | Current |
| v3 | Tighten stops in Sydney SL | Exit Placement · May window | — |
| v2 | Keep New York breakouts only Keep | Regime Analysis · all time | — |
| v1 | Take-profit at 1.5× opening range TP | Exit Placement · all time | — |
If you use Pinescript
Paste your existing TradingView script onto the strategy. When you have a policy you want to use, Tessera writes it into a copy of that script and gives you the result to paste back into TradingView.
Your original stays where it is. You can see both side by side, the script you wrote and the one Tessera composed from it.
Three modes
Merge into your strategy
The policy goes into your script, gating the entries you already have.
Append to an indicator
For indicator scripts, the policy block is added at the end for you to wire in yourself.
Separate overlay
A standalone script that leaves your original untouched.
Stop and target distances carry across. Breakeven, trailing and time based exits are applied when you simulate in Tessera, but on TradingView they appear as labels only. They do not move orders there.
Match the candle timeframe from your report when you load the script.
If you change your master script, compose again. The old composed version is marked stale until you do.
The whole trail, on one canvas
Open a strategy on the workspace canvas and you can see everything hanging off it. Reports under the strategy, simulations under the reports, policies under the simulations. It is a read only view, so nothing moves while you are looking at it.
Create your first strategy
Attach reports, simulations, and saved rules to one approach, on the account you trade it in.