Trust Graph Lens Matrix
What each party sees when they look at every other party
The Governing Principle
Same underlying data. Different views per relationship type. Derived signals for third parties — never raw records. Progressive consent: standard → with consent → advanced consent. AI generates all derived representations. Raw records are never exposed. The lens matrix does not change the underlying data. It changes what is visible based on relationship context and consent.View 1: Buyer or Resident → Principal
View 2: Buyer or Resident → Agent (Solo or Org Staff)
View 3: Buyer or Resident → Organisation (BRN)
View 4: Buyer or Resident → Property (Property RIN)
View 5: Principal → Buyer or Resident
View 6: Agent (Solo or Org Staff) → Buyer or Resident
View 7: Bank/Lender → Buyer or Resident
View 8: Service Provider → Service Request
View 9: Anyone → Service Provider
The Consent Consent Mechanism
Standard consent is granted when a user submits a rental application. It covers: Score tier, payment timeliness rate, tenancy duration, exit quality. It does not expire automatically — but the user can revoke it at any time. Advanced consent is granted explicitly per institution per purpose. It requires a named institution, named purpose, time limit, and explicit acknowledgment (checkbox + PIN or biometric). See10_Compliance/01_ndpa_consent_framework.md for full language requirements.
Federated computation consent is a separate consent with specific language:
- Named institution
- Explicit statement that raw data stays on Leja’s servers
- Time limit (30 days or per-application)
- Revocation path clearly stated