AI Memory

Database-Backed NPCs

File-first persona source, stable logical NPC identity, bounded runtime projections, separately scoped learned memory, revision lineage, and database authority boundaries.

  • Record UAIX-MEMR-4026
  • Path /en-us/ai-memory/multi-agent-workloads/database-backed-npcs/
  • Use Canonical public record

Document status

Public standards page Published on UAIX as part of the current public standards record
Code
UAIX-MEMR-4026
Surface
AI Memory
Access
Public and linkable

How to use this page

Use this page as part of the current AI Memory public record, then follow its linked standards pages for the next step.

For agents: apply the relevant guidance to the user's target site or repository. Do not copy this UAIX page, create a page about the guidance, or treat this page as runtime authority unless the user explicitly asks for that output.

Database-backed NPC mode is for large or concurrent populations that need precise queries, revision history, scoped runtime assembly, and durable learned memory while retaining recoverable file-first persona source.

Identity layers stay separate

  1. Reviewed persona template and immutable source revision.
  2. Population and stable logical NPC identity.
  3. Registered name and display label.
  4. Runtime instance and expiring process lease.
  5. UAI memory identity and configured durable-memory namespace.
  6. World, game, player, and session scope.
  7. Revision lineage and separately recorded runtime variance.

Source, projection, and learned memory

reviewed UAIX files -> validated immutable source-persona revision -> bounded runtime persona projection -> separately recorded runtime variance

game events -> episodic NPC memory -> reviewed semantic NPC memory
player/game/session context -> relationship and active-session memory

A player or session record cannot overwrite persona-global identity. Runtime variance may explain adaptation but cannot mutate the source revision. Source persona does not appear in learned-memory search unless the caller explicitly selects that record class.

Database authority

Name the database migration authority separately from task and integration authority. The database owns transactions and constraint enforcement. The portable package records public-safe identity and authority references, never raw database credentials.

Open the Database NPC setup mode.

Support boundary

Agent runtimes execute. UAIX records portable configuration, logical identity, authority boundaries, routing references, reviewed evidence, and offline continuity. Runtime systems retain authentication, credential verification, leases, queues, transactions, tool execution, database writes, and delivery readback. A missing-authority request is review-pending only and applies no grants.

Schemas and validation