Prepare for Grid 0.65.0

This site is showing the reviewed 0.65.0 candidate documentation while the product release is still being built and landed. Treat these pages as the contract to prepare against, not as proof that a 0.65.0 installer, server image, or deployment is available. Grid 0.63.2 remains the latest stable product. Locally rebuildable candidate evidence identifies itself separately.

Grid 0.65.0 carries forward the capability work documented for 0.64.0 and changes how source repositories and build provenance are organized. Existing formulas, Registry wire protocols, stored Registry data, and gridctl commands keep their meanings.

What changes for users and model authors

Research Workspace adds five Pro, model-scoped workflows for reproducible evidence, research-use policy, bibliography standards, specialist validation, and scholarly release.
Calibrated predictions add admitted upper P90 endpoints for eligible XGBoost regression artifacts, along with exact-version uncertainty inspection.
Symbolic mathematics adds bounded hybrid computational algebra. FLINT-backed operations remain optional, Pro-only, and target-qualified; a missing native capability fails admission instead of selecting a weaker method.
Product surfaces now document broader resident workflows for experiments, requirements, research, prediction, and other domain views. Availability still depends on product edition and deployment policy.

What changes for integrators and operators

Ordinary in-process and v1 Backbone remains the default. Exact-node HTTP v2 and distributed DDIL are explicit startup selections with separate trust, durable state, recovery, and readiness obligations. Read Choose a Backbone topology before changing any Backbone selector.
Connector clients that use the ordinary Node API do not become exact-node v2 peers. V2 is a deployment-owned Runtime Host or Edge topology.
Source builds now use independent sibling repositories: grid-core owns the compiler and runtime, grid-cli owns gridctl, and grid-registry owns the Registry provider. The grid-ns executable and GRID_NS_* settings remain compatibility surfaces.
Reproducible desktop builds record exact Core and CLI revisions and a combined native fingerprint. Source builders need the repositories they actually build as sibling checkouts or through an explicit source selector.

Compatibility boundaries

No workbook migration is required for the repository split. Grid continues to use one Rust-hosted LIR semantic execution path. Optional Research, native algebra, Backbone v2, DDIL, mission, and defense capabilities do not become active merely because their code exists in a package.

Do not infer these claims from the candidate docs:

that a public 0.65.0 product artifact has shipped;
that every target includes qualified FLINT methods;
that Research Workspace supplies an HPC executor, DOI authority, or repository deposit;
that Backbone v2 supplies identity, consensus, automatic failover, or an atomic external sink;
that evaluated Defense Edge tooling is a shipping field product.

Site migration status

The canonical product and language docs on this site now come from the clean Grid Core 0.65.0 candidate source. Pages and artifacts with older execution evidence show their own release pin. The App tutorial artifacts, four source bundles, 12 portable canonical example receipts, and 1,181-record learning corpus have been rebuilt or checked against the frozen candidate source. Real-product films stay on their verified older release until recaptured from exact 0.65.0 product bytes.

Before changing a production integration, compare its deployed /api/capabilities version and catalog digest with the page's version badge. Before distributing a source-built component, record the exact repository revisions used for every selected component.