Carbide

03 / THE MODEL

One boundary.
Three planes.

Your domain stays in the contract and implementation. Generated code connects it to build-time tooling and a composable runtime.

01Pure Kotlin

Contract

Interfaces and serializable data. No transport, server, generated code, or deployment concern leaks into the service contract.

  • IService
  • Response<T>
  • Flow<T>
02Compile time

Build

KSP and compiler tooling derive descriptors, proxies, server bindings, wire schemas, and public API artifacts.

  • KSP
  • Compiler plugin
  • SDK generation
03Composable

Runtime

Hosts, transports, gateways, interceptors, diagnostics, and telemetry meet through small stable contracts.

  • Host
  • IBinding
  • IProxyFactory

04 / THE CALL PATH

Your code at
both ends.

The generated and operational machinery owns everything in between. Protocol and policy remain composition choices, not business concerns.

01Calleryour code
02Proxygenerated
03Policiesinterceptors
04ProtocolRSocket / JSON-RPC
05Serviceyour business code
Three interaction shapes

Fire-and-forget, request/response, and request stream are derived directly from the Kotlin signature.

One pivot abstraction

IBinding is the common seam for proxies, transports, gateways, interceptors, and generated server dispatch.