01 /
Credential relationships
Connect subjects, issuers, verifications, and proofs so a reviewer can understand where a claim comes from.

Trust Graph / Relationship context
Connect claims, credentials, issuers, and lifecycle events in a traceable model of relationships—not a shortcut to a verdict.
Trust is relational
A credential has an issuer. A verification has evidence. An assertion has a purpose and a point in time. Understanding those relationships makes a trust workflow more explainable.
Trust Graph is the architectural model for connecting that context across identity, institutions, credentials, and reputation signals while keeping access boundaries intact.
Relationships with meaning
01 /
Connect subjects, issuers, verifications, and proofs so a reviewer can understand where a claim comes from.
02 /
Represent the responsibilities and scopes behind a relationship. A connection alone does not establish endorsement or authority.
03 /
Keep lifecycle events, expiry, and dispute history available to authorised review rather than presenting a timeless risk label.
Read a relationship responsibly
A useful graph answers a bounded question. It should not become unrestricted discovery of people, organisations, or private evidence.
Start with the authorised question and relevant scope. Do not expand access simply because two records are connected.
Identify who made the assertion, what evidence supports it, and the relationship between the issuer and the subject.
Distinguish current, expired, revoked, and disputed evidence. A historical connection is not necessarily valid today.
Present the reasons and uncertainty behind a conclusion. High-risk outcomes require an accountable review path.

Context supports judgement
Reviewers need to understand why a signal matters, not just that two points are connected. Clear provenance helps them ask the right questions and recognise missing evidence.
The aim is informed judgement with human recourse—not guilt by association, indiscriminate surveillance, or an unexplained score.
Bounded by policy
Tenant isolation and purpose-specific access must remain enforceable across relationships. Sensitive personal evidence stays protected; a graph view does not grant permission to disclose it.
This page describes the product architecture, not a live graph explorer or a measure of deployed network size. It does not query people or expose private relationships.
Review the security approachConnect the model to the workflow
Explore how the API layer connects verification, evidence, and lifecycle events to a product experience.