Normative scope
NELSE executes and maintains the corpora, policies and versions explicitly included in the applicable contractual scope or Service Charter.
Service Description · Version 1.0
This page describes the general service framework. For a specific customer, the binding perimeter is the one defined in the applicable proposal, Service Charter, order form and schedules: products, corpora, jurisdictions, versions, integrations, assurance level, maintenance and responsibilities.
What NELSE does
NELSE executes and maintains the corpora, policies and versions explicitly included in the applicable contractual scope or Service Charter.
Within the formalised perimeter, deterministic rules produce reproducible execution for the same confirmed context, corpus, version and configuration.
Where interpretation, discretion or accountable approval is required, NELSE keeps that state human rather than silently replacing it with automation.
Depending on product and assurance profile, NELSE preserves version, event, review and evidence references needed to examine the path later.
Normative maintenance, scope extensions and reassessment depend on the maintenance programme and service level contracted.
What the service depends on
A regulatory engine cannot correct a business reality that is absent or false. Results depend on information actually supplied or connected.
Customer procedures, thresholds and internal policies must be approved and maintained by the competent functions inside the organisation.
A regulation, jurisdiction, version, system or action outside the contracted perimeter is not covered merely because another corpus is deployed.
A runtime control only applies to systems, channels, events or actions actually connected to the NELSE perimeter.
What NELSE is not
NELSE structures and executes the formalised perimeter; qualifications, interpretations and judgements requiring a professional remain attributable.
Compliance depends on applicable law, actual facts, systems, practices and decisions inside the organisation.
NELSE can keep its own evidence and dossiers but does not automatically replace ERP, line-of-business, GRC, EDC, CTMS or other source systems.
A multi-regulatory engine does not mean every rule in every jurisdiction is enabled under your contract.
Contract the right scope
A Deploy NELSE programme closes the use case, corpora, actors, integrations, human governance, evidence expectations and maintenance cycle before deployment.
Bring us your case
Describe the operating problem. We prepare the relevant product, deployment programme and integration path around your actual scope.