MPath

MPath is the coordination layer of the Kumbatio ecosystem: project and work coordination that adapts to actual human capacity.

The problem it addresses

Project tools plan in time: deadlines, sprints, hours estimated and hours logged. But time isn't what produces output - productive capacity is. A plan that assumes every hour is equal breaks the moment a real person has a low week, and then the tool makes it worse: red overdue markers, slipping burndown charts, pressure mechanics.

MPath is being built to coordinate work around what people can actually do - useful for individuals, and especially for mixed-neurotype teams where capacity varies across people as well as across days.

What's being built

MPath is an energy-aware coordination system with multi-level planning. It uses mountain metaphors for its planning hierarchy - strategy down to individual tasks - the "Mountain Path" that gives the product its name.

Unlike the other products, MPath does not currently run on energy-system. Its energy model is server-side and predates the SDK: a numeric level plus a qualitative reading, logged per check-in and stored in Postgres, because coordination needs history and cross-user aggregation that a client-side engine does not provide. Adopting the SDK here means bridging the two through createExternalLevelCompatibility rather than swapping one for the other - product work, not a mechanical migration. It is planned, not done.

The model is well developed; the implementation is still being built and aligned. Because it isn't released, we won't present the design as a finished feature list. When MPath ships, this page will document what it actually does.

Where it sits in the ecosystem

MPath covers the planning and tracking moment. Anasa covers creating, and Nami covers support when executive function is low.