> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neuro-tech.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Glossary

> Key terms and concepts used across the Neuro platform

This page collects the most important terms used across the platform.

You do not need to understand every term before you begin, but having a shared vocabulary makes the rest of the documentation much easier to follow.

<ResponseField name="Neuron">
  The core runtime and broker in the Neuro platform. It enables secure, federated interaction across domains and hosts higher-level capabilities such as identities, contracts, tokens, and ledger-backed services.
</ResponseField>

<ResponseField name="Neuro-Ledger">
  The distributed audit and persistence layer used by the platform. It is designed to support auditable, distributed systems without depending on a traditional blockchain model.
</ResponseField>

<ResponseField name="Trust Provider">
  A trusted actor within a domain that validates identities, approves or governs important platform objects, and contributes trust to the network through signatures and policy. Often described as a digital equivalent of a notary.
</ResponseField>

<ResponseField name="Network identity">
  The identity used to participate in the network as a connected actor or account. It identifies who is communicating at the platform level.
</ResponseField>

<ResponseField name="Legal identity">
  A stronger, cryptographically protected identity tied to a real legal actor such as a person or organization. Legal identities are used when trust, signatures, ownership, or compliance matter.
</ResponseField>

<ResponseField name="Smart contract">
  A structured digital agreement used in the platform. In Neuro, smart contracts combine human-readable and machine-readable content, support signatures and lifecycle rules, and are designed to work across domains.
</ResponseField>

<ResponseField name="Token">
  A digital instrument tied to ownership, agreements, and traceable events. In the platform, tokens can represent NFTs, asset-backed instruments, rights, or other digital and cyber-physical assets.
</ResponseField>

<ResponseField name="Neuro-Feature">
  The Neuro platform's token model for digital instruments and tokenized assets. Neuro-Features are created using smart contracts and can represent ownership, rights, or asset-backed structures.
</ResponseField>

<ResponseField name="eDaler">
  A federated digital payment mechanism used in the broader platform model. It can be linked to contracts, tokens, and programmable payment flows.
</ResponseField>

<ResponseField name="Federation">
  A model where multiple domains manage their own infrastructure but still interoperate in a shared framework. Federation is a core part of how Neuro supports cross-domain interaction.
</ResponseField>

<ResponseField name="Domain">
  A distinct operating boundary in the federated network. Each domain can manage its own users, services, policies, and trust relationships.
</ResponseField>

<ResponseField name="Signature">
  A cryptographic proof attached to an identity, contract, or other platform object to verify integrity and authorship. Signatures are central to how Neuro establishes trust.
</ResponseField>

<ResponseField name="Public key">
  The part of a cryptographic key pair used to validate signatures or encrypted interactions.
</ResponseField>

<ResponseField name="Private key">
  The secret part of a cryptographic key pair used to create signatures. In Neuro identity material, private keys are intended to remain under the control of the client.
</ResponseField>

<ResponseField name="State machine">
  A structured model for representing workflows as states and allowed transitions over time. In Neuro, state machines can be connected to contracts, tokens, and programmable payment logic.
</ResponseField>

<ResponseField name="Agent API / Neuron API">
  The API surface used by external systems that do not connect directly through XMPP bindings. The Agent API lets backend agents perform tasks such as messaging, account creation, and contract signing without maintaining a live XMPP connection.
</ResponseField>

<ResponseField name="XMPP">
  The federated communication protocol underlying the Neuron's communication model. It provides the base for secure, cross-domain messaging and interaction.
</ResponseField>

<ResponseField name="Auditability">
  The ability to inspect and verify what happened, who acted, and what was recorded. Auditability is one of the main reasons the platform uses Neuro-Ledger together with signatures and identities.
</ResponseField>

## Further reading

<CardGroup cols={3}>
  <Card title="Neuro-Foundation" icon="globe" href="https://neuro-foundation.io">
    Platform specification and standards
  </Card>

  <Card title="Neuro Documentation" icon="book" href="https://lab.tagroot.io/Documentation.md">
    Neuron and associated technologies
  </Card>

  <Card title="Neuro Community" icon="users" href="https://lab.tagroot.io/Community.md">
    Tutorials and implementation guides
  </Card>
</CardGroup>