
Well I think we have our answer.
I'm not going to measure any verdicts yet. Softmax with learned positions is strong, but multiple forms of rotary are known to extend models to huge context windows.
rotary hubs + rotary softmax alternating is a very powerful craft. The outcome within noise matters, but I will test the paired rotary version as our hybrid at depth. This might just form the necessary continuum behavior I've been looking for, preserving and updating records rather than suffering at depth for a while until the model catches up.
There are definite causal relational behaviors related to framing data within a context window. I'm starting to see the causal outcomes of the aleph resizing system and the behavior expected from this window. I believe we need a couple more scaling mechanisms to cultivate a full geometric skip-continuum behavior in the future, that's another experiment though. I've experimented in the past, chopping up the window does weird things, however this entire model is modular, so when the window behaves correctly we ought to be able to slice off pieces of the window itself for necessary safety points, guarded sections, and so on.
Not enough data to be certain yet.
Context window is starting to behave though, which means the model will function. The rotary system is most definitely functioning for both the hub AND the softmax. This will saturate the 4096 context window with room to spare, and next 8192 may be possible on the nano. Oddly enough, I don't know the limit just yet. I'm thinking there is inherent hardware limits to this, rather than conceptualization limits at this point.
I'm thinking the naming should be; nano, micro, mini, small for now. The small versions being what I trained already and were the prelude to the required answers.
I will not make any promises about beginning v4 yet, as we have to answer many questions before we can reach a verdict of continuity. Then, and only then, we cook.
Historically, each book has been stable up to 2048 positions. The last train shows that a single book cannot house the entirety of 4096, and trying to do this causes the system collapse.
However, two books... is another story. This aligns with our structure and fits comfortably within the system.
With two small-sized books, scaled on tiny shallow tests from before, we have a fairly inaccurate recall shown by the 2s and worse by the v3.
The v1 model had k128 and this was was sliced for optimization to k64 for v2 and v3 due to shallow tests, data expressing that earlier train steps were not affected drastically BY this book's k. However, I never set canary checks for recon shifts as they historically showed durability, which showed they quite literally fell apart over time. I looked for many useful traits and forgot one of the most critical, depth recon.
Now, k256 on the other hand, seems to be doing quite well. Same dimensional shape, different format.

I'll be testing k128, k512, and k1024 as well.
Each book is structurally compliant with signed predicted structures fitted to 2048 slots, larger books were often never used in testing. Classifiers almost never cared about numbers beyond 512 or so, depending on the classifier's shape and size. However, that was an entirely different process. THESE books are being fully saturated with the billions of bytes being fed. They can handle the differences.
Tests show that k64 is nowhere NEAR good enough, like mounting a single home printer in an office for 500. K128 will likely show a similar curve between k64 and k256, and k512 will likely be the strongest and fastest to converge, so we'll likely be using k512 for the nanos.
More than likely we can handle 4-8 books of k1024 and create a collective delegation for 8192 to 16384. Each book specifically tuned to datasets and their learning mutations slowed or frozen. We'll see how k512 handles first though.
That's why this system exists.
These tests are all being done directly on fineweb using the upcoming nano prototypes. There will be hundreds as they surge train.
