Explicit authentication
Service identity, user identity and permissions remain separate; insufficient access context is rejected.
NELSE Developers
Integrate NELSEwithout guessing the contract.
This is the developer-facing view of NELSE API: business states, versions, errors, idempotence, observability and integration patterns. The public contract exposes what consuming software needs while keeping the proprietary normative implementation private.
RESTSDKMCPEVENTS
The contract
Predictable for the developer. Explicit for the auditor.
Idempotence
Critical transport operations can be retried without silently creating a second business decision.
Pinned versions
The call can retain the normative version and execution context required for explanation and replay.
Explicit business states
READY, REVIEW_REQUIRED, MISSING_FACTS and BLOCKED remain visible instead of becoming generic success or error.
Typed errors
Validation, authorisation, version, missing-data and availability failures can be handled differently by the client.
Observability
Request, decision, version, event and evidence identifiers support correlation without opening proprietary engine internals.
Decision trace
A regulatory result should remain traversable from source to proof.
SOURCE
Text, standard or policy and its version.
RULE
Formalised requirement retained in the executed corpus.
FACT
Confirmed, missing or conflicting contextual value.
RESULT
Business state, action, deadline or requirement.
HUMAN
Review, modification or approval when required.
PROOF / REPLAY
Reference used to examine the result later.
Reproducibility contract
Within the formalised scope, the same confirmed context, same corpus, same version and same configuration produce the same normative execution. Missing information stays missing; it is not silently converted into a negative fact.
Public primitives
Evaluate a scoped factual context against the selected normative capability.
Calculate a regulated timing consequence under the selected time rules.
Determine the information or evidence path required for the selected journey.
Support a regulated information/decision journey without reducing consent to a checkbox.
Resolve the versioned information/terms path to be presented or reviewed.
Check the public proof contract independently from the business UI.
Patterns
Synchronous
Call NELSE during a user journey and receive requirements, actions and review states.
Event-driven
Trigger reassessment or downstream work when a fact, state or governed rule changes.
Batch
Re-evaluate a portfolio against an explicit version and retain correlated results.
Agents & MCP
Let an agent ask NELSE what is required without delegating normative judgement to the LLM.