Skip to article frontmatterSkip to article content
Site not loading correctly?

This may be due to an incorrect BASE_URL configuration. See the MyST Documentation for reference.

API reference

Use this reference when you know the operation you need and want its current Python owner, records, transform behavior, failure contract, and evidence. The groups below are documentation routes; they do not create Python namespaces.

SurfaceStatusDocumentation rule
Owner-qualified module APIsCurrentCanonical reference path
Flat jaxstro.numerics callable re-exportsCurrent legacy inventoryRemain importable until the Project 2 hard cut
Proposed or delegated capabilitiesPlanned or ecosystem-ownedRemain outside API reference until an owner and contracts exist

Canonical import policy

Import a coherent module and qualify the call:

from jaxstro.numerics import rootfinding

result = rootfinding.safeguarded_bracketed_root(...)

Or import a symbol directly from the module that owns it:

from jaxstro.numerics.rootfinding import safeguarded_bracketed_root

Flat callable re-exports from jaxstro.numerics are legacy inventory awaiting Project 2. They remain importable for now, but they are not the canonical documentation path. This reference does not change runtime exports.

Method owners

Representation and data owners

Research infrastructure owners

See Numerical checks, Numerical type aliases, JAX configuration, Scientific contract registry, Computational evidence, Runtime provenance, and Validation and provenance tooling.

Only current importable surfaces appear here. Proposed capabilities remain in the Methods, Representations, Workflows, and Project roadmaps until runtime owners and executable contracts exist.