Version boundary
Pin API/schema/profile versions in test evidence.
DEVELOPER GUIDEREFERENCE CONTRACT
Conformance Lab
Test exact profile/version/environment combinations and retain evidence for release approval.
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.
CONFORMANCE RECORD
Test the exact combination.
Profile + version + environment + connector/client + test corpus + result + limitation + evidence.
| Field | Required |
|---|---|
| Profile/version | Yes |
| Environment | Yes |
| Implementation/client | Yes |
| Test corpus | Yes |
| Result | Yes |
| Known limitation | Yes |
| Evidence ID | Yes |
| Owner/review date | Yes |
TEST SUITE CATALOGUE
Positive + negative cases, state and evidence.
Reference tests are not presented as executed results unless evidence is linked.
| Test ID | Purpose | Condition | Input | Expected Result | Case | Maturity |
|---|---|---|---|---|---|---|
| CT-RES-001 | Resolver success | Official identifier resolves | Known identifier | Resolved context + source authority + evidence reference | Positive | REFERENCE |
| CT-RES-002 | Resolver ambiguity | Alias collision is not silently accepted | Ambiguous alias | Conflict/ambiguity response; no false authoritative result | Negative | REFERENCE |
| CT-DPP-001 | DPP validation success | Applicable profile validates required fields | Valid DPP draft | Validated state + validation evidence | Positive | REFERENCE |
| CT-DPP-002 | DPP validation failure | Missing mandatory field is rejected | Incomplete DPP | Validation error + no publish transition | Negative | REFERENCE |
| CT-POL-001 | Restricted disclosure | Insufficient scope cannot reveal restricted field | Authenticated user without mandate | Narrow/denied view + policy evidence | Negative | REFERENCE |
| CT-REL-001 | Ownership transfer | Transfer requires evidence/acceptance | Valid transfer request | Pending/accepted transition + evidence | Positive | REFERENCE |
| CT-CON-001 | Registry timeout | Transport failure does not equal business rejection | Timeout | Retry/reconciliation state + evidence | Negative | REFERENCE |
| CT-CON-002 | Registry mismatch | Contradictory external status triggers reconciliation | Mismatched status | Reconciliation required; external authority preserved | Negative | REFERENCE |
| CT-DEV-001 | Attestation success | Valid evidence is appraised separately from certificate status | Valid attestation | Appraisal decision + evidence | Positive | REFERENCE |
| CT-DEV-002 | Attestation failure | Failed runtime appraisal leads to policy action | Invalid/stale evidence | Failed/quarantine decision + audit | Negative | REFERENCE |
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.