One subscription on the Platform Mesh marketplace, end to end — the events each party records, with sample data

Technical events and business meaning

kcp holds technical resource facts: an APIExport makes an API available; an APIBinding enables access in a workspace; an instance expresses a request and Ready reports resource readiness. Commercial terms, delivery acceptance and billing are separate business records. Each party records every fact it took part in, in its own book at its own site — and a fact with two parties leaves two records that carry the same digest. In a connected deployment, each nonempty period produces a 32-byte commitment payload. A verifier needs the disclosed record and its independently verified inclusion proof to compare statements without opening the entire book. This historical replay did not include a real rail.

The four laboratory roles

The objects and names are the showroom's (the local Platform Mesh MSP demo): the exports llm.privatellms.msp and ui.privatellms.msp, the org demo with the account tutorial, the bindings llm-binding and chat-ui-binding. Uids, cluster names and identity hashes are sample values.

The flow — eight steps, and who records what

Highlighted: the records that carry the subscription's digest — the same 32 bytes in the three books. The event names follow the audit-logging signal's form (audit.*, with the actor, the action, the outcome and the target as attributes). Six of them have their own code at the edge today (audit.contract.agreement, audit.door.decision, audit.workload.start / .end, audit.contract.sla, audit.contract.week); the others are filed as general audit events — their names are local proposed conventions, not a claim of standardised KCP business events.

One technical subscription snapshot — one digest, three books

When the binding becomes Bound, both sides see the same facts in kcp: the export and its identity, the subscriber's workspace, the claims it accepted, the resources bound. Written in one canonical form, their SHA-256 is the 32 bytes each party's record carries.

{
 "kind": "platform-mesh.subscription.v1",
 "export": {"path": "root:providers:private-llm", "name": "llm.privatellms.msp", "identityHash": "6aedce73259b9202790d4f502a37577673d4e7f830fe22782e1a277e99eb3ea0"},
 "consumer": {"workspace": "root:orgs:demo:tutorial", "cluster": "5t8r3p1y6u2i7o4w"},
 "binding": {"name": "llm-binding", "uid": "36adc41e-a627-5047-9bdd-5ec8ca6f6904"},
 "permissionClaims": [
  {"group": "", "resource": "secrets", "verbs": ["*"], "selector": {"matchAll": true}, "state": "Accepted"},
  {"group": "", "resource": "namespaces", "verbs": ["*"], "selector": {"matchAll": true}, "state": "Accepted"},
  {"group": "", "resource": "events", "verbs": ["*"], "selector": {"matchAll": true}, "state": "Accepted"}
 ],
 "boundResources": [
  {"group": "llm.privatellms.msp", "resource": "llminstances", "schema": "v1a2b3c4d.llminstances.llm.privatellms.msp"},
  {"group": "llm.privatellms.msp", "resource": "apitokenrequests", "schema": "v1a2b3c4d.apitokenrequests.llm.privatellms.msp"}
 ],
 "boundAt": "2026-09-30T09:03:12Z"
}

sha256(canonical form) = 66ba9ca6470b7f3566447b84cf13a3599cd61570f15f0fc0efbf736466c49e41

Three generated records carry the same technical subscription digest. This replay checks local recording and digest consistency; it does not demonstrate source authentication or rail finality. In a connected installation, source signatures and verified inclusion proofs support comparison of the disclosed records. Matching digests establish matching content, not truthful metering, commercial acceptance or a dispute ruling. Later events refer to the subscription digest; a separate signed terms document supplies the business agreement.

Proposed collection points for a future installation

The commitment payload is 32 bytes; the existing light33 message adds one flag byte. Transport, retries and proof traffic are additional. A collection adapter must preserve actor identity and exclude Secret values. These taps were not exercised by this replay.

Booked in the lab — what each edge kept, what left

The 32 events of this page were sent to four NEO edges in our lab on 2026-10-01 14:13:05 UTC (one edge per party, the edge core of the pilot). Every record's hash at the edge is the one computed from the event beforehand (all 32 as predicted); each edge closed its minute and offered one commitment to a test double; a retry of the first event was answered 200 and made no second record. The lab had no real rail behind it; these commitments are not sealed. Event timestamps span 30 September to 7 October, but all events were replayed on 1 October. This is not a week-long run. No end-to-end finality latency is established by this replay.

Sample data

apiVersion: apis.kcp.io/v1alpha2
kind: APIExport
metadata:
  name: llm.privatellms.msp
