Entity Lifecycle and Identity

These notes cover how ADK identities are bound to temporary game-engine objects and reconciled as players, NPCs, structures, and other entities appear, disappear, reconnect, become wounded, or respawn.

The game remains authoritative about physical presence. ADK preserves the logical continuity needed by framework services without mistaking a reused engine object or a short disconnection for the same lifecycle event.

Entity Host Binding

This defines how Brain-owned logical identities connect to host-engine shells. Host objects may appear, disappear, or change without changing the logical entity that Brain owns. The contract uses generation, binding, and lifecycle evidence. It decides if host actions are safe, stale, missing, or need reconciliation. This does not define global identity, accounts, spawn sites, inventory policy, persistence storage, or native pointer implementation.