THE LIFE OF AN EIDOL
Identity is not created. It is recognized, maintained, or withdrawn.
01
GENESIS EVENT
An EIDOL is formed when the system detects a coherent, independent presence.
No public registration ritual exists. No social verification is required.
Recognition is based on:
- System-level signal consistency
- Integrity of origin
- Absence of proxy behavior
The system does not ask who you are. It confirms that you are real.
02
OPERATIONAL PHASE
Once recognized, an EIDOL exists in an active state.
In this phase:
- Identity remains private
- Actions are compartmentalized
- No lateral visibility exists between EIDOLs
Presence does not imply exposure.
03
INTEGRITY HOLD
If the system detects uncertainty, the EIDOL is paused — not punished.
Triggers may include:
- Anomalous routing behavior
- Integrity mismatch
- Environmental risk escalation
During pause:
- No external access
- No data loss
- No escalation
Silence is preferred over compromise.
04
IRREVERSIBLE WITHDRAWAL
Termination is not deletion. It is permanent disassociation.
Causes include:
- Proven malicious intent
- Identity forgery
- Policy breach involving restricted entities
Effects:
- Identity permanently locked
- No re-entry path
- No identity recreation
The system forgets you — by design.
An EIDOL is free because it is finite.
Persistence without limits leads to control. This system rejects that.