Choosing the right binding
Documentation status: reference — see Maturity and evidence.
A binding is an idiomatic projection of the public logiCells Runtime contracts into a developer ecosystem. Choosing a binding does not change the engine.
Start with architecture, not language
Before choosing C#, F#, Python, Rust, Java, or another language, determine:
- is the Runtime local or remote?
- is the engine embedded in-process or operated as a service?
- what latency, security, and deployment constraints apply?
- which published capabilities are required?
- what level of control is needed for ownership, callbacks, async, and cancellation?
Today: .NET
The .NET binding is currently the most fully documented surface. It provides the same generated object model for local and remote execution through IClientRuntime.
Generated .NET API
|
v
IClientRuntime
| |
Native ABI RPC
Future bindings
Future SDKs should preserve the same principle: a shared Runtime contract, an idiomatic projection per language, and explicit operational differences.
The documentation must not invent an API for an unpublished binding. A future surface is labeled as a roadmap item or target, never as an available contract.