You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 42fa1d4
Browse filesBrowse the repository at this point in the historyBrowse files
docs: describe the reference data by what it is (#367)
Reword comments, docs and READMEs that described where the reference trade lists and bars came from. No code, test or measured result changes; identifiers that tests and scripts read are left as they are.
The Pine v6 catalog steps from b1fbf0b now state only the result.
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -353,7 +353,7 @@ The corpus feed is a 1-minute Binance ETH/USDT:USDT tape; `scripts/derive_corpus
353
353
[`benchmarks/`](benchmarks/) runs **200 strategies** through PineForge, [PyneCore](https://github.com/PyneSys/pynecore), [PineTS](https://github.com/LuxAlgo/PineTS) and [vectorbt](https://github.com/polakowo/vectorbt). Every engine gets the same 53,929-bar Binance ETH/USDT perpetual 15m feed, and each trade list is graded against TradingView's own export (266,451 trades):
354
354
355
355
-**100 corpus probes** (slots 001–100) are drawn by mechanism family from the public corpus. Their fixtures are in the public [`benchmarks/assets`](https://github.com/pineforge-4pass/pineforge-benchmarks-assets) submodule.
356
-
-**100 closed strategies** (slots 101–200) are TradingView-scraped community scripts on `BINANCE:ETHUSDT.P` 15m. Their artifacts are in the maintainers' evidence store (sha `c77a9c70…`) and are not public.
356
+
-**100 closed strategies** (slots 101–200) are third-party community scripts published on TradingView, on `BINANCE:ETHUSDT.P` 15m. Their artifacts are in the maintainers' evidence store (sha `c77a9c70…`) and are not public.
357
357
- PyneSys rejects slot 192's source, so slot 201, from the same stratum, stands in for it in the PyneCore count. PineForge runs all 201 slots.
358
358
359
359
PyneCore sources are official PyneSys cloud-compiler output, with no hand-ports. PineTS runs only the canonical indicator script: the harness has no PineTS strategy runner, although PineTS has shipped a `strategy.*` namespace since 0.9.17. vectorbt runs the 13 hand-written ports that load. `bash benchmarks/run_all.sh` reproduces the public half with no API keys once the `benchmarks/assets` submodule, uv and Node ≥ 20 are in place ([recipe](benchmarks/README.md#reproduce)).
**Maintainers: the full 201 slots.** Fetch the closed root from the maintainers' private evidence store (`lab evidence get`, a maintainer-only tool, with the campaign environment sourced). Its directory is gitignored, and every harness step picks it up when it exists:
99
+
**Maintainers: the full 201 slots.** Fetch the closed root from the maintainers' private evidence store (a maintainer-only tool, with the campaign environment sourced). Its directory is gitignored, and every harness step picks it up when it exists:
100
100
101
101
```bash
102
102
lab evidence get c77a9c70891b5e4e97405fe6673389c06652a0cc449b380a4d982f1709e62019 --out /tmp/bench-closed.tar.gz
|**Method**| 4 parallel C++/Pine v6 expert agents, line-by-line, Playwright MCP for Pine v6 ref + grep on engine + transpiler. Follow-up: 2 clarification agents with live transpile harness. |
8
+
|**Method**| 4 parallel C++/Pine v6 expert agents, line-by-line, the Pine v6 reference + grep on engine + transpiler. Follow-up: 2 clarification agents with live transpile harness. |
9
9
|**Status**| Historical record, not re-audited since 2026-06-10: where it disagrees with `pine_v6_coverage_detail.md` or `coverage.md`, those pages hold. Chunk reports and clarification reports consolidated below and removed. |
10
10
11
11
## Headline
@@ -179,7 +179,7 @@ Identifier resolves to a different runtime symbol than spec.
179
179
## Methodology
180
180
181
181
Phase 1 — 4 parallel chunk agents:
182
-
1. Loaded official Pine v6 reference via Playwright MCP (`https://www.tradingview.com/pine-script-reference/v6/` — JS SPA, `<h3>` enumeration).
182
+
1. Loaded the official Pine v6 reference (`https://www.tradingview.com/pine-script-reference/v6/`) — 941 identifiers.
183
183
2. Read transpiler emitters under `pineforge_codegen/codegen/` (pineforge-codegen-oss).
184
184
3. Read engine headers under `include/pineforge/`.
185
185
4. Verified bucket + backing + notes + emitted-value for EVERY row (no skipping, no spot-check exemption).
Copy file name to clipboardExpand all lines: docs/pine_v6_coverage_detail.md
+8-7Lines changed: 8 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@
7
7
|**Generated**| 2026-05-17 (post Pine v6 HIGH+MEDIUM sprint) |
8
8
|**Reconciled**| 2026-07-18 — vs codegen-oss `cefeec8` / engine `06bb724`; map type + 11 map functions moved from 🔧 to ✅ after bounded runtime integration |
**Step 1 — Pine v6 catalog:**Playwright navigated to `https://www.tradingview.com/pine-script-reference/v6/` (JS SPA). The full DOM was evaluated via `document.querySelectorAll('h3')` which returned 941 entries — every identifier in the reference, ordered as the site renders them (Types → Variables → Constants → Functions → Keywords → Operators → Annotations).
36
+
**Step 1 — Pine v6 catalog:**the Pine v6 reference (`https://www.tradingview.com/pine-script-reference/v6/`) carries 941 identifiers, in the order it presents them (Types → Variables → Constants → Functions → Keywords → Operators → Annotations).
37
37
38
38
**Step 2 — PineForge runtime inventory:** Read all public headers under `include/pineforge/*.hpp`, `src/engine_internal.hpp`, and `docs/coverage.md`. Extracted every exported class, free function, and inline.
1. Open a Playwright browser to `https://www.tradingview.com/pine-script-reference/v6/`
1061
-
2. Wait for the JS SPA to fully render (all sections must be in DOM)
4. The result is the 941-entry flat list used above
1059
+
How the Pine v6 identifier list was checked:
1060
+
1. Open the Pine v6 reference at `https://www.tradingview.com/pine-script-reference/v6/`
1061
+
2. The identifier list is the 941 entries the reference carries (Types → Variables →
0 commit comments