Narrative Protocol

Concepts

Core concepts of Narrative Protocol

Core Concepts

Narrative Protocol is a World State & Event Engine that manages complex simulations with versioned events, immutable state transitions, and AI-driven event execution.

System Architecture

The system uses a two-layer architecture:

LayerPurposeComponents
BlueprintDesign-time definitionsWorlds, Entity Schemas, Events, Event Versions
LiveRuntime state & executionDeployments, Entity Instances, Event Bindings, History

Terminology

  • Entity Schema: A blueprint that defines fields and types.
  • Entity Instance: Runtime data that follows an entity schema.
  • Event: A named action that can be executed.
  • Event Version: An immutable implementation of an event after publishing.
  • Deployment: A running instance of a world with isolated state.

Key Concepts

Architecture

Blueprint vs Live layer separation. How design-time definitions become runtime instances.

Entities

Multiple instances per schema, each with their own state.

Events

Events are the actions, triggers, or occurrences that drive state changes in your simulation.

Deployments

Running instances of a world with isolated state and on-chain oracle support.

AI Engine

Events are executed by an AI engine that computes state changes.

On-chain Oracle

Event records are pushed to Solana and/or NEAR for on-chain immutability.

Data Flow

World (Blueprint)
├── Entity Schemas (define structure)
│   └── Attributes
└── Events (define behavior)
    └── Event Versions (immutable after publish)

Deployment (Live, targetChains: ["solana-devnet"], etc.)
├── Entities (actual data)
├── Event Bindings (which versions to use)
└── Event History (execution records)
    ├── Solana Records (on-chain verification)
    └── NEAR Records (on-chain verification)

Getting Started

New to Narrative Protocol? Start with the Quickstart Guide to get running in 5 minutes.