Summary
Wherever a participant's pseudonym appears in the app, it should be actionable — showing a profile card with basic stats and the ability to extend or withdraw trust in context.
Profile card contents
- Trust stats: how many participants trust them (in), how many they trust (out) — counts only, never names
- Current relationship state: none / you trust them / they trust you / mutual
- Context-sensitive action: Extend trust or Withdraw trust
- Basic info: join date, activity level / participation summary
- Link through to a full profile page for more detail (contribution history, etc.)
Where it appears
Anywhere a pseudonym is rendered: authored content, comments, UserGroup member lists, etc.
Availability
Available for any participant regardless of trust graph distance. No restriction needed — the graph already filters what content and participants you encounter in practice. The trust action itself remains voluntary.
UX pattern
- Popup/card for quick in-context trust actions (low friction)
- Full profile page for deeper context (contribution history, public activity)
Bounded context
Read side likely spans Reputation (trust stats, relationship state) and whichever context owns participation/activity data. Trust actions dispatch to Reputation.
Summary
Wherever a participant's pseudonym appears in the app, it should be actionable — showing a profile card with basic stats and the ability to extend or withdraw trust in context.
Profile card contents
Where it appears
Anywhere a pseudonym is rendered: authored content, comments, UserGroup member lists, etc.
Availability
Available for any participant regardless of trust graph distance. No restriction needed — the graph already filters what content and participants you encounter in practice. The trust action itself remains voluntary.
UX pattern
Bounded context
Read side likely spans
Reputation(trust stats, relationship state) and whichever context owns participation/activity data. Trust actions dispatch toReputation.