Glossary
ExergyNet terminology,
in plain English.
Every proprietary term with a one-sentence definition, its architectural role, the industry concepts it resembles, and an explicit boundary of what it is not.
Foundational distinction used throughout: capability is what an actor technically can do; authority is what it is permitted to do under defined conditions.
xLMP
ExergyNet Ledger Memory Protocol
- Plain English
- A persistent-state delivery architecture for model reasoning.
- Role
- Supplies the relevant state to a reasoning event without requiring the complete stored corpus to remain active in model context.
- Comparable
- Context management, memory architecture, state retrieval.
- Not merely
- Not vector search or conventional prompt-stuffing, and not measured as an energy or HBM-byte reduction — token and active-context behavior are reported as measured on their tested envelopes.
Exergy Vault
Persistent state and evidence substrate
- Plain English
- Persistent, addressable state for intelligent systems, and a substrate for retaining the evidence associated with machine reasoning and action.
- Role
- Stores state as durable, integrity-rooted objects that survive sessions, models, and restarts.
- Comparable
- Content-addressed storage, object store, an evidence/audit store.
- Not merely
- Not just another AI memory or object-storage product, and it does not assert compliance or immutability guarantees beyond what is validated.
xISA
Machine identity and capability architecture
- Plain English
- Defines what a machine actor is capable of doing and provides a foundation for expressing the authority under which those capabilities may be used.
- Role
- Represents and bounds machine identities and capabilities; the anchor for the capability-versus-authority distinction.
- Comparable
- Capability registry, machine identity, an authorization schema.
- Not merely
- Not a user-login/IAM product, and capability alone is never treated as permission to act.
LNES-22
Authenticated, policy-bound machine-event layer
- Plain English
- The transport and transaction layer through which authenticated, policy-bound machine events can move.
- Role
- Carries an event structure answering: who acted, what was requested, under what authority, against what state, under what policy, what result occurred, and what evidence remains.
- Comparable
- Authenticated messaging, a policy engine, a transaction/audit bus.
- Not merely
- Not a claim that agents become "completely secure." Signature verification, policy gates, and rejection conditions are validated within their tested implementation only.
Vanguard
Cognitive execution engine
- Plain English
- Performs reasoning and tool execution within an architecture designed to preserve state, apply authority boundaries, and produce attributable actions.
- Role
- Consumes bounded evidence from the state plane and operates under explicit authority constraints. The important characteristic is bounded machine authority, not maximum autonomy.
- Comparable
- An agent runtime, an orchestration/execution engine, an inference execution mode.
- Not merely
- Not "our frontier model" and not a required replacement for your existing model provider — it is one execution mode inside the architecture.
Consequence Boundary
Authorization layer for autonomous agents
- Plain English
- An independent identity, capability, freshness, and integrity check placed between an agent's reasoning and any system that reasoning can affect.
- Role
- Enforces that AI can propose a consequence but cannot authorize its own consequence.
- Comparable
- A policy decision point, an authorization gateway.
- Not merely
- Not a guarantee that eliminates all AI risk. Live-tested against a real prompt-injection red team; patent pending (U.S. Provisional Application No. 64/134,973).
Omega Carrier
Memory transport architecture
- Plain English
- Moves persistent memory between nodes while preserving identity, provenance, integrity, and freshness.
- Role
- Portability of state across nodes and environments.
- Comparable
- A replication/transport layer for stateful memory.
- Not merely
- Memory portability does not grant execution authority.
VMN
Vanguard Memory Node
- Plain English
- An open-source local node implementing xLMP-style deterministic, content-addressed memory over MCP.
- Role
- Runs the memory plane locally, with no cloud required.
- Comparable
- A local memory server, an MCP memory backend.
- Not merely
- A local node, not the full hosted platform; results are workload-dependent and bounded to tested scales.
LNES
ExergyNet internal work-unit / release numbering
- Plain English
- The internal identifiers ExergyNet uses to label specific systems, experiments, and releases (for example LNES-22 authority, LNES-04 settlement, LNES-82C scaling).
- Role
- Traceability between a public claim and the specific validated work behind it.
- Comparable
- Internal component or RFC numbering.
- Not merely
- Not product names for end users; each maps to a documented scope in the benchmark and claim ledgers.
Component names describe responsibilities and interfaces. They do not define ExergyNet's category: execution infrastructure for machine intelligence. Mechanism-level detail is intentionally omitted.