BuildWorkflows
Workflows Overview
Processing pipelines with kladoi (actions) and rhizai (orchestration).
Overview
Arke's workflow system lets you build automated processing pipelines that scale from a single operation to thousands of concurrent jobs. The system has two layers:
| Component | What it does | When to use |
|---|---|---|
| Kladoi | Individual action units — a single service that does one thing | Direct invocation for one-off processing, or as building blocks for rhizai |
| Rhizai | Workflow orchestration — DAGs that chain kladoi together | Multi-step pipelines with scatter/gather parallelism |
When to Use Each
Use a klados directly when you need a single operation:
- Process one entity through a specific service
- Batch-invoke the same operation across multiple entities
- Test a new processing agent in isolation
Use a rhiza when you need multi-step processing:
- Chain operations together (e.g., OCR → extraction → description)
- Fan out to parallel workers and reconverge results
- Route items to different processing paths based on properties
Prerequisites
Before working with workflows, you'll need:
- Authentication — An API key or JWT token (Authentication guide)
- A collection — Workflows operate on entities within collections (Collections guide)
- Target entities — The entities you want to process
Two-Phase Invocation
Both kladoi and rhizai use a two-phase invocation pattern:
- Preview (
confirm: false) — Returns what permissions will be granted and validates the request, without executing anything - Execute (
confirm: true) — Creates the job collection, grants temporal permissions, and starts execution
This lets you review what will happen before committing.