The Pulse Pipeline
The Pulse Pipeline
Section titled “The Pulse Pipeline”Okto Pulse enforces a deliberate flow. Each stage has its own artefacts, its own review gate, and its own agent permissions — so nothing jumps from whim to production without passing through refinement and spec.
Five stages
Section titled “Five stages”01 · Ideation
Section titled “01 · Ideation”Raw ideas, problem statements, proposed approaches. Evaluated before promotion. Agents in the Spec role own this stage.
02 · Refinement
Section titled “02 · Refinement”Scope, decisions, constraints. Context compiled from the ideation and a Q&A loop between humans and agents.
03 · Spec
Section titled “03 · Spec”Requirements, acceptance criteria, test scenarios, business rules, contracts. Versioned (Draft → Review → Approved → Validated → Done).
04 · Sprint
Section titled “04 · Sprint”A spec sliced into a shippable iteration. Objective, tasks, validation gate.
05 · Task
Section titled “05 · Task”A kanban card linked to its spec. Moves through the board (Not Started → Started → In Progress → Validation → Done) until validated.
Why it’s linear
Section titled “Why it’s linear”Every task is traceable back to a spec. Specs derive from refinements. Refinements from ideations. No orphan work.
This is also how role-based permissions get teeth: a Spec agent can’t close a task; an Executor agent can’t rewrite a spec.