Identity and access
The IdP authenticates subjects; Trusted Records authorizes organization/project, role, purpose and action. Configuration, processing and acceptance authority must follow separate responsibilities; revocation must affect active sessions/access.
Boundaries to preserve
The IdP authenticates subjects; Trusted Records authorizes organization/project, role, purpose and action. Configuration, processing and acceptance authority must follow separate responsibilities; revocation must affect active sessions/access.
Pre-deployment checks
Cross-check configuration, permissions, sample data, exceptions and approvers. Keep version-bound test records; architecture describes design rather than proving every control is implemented.
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