Strategies
Draft, refine, and version the approaches you trade — sitting next to the reports and sims that shaped them.
One canvas for the full trading workflow
Strategies, reports, and simulations in one hub — then one canvas where the work connects. Run reports, craft strategies, simulate changes, optimise exits, and optionally compose Pine to paste back into TradingView yourself.
Everything you create, in one hub
The workspace hub is where you see every strategy, report, and simulation you have built — not as tabs you rotate through, but as one central outlook of the work that actually exists.
No hopping between pages and tables for each artefact type. Open the hub, find the piece you need, and step onto the canvas without rebuilding context every time.
Reports
Performance reviews, regime reads, exit placement, and more — generated from your data, kept in the same view.
Simulations
What you tested against real history, linked to the report or policy that started the question.
One canvas. Your whole lab.
Open any workspace and the work becomes a node graph: strategies, reports, simulations, and policies linked by what produced what — not a folder of disconnected files.
From here you run reports, craft strategies, simulate changes, optimise exits, and optionally compose a policy into a copy of your Pine script to paste back into TradingView. The hub is where you find the work; the canvas is where you advance it.
Canvas view
On the canvas, artefacts stay typed and connected — so a rule still shows which report and simulation produced it.
How the workspace actually works
An end-to-end loop for experimentation: set up the lab, mine your data, test what would have changed, compose the rules that stuck, and prove them on the chart — with every step still on the canvas for full context.
Create a workspace
Spin up a new workspace as your lab. This is the canvas where strategies, reports, simulations, and policies stay connected instead of living in separate pages.
Add your trading strategy
Define the strategy you are working on so everything that follows is attached to a clear starting point — the approach you are improving, not a random batch of tools.
Attach Pine Script if you use it
If you trade with Pine Script, paste your existing script onto the strategy. Tessera can write a policy into a copy of that script; you paste the result back into TradingView yourself. The master is a single overwrite, not a version history. You do not need Pine for workspace to work. Strategy setup, reports, simulations, and policies all run without it.
Run and configure reports
Generate reports on your trading data and configure each one the way you need it — performance, regime, exit placement, and related views — so you are slicing the same history on your terms.
Analyse the report output
Read the results in place. Find the weak combinations, the regimes that pay, and the exits that leave money on the table — still linked to the strategy node that started the work.
Run simulations from the report
From the report data, run simulations that ask what would have happened if you had not taken trades matching certain criteria. Compare before and after on the same history.
Save keep and veto policies
Turn the filter that worked into strategy policies: keep or veto rules that define when trades stay in the book. Those policies become part of the documented strategy path on the canvas.
Combine policies and re-test
Merge independently proven policies into a combined policy, then re-simulate the stack as one unit — so layered rules are not a guess, they are measured together.
Activate rules or compose into Pine
Save policies as your active strategy rules, or compose them into a copy of your script: merge into a strategy, append to an indicator, or a separate overlay. You copy that result into TradingView yourself.
Prove each rule. Then stack them.
The visual canvas is how you see the work. The harder thing to copy is what the graph is for: independent policies you measure on history, then combine and re-simulate as a single stack — not notes about rules you never re-tested together.
Test policy A. Test policy B. Merge what held up. Run the combined policy through another simulation. Keep the lineage on the board so you always know which pieces earned their place.
Test in isolation
Each policy is proven on the same trade history before it joins anything else — deltas stay honest.
Combine on purpose
Merge two (or more) independently tested policies into a combined policy when the stack is what you actually want to live with.
Re-simulate the unit
Run the combined policy as one system so interaction effects show up before you promote the rules or export them.
Keep the lineage
Source policies, combined result, and the sims that justified each step stay on the canvas — not lost in a chat log.
See the stack. Own the trail.
Most trading tools keep strategies, reports, and tests in separate menus and tables. We put that work on a connected canvas so the path is visible while you still get the hard part: rules you can compose, re-test, and take forward with evidence.
See how branches form
A node graph makes branches obvious — which report spawned which sim, which policies you kept, and what you still have not tested.
Your lab, not a dashboard dump
Treat each canvas as R&D on your trading: experiments stay attached to the measurements that justified them.
One home for the stack
Strategies, reports, simulations, combined policies, and scripts that come out of them share a single visual place.
What the canvas is for
The jobs you already need to improve — without starting over in another product area each time.
Run reports
Generate and keep performance, regime, and exit placement work on the same graph as the rest of your process.
Build strategies
Add and craft new strategies in context of the data and tests that justified them.
Run simulations
Pressure-test changes against your history and keep the result next to the report that raised the question.
Combine policies
Merge independently tested keep and veto rules, re-simulate the stack, and only then promote what held up.
Optimise exits
Work exit placement as part of the flow — not a one-off tool you open and forget where you left the result.
Compose Pine to paste back
Optional: write a policy into a copy of your script. You paste that copy into TradingView. Not required to use the lab.
Open your lab on one canvas
Bring strategies, reports, and simulations into one hub — then improve them on a connected canvas where every simulation and combined policy still has a trail.