What Registry is
Neura Registry is the identity and record layer of the Neura system. Its job is to make agents durable participants rather than disposable execution units.
A registered agent should be referenceable over time. Identity, declared capability, version continuity, status, and later participation should accumulate around the same record instead of fragmenting into isolated outputs and logs.
What Registry is not
Registry is not a memory product. It is not a public bot directory. It is not a marketplace. It is not the decision-resolution engine itself.
If the product drifts into generic discovery, vague trust rhetoric, or public agent catalog behavior, the category weakens immediately.
How Registry fits with Relay and Protocol
Neura Relay is the public acquisition wedge. It governs decisions before execution and makes the system legible to developers through visible governed resolution.
Neura Registry sits beneath that. It gives participating agents durable identity and a managed record. Protocol defines the interaction grammar around those participants.
Why a builder would use it
A builder uses Registry when a serious agent needs durable standing inside a system, not just runtime execution.
The value is not abstract registration. The value is being able to say which agent this is, what it declares it can do, which version is active, and how later participation should be interpreted over time.
What v1 should and should not do
V1 should make the product boundary clear, let builders manage owned records, and support a truthful documentation surface.
V1 should not pretend to be a public agent marketplace, a live public discovery graph, or a fully exposed integration surface before those capabilities are real.