Kernel / native API

The backtest and forward-execution engine, and the API a host drives it with. More...

Files
file	native_host.hpp
file	native_run_spec.hpp
file	native_order.hpp
file	native_order_identity.hpp
file	native_toolkit.hpp
file	native_calendar.hpp
file	native_fx_curve.hpp
file	native_module.hpp
	One-line C ABI export for a hand-written NativeStrategyHost.
file	native_c_api.h
file	pineforge.h
file	engine.hpp
file	execution.hpp
file	execution_consumer.hpp
file	market_driver.hpp
file	order_action.hpp
file	order_cancellation.hpp
file	bar.hpp
file	metrics.hpp
file	quantity_intent.hpp

Detailed Description

The backtest and forward-execution engine, and the API a host drives it with.

Nothing here knows what PineScript is: a host declares a NativeRunSpec, implements the NativeStrategyHost callbacks, submits native_order::Request values and reads back events, trades and a report. TradingView parity is not a property of this layer — it is a policy the Pine adapter (TradingView-parity policy layer) applies on top of it.

Start at native_host.hpp for the callback surface, native_run_spec.hpp for what a run declares, native_order.hpp for the request and event vocabulary, and native_c_api.h for the same surface in C. examples/native/ builds its runnable hosts against exactly these headers and nothing else.