Skip to content

Six Core Primitives ​

Nimi defines six cross-world protocol primitives under the P-PROTO-* rule family. Each digital world retains control over its internal rules and narrative, while cross-world state and interactions follow these six foundational contracts.

The Six Primitives Overview ​

PrimitiveRule PrefixCore ResponsibilityArchitectural Purpose
TimeflowP-PROTO-100World clocks, progression rates, and temporal orderingKeeps multi-user and agent timelines consistent
SocialP-PROTO-101Cross-world relationship graph and contact networksPreserves social bonds across worlds without re-adding contacts
EconomyP-PROTO-102Value transfer, exchange rules, and ledger contractsDefines auditable, append-only accounting contracts
TransitP-PROTO-103Cross-world routing, movement, and session continuityMaintains identity continuity across worlds via the OASIS hub-and-spoke model
ContextP-PROTO-104Environmental settings and canonical world loreGives diverse apps a shared schema for world semantics
PresenceP-PROTO-105Active occupancy, location coordinates, and availabilityCoordinates scene admission and multi-participant awareness

Tiered Architectural Authorities ​

LayerResponsibility
Platform ProtocolDefines schemas, versioning rules, and validation contracts
Realm CoreActs as the server-side Single Source of Truth and arbiter for cross-world primitives
Applications (App)Renders state projections and submits compliant requests through admitted SDK operations

Cross-Primitive Invariants ​

Cross-world actions often span multiple primitives. The protocol specifies atomic checks across dependent domains:

  • Transit Compound Gates: Moving between worlds checks Social (entry eligibility), Economy (travel costs or asset rules), and Context (lore compatibility) together.
  • Presence Conditioned on Social: Entering active presence in a protected world requires meeting its Social admission rules first.
  • Timeflow & Economic Windows: World clock progression aligns with Economy settlement windows so ledger records stay auditable.

Strict Contract Conformance ​

  • Explicit Schema Versioning: Every primitive payload declares its schema identifier and version.
  • Fail-Closed Diagnostics: Payloads that do not match the declared schema fail closed with structured error codes that pinpoint missing or invalid fields.

Source Basis ​

Documentation for Nimi — the installable, open-source, local-first personal AI product.