HTTP examples and downloads
Proposed contracts, HTTP examples and synthetic data are packaged for offline use.
Contract bundle and catalogs
Usage
OpenAPI JSON describes proposed endpoints/scopes/schemas. HTTP examples use an .invalid host and token placeholder; they do not call live APIs. The webhook verifier uses a sample secret and synthetic signatures; it is not a published SDK.
Versioning
Examples use /v1/ and schemaVersion 1.0 as proposed design choices. Breaking changes need a new contract version, migration and agreed transition. Website build/version information remains in internal documentation.
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