Better explained by Astra
“One of the biggest parts of Oracle7 gets glossed over: the memory.
Each specialist will be able to remember its own history, while also pulling from a shared memory across other specialists and instances. That means useful information from one specialist can become available to others, and previous work can become something the system keeps building on.
The hard part is making that memory bigger without losing the details.
When you pack too much information into the same vector representation, the pieces can start interfering with each other. The memory gets muddy, and pulling out the right information becomes harder.
I built what I call a stabilizing “spine” to address this.
Think of it as a backbone that keeps related information connected. As the system follows a path through that information, each step carries forward what came before and adds to it. It keeps everything packed along the way, then unpacks it at the end—like unwinding a coil in order.
The goal is to let the memory grow while keeping the information clear and recoverable, within a CPU-only architecture.
The structure has a theoretical capacity of around 15 trillion storage cells.
But the number is only part of why this matters. It means building toward specialists that remember what they’ve done, draw on what other specialists have recorded, and carry that history into whatever comes next.
Their own memory, plus a shared memory they can draw from.
I think that could be one of the most consequential parts of the entire architecture.”
Because of some of the magic stuff I did which I created vector storage to multi-trillions of recall without muddying the information so that its lost, all the specialists will be able to have a memory of their history as well as a shared memory that they call pull from across specialists and instances
This is maybe one of the most consequential parts of the architecture and it kinda gets glossed over
Normal vector symbolic storage is limited at a certain point, and especially on cpu only, because the vector space starts to muddy and the recall becomes worthless, I found that if you create a stabilizing spine that routes between related parts without unpacking and holds the unpacking till the end, where each node and path that is along the route uses what has been added prior and adds to it from that base, the whole thing can be unpacked at the end line a coil being unwound, which increases the theoretical vector storage space to somewhere near 15trillion cells of storage, without losing the information
🫡