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.

Jaxstro research-software assessment scorecard

This scorecard assesses Jaxstro as scientific infrastructure and a public research-software package. The companion Package and documentation SOTA assessment ranks investments; this page records current evidence and what would justify changing an assessment.

Assessment date: 2026-07-15; registry reconciliation: 2026-07-15. Grades describe repository evidence reviewed on that date and must be re-audited when supporting contracts change.

Evaluation criteria

Current grades

DimensionGradeEvidenceEvidence-backed rationaleDeficiency preventing the next gradePromotion evidence required
Research workflow coverageB+Executable research investigationsThree executable investigations connect public APIs to contracts, evidence, limitations, and warranted claimsCoverage is narrow relative to public callable breadthMore question-driven workflows with independent evidence artifacts
Contract coverageB+Qualified scientific core and Scientific contract registryA deliberately bounded qualified core and public modules have export-audited contracts235 public callables remain explicitly unclassifiedPrioritized callable coverage with tested transform and failure claims
Evidence linkageA-Scientific evidence indexComputational evidence, source provenance, and scientific policy remain distinct and freshness checkedEvidence depth is uneven by moduleMethod-appropriate artifacts for consequential contracts
Limitation coverageB+Evidence and claim boundariesWorkflows and contracts record bounded non-claimsLimitation coverage is not generated for every public callableA limitation-coverage ratchet tied to contract records
Architecture and ownershipAArchitectureThe thin foundation and one-way ecosystem boundary are explicitConsumer evidence for future abstractions is incompletePinned multi-consumer ownership evidence
Numerical correctnessA-ValidationAnalytic cases, limits, round trips, convergence, adaptive-quadrature failure envelopes, and FD comparisons cover major kernelsValidation and performance artifacts remain unevenPer-contract evidence coverage and missing-evidence ratchets
AD honestyARoot-findingSmooth, blocked, zero, value-first, validation-only, and certified implicit paths are distinguishedThe taxonomy is not uniformly generated per callableCallable-level AD coverage with evidence links
JAX architectureA-Numerical methodsJIT, VMAP, scan, PyTree, JVP/VJP, and gradient behavior are tested on substantial surfacesTransform and batching-cost behavior is hard to discover per callableGenerated transform matrix linked to executable evidence
Units and dimensional safetyB+Unit systems and quantity adoptionUnitSystem is mature and quantity is implementedAdoption remains deferred while two dimensional surfaces coexistDownstream parity, performance, serialization, and migration evidence
Performance evidenceB+Scientific evidence indexRootfinding and spectra use units-explicit records with freshness checksCompile, graph, memory, and cost coverage remains unevenMethod-appropriate performance records
Downstream usefulnessB+Astro-first, science-general visionSibling packages motivate selected shared foundationsAdoption claims are not generated from pinned revisionsCompatibility records and consumer validation
Maintenance readinessB+Release checklistRelease gates, deterministic docs, Ruff, MyPy, and wheel smoke existType strictness and manually duplicated truth remain unevenContract-driven docs and stricter typing evidence

Coverage by research workflow

The workflow registry measures executable connections rather than page volume. Each investigation names public APIs, contract links, indexed evidence links, validation targets, limitations, and a warranted claim. This structure does not automatically validate any downstream scientific model.

The next useful additions are investigations that expose currently weak contract, evidence, or limitation coverage. A large number of shallow examples would not justify a higher grade.

Grade-change policy

A grade changes only when the relevant contract, independent validation, limitation statement, reproducible artifact, and consumer evidence are present. Every change records its date, supporting evidence, and newly satisfied criterion. A newly discovered defect can lower a grade immediately.

Current hardening sequence

Scientific contract registry: implemented. Evidence depth remains uneven, and an unclassified symbol is not treated as supported.

Metric identitySymbolValueUnits
Registered public modulesN_module,contract19modules
Callable-level contractsN_callable,contract18callables
Explicitly unclassified public callablesN_callable,unclassified242callables
Module-inherited public record typesN_symbol,inherited178symbols

Unified evidence infrastructure: implemented. Computational measurements, source provenance, and scientific policy remain separate evidence classes. Method-specific scientific thresholds remain method-owned.

Metric identitySymbolValueUnits
Indexed evidence artifactsN_artifact,evidence13artifacts
Distinct evidence classesN_class,evidence3evidence classes

Executable research workflow registry: implemented. The schema-2 registry connects investigations to contracts, evidence, validation targets, and limitations.

Metric identitySymbolValueUnits
Executable research investigationsN_workflow3investigations
Callable contract linksN_contract,workflow7contract links
Indexed artifact linksN_evidence,workflow2indexed evidence links

The next investment is broader workflow coverage with independent evidence and explicit limitation records. Callable coverage and downstream adoption remain separate promotion gates.