Native Runtime: practical programming paths

Documentation status: guide. This section synthesizes the LaTeX book logiCells Runtime Programming with RadStudio. It explains implementation paths; the published API and evidence rules remain authoritative for exact signatures and platform guarantees.

Start with the task, not a class catalog. Each link below goes directly to the decision or workflow in question.

I need to…	Open directly
Understand MODEL, APPLICATION, SEMANTIC and execution state	Layers, authorities and state
Initialize an application without confusing the Runtime layers	Native end-to-end path
Build or query conceptual knowledge	Hypergraph and H-Logic
Execute procedural code or expose a native call to FPL	FPL and native ABI
Publish runtime services or exchange messages	Services and communication
Connect collections, SQL and serialization	Data and persistence
Manage ownership, sessions and shutdown	Lifecycle and ownership
Verify an extension before deployment	Testing and production
Combine reasoning with LLM or Tensor runtime	Neuro-symbolic and resident inference
Determine whether an example or capability is proven	Documentation authority and status

Boundaries to keep explicit

The Runtime exposes composable layers; an application does not need to enable every layer. Native Runtime access is one engineering surface, whereas generated SDKs and declarative application construction serve other entry points over the published contracts.

Use operations and deployment for production configuration and the ABI reference for binary contract details. The LaTeX guide is a task-oriented companion, not a replacement for source, generated ABI manifests or current tests.

Source traceability

Derived from Runtime/logiCells Runtime Programming with RadStudio/main-matter.tex, runtime-overview.tex and runtime-layer-map-and-programming-paths.tex in the provided sources. The detailed pages identify their own source chapters.