The Workflow Collision

A pull-based Kanban workflow lets team members finish current work, respect WIP limits, and pull the next highest-priority item from a ready queue without assignments. An agent lifecycle in an agentic framework uses an operator-initiated process where a human starts work on a specific issue, and enforced state-machine transitions prevent skipping steps. The Kanban approach assumes trust in workers to self-organize, while the agent lifecycle constrains the agent because it cannot be trusted to choose freely, treating the operator as a security boundary. Planning in teams occurs just-in-time through collaborative design sessions that focus on inquiry and risk discovery rather than producing documents. The collision arises when these differing assumptions meet in shared systems.

"A mature Kanban workflow is pull-based. Team members finish what they are working on, check their WIP limit, and pull the next highest-priority item from the ready queue. Nobody assigns work. The system trusts the people to self-organize. An agent lifecycle is operator-initiated. A human tells the agent to start working on a specific issue. The agent cannot pick up work on its own - and for good reason. If any agent could grab any issue the moment it was filed, the issue body becomes an attack surface. Requiring an operator in the loop is a security boundary."

"The problem is that they disagree on almost everything that matters. On one side you have the workflow your team actually uses. If you run a platform or operations team, it probably looks something like Kanban: pull-based flow, WIP limits, design sessions before implementation, a small number of states that everyone understands. The workflow exists to serve the people. You have spent years tuning it. It works. On the other side you have the lifecycle your AI agent needs. If you are using an agentic framework - Swamp, or something like it - the agent operates through a state machine with enforced transitions, upfront planning, adversarial review gates, and checks that physically prevent skipping steps. The lifecycle exists to constrain the agent. It works."

"Pull-based flow says: trust the worker to choose well. Agent lifecycles say: constrain the worker because it cannot be trusted to choose at all. How planning works In a team workflow, design sessions are collaborative explorations of the problem space. The whole team asks questions: What are the risks? What do we not know? What is the simplest experiment? The value is in the inquiry itself, not in producing a document. Planning happens just-in-time, at the appropriate level of"

Read at Webframp