Skip to content

LEGAL: describe how the TradingView reference data is produced, result only #364

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
luisleo526 merged 1 commit into from
Oct 10, 2026
Merged

LEGAL: describe how the TradingView reference data is produced, result only #364

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion LEGAL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,7 @@ If you run `bash benchmarks/run_all.sh`, `npm install`, or install the Python de

## TradingView trade-list exports (`tv_trades.csv`)

The `corpus/` and `benchmarks/assets/` trees include TradingView **"List of Trades"** CSVs. These are produced by running our **own clean-room `strategy.pine`** files inside a TradingView account and exporting the result **manually** — no scraping, no TradingView API, no automated extraction. They are included as **factual parity reference records**.
The `corpus/` and `benchmarks/assets/` trees include TradingView **"List of Trades"** CSVs. These are produced by running our **own clean-room `strategy.pine`** files in a TradingView account and exporting the strategy report. They are included as **factual parity reference records**.

- **Our position:** the trade records are factual outcomes of our **own** strategies executed against public market data — factual data the author is free to keep and publish (facts are not copyrightable).
- We do **not** Apache-relicense TradingView's export *format/columns* (those are TradingView's, not ours to license), so these files sit in-tree as **factual reference**, not as an Apache-2.0 work of ours.
Expand Down
Loading