Glossary

Stable identifier for an entity, often in the did:ixo: namespace; see Identity and credentials.

Standard registration for a digital twin: DID, type, protocol, controllers, metadata; see Core concepts — Domains and Entity domains.

The modeled counterpart of a real-world subject on the stack; see Digital twins.

Structured assertion with evidence, evaluated under protocol rules; see Claims.

Issuer-signed, verifier-checkable credential about a subject DID; see Credential issuance.

Party authorized to update a DID document or domain record within protocol rules; see Identity and credentials.

Programmable organizational domain—a secure place for people, agents, and services to cooperate; see PODs.

Governed sequence of steps coordinating work; see Core concepts and user guides such as Build a flow.

Reusable protocol template (rules, rubrics, evidence expectations); see Build a blueprint.

Verification, measurement, or decision-support capability—often AI-assisted; see IXO Oracles and Oracle architecture.

A concrete interface family (for example RPC or a specific REST service); see API introduction.

Node-level access to IXO Protocol state and transactions (RPC, REST over gRPC); compare the matrix in API introduction.

Operator-hosted HTTP or GraphQL services over indexed or app-layer data (Blocksync, Registry, Matrix state bot, USSD); auth varies by deployment (Authentication matrix).

Indexed query layer for chain-derived data; see IXO Blocksync and Blocksync GraphQL API.

Encrypted cooperation and data-room layer; see IXO Matrix.

Application API for Impact Hub Registry workflows; see Registry and Registry API.

Intelligent cooperating system over IXO-backed state—workspaces, tools, governed automation; see Qi.

Model of connected verifiable state; see IXO Graph.