Prerequisites and installation contract

Documentation status: architecture. The sources available to this documentation set do not certify a single public installer or download command for every target.

A first-run page must separate three things: the managed application prerequisites, the native/local Runtime assets, and the remote Runtime endpoint.

.NET consumer prerequisites

A .NET application should consume the generated/public client binding as an ordinary dependency. A production package may separate abstractions, client wrappers, local-native assets, RPC transport and F# conveniences. Exact package names are release-management choices and must be taken from the release being installed.

Local mode

Local execution requires a native Runtime matching the process architecture and its dependent native libraries. Do not rely on Any CPU when native Runtime libraries are loaded; choose an explicit Runtime Identifier when the release requires it.

Remote mode

Remote execution does not require the application process to load the native Runtime locally. It does require a reachable Runtime endpoint and compatible published capabilities.

Publication gate

An installation recipe becomes reference only when it identifies: release/version, artifact or package source, supported Runtime Identifier, dependency list, installation command or installer action, verification command, and expected result. Until then this page is the contract that release documentation must satisfy.

Discovery versus installation

logiCells.com — Developer start is the discovery/orientation entry point. This .net page is the technical authority for prerequisites and installation evidence. If an installer, package or command is not certified here for a release, the .com site must not invent one.