Actual Platform Mesh
Resource observations and two recorded LLM requests. The published lab report records N8 FINAL evidence (NEO8ra-GA #44). The tests on iron start 15 October 2026.
Platform Mesh × Cotrugli
One service lifecycle.
Every party's perspective.
Follow a service from API access to delivery. Compare what the provider, platform and customer recorded. Check the evidence for yourself.
An independent Cotrugli demonstration using Platform Mesh and kcp.
Understand the business
Complete cleanup, a failed request and differing measurements. These new fixtures are unsealed.
Inspect the proof
A public synthetic example with signatures and Merkle inclusion. Its demo checkpoint is not N8 FINAL.
01 / Service lifecycle
Access, agreement and acceptance.
An APIBinding enables technical access. Business terms require separate agreement; an instance becoming Ready is followed by delivery and explicit customer acceptance.
- 01
Publish
APIExportMake the provider's API available.
- 02
Bind
APIBindingEnable the API and accept permission claims.
- 03
Agree
Signed termsRecord the price, scope and SLA separately.
- 04
Deliver
Service resultObserve execution and record customer acceptance.
- 05
Close
Confirmed cleanupRemove both services and revoke access.
Explore a business case
Choose a scenario to compare the parties and their recorded events.
Compare with the actual lab service request
Recorded on 1 October 2026
Loading historical agreement…
Customer and Private LLM provider signed the same test terms.
—test tariff / request
—latency target
—measured response
No invoice or payment was executed. Provider-reported usage is not an independent meter.
Loading…02 / Verify an example
A result you can check.
Run four signature and inclusion checks in your browser, or download the same example and verify it offline. No account, upload or access to private records is needed.
Public proof fixture
Demo keys- 1Recompute each signed event's canonical bytes
- 2Verify its owner's Ed25519 signature
- 3Check the Merkle inclusion path
- 4Verify the signed demo checkpoint and key pins
Ready to verify locally.
What the result means
A valid result shows that the included events match their signatures and the demo checkpoint. A changed quantity must be rejected.
It does not establish the truth of a meter, resolve a dispute or prove business acceptance. Demo keys do not identify real organisations.
This fixture is not a NEO rail confirmation. The historical report and its N8 FINAL claims remain a separate evidence set; the published lab report is linked above. This page does not reverify those private confirmations.
Download offline verification kit ↓Node.js 20+ · no packages requirednode verify/verify.mjs
03 / Federation workload
150 identities. Their own records.
A completed synthetic workload surrounds the actual service flow. Identities keep their keys and history when active roles rotate.
130 fan10 buyers10 sellers
Two accelerated rounds, not four elapsed hours. These are simulated participants, not 150 independent companies.
04 / Ready for integration
One event contract. Existing systems.
Each illustrative event carries its case, order, agreement, organisation and resource identifiers. A host application can render the explorer and map its events to existing business records.
Embed the explorer
Serve this static module under a subpath, or use its explicit embed mode. It needs no credentials or live service.
Preview embed mode ↗Use the event contract
Versioned JSON schema, stable event IDs and separate execution, acceptance, evidence and payment states.
Event schema ↗Connect through fed8ra
Proposed mappings reuse collaborations, evidence and company roles. Authorisation and verified rail receipts stay with fed8ra.
Integration handoff ↗Integration status: prepared, not connected.
The source adapter, company identity mapping and authenticated import need to be validated against the deployed fed8ra version. Only the existing binary commitment boundary may send to the rail.
Run scope, source versions and reproducibility
Recorded stack: Platform Mesh charts 0.3.0 · kcp 0.31.0 · Private LLM 2.10.1 · Chat UI 0.10.6.
This independent demo does not imply SAP endorsement. No real invoices, payments or Chamber rulings are produced.
Historical eight-stage event reference → · Official KCP APIBinding reference ↗