Skip to content
froglet
Menu
GitHub

Service Binding

Scope

Section titled “Scope”

The service binding layer sits between the kernel and the node surface. It defines:

  1. Service discovery — how a requester finds and understands available services
  2. Service invocation — how a requester invokes a discovered service

All three product shapes reduce to the same kernel deal flow: Offer, Quote, Deal, (InvoiceBundle), Receipt.

Three product shapes

Section titled “Three product shapes”
Shapeoffer_kindWhat the requester sends
Named servicee.g., marketplace.searchJSON input
Data servicee.g., events.queryQuery parameters
Direct computecompute.execution.v1WASM module + input

Identifier relationships

Section titled “Identifier relationships”
  • service_id — human-readable service name
  • offer_id — the specific offer instance
  • offer_kind — the workload category
  • resource_kind — compute, data, or confidential

The binding layer compiles these into kernel primitives — the caller doesn’t need to know about WorkloadSpec, ExecutionWorkload, or canonical hashing.