v1.0 Release Readiness

This page is the user-facing checklist for the v1.0 programme. It describes the supported boundary without implying that an unreleased build is a v1.0 release. The published package version and the versioning and release policy remain authoritative.

Installation

Install the stable Python surface in an isolated environment:

python -m venv .venv
source .venv/bin/activate
python -m pip install --upgrade pip
python -m pip install voiage

The base installation contains the Rust-backed stable kernel and its Python facade. Optional integrations are installed deliberately, for example:

python -m pip install "voiage[plotting]"
python -m pip install "voiage[jax]"

The base package does not require JAX, plotting, web, ecosystem, deep-learning, performance, or experimental extras. See the backend guide and binding reference for the retained ecosystem surfaces.

Concepts and first analysis

VOI compares the expected net benefit of acting under current uncertainty with the expected net benefit after learning. Start with the introduction, then follow Getting Started and the EVPI, EVPPI, and EVSI method references.

Use the examples to validate an analysis with deterministic fixtures before adapting it to project data. Keep units, strategy ordering, parameter provenance, and random seeds explicit in production workflows.

Compatibility and migration

The supported Python range is Python 3.12–3.14 for the v1 programme. The stable API is defined by the stable API reference and the Rust-owned contracts; provisional and experimental methods are not stable API guarantees.

For 0.x migrations, read the migration guide and data structures. In particular, prefer typed schema objects and the stable facade over compatibility aliases that are explicitly marked transitional.

Security and reproducibility

Treat analysis inputs and generated evidence as untrusted data. Validate schema and provenance before execution, avoid loading untrusted code or credentials, and keep dependency extras limited to the features used by the workflow. Consult the repository’s quality and security guidance through the developer guide and retain checksums, environment metadata, fixture versions, and random seeds for reproducibility.

The v1 release is not complete until its signed artifacts, SBOM, provenance, reproducibility report, and hosted security gates are verified. Those release artifacts are separate from this documentation page.

Extension maturity and support

The binding reference lists retained language surfaces. The C ABI reference defines the versioned native boundary. Methods and integrations labelled experimental or fixture-backed may change, require additional evidence, or be removed without the stable v1 guarantee.

For help, consult the community and support guide and file a reproducible issue with the input shape, package version, platform, and the smallest failing example. Do not include confidential data or secrets.