Development roadmap entry¶
The root ROADMAP.md is the single authoritative roadmap. This page links to it rather than reproducing milestone scope or status. Use the architecture charter, API inventory, conventions and compatibility policy for design constraints.
Open decisions¶
These recommendations need maintainer review before implementation or release; they do not change existing APIs or block this documentation-only review.
| Decision | Recommended next step | Compatibility consequence |
|---|---|---|
| Remaining platform verification | Phase 5A verifies CPython 3.10–3.14/Linux x86_64; test Windows, macOS and PyPy separately | Python 2.7 is unsupported; retain six for current helpers |
| Experimental alias removal boundary/window | Retain current shims through architecture/release review; explicitly announce a future approved boundary before deletion | Complete package elimination would break documented imports and some serialized references |
| 1.0 public stability/versioning promise | Review raw kernels, historical helpers and mutable fields separately from well-documented contracts; confirm proposed semantic-version policy | Passing tests alone cannot freeze every incidental public attribute |
| Wider shape/scalar/error policy | Keep current narrow contracts; separately design mismatch, nonfinite, degeneracy and numeric-protocol rules | Uniform validation/reflected operators would change current exceptions/accepted operands |
| Future Ray intersection results | Define hit validity, distance versus parameter and ownership before adding queries; keep legacy end state untouched | Zero end cannot identify an unset hit; silently reinterpreting it would break state semantics |
| Future module organization and release tooling | Review conceptual areas and release tooling separately; MkDocs build and non-destructive Wiki migration are prepared in the documentation website phase | Do not rename current imports or treat provisional API sketches as shipped |
Previously settled row-vector, quaternion, refraction, plane, sampling and legacy helper conventions are not reopened here. Their historical decision trail is in PHASE2-DECISIONS.md; current summaries describe the implemented outcomes. See verification for the documentation review evidence and unresolved scope boundaries.