KM² roadmap / when should teams start adopting it in 2026?

[nurkmez2]

@dluc hi 👋

Thanks for the clear note in the repo about KM² being an active research project and a full rewrite of the initial prototype.

We are currently using Kernel Memory v1 and would definitely like to use KM² as well.
The main question for us is mostly about timing:

When do you think KM² will be usable for broader adoption (or early production-style usage) in 2026?

I completely understand this is a research project and may evolve quickly.
Still, even a high-level direction would really help teams like us plan better — especially around:

• expected maturity/stability,
• API changes,
• migration considerations from v1,
• and general priorities for 2026.

Even a short update would be very helpful.

Thanks a lot.

[aniruddhaadak80]

From my point of view, teams do not need a precise date as much as they need explicit adoption signals. A short matrix covering research-only, early production experiments, migration readiness, and expected API churn would already help current v1 users plan much better.

That kind of guidance matters especially when a rewrite is active, because waiting and adopting too early are both expensive mistakes.