Version boundary
Pin API/schema/profile versions in test evidence.
DEVELOPER GUIDEREFERENCE CONTRACT
Events / AsyncAPI
Asynchronous lifecycle, claim, evidence and connector events with correlation and replay-safe semantics.
CONTRACT PRINCIPLES
The protocol carries business semantics.
Each integration must preserve authority, policy, evidence and recovery context.
Correlation
Carry a correlation ID across request, event, connector and evidence records.
Idempotency
Protect material write operations from accidental replay.
Authority context
Never infer legal authority solely from transport success.
EVENT MODEL
Events are not databases.
Events carry correlation, subject, previous/resulting state and evidence references while systems of record remain explicit.
| Channel | Purpose | Key context |
|---|---|---|
| thing.lifecycle.changed | Material lifecycle transition | thingId, event, policyVersion, evidenceRef |
| claim.status.changed | Claim status/supersession | claimId, previous, result, evidenceRef |
| evidence.recorded | Evidence registration | evidenceId, source, digest, timestamp |
| connector.status.changed | Connector state | connectorId, mode, reason, recovery |
ARCHITECTURE WORKSHOP
Move from integration to evidence-backed approval.
Align product-group applicability, authority boundaries, portal journeys, integration contracts and evidence before committing to production claims.