Read name purpose and source
Fictional S46 has independently confirmed directory preferred display “Sam”, badge print “Sam Lee” and internal document display “S. Lee”. Local administration treats these as three purpose-specific values, all linked to S46. A directory refresh uses “Sam” only in that output; it does not instruct badge or document replacement. No legal-name determination or identity merge is involved.
| Purpose | Supplied value | Refresh disposition |
|---|---|---|
| Directory | Sam | Use for directory |
| Badge | Sam Lee | Preserve badge value |
| Internal document | S. Lee | Preserve document value |
Select the matching output value
- Match output purpose to S46 source field
- Use directory preferred Sam
- Retain Sam Lee and S. Lee in their fields
- Verify all three still link S46
A new badge-name request needs its own supplied badge-purpose decision; directory preference alone cannot replace it.
What names appear in the directory and badge outputs after the directory refresh?
Show the worked answer
Directory “Sam”, badge “Sam Lee”; internal document stays “S. Lee”. Three values remain valid for their supplied purposes under one staff identity S46.
Preserve the other legitimate names
| Case | Action or result | Evidence boundary |
|---|---|---|
| Replace every name with Sam | Reject global overwrite | Badge/document purposes unchanged |
| Select each supplied purpose field | Accept | Distinct outputs preserve sources |
Store purpose beside each name field and output reference. A disagreement between these three strings is not an identity conflict in this supplied model.