service-contractsService Contracts
Keep APIs and events explicit, versioned, and compatible.
Production domain 02
Backend, API & Business Logic
3 capabilities and 3 controls define the canonical obligation set for this domain.
Applicability and claim boundary
This domain defines obligations. It does not prove that a specific repository or run satisfies them.
- Applicability
- Assess this domain when the authorized workload can affect its capabilities. Resolve every control as required, potentially affected, or not applicable before completion.
- Proof level
- The accepted formats below identify possible evidence inputs. A format alone does not establish semantic or authoritative assurance; provenance and the commissioned proof contract set the supported level.
- Claim boundary
- Static controls are requirements, not execution evidence, provider attestation, or proof of production readiness.
Capabilities
failure-resilienceFailure Resilience
Make dependency, timeout, retry, and idempotency behavior safe and testable.
request-observabilityRequest Observability
Preserve correlation and diagnostic context across request boundaries.
Controls
API-CONTRACT-001Service ContractsAPI and event contracts are versioned and compatibility-tested.
Accepted evidence format: Command outputAPI-FAILURE-001Failure ResilienceTimeout, retry, idempotency, and dependency-failure paths are proven.
Accepted evidence format: Command outputAPI-TRACE-001Request ObservabilityRequests carry end-to-end correlation and observable failure context.
Accepted evidence format: Artifact, Provider report