Deep dives de engenharia.
Posts sobre semântica de Pine, engenharia de paridade, design de transpiler e a disciplina de backtests reproduzíveis byte a byte. Posts novos conforme a gente entrega.
Pine v6's type system, in practice
PineScript v6 is more strongly typed than its reputation suggests. Walking through the type rules, the inference, the gotchas — and what shipping a transpiler taught us about which rules actually matter at runtime.
Margin checks at signal time vs fill time: a TradingView parity story
Our broker emulator ran the margin gate at fill time using next-bar open; TradingView runs it at signal time using current-bar close. The 3-cent gap between those prices silently dropped 25 trades from a 2,632-trade strategy. How six isolation probes triangulated the bug to one line of C++.
Compiled-binary licensing for trading strategies: the design space
Selling a strategy as source is risky. Selling it as a hosted service is heavy. Selling it as a compiled binary with seller-defined license bounds is the path PineForge's marketplace is built around — here's the design exploration that got us there.
Reading the engine_trades.csv format
Complete reference for the trade-list CSV that PineForge emits. Column-by-column meaning, how trade pairs are encoded, and a 30-line Python snippet for loading into pandas.
When two Pine engines disagree: cross-validating PineForge against PyneCore
We run every release through a parity sweep against both TradingView and PyneCore. Here's what the numbers from the latest sweep look like, and why having a friendly second-source engine is the most useful debugging tool we own.
Backtest a Pine strategy from Claude Code in 90 seconds
Walk-through of the @pineforge/codegen-mcp server: install in one npx command, ask Claude to transpile your Pine, run a Docker backtest, and read the trade list back. Your OHLCV never leaves the machine.
167 strategies, by the numbers
What's in the PineForge parity corpus: how strategies break down by category, asset, and complexity. Read like a museum guide to the gallery.
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.