Recent Grid capability map

Grid changed quickly between the earlier Grid Developers evidence baseline and the 0.65.0 candidate documentation. This map makes the main capability lines discoverable without presenting every implementation commit as a released product feature.

The canonical documentation on this site comes from the clean, active 0.65.0 frozen source. App tutorial artifacts, four source bundles, 12 portable canonical example receipts, and the 1,181-record corpus have been reverified against that candidate. Real-product films keep their older evidence pins until recaptured. A documented capability may also require Pro, a qualified target, explicit startup selection, a separately configured authority, or a released artifact.

Capability line	What changed	Start here	Boundary to preserve
Product surfaces and App Builder	Grid documents a wider set of resident workflows, including Apps, Requirements, Experiments, Planning, Calendar, Visuals, Predict, and research entry points.	Workbook surfaces and Build Grid apps	A named surface does not prove that every edition, deployment, or older captured film contains its current implementation.
Public pretrained models	Pro distributions can install exact signed model coordinates from a pinned Registry and verify their release graph, publisher trust, target, runtime, and memory compatibility.	Get to a running model for supported distribution boundaries	Model bytes are separate downloads. Catalog presence does not create a loader, accelerator, memory, publisher trust, or compatibility.
Package federation	The implementation line adds exact, locked acquisition lanes across npm, PyPI, NuGet, Maven Central, crates.io, Go modules, RubyGems, vcpkg, and Grid packages.	Track the focused public guide as an identified documentation follow-up; use the canonical language and extension contracts currently published here in the meantime.	Ecosystem support is profile-specific. It is not blanket compatibility with every package, platform, build hook, native dependency, or network behavior.
Contested logistics and mission lifecycle	A bounded Domain Pack and workspace cover represented mission definition, planning, authorization, cancellation, retained delivery, and repair. Later selected owners add durable mission-dispatch operations.	Choose a Backbone topology for the selected runtime boundary	The model does not supply mission authority, releasability, identity policy, transport availability, or proof of an external effect.
Research Workspace	Pro adds five model-scoped workflows for reproducibility, research-use policy, bibliography standards, specialist validation, and scholarly release.	Research Workspace and Operate Research Workspace services	Grid preserves and governs artifacts. It does not determine scientific validity, run an HPC scheduler, mint a DOI, or deposit a publication.
Calibrated predictions	Eligible XGBoost regression artifacts can advertise a signed-residual conformal upper endpoint through provider-neutral formula and inspection contracts.	Train and integrate predictive models and Train and use calibrated predictions	An admitted upper P90 is a marginal coverage target for comparable future rows, not a per-row guarantee or a full predictive distribution.
Native CAD hardening	The supported partial-turn shell lane adds earlier resource refusal, exact post-solve checks, bounded resident artifacts, and stricter source identity.	Workbook surfaces for the current CAD surface description	Hard ceilings are safety stops, not a claim that every shape below them is supported or that every target carries the native lane.
Symbolic mathematics	The language expands into bounded polynomial decomposition and systems, exact matrices, integration, and prepared linear ODE work, with independent verification.	Symbolic mathematics	FLINT-backed operations are optional, Pro-only, and target-qualified. Missing native capability fails admission instead of selecting weaker mathematics.
Connector and tenant isolation	Connector ingress, credential handling, endpoint policy, tenant binding, artifact egress, and runtime proxy boundaries were tightened across the recent release line.	Send connector events to Grid and Run Grid in production	A connector credential is not a public API token, model authority, arbitrary cell-write permission, or unrestricted endpoint capability.
Backbone v2 and DDIL	Exact deployments can select mTLS/HMAC v2, durable replay and outbound recovery, atomic publication, lifecycle-v3, and bounded disconnected authority.	Choose a Backbone topology	Ordinary Backbone remains the default. V2/DDIL does not supply identity, consensus, automatic failover, arbitrary merging, or exactly-once external effects.
Defense Edge evaluation	Tooling can construct and verify exact immutable candidates and offline bundles under explicit profiles and injected lifecycle providers.	Use the release guide's evaluation boundary until a focused public evaluation guide is admitted.	This remains evaluation tooling. No shipping field artifact, accreditation, production trust provider, or representative hardware and power-loss qualification is implied.
Core, CLI, and Registry split	Grid Core, grid-cli, and grid-registry now have independent workspaces and source ownership, with combined provenance in product builds.	Prepare for Grid 0.65.0 and Publish Grid artifacts after the repository split	The split does not change formulas, create another evaluator, migrate stored Registry data, or make mutable path dependencies reproducible without exact revision records.

How to use this map

For authoring behavior, follow the linked canonical language or product page. For deployment behavior, compare the exact package's /api/capabilities, edition, target qualification, startup selectors, and retained source identities with the page you are reading. For evidence, use the version badge on the example, tutorial, corpus, source bundle, or film itself.

Items that point to a documentation follow-up are intentionally visible gaps from the August audit. They should become focused public guides only after their source contract and claim boundary are admitted into the Grid Core public export or an equally explicit site-owned authority.