Platform · process anatomy

A process is phases, steps, sub-agents and tools

Written once, versioned, and executed the same way every time. This is the same console your team works in, not a marketing rendering of it.

Phases & steps

The unit of work is a step

A process is an ordered set of phases, and each phase holds steps. A step names the sub-agent that performs it, the tools that sub-agent may call, and whether a person signs off before the run continues. Because the structure is explicit, you can change one step without re-testing the whole process.

A phase, its step, the sub-agent it calls and its approval gate

Fig 1 · a phase, its step, the sub-agent it calls and its approval gate

Flow diagram

One definition, drawn start to end

The same definition, drawn start to end. Operations teams read the diagram; the runtime reads the definition. There is no second model of the process to keep in sync.

The process drawn from entry to completion

Fig 2 · the process drawn from entry to completion

Sub-agents & tools

Each sub-agent carries its own model and tools

A cheap model handles classification, a stronger one handles the judgement calls, and neither can reach a tool it was not granted.

A sub-agent with its assigned tools and model

Fig 3 · a sub-agent with its assigned tools and model

Versioning & limits

Sensible defaults, all configurable

PropertyDefaultConfig
Process versions retainedAll
Step retries before halt3
Run history retentionUnlimited
Audit log immutabilityEnforced

See a process built end to end

Thirty minutes, your process, our console.