Design Pattern · September 2026
The person and the role are two records
Keep a role specification and a person's Eidolon as separate linked objects so work is not written for an office as though it were a personality.
Under the pillar Eidolons: working digital reflections
The split
The role specification states scope, decisions, authority, reporting, accepted outcomes, and the evidence the office must produce. It survives a change of occupant. The person's Eidolon states how the current holder thinks, communicates, decides, what they have done before, and what they consider settled.
Link them in both directions and date the link. When the person leaves, the role record stays and the Eidolon detaches.
Why it matters in practice
Merged records produce two failures. Work written for the office sounds impersonal and ignores how decisions are actually made here. Work written for the person assumes authority the office may not hold.
Put this to work
The person and the role are two records application record
Apply The person and the role are two records to a real piece of work and record what happened.
- For
- Operators redesigning a team, service, or AI workforce.
- What you keep
- A the person and the role are two records application record you can review, revise, and send.
- What counts as sound
- Names a real setting
- Shows the work before and after
- Records exceptions
- Uses an observable result
- Ends with keep, revise, or stop
Do not infer that a task can move merely because it can be described.
Nothing entered here is stored or sent. Review the prompt before sharing confidential, personal, patient, or privileged information.
Review the prompt
You can leave any field blank. The prompt will mark it as not provided.
If the record survives your review, send the question, evidence, unknowns, and requested next step.