Accounts and Legal Identities

An Account establishes access to a Neuron. A Legal Identity represents an actor for workflows that require reviewed identity data, signatures, contract participation, or another stronger trust decision. They are related, but they are not interchangeable.

Object	Answers	Typical lifecycle
Account	“Which Neuron principal is authenticated?”	Created, contact details verified where required, authenticated, recovered or transferred
Legal Identity application	“Which identity is being submitted for review?”	Prepared, submitted with required attributes and attachments, reviewed
Legal Identity	“Which reviewed actor participates in this workflow?”	Returned with its current status and used according to the relying workflow’s policy

Why the distinction matters

Logging in proves control of account credentials. It does not by itself prove that the account has a current Legal Identity or that a relying application should accept that identity for a particular purpose. An application must state its own requirement explicitly:

Authenticated account only
        or
Current Legal Identity required
        or
Specific provider, review, role, or contract rule required

Onboarding paths

Situation	Start with
Trusted backend creates a new account	User onboarding
Browser user creates an account	Browser-based signup
Existing Neuro user signs in	Sign in with Neuro
Account applies for a Legal Identity	Verified identity

State applications must retain

Persist identifiers and status needed to resume the workflow. Do not use display names or email addresses as substitutes for returned account, application, key, or Legal Identity identifiers. Identity review is asynchronous. The application must handle at least a pending outcome and a terminal approved or rejected outcome using the delivery or query mechanism supported by its Neuron.

Keep account and identity data separate

Never put an account-creation API secret in browser or distributable mobile code. A browser onboarding flow can differ from normal Agent API JSON requests and may use hosted forms, redirects, and a session-token exchange; follow the dedicated guide instead of adapting backend examples.

Platform overview

Platform concepts

Neuro-Ledger

Extend the Neuron

Neuron Script

Protocols

IoT

Operate the Neuron

Why the distinction matters

Onboarding paths

State applications must retain

Keep account and identity data separate

Reference

​Why the distinction matters

​Onboarding paths

​State applications must retain

​Keep account and identity data separate

​Reference

Why the distinction matters

Onboarding paths

State applications must retain

Keep account and identity data separate

Reference