Architectural decision
Membership is not Assignment
Belonging and working have different lifecycles.
Before · Conflated concepts
MembershipAssignment
After · Explicit boundaries
Relationships
- Production Membership performs work through Production Assignment
- Production Assignment retains participation Production Membership
Problem and decision
One membership field cannot accurately describe several simultaneous or successive jobs.
Attach work assignments to stable production participation.
Alternatives considered
- Put one job on membership
- Create a new membership for each role
Tradeoffs and consequences
Work history needs its own identity and lifecycle.
Changing work preserves the person and participation.
Related architecture
Related workflows
Current architectural direction; this record does not establish production release.