Memory outside generation
What is a fact lives in NVSS. The answer is a recovered state, not the most plausible token.
NVSS · CPU
67 µs
P50 of a full cycle, measured over twelve hours. Not a demo.
1 µs
recognize
16,762
cycles
0
errors
The model cannot guess on your behalf.
In telecom, tax, defense, and onboard systems, an invented sentence is an incident. Intelligence has to recover a state that was already verified.
The problem
A transformer emits the most likely token. It does not know whether the fact is true. Agent frameworks on top loop, lose context, and blow the window. The GPU bill rises. Trust falls.
A transformer emits the most likely token. It does not know whether the fact is true. On top of that, the agent loops, loses context, and blows the window. The GPU bill rises to answer a question that already had an answer. Over twelve measured hours, NVSS held 16,762 cycles, zero errors, a P50 of 67 µs for a full cycle and 1 µs to recognize. On CPU.
What the work includes
67 µs, measured
P50 of a full cycle. Recognition in 1 µs. 16,762 continuous cycles, zero errors, no latency decay on that run.
An agent with a guard
NEXUS moves the task on a state machine. The open loop, which eats context until it bursts, stops being the design.
The machine you have
The cycle fits on an ordinary CPU. A GPU cluster is not the price of a question that was already answered.
How we step in
- 01
Separate memory from generation
What is a fact stays in a deterministic state. The model consults. It does not improvise.
- 02
Give the agent a state
The task moves on a state machine, with an execution guard, instead of an open loop.
- 03
Run on the machine you have
The measured cycle fits in microseconds, on an ordinary CPU, without waiting for the cloud.
Where the problem usually shows up
NVSS Substrate (P50 67 µs over a 12-hour cycle, 16,762 cycles without error) + NEXUS (`nexyus`, deterministic FSM) + the Metacognition Layer + 4-layer Fractal Memory. Stack sovereignty: no LangChain, no LiteLLM.
“The model answered, confidently, something that was not true.”
“The agent looped and the context window ran out.”
“The GPU bill does not fit a lookup that already has an answer.”
“The operation cannot depend on a model cloud to decide.”
HOP 07 · CONTATO
Tell us the problem. We answer.
Network, data center, ISP, clinic, firmware, agent, database — or any combination. Who answers is who operates what we deliver.
José Rinaldi
Founder · Engineer
Direct channels
HBR 167, 935, Block C — Suites 2001-2009, Holambra/SP, 13829-899, Brazil · Mon–Fri, 9am–6pm (BRT)