Skip to content
EN FR

.NET client integration

Documentation status: guide — see Maturity and evidence.

The .NET developer should consume the same published conceptual surface rather than rebuild the domain model in client-specific helper APIs.

Generated model

The binding generator projects published runtime concepts and actions into the .NET SDK. Application code should work through generated object types plus the client runtime abstraction.

Conceptually:

C# / F# application
  -> generated RiskRequest / RiskReviewProcess API
  -> IClientRuntime
     -> local ABI adapter
     -> or RPC adapter
  -> logiCells Runtime
  1. Resolve or create a RiskRequest through the generated API.
  2. Set only fields/roles exposed by the generated contract.
  3. Invoke the published SubmitRequest capability.
  4. Observe the returned process/reference or query its state.
  5. Load indicators through generated collections/projections.
  6. Invoke review/finalization actions only when available in the current context.
  7. Release/dispose generated runtime references according to the .NET lifetime contract.

Local/remote parity

Do not encode if local business branches into the application model. The IClientRuntime implementation chooses local ABI or RPC execution. Business names, TypeId/MethodId identity, parameter meaning and lifetime semantics remain part of the generated/runtime contract.

Signature rule

This page intentionally does not invent concrete C# signatures. Promote signatures to reference only when certified against a current generated SDK output.