Distinguish relationship purposes
Synthetic S30 has primary team T-A and secondary project circle T-C. Supplied decision replaces primary with T-B; T-C remains. Local administration permits exactly one primary team and any listed secondary memberships. This is organisational display/routing data, not software access or financial allocation.
| Relation | Before | After |
|---|---|---|
| Primary | T-A | T-B |
| Secondary | T-C | T-C |
Apply the primary-team decision
- Read primary-change scope
- End active primary T-A
- Start primary T-B
- Retain secondary T-C
Adding T-B without ending T-A would violate the one-primary rule.
How many active relationships and primary relationships remain?
Show the worked answer
Two active relationships, one primary T-B and one secondary T-C. T-A remains historical.
Check secondary memberships unchanged
| Case | Action or result | Evidence boundary |
|---|---|---|
| Overwrite all memberships withT-B | Reject | Would remove T-C |
| Change primary only | Accept | Preserves secondary purpose |
Use relationship purpose in the export. A flat team-name field cannot preserve this two-purpose record.