Skip to content
Get started

Release notes

Eqiora’s public alphas establish a coherent public identity and a bounded compatibility policy; they are not a stable-1.0 promise.

0.1.0a7 — reusable numerical meaning and execution ownership

Section titled “0.1.0a7 — reusable numerical meaning and execution ownership”

Eqiora 0.1.0a7 retains one admitted chain from recognized conservation or continuum meaning through formulation, material, mesh, realization, Plan, and Run. Reusable scalar conservation now spans Cartesian 1D–3D, while elasticity shares continuum kinematics and solid primitives.

Immutable execution structure, accepted actions, and reusable Faer factorization ownership are prepared once per Run. Python Source gains natural equation authoring, model-local aliases infer dimensions, cancellation exposes the last accepted State, and mesh generation converges on MeshPlan. Legacy physics-specific dimension aliases and duplicate Marimo/Jupyter paths are removed; Colab is the sole maintained hosted-notebook path.

0.1.0a6 — authored scalar meaning and local artifact interchange

Section titled “0.1.0a6 — authored scalar meaning and local artifact interchange”

Eqiora 0.1.0a6 extends the ordinary language/compiler path with exact scalar property bindings, affine coefficients, authored scalar primal Formulations, directional Stokes correspondence, canonical math.pi, typed model-local let, and coherent derived-dimension aliases. Equivalent additive equation orientations retain one canonical residual meaning.

Resolved Plans, complete Results, and complete Trajectories now have atomic local file I/O, and Rust exposes an exact common transient RunRequest. Cylinder presentation meshes and startup media are refined without widening their scientific claim. Cloud transport, a universal remote job format, and new scientific verification remain outside this release.

0.1.0a5 — inspectable formulations and canonical execution artifacts

Section titled “0.1.0a5 — inspectable formulations and canonical execution artifacts”

Eqiora 0.1.0a5 converges the ordinary product path on one inspectable Model/Formulation/Realization boundary and one native common Plan. Resolved Plans, restartable States, complete Trajectories, and complete Results have bounded canonical artifacts with exact upstream identity checks.

Static scalar, elasticity, and Stokes execution publishes the common Result directly. The optional shared semantic eqiora.View V0-V3 presents 2D Geometry, Mesh, selections, and scalar Fields through installed Python. Studio integration, broader field/trajectory viewing, project archives, cloud transport, and new scientific claims remain outside this release.

0.1.0a4 — common Plan lifecycle and transient cylinder startup

Section titled “0.1.0a4 — common Plan lifecycle and transient cylinder startup”

Eqiora 0.1.0a4 converges installed Python on .eqi → eqiora.compile() → eqiora.resolve() → eqiora.run() with caller-owned Geometry, Mesh, and typed numerical policies. It also publishes an accessible, GitHub-backed Colab gallery for a bounded transient cylinder startup. The gallery is explicitly unverified and makes no benchmark, convergence, developed-shedding, or validated-force claim.

The Studio packaged DC-drive example remains executable, but its current a4 compilation, Run, and binding lineage is explicitly unverified. The registered a3 case remains historical attribution rather than being silently promoted.

Eqiora 0.1.0a3 switches the bounded exact-cylinder Python workflow to Gmsh 4.15.2 and updates its Result and Gallery pressure image. Exact supported boundaries remain indexed by the capability matrix and case evidence.

Eqiora 0.1.0a2 is published with the current Python, CLI, MCP, Gallery, and evidence surfaces. Their exact boundaries remain indexed by the capability matrix and case evidence.

The repository changelog is the single maintained record of notable changes. It distinguishes additions, changes, and compatibility-relevant removals.

Python packaging and candidate validation follow the Python release policy. The published release notes bind the exact source, artifact manifest, support matrix, and limitations.

For exact support at any revision, use the capability matrix and verification guide.