Architectural decision
Person is not Profile
Identity persists while its presentation changes.
Before · Conflated concepts
PersonProfile
After · Explicit boundaries
Relationships
- Person has presentation Profile
Problem and decision
Using a public profile as identity couples biography and discoverability to operational participation.
Keep durable person identity separate from profile presentation.
Alternatives considered
- Use the profile as the person record
- Recreate a person for every production
Tradeoffs and consequences
Additional joins and projection rules are required.
A profile can change without rewriting production work.
Related architecture
Related workflows
Current architectural direction; this record does not establish production release.