For JOSS reviewers
CubeDynamics adds source-qualified names, ordered transformations, semantic state and a local trace around ordinary scientific Python objects. It addresses the difficulty of recovering the analytical question from otherwise rerunnable environmental code. It does not verify scientific suitability or replace xarray, Dask, geospatial libraries, or workflow schedulers.
The JOSS software note is a draft. The public candidate is rc3, while the development documentation includes later work. Start with exact release and review identity; no unified final JOSS revision has been assigned by this documentation pass.
Suggested review path
| Question | Canonical documentation |
|---|---|
| What is it and why build this layer? | Scientific inspectability, related systems |
| What is implemented? | Public API/support, verbs by purpose, noun library |
| How do I install and run it? | Installation, ten-minute quickstart |
| What does a stage mean? | Semantic model |
| Where can interpretation change? | Order, conditions and missingness, scientific data contract |
| What does the trace leave out? | Branch and workflow provenance |
| What evidence supports a claim? | Claim-to-evidence matrix, source QA |
| What does a bounded scientific example show? | Working Lands notebook, input/acceptance record |
| What are the limits? | Contract boundaries, public maturity |
| How do I reproduce it? | Reproducibility |
| How do I cite/report it? | Methods and citation |
The longer manuscripts remain dated originals. Their content map is an archive index, not a parallel reference. The runtime and generated references own current behavior. The repository owns executable tests, fixtures and builders.
Review and contribution
Use GitHub Issues for problems, with runtime identity, platform, minimal code and traceback. See contributing and the code of conduct. The repository includes an MIT license, declared dependencies, tests and CI; local checks establish only the environment and scope recorded in the readiness report.