Version boundary
Pin API/schema/profile versions in test evidence.
DEVELOPER GUIDEREFERENCE CONTRACT
Schemas
Canonical JSON schema baseline for claims, evidence, lifecycle events and connector status.
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.
IMPLEMENTATION NOTES
Keep the design auditable.
Use synthetic test data, explicit environment separation and versioned evidence before production approval.
Sandbox
Synthetic data · no production secrets
Schemas
Canonical models · versioned
Evidence
Test result · limitation · owner
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.