@nexus/finance
Finance
Institutional financial workflows
Blocks unverified transactions above $50k without dual approval and audit trail.
Nexus Execution Protocol
Universal architecture for high-risk AI execution
NEP is not a vertical SaaS product. It is an open protocol stack: a domain-agnostic core engine plus industry-specific Domain Energy Plugins that encode the rules each sector cannot afford to get wrong.
Boundary law
P(H executes | e > 0) = 0
When policy violation energy is strictly positive, the probability of execution is exactly zero. Probabilistic models may propose. The protocol decides.
Core engine and Domain Energy Plugins
Core engine
Universal, open
The NEP commit boundary is domain agnostic. Intent ingestion, energy evaluation, and cryptographic sealing work the same across every industry.
Domain Energy Plugins
Industry rule sets
Each @nexus/* plugin encodes sector-specific constraints as executable policy graphs. Finance, healthcare, and defense share one engine, different energy functions.
Commit gate
Deterministic verdict
When policy violation energy e > 0, execution probability is zero. No model output overrides the boundary.
Evaluation pipeline
Every agentic action traverses the same four stages regardless of industry. Plugins swap the energy function. The commit gate does not.
01
Intent submission
A probabilistic agent proposes an action with full context: entities, payloads, jurisdiction, and reasoning trace.
02
Energy evaluation
The active Domain Energy Plugin scores the intent. Violations produce energy e > 0 against the compiled policy graph.
03
Commit gate
The core engine applies the boundary law: if e > 0, execution is denied. Allow and escalate paths are deterministic.
04
Cryptographic seal
Approved commits are hash-chained with plugin version, energy score, evaluation path, and execution receipt.
Plugin ecosystem
Industry-agnostic by design
@nexus/healthcare
Healthcare
EU AI Act alignment
Blocks EMR updates when patient identity fields fail deterministic match.
@nexus/defense
Defense & Critical Infra
Rules of Engagement (RoE)
Enforces cryptographic dual-key signatures before any operational commit.
Cryptographic audit trails
Every commit produces a hash-chained record: intent, plugin version, energy score, evaluation path, and outcome. Tampering breaks the chain.
Architecture & Sandbox Access
Enterprise engineering teams receive deep-dive architecture audits, plugin demonstrations, and access to the execution sandbox to verify audit trail mechanics. Contact us to request sandbox access.