Errors and next actions
A consistent error envelope guides recovery without disclosing sensitive data.
Error classification
401: authenticate/check issuer, audience and expiry. 403: request context-specific permission rather than evade authorization. 404: check the identifier within scope. 409: reread version or change keys after verifying state. 422: correct details. 429: honor Retry-After when provided. 503: check state and apply eligible retries.
Diagnostic data
code, message, requestId, correlationId, retryable and details form the proposed envelope. Logs retain minimum identifiers/states/errors rather than credentials, files or sensitive metadata. Support requests include correlation and synthetic reproduction steps.
Continue the workflow
Two journeys, one records lifecycle
Connect paper and born-digital records through persistent identifiers, policies and evidence.
Read detailsIntegration quickstart
Exercise ingest → job tracking → registration → verification with synthetic data.
Read detailsIntegrity, provenance and evidence
Each evidence type answers a different question; hashes, timestamps and approvals are not interchangeable.
Read detailsStart with a verifiable scope.
Agree record classes, quality criteria, permissions and evidence before scaling.
Plan assessment