> ## 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.

# Neuro object model

> See how accounts, identities, contracts, assets, states, wallets, and transactions relate

Neuro applications work with several long-lived objects. Use this map to decide which identifiers and state your application must store.

<Warning>
  This diagram explains application concepts; it is not an API schema. Use the generated operation pages for exact request and response fields.
</Warning>

## Relationship map

```text theme={null}
Neuron
  └── hosts Account access and application-facing services

Account
  ├── uses Keys
  ├── can apply for Legal Identities
  └── accesses Wallet capabilities

Legal Identity
  ├── identifies a Contract Party
  └── participates under a Contract Role

Smart Contract
  ├── defines Parties and Roles
  ├── contains Parameters and human-readable text
  └── may define a State Machine and Neuro-Feature creation

Neuro-Feature
  ├── is associated with its creation contract
  ├── may have State Machine state
  └── has an event and provenance history

Wallet
  └── exposes balances and Transactions
```

## Objects your application may store

| Object         | Created by                              | Identifier to persist                                | Mutable state                                 | Related workflow        |
| -------------- | --------------------------------------- | ---------------------------------------------------- | --------------------------------------------- | ----------------------- |
| Neuron         | Operator                                | Host/domain                                          | Configuration and installed capabilities      | Environment setup       |
| Account        | Onboarding flow or operator             | Account identifier or username as defined by the API | Verification, session, privileges             | Verified identity       |
| Key            | Account through cryptographic operation | `keyId` when returned                                | Key lifecycle requires verification           | Signatures and identity |
| Legal Identity | Account application plus review         | `legalId`                                            | Application and approval state                | Verified identity       |
| Smart Contract | Creator from an approved template       | Contract ID                                          | Proposal, signing, and lifecycle state        | Agreement               |
| Party and Role | Contract template and instance          | Contract-defined identity/role references            | Participation and signature state             | Agreement               |
| Neuro-Feature  | Approved creation-contract workflow     | Token/feature ID                                     | Ownership, notes, events, state-machine state | Product passport        |
| State Machine  | Contract/template definition            | Contract or feature association                      | Current state, variables, reports             | Asset lifecycle         |
| Wallet         | Neuron account capability               | Confirm with wallet API                              | Balance and pending transactions              | Payments                |
| Transaction    | Wallet/payment workflow                 | Transaction ID                                       | Provider-specific transaction state           | Payments                |

## Store returned identifiers and state

When an operation creates or retrieves a long-lived object, store the identifier returned by that operation. For asynchronous work, also store the latest returned status and the mechanism used to check for changes.