Design Pattern · September 2026
Minimum viable company Eidolon
The smallest institutional reflection that changes AI output: what the company does, how it is organised, who decides, what it sells, and what it will not claim.
Under the pillar Eidolons: working digital reflections
What it holds
A first company Eidolon fits in an afternoon of writing and still changes results. What the organisation actually does in plain words. Its units and what each one owns. Its products and services as sold, not as described in marketing. Its customers by type. Its decision rights. Its terminology, including the words it uses differently from the rest of its industry. Its current priorities and its hard constraints.
Then the parts most teams skip: the unresolved questions, the places where the strategy and the observed behaviour differ, and the claims the company is not willing to make without evidence.
How to tell it is working
Give the same task to an engine with and without the file and have somebody who knows the company mark both. If the reader cannot tell which output had the reflection, the reflection is not yet carrying anything specific.
Put this to work
Minimum viable company Eidolon application record
Apply Minimum viable company Eidolon to a real piece of work and record what happened.
- For
- Operators redesigning a team, service, or AI workforce.
- What you keep
- A minimum viable company eidolon 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.