SDKs and bindings

Documentation status: reference — see Maturity and evidence.

Bindings project the public logiCells Runtime contracts into a developer ecosystem. They do not define separate engines.

Application
   -> SDK / binding
   -> public Runtime contract
   -> local or remote Runtime
   -> logiCells Engine

Fast paths

• .NET binding
• Choose a binding
• ABI contracts

Currently documented binding

• .NET — C# / F#
• Binding generation pipeline

Planned bindings

See the roadmap and status model.

The documentation architecture is ready for Python, Rust, Java, Node.js, Go, and additional bindings. A binding page should only be published when its contract is defined well enough to document accurately.

Publication rule

A binding page must clearly distinguish:

• generated and available API;
• API generated when a member is published;
• next-generation binding target;
• application pattern built above the binding.