Design Pattern · September 2026
The customer Eidolon and its limits
Enough reflection of an account that anyone can prepare before acting, bounded by confidentiality terms, privacy obligations, and contractual restrictions.
Under the pillar Eidolons: working digital reflections
The content
What the customer does, why they buy, who decides, what they run, what has been promised, what has gone wrong, what remains open, and the evidence behind each claim that matters. Written so a competent stranger could prepare for a call from it.
The boundary
Decide before writing which material is contractually restricted, personally identifying, or shared under confidentiality. Hold restricted material in a separate tier with its own access rules, and let the general projection reference its existence without reproducing it.
A reflection that quietly accumulates material the company had no right to retain is a liability, however useful it is.
Put this to work
The customer Eidolon and its limits application record
Apply The customer Eidolon and its limits to a real piece of work and record what happened.
- For
- Operators redesigning a team, service, or AI workforce.
- What you keep
- A the customer eidolon and its limits 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.