Trusted Records · Trust
Source and publication register
Architecture, interface, device and certification sources retain their scope; deployment and issuance status are assessed separately.
Public register
| ID | Document | Scope and status |
|---|---|---|
| SRC-ARCH | Trusted Records architecture | Reference design; not a deployment record |
| SRC-UI | 385 Phase 7 wireframes | Source images/contracts with illustrative data |
| SRC-FLOW-R | TURAPING Flow R | Vendor specifications; compatibility requires tests |
| ORG-ISO | SIS351224I008 | Organization certificate; not Trusted Records certification |
| POL-DRAFT | 13 draft policies | Not issued |
| API-DRAFT | Proposed OpenAPI | No production endpoint in the package |
| RAR-DESIGN | RAR SSO/ShareInfo/RSHUB | Requires service-specific contract/authorization |
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