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

> Learn what the ledger records and which interface to use for application access

Neuro-Ledger is the Neuron's distributed audit and persistence layer. It records selected object changes in signed blocks and synchronizes them with authorized peers.

It is not a public cryptocurrency chain, a smart-contract virtual machine, or an API that every application writes to directly.

## Where it fits

```mermaid theme={null}
flowchart LR
  A[Application] --> I[Neuron interface]
  I --> O[Contracts, tokens, identities, and other objects]
  O --> L[Neuro-Ledger]
  L --> P[Authorized ledger peers]
```

Most developers use the [Agent API](/neuron-api/introduction), [contracts](/contracts/overview), or package APIs. The Neuron decides which resulting records belong in the ledger.

## What applications gain

* Important changes can be traced over time.
* Blocks and references are signed and can be checked for integrity.
* Synchronization is between identified, authorized peers rather than an anonymous global network.
* Access controls can protect ledger content that should not be public.

## Use a Neuron interface

The supported developer surface is the installed Neuron and its documented APIs. The Neuro-Ledger implementation repository is not required for application development and is not currently part of the public integration surface.

<CardGroup cols={2}>
  <Card title="How it works" icon="cubes" href="/neuro-ledger/how-it-works">
    Follow a record from persistence to a synchronized block.
  </Card>

  <Card title="Developer access" icon="code" href="/neuro-ledger/developer-access">
    See which interface to use for each task.
  </Card>
</CardGroup>