Implementation Details

Technical rationale for engine boundaries, route responsibilities, and the default statistical execution policies used in the current release.

This section explains why the current implementation behaves the way it does.

It is the right place to look when you need answers to questions such as:

  • Which responsibilities stay in API and orchestration layers, and which ones belong to the numerical engine?
  • Which statistical defaults are implementation policy rather than user-facing tutorial guidance?
  • How should route behavior, engine behavior, and audit behavior be read together?

Child pages

API Routes and Engines

Explains the product-facing boundary between HTTP routes, orchestration logic, engine calls, and export-oriented metadata surfaces.

JS vs Python Execution Model

Explains why the current release splits orchestration and numerical execution, and why certain statistical defaults are implemented as engine policy.

Start here

  1. Start with API Routes and Engines if you need to understand system boundaries.
  2. Continue to JS vs Python Execution Model if you need to understand engine-level defaults and statistical execution policy.