The ecosystem
Four products, one underlying model - infrastructure, creation, coordination, and support for variable cognitive energy.
Kumbatio currently has four products at different stages. They share the same five-level model of self-reported cognitive capacity.
The products do different jobs and use different interfaces. They share the underlying energy model and the same design principles.
Current status
Honest snapshot: energy-system is live - an open-source SDK you can install today. Anasa is in public alpha - you can download it at anasa.md. MPath and Nami are in development and currently waitlist-only.
| Product | Role | Layer | Runs on the SDK | Status |
|---|---|---|---|---|
energy-system | SDK for energy-aware application behavior | Infrastructure | - | Live |
| Anasa | Writing and thinking workspace | Creation | Yes | Public alpha |
| MPath | Project and work coordination | Coordination | Not yet | Waitlist |
| Nami | AI cognitive support copilot | Support | Yes | Waitlist |
The products
energy-system
The infrastructure layer. An open-source TypeScript SDK that models cognitive energy as application state. Live and installable today.
Anasa
The creation layer. A local-first writing and thinking workspace with an energy-aware interface. In public alpha at anasa.md.
MPath
The coordination layer. Project and work coordination that adapts to actual human capacity. In development, waitlist open.
Nami
The support layer. An AI cognitive support copilot for when executive function is low. In development, waitlist open.
How they fit together
energy-system is the foundation - it defines the five-level energy model and the strategy system for adapting behavior to capacity. Anasa and Nami are built on it directly; MPath runs its own server-side energy model today and is planned to bridge to the SDK rather than replace its model with it. Each covers a different need:
- Create with Anasa when you need to think and write.
- Coordinate with MPath when you need to plan and track work - alone or with a team.
- Get support from Nami when executive function is low and you need help getting through the day.
One shared state can therefore mean the same thing in each product, even though the products respond to it differently.
If you're a developer, you don't have to wait for the apps - you can build energy-awareness into your own product with the SDK today, the way Meltemi - an email client from entro314 labs, the studio behind Kumbatio, built outside the Kumbatio product line - already has. Start with the energy-system documentation, and see the production patterns guide for how real apps integrate it.