Capability boundaries: Runtime, LP and LCH

Documentation status: architecture. This page is a documentation boundary, not a commercial entitlement table.

The public Runtime/ABI/.NET programming model is the common execution boundary: published types and calls, generated bindings, IClientRuntime, local ABI execution and RPC execution.

Declarative application construction is documented as a model/runtime capability. H-Logic reasoning is documented as a reasoning layer over conceptual knowledge. Do not infer from a generic Runtime page that every H-Logic/LCH capability is present in every LP release, and do not infer a commercial license right from technical documentation.

Rule for cross-linking

A page that depends on a product-specific or release-specific capability must say so explicitly and link to an authoritative capability/platform matrix. If the current package cannot certify that matrix, the page remains architecture or roadmap rather than silently upgrading the claim.

.NET rule

The .NET binding preserves the conceptual contract but does not define product entitlement. Generated API presence and negotiated Runtime capability are the technical authorities for a concrete deployment.