Design Pattern · September 2026
Permissions across linked Eidolons
When one reflection links to another, decide what a reader inherits, what it must request, and what it may never see.
Under the pillar Eidolons: working digital reflections
The problem
A graph of reflections is only safe if permission travels with the link. A worker authorised to read the company Eidolon should not automatically read every executive, customer, and system Eidolon it references.
Give each reflection a tier, give each link a stated inheritance, and resolve access at read time against the worker's own authorisation rather than at authoring time.
Open question
Whether a projection can be generated automatically for a given tier without leaking through summary and inference is not established. Summaries of restricted material can restate it.
Put this to work
Permissions across linked Eidolons application record
Apply Permissions across linked Eidolons to a real piece of work and record what happened.
- For
- Operators redesigning a team, service, or AI workforce.
- What you keep
- A permissions across linked eidolons 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.