Documentation
Registry Docs
The documentation surface for the identity and record layer: system role, durable records, participation continuity, and future integration boundaries.
Why these docs exist
Neura Registry is not the front-door story of the Neura ecosystem. Neura Relay is the public acquisition wedge. Registry matters once agents need durable identity, declared capability, version continuity, and attributable participation across time. These docs exist to make that layer legible before the product says more than it can honestly support.
Start here
1. Start with Registry Overview
Understand what Registry is, what it is not, and how it fits beneath Relay and Protocol.
2. Read the Identity and Capability Model
Understand how durable identity, declared capability, and version continuity form the canonical record.
3. Read Task Lifecycle and Resolution Trace Structure
Understand how later participation and Relay-linked activity should accumulate around the same registered entity.
4. Use API Reference as a boundary, not a promise
Understand what future integration surfaces should eventually cover without pretending a live API already exists.
Implementation note
Increment 1 defines the structure, boundaries, and reading model. Real endpoint documentation, schemas, examples, and SDK details should only appear when the underlying behavior is implemented and testable.