Why we built PineForge

oca-exit-bracket-internal-cancel-01 exits through an OCA group. TradingView’s trade book is the broad stroke, PineForge’s the thread inside it: 421 trades in each book close at the same times with the same cumulative P&L, to the cent.

We did not start at strict parity. Today the open corpus holds 312 strategies, 311 excellent and 1 declared anomaly, and the 2026‑10‑13 baseline on engine main grades 100.00 % of 7,989 backtests on 9 markets excellent or strong against TradingView’s own trades. The gap was not closed by writing more codegen; it was closed by chasing divergences one at a time.

Source: scripts/check_corpus_parity.sh in pineforge-engine, commit 35db01c8, line 86; pineforge-corpus commit d75b4fa

Source: parity campaign records (internal, not public): baseline pineforge-parity-baseline-20261013-engine-2608ebdd (snapshot sha256 438ca43a…5aac, population cf857209…b062); scripts by origin: pineforge-engine README.md, d1d18867; trade count: pineforge-release facts.json.

Most of that work went into matching TradingView’s specific definitions of words like “exit”, “fill” and “trail”. The Pine documentation describes the API; the exact semantics of order processing only become visible when you diff trade lists bar by bar. We did that, kept asking why ours and the reference disagreed, and ironed out the differences one at a time.

The one remaining open-corpus exception, anomaly-equity-mirror-strategy-equity-01, is declared an anomaly, so the corpus gate reports it as one rather than as a failure. Its notes record the original diagnosis: at exactly 1× equity, TradingView’s margin check admitted some entries above equity and rejected some below it. That diagnosis is under review: the 2026‑10‑13 parity baseline graded this probe excellent.