Trust and federation - Neuro Developer Documentation

Neuro deployments are operator-controlled and can participate in federated workflows. Applications therefore need to ask both who attests a fact and where that attestation is accepted.

Separate the trust decisions

Decision	Example question
Authentication	Which account is controlling this session?
Identity review	Which provider reviewed the identity, under which policy?
Authorization	Is this account allowed to perform this operation?
Contract participation	Does this Legal Identity satisfy the party and role requirements?
Federation	Will the relevant Neurons and domains exchange and accept this operation?
Application acceptance	Does the relying application accept the returned status and evidence?

A successful HTTP response only answers the operation-level question. It does not automatically answer every policy or cross-domain question above.

Confirm which Neuron and domain you trust

The application connects to an exact Neuron host supplied by its operator. The Neuron’s enabled packages, providers, privileges, templates, and federation relationships determine which workflows can complete. Before relying on cross-domain behavior, confirm:

the participating Neurons and identities;
the Trust and Identity Providers involved;
the accepted template or workflow policy;
required privileges and authorization grants;
event or polling behavior for remote state changes;
development, staging, and production federation boundaries.

Design for asynchronous results

Review, approval, proposal, signature, and remote operations can remain pending after the initiating request. Persist the returned identifier and state, then use the documented event, callback, XMPP, or polling mechanism for that deployment. Do not translate “request accepted” into “business workflow complete.”

Apply the trust model