Manual workflows
Planned
Katra workflows are manual-first. A workflow must be useful with people and teams before Agent Profiles become optional executors for selected steps.
Intended first release
Section titled “Intended first release”- Canonical YAML representation
- Draft and published versions
- Validation and reliable visual-editor round trips
- Manual triggers
- Human tasks and team assignments
- Decisions and conditional routing
- Approvals, returns, pause, resume, cancellation, and completion
- Durable Attention and audit history
- Recovery across client disconnects and worker restarts
Visual editor
Section titled “Visual editor”The planned editor is a full canvas for mapping steps and inspecting their configuration. It is not a simple modal. The visual and YAML representations must describe the same versioned workflow without lossy conversion.
Agent boundary
Section titled “Agent boundary”Agent tasks are optional step types. A workflow does not require an agent, model provider, external harness, or paid service. Agent execution will be introduced only after manual workflow behavior and authorization are proven.
Current status
Section titled “Current status”The visible Workflows interface demonstrates the intended interaction model. It is not connected to an authoritative workflow engine yet.