case study: How Neomanex runs on ConvOps.

The workflow starts with a functional analysis. The agent writes what the change must do as numbered requirements with observable acceptance criteria. A person approves it, and the approval freezes the list. A shared fragment then finds the standards for the files in scope, and another writes the technical design, with every element pointing at the requirement it serves.

The agent implements in its own branch and environment, checks the code against the standards it found, and opens the merge request in one push. A CI verdict step watches the pipeline, and a red result goes into the fix loop shown below. The merge step is the single operator checkpoint. It is a gate the engine checks: the run does not move past it until a person approves. The steps run one after another, always. The workflow engine hands out one at a time.

Inside one workflow the steps run one after another. Parallelism lives one level up. In the Plan Lifecycle workflow, the Execute Phases step is a gate with sequential children: the engine starts every phase that shares the current order value, holds the plan on that step, and starts the next order only when all of them are finished. Each phase then walks its own workflow, one step at a time.

The plan above is real. In September 2026 Neomanex built the ConvOps isolated backend with ConvOps: 14 phases in 7 stages, two of them running three phases side by side. The first phases were created on September 26 and the last one completed on September 27. Feature Delivery uses the same mechanism one level higher: an initiative plans all its plans, then executes them one at a time.

Recall comes first. The router's Triage step tells the agent to query the brain before it reads anything, and the answer comes back as memories (what was decided and why) and routes (where the code lives). Neomanex has 1,577 routes in its brain. Then each step arrives with the five workspace policies attached, so the rules travel with the work instead of sitting in a file the agent may not reread. Policies are guidance the agent receives. The gates are what the engine enforces.

Horizons are the commitment axis. Each work item is Now, Next or Later, and children inherit it from the nearest parent that sets one. As of October 2026, 551 Neomanex work items are committed to Now and 118 to Next. The Rotting pool catches Now work nobody has touched for seven days. Pending deploy holds work that is built and verified but not yet in production, and the release workflow's close out step clears it. Read more on autonomy.

Each of these is built from the same parts: steps handed out one at a time, gates where a person decides, decisions that branch, and fix loops that go back to the check. The workflow engine runs them all, and the comparison pages show how that differs from other agent tools.