What we'll write here
An empty blog is honest. Here's what we plan to publish — engineering deep dives on Pine semantics, transpiler design, and parity-grade backtests — and why we'd rather wait to write it well than rush it.
This blog is empty on purpose.
The PineForge team has been heads-down on the engine — 162 strategies in the parity sweep, 158 hitting strict trade-for-trade, and the codegen pipeline shipping as a free API. The marketing site went up first. The writing comes next.
What's coming
A handful of engineering posts are queued. We'd rather publish each one with real artefacts — reproducible CSVs, side-by-side traces, code that runs — than ship vibes. Here's the rough roadmap:
-
The transpiler architecture. How Pine v6's lexer / parser / analyzer feed the C++ codegen, why we chose AOT compilation over an interpreter, and where the proprietary core ends and the Apache-2.0 runtime begins.
-
Parity engineering as a discipline. What it actually takes to hit trade-for-trade agreement on 158 of 162 reference strategies. The infrastructure (CI sweep, comparison harness), the corpus design, and the methodology we use when two engines disagree by exactly one bar.
-
Strategies as compiled binaries. The marketplace thesis (designed for 2027): why a
.sowith seller-defined license bounds is a better distribution model than a JSON-encoded signal feed, and how the runtime handles license checks without phoning home on every backtest. -
Optuna + walk-forward, integrated. Shipping in Q3 2026. Why we exposed the optimizer as a Python lambda objective rather than a UI-built fitness slider, and how out-of-sample validation gets baked into every optimization run.
In the meantime
If you'd like to skip the wait and just use the engine:
- Get a free codegen API key →
- Browse the 162 backtests we ran →
- Use it from Claude / Cursor / any MCP client →
- Read why we built it →
We'll add to this list as posts ship. No newsletter spam — when something is worth your attention, we'll send it once.