Why the Project Is Called Multivergence

The name is two halves of an idea. Divergence is the moment one state becomes several: an agent forks three plans and each goes its own way. Convergence is the moment they become one again: the evidence is in, two plans are dead, and the third becomes the state everyone works from. Multivergence is both halves, and the whole loop the engine runs.

It also says how many. A fork in version control is usually drawn with two branches. Here there are as many as the problem needs, each with its own weight. And it nods to the multiverse, many possible worlds alive at the same moment, which is a fair description of a store with a dozen live branches in it.

Many ways apart, then one.

The name had to be a word a developer could say once and remember. It’s long, but it’s regular: you can spell it after hearing it, and it reads the same in code, as a package and a command called multivergence. Its store file is called multivergence.mv unless you name it.

Most of all it names what the engine does. Plenty of tools fork state. What this one adds is the second half, the coming back together, with rules for which branch earns it. A name built on “branch” or “fork” would have left that half out.