Versioning, changelog and deprecation
TR API 1.1.0-proposed · OpenAPI 3.1.1 · no released API in this package.
Contract changes
Retain nine v2 operations; add proposed device-command and payment/invoice designs for discussion, with tags, constraints, examples and an event catalog. JSON/YAML/Swagger derive from one spec. This is not a production compatibility commitment.
Release conditions
Confirm owner, endpoint, OAuth profile, schemas, limits, signing and SLA; run authorized sandbox contract tests. Breaking changes require a new version and migration guide. No deprecation schedule is issued.
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