Govern
Record/version, authority, retention and holds
Trusted Records · Integration & Developer
Trusted Records ecosystem
Identity, permitted shared information and signing transactions connect to records under explicit purpose and authority.
Four connection routes
GoPaperless SSO
Shared identity for four portals; business authority remains organization- and project-scoped.
Read detailsRAR SSO
External identity route for authorized journeys; bind the result to subject, application and session.
Read detailsRAR ShareInfo
Permitted information sharing for a stated purpose; it does not confer unrestricted citizen-data access.
Read detailsRAR RSHUB
RAR connectivity requires an official contract before establishing Trusted Records functions.
Read detailsIdentity and transactions retain their roles
| Route | Intended purpose | Go-live prerequisite |
|---|---|---|
| GoPaperless SSO | Four-portal sessions | IdP configuration, mapping and authority |
| RAR SSO | External identity | Deployment authorization and contract |
| RAR ShareInfo | Permitted shared attributes | Purpose, grounds/authority and minimum data |
| RAR RSHUB | Functions defined by the RAR contract | Read the contract before functional claims |
Mobile-ID capability and service scope
Mobile-ID publishes RAR VNeID SSO/ShareInfo connectivity. Trusted Records deployment scope, authorization and contracts are not verified in the package. Exchange only permitted attributes with purpose/grounds and retention controls; SSO does not sign records.
Mobile-ID ↗Content, usability and evidence
Store content
Source bytes, replicas, locations and operator permissions
Preserve usability
Formats, representation information, migration/lineage
Preserve evidence
Contract-specific validation, profiles, receipts, renewal and verification
Backup / DR
Restore operations without replacing preservation layers
LTANS — long-term evidence preservation
Connect records lineage to Mobile-ID’s published LTANS capability; agree the Records configuration in a contract and profile.
Read detailsPreservation Profile Center
Choose preservation configurations by record class, designated community and required evidence. Illustrative profiles are not approved service offerings.
Read detailsPreservation standards and evidence
Standards → controls → workflows → contracts → evidence. Reference design mappings rather than Trusted Records certification.
Read detailsService Playground — task-based experience
Exercise a records workflow with forms, requests/responses and a timeline. Use synthetic data in offline simulation or a local HTTP mock.
Read detailsContinuous business context
Preserve organization, project, subject, record and transaction references across systems. A login result does not replace acceptance authority or record-access permission.
Connector readiness
The source architecture identifies GoPaperless SSO/Keycloak. RAR SSO, ShareInfo and RSHUB are integration routes to agree for Trusted Records; the baseline contains no service-specific released contract or deployment record. Confirm each route before go-live.
Content and evidence preservation
Choose a profile before admission. Separate content storage, readability, LTANS evidence and backup/DR. Mobile-ID connectivity is based on published capability; storage models, APIs, receipts and deployment authority require agreement. Hash/fixity checks do not replace signature or provenance validation.
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