Entity

1. An entity is an unique instance of a entity type as described in a blueprint.
2. An entity exists as a recognised and asserted separate identity.
3. An entity can be one of (at present) 3 types.
   1. A creature - an entity composed of data attributes and functions.
   2. Matter - an entity composed only of data.
   3. A machine - an entity composed only of functions.
4. An entity has a Entity Interaction document (part of the blueprint) which allows it to interact with other entities in the cybersea. All interfaces in KOSH will be defined using a standard Logical ENTity Interaction Language (LENTIL). This will provide the entity specific content to the cybersea interaction service.
5. An entity can be in one of a fixed number of life cycle states
6. An entity can have either a transient or a permanent existence. This can be specified either in the blueprint itself or be specified at creation time. A transient entity must log itself as transient with the entity manager, along with an event that must occur for it to be deleted, whether it be triggered externally or internally. A permanent entity requires confirmation before it can be destroyed.