Read the relationship purposes
Fictional directory has S36→S37 line manager, S37→S38 line manager and S38→S36 dotted-line project contact. Local administration question route follows line-manager relations only and stops when that relation is absent. The dotted-line link is valid coordination data, not a third line-manager edge or new approval authority.
| From→to | Purpose | In administration route |
|---|---|---|
| S36→S37 | Line manager | Yes |
| S37→S38 | Line manager | Yes |
| S38→S36 | Project contact | No; retain separately |
Follow only the specified manager relation
- Match question to line-manager route rule
- Follow S36→S37→S38
- Stop at missing S38 line-manager link
- Keep dotted-line contact unchanged
Do not reinterpret a project-contact edge as a line-manager edge to continue the route.
Which staff appear in the administration route, and must the dotted-line link be deleted?
Show the worked answer
S36, S37, S38, then stop. The S38→S36 project contact stays valid; it is outside the selected relation purpose and does not create a manager-route cycle.
Retain coordination contacts separately
| Case | Action or result | Evidence boundary |
|---|---|---|
| Traverse every relation type | Wrong route | Mixes coordination with management |
| Filter line-manager purpose | Correct route | Stops atS38 without deleting contact |
The output names the route and terminal contact, not a new manager assignment. Preserve relationship type in exports so the receiving administrator can reproduce it.