Product scope / controlled beta
Capabilities
Implemented, partial, planned, and external-backend-required work are labelled so research groups can assess the beta on its actual evidence.
Readiness is part of the product surface
| Catalogue status | Count | Meaning in this technical beta |
|---|---|---|
| READY | 29 | Implemented for the documented scope. |
| PARTIAL | 17 | Available with documented limitations or incomplete workflow coverage. |
| PLANNED | 101 | Public scientific intent; not represented as implemented. |
| EXTERNAL BACKEND REQUIRED | 1 | Requires an external backend before completion. |
Current workflow scope
- Structure and project preparation
- Project management, structure building, structure import, and supported preparation workflows.
- Atomistic construction
- Crystal, slab, supercell, nanotube, heterostructure, and moiré workflows where supported.
- Electronic-property workflows
- Calculation planning and documented electronic-property workflow support with explicit readiness boundaries.
- Results and analysis
- Structured scientific results and result-analysis workflows within the documented beta scope.
- Verification and reproducibility
- Verification-oriented execution practices and public documentation of status and limitations.
- Platform and packaging
- Validated Windows packaging/lifecycle evidence and a Linux x86_64 staging AppImage, with production-release boundaries stated separately.
How to use these labels
READY is limited to the documented scope. PARTIAL and PLANNED are not silently promoted to complete capabilities. The catalogue also identifies the one EXTERNAL BACKEND REQUIRED intent.