Jaxstro is the dependency-light foundation for reusable, JAX-native scientific software. It owns domain-general constants, units, coordinates, numerical primitives, scientific representations, provenance, and validation tooling. It does not own domain simulations, scientific acceptance policy, or general solver stacks already maintained elsewhere.
Use this section to inspect why that boundary exists and how it changes:
Inspect the current package map and one-way ecosystem dependency rule.
Apply the science-general admission criteria before adding a new foundation capability.
Follow assessed gaps, definitions of done, and capability roadmaps.
Read the decision index; individual records retain their established routes.
Separate local qualification from explicitly authorized publication actions.
Trace constants and methods to the scientific sources that constrain them.
| Material | Status | Authority |
|---|---|---|
| Architecture and decisions | Current | Package ownership and accepted design rationale |
| Development roadmaps | Planned | Admission and evidence requirements, not schedules |
| Release records | Current policy | Local qualification remains distinct from publication authorization |
| Bibliography | Current source record | Scientific provenance, not independent validation |
Project claims follow the same evidence boundary as runtime claims: an implemented feature is not automatically validated, and a local verification result is not authorization for a remote release action.