Cause becomes memory.
An event is not remembered because somebody shoved a row into storage. It becomes memory because a lawful event changed the mounted state.
DUHBLE
Memory should be part of the machine, not a pile beside it.
DUHBLE
Memory should be part of the machine, not a pile beside it.
DUHBLE is a stateful software substrate that can sit underneath an application, game, agent, language model, robot, simulation, scientific instrument, or distributed system.
Instead of asking a database what happened, DUHBLE carries the consequences of what happened. Information can strengthen, weaken, decay, collide, persist, conduct, and change future behavior because of its history.
If a system cannot trace why it knows something, DUHBLE does not treat that knowledge as real.
Relationships become computation.
Trust, hostility, association, eligibility, affinity, reinforcement, inhibition, and decay can live in the system itself and shape what happens next.
Continuity stops being theater.
A machine can leave, return, reconnect, move between hosts, and continue from owned state without rebuilding its identity from a giant conversation transcript.
Provenance becomes law.
The host does not get to invent why something changed. Source, path, timing, eligibility, and state determine whether change is allowed to become part of the machine.
ADD IT TO AI
Give LMs and LLMs something they were never built with: durable internal continuity.
Let the language model generate language. Let DUHBLE carry the state underneath it.
An LLM can plug into DUHBLE as a reasoning or language surface while DUHBLE remembers relationships, prior causes, learned associations, persistent state, permissions, and what actually changed over time.
Stop spending the whole context window reminding the machine who it was five minutes ago.
LLM / LM
language · reasoning · generation
⇅
DUHBLE
state · memory · provenance · topology · continuity
⇅
APP / GAME / ROBOT / DEVICE / INSTRUMENT