Two-system split
A small high-attention reasoner plus an unbounded memory runtime — unlimited external state, a small working set in attention.
← Store · // product
subnext is a Dynamic Context Runtime (DCR): a zero-dependency Rust engine that pairs a small high-attention reasoner with an unbounded memory runtime, so a model works from a small planned working set instead of an ever-growing context window. Support and integration from $299.
// what it is
subnext is a Dynamic Context Runtime (DCR) — a specification plus a working, zero-dependency Rust implementation. Its thesis is simple: unlimited history is not the same as unlimited attention. Recursive language models move the context-rot problem out of the transformer and into a program; subnext takes the next step and makes that program a runtime.
It splits the system in two: a small, high-attention Reasoner, and an unbounded Memory Runtime that decides which representation of the history to hand it. Incoming context is indexed into external state, and only a small, planned working set is ever placed in front of the model.
The repository ships worked examples and benchmarks — DCR against full context, sliding window, RAG, summarize-all and recursive baselines — so the behaviour is something you can run and measure, not just read about.
// capabilities
A small high-attention reasoner plus an unbounded memory runtime — unlimited external state, a small working set in attention.
Incoming context is indexed into external state and recalled as the right representation on demand, instead of being stuffed into the window.
Worked example covers correction, exact-quote recall, justification and recompute — the primitives a long-running agent actually needs.
bench compares DCR against full context, sliding window, RAG, summarize-all and recursive baselines out of the box.
Pure Rust with no external crates to audit or pin — small, inspectable, and easy to drop into an existing service.
The design lives in docs/; the runtime lives in src/, so the behaviour and its justification travel together.
// under the hood
cargo run --release -- demo / -- bench// what you pay for
subnext is open source (MIT). What you pay for is getting it into your stack and tuned to your workload.
// the fine print
As-is, without warranty. subnext is research-grade software provided for evaluation and integration. To the maximum extent permitted by law, Cyber Sec and Stephan Botes accept no liability for any damage, data loss or consequence arising from its use.
What the fee buys. The price shown is a starting point and covers the engineer’s time — integration, custom representations, benchmarking and fixes. The source is MIT, so you are paying for the work, not for access.
Questions about scope, licensing, or authorization? Get in touch first.