Four tools. One energy model.
energy-system is the shared layer. Anasa and Nami run on it directly; MPath coordinates work against its own server-side energy model and is planned to bridge to the package rather than replace it. They are at different stages, so each card says what is available now.
energy-system
A person chooses one of five capacity levels. Applications use that state to decide what stays visible, what may interrupt, how long undo lasts, and how much an agent may do without asking. The level is not inferred or uploaded.
Anasa
A local-first Markdown workspace in public alpha. Its interface responds to the level you report: deeper tools remain available at high capacity, while lower levels reduce noise and secondary actions.
MPath
A project and teamwork application being built around current capacity instead of uniform hours. Tasks can carry energy estimates, and plans can account for what individuals and teams can realistically take on.
Nami
An AI assistant being built for days when planning, remembering context, or choosing the next action is difficult. It supports workflow and self-management; it is not therapy or crisis care.
Built on the engine
Three applications from entro314 labs, the studio behind Kumbatio, run on energy-system from outside the Kumbatio product line - and adopt nothing else from it.
Meltemi
Inbox scope, undo-send windows, deferral presets, agent autonomy limits, and a notification gate that holds rather than drops.
Entromail
Thread density, snooze ordering, undo windows, and every line of level copy read from the package rather than restated.
Equidock
The dial itself, persisted to local SQLite through a custom adapter.