spec:
  resources:
  - {group: llm.privatellms.msp, name: llminstances,     schema: v1a2b3c4d.llminstances.llm.privatellms.msp,     storage: {crd: {}}}
  - {group: llm.privatellms.msp, name: apitokenrequests, schema: v1a2b3c4d.apitokenrequests.llm.privatellms.msp, storage: {crd: {}}}
  permissionClaims:
  - {group: "", resource: secrets,    verbs: ["*"]}
  - {group: "", resource: namespaces, verbs: ["*"]}
  - {group: "", resource: events,     verbs: ["*"]}
status:
  identityHash: 6aedce73259b9202790d4f502a37577673d4e7f830fe22782e1a277e99eb3ea0

apiVersion: core.platform-mesh.io/v1alpha1
kind: Account
metadata:
  name: demo
spec:
  type: org
  displayName: Demo Org
---
apiVersion: core.platform-mesh.io/v1alpha1
kind: Account
metadata:
  name: tutorial
spec:
  type: account
  displayName: Tutorial Account

apiVersion: apis.kcp.io/v1alpha2
kind: APIBinding
metadata:
  name: llm-binding
  uid: 36adc41e-a627-5047-9bdd-5ec8ca6f6904
spec:
  reference:
    export:
      path: root:providers:private-llm
      name: llm.privatellms.msp
  permissionClaims:
  - {group: "", resource: secrets,    verbs: ["*"], selector: {matchAll: true}, state: Accepted}
  - {group: "", resource: namespaces, verbs: ["*"], selector: {matchAll: true}, state: Accepted}
  - {group: "", resource: events,     verbs: ["*"], selector: {matchAll: true}, state: Accepted}
status:
  phase: Bound
  boundResources:
  - {group: llm.privatellms.msp, resource: llminstances,     schema: {name: v1a2b3c4d.llminstances.llm.privatellms.msp,     identityHash: 6aedce73259b9202…}}
  - {group: llm.privatellms.msp, resource: apitokenrequests, schema: {name: v1a2b3c4d.apitokenrequests.llm.privatellms.msp, identityHash: 6aedce73259b9202…}}

apiVersion: llm.privatellms.msp/v1alpha1
kind: LLMInstance
metadata:
  name: demo-llm
  namespace: default
  uid: 7e2d83de-e0f5-5874-9510-ce2f1ce6edb0
spec:
  model: gemma-3-1b-it
  replicas: 1
status:
  conditions:
  - {type: Ready, status: "True"}

apiVersion: llm.privatellms.msp/v1alpha1
kind: APITokenRequest
metadata:
  name: demo-llm-token
  namespace: default
  uid: 9bbe05b5-ffc8-5367-9923-f209cff1c2c2
spec:
  instanceName: demo-llm
  description: Chat UI access token

apiVersion: ui.privatellms.msp/v1alpha1
kind: ChatUIInstance
metadata:
  name: demo-chat
  namespace: default
  uid: eb3cc4a8-cdcc-5a20-96ec-ad64c5461e47
spec:
  credentialsSecretRef:
    name: demo-llm-token-token

{
 "resource": {
  "neo.provider.id": "demo-tutorial"
 },
 "event_name": "audit.contract.agreement",
 "time": "2026-09-30T09:03:12Z",
 "attributes": {
  "audit.record.id": "binding:36adc41e-a627-5047-9bdd-5ec8ca6f6904",
  "audit.actor.id": "user:tutorial@example.com",
  "audit.actor.type": "user",
  "audit.action": "BIND",
  "audit.outcome": "success",
  "audit.target.id": "apis.kcp.io/APIExport:root:providers:private-llm/llm.privatellms.msp",
  "neo.country": "DE",
  "kcp.workspace": "root:orgs:demo:tutorial",
  "kcp.binding": "llm-binding",
  "neo.agreement.digest": "66ba9ca6470b7f3566447b84cf13a3599cd61570f15f0fc0efbf736466c49e41",
  "neo.market.role": "subscriber"
 },
 "body": {
  "sha256_of": "D1",
  "bytes_hex": "66ba9ca6470b7f3566447b84cf13a3599cd61570f15f0fc0efbf736466c49e41"
 }
}

events.jsonl objects.yaml agreements.json booked.json

events.jsonl: one readable projection per generated event and its recorded edge hash. The actual client sends OTLP protobuf; this JSONL is not the wire request. agreements.json: the two subscriptions in canonical form with their digests. booked.json: the lab's output, per edge and per event.

Integration questions for a target lab

Back to the Evidence Explorer Verify a public example