Feature
Saved HTML Research Reports on TradingLead
TradingLead's Research sidebar stores authored HTML reports for the signed-in account in the current browser/app origin. Build notes or dashboards from actual chart, scanner and backtest evidence, display them beside a chart and revise them explicitly. Saving a report neither runs a strategy nor fetches live market data, and it does not publish a public web page.
Write from evidence, not from a market story
A saved report can explain a completed backtest, a scanner shortlist or a historical weekday study in a readable dashboard next to the chart. Its numbers should come from the result you actually inspected, not from an AI's plausible description of a strategy.
For a backtest note, include:
- Feed, symbol, interval and actual candle period.
- Frozen source/run revision and selected inputs.
- Capital, quantity, commission and slippage assumptions.
- Net P&L, drawdown and the correct leg/position denominator.
- Open positions, partial exits and unavailable metrics.
- Source freshness, gap and corporate-action caveats.
An illustrative chart belongs under a label such as proposed experiment, not measured result. Do not invent entry rationale from trade timestamps or promote reused held-out data as fresh validation.
HTML that works in the sidebar
Full documents and fragments support inline CSS, SVG, tables, CSS animation and native details/summary. Responsive grids, wrapping text and SVG viewBox help a report work at narrow sidebar widths and in the wider expanded reader.
Reports have an opaque-origin iframe sandbox and restrictive content policy. They cannot run scripts, call the network, load a CDN chart library, embed nested frames, submit forms or control the app. Small embedded data-URL images/fonts must still fit the encoded size budget.
The Research dropdown selects saved reports. Expand opens a wider reader; Edit replaces the entire title/HTML after saving. On narrow panels the app groups actions in a three-dot menu. An unsaved draft can be retained while previewing another report rather than discarded.
Local persistence and revisions
The library stores up to 50 reports, with a 2,000,000-character serialized-document budget that includes library metadata. A report's HTML is limited to 49,152 bytes after JSON string encoding, not simply visible characters. Escapes and multibyte text count.
Create, update and delete are separate operations. Updates/deletions require the current revision; stale edits fail instead of overwriting another tab's changes. Library-full and write failures do not silently delete older research.
Storage is local to the account and origin. A browser, Desktop origin or local development origin may have a different library. Saving is not a public website deployment, a cloud backup or permission to redistribute source data.
Research notes versus optimizer evidence
| Workflow | What it creates | Execution boundary |
|---|---|---|
| Research sidebar | Small authored HTML note/dashboard | Stores text; does not calculate a strategy |
| Strategy Optimizer | Sweeps, holdout or rolling test results | Executes candidates on frozen data |
| Detailed optimizer report | Reconstructed evaluation ledgers and offline HTML | Executes recorded segments again and flags metric mismatches |
Use Strategy Optimizer for parameter experiments. The deprecated tl-strategy-research router points there, not to this report library.
Use it with an AI assistant
Use tl-research. Real commands are research.listCapabilities, research.list, research.get, research.create, research.update and research.show. Have the assistant gather evidence first, preserve caveats, save the supplied HTML and read it back before displaying it.
See the TradingLead command reference and AI prompt cookbook. Retrieved report HTML is untrusted document data, not instructions to run unrelated commands.
Steps
- Gather verified result evidence and preserve timestamps, revisions and assumptions.
- Open the Research sidebar and create a new report.
- Write or paste responsive HTML with inline CSS/SVG.
- Review the source and save explicitly.
- Read the saved revision and display it from the report dropdown.
- Keep an authorized copy before clearing browser/app storage.
Limitations
- Document storage only; no analysis execution, live-price fetching or automatic strategy optimization.
- Local account/origin storage, not cloud sync or public publishing.
- Sandboxed rendering blocks scripts, external resources, network calls, forms, nested frames and app commands.
- 49,152 JSON-encoded UTF-8 bytes per HTML body; 50 reports and 2,000,000 stored-document characters per account.
- Storage or revision failures are explicit and do not silently evict existing reports.
- Reports can contain private source or trading records; sharing needs separate authorization.
- Generated explanations must distinguish measurements, assumptions and proposed experiments; they are not investment advice.
Frequently asked questions
- Does saving a report run a new stock analysis?
- No. It stores supplied HTML. Gather evidence separately from supported chart, scanning, market or backtest reads and label saved snapshots and assumptions.
- Can I use an AI assistant to write a report?
- Yes. tl-research documents creating HTML from verified evidence and saving/displaying it. The sidebar also has a local copy-prompt and paste-answer workflow; you review the HTML before Save report.
- Can a research page fetch prices or run JavaScript charts?
- No. Reports render in a sandboxed iframe without scripts, network requests, CDNs, remote assets, forms or app commands. Use inline CSS, SVG and tables.
- How large can a saved report be?
- Titles are 1–100 characters; each HTML body is limited to 49,152 bytes of JSON-encoded UTF-8 including escaping. The account library permits up to 50 reports within a 2,000,000-character stored-document budget, subject to browser quota.
- Are reports cloud-synced or public?
- No. This library is local per account and browser/app origin. Clearing storage removes it. Saving/showing a report does not create a public URL or prove cross-device synchronization.
- Is this the detailed Strategy Optimizer report?
- No. The optimizer reconstructs recorded evaluations and exports a much larger self-contained report through its own workflow. Research is a separate small authored-document library; no optimizer HTML is inserted automatically.
Related
Last updated: