Prompts and inputs
Shape the request and create the structure needed by later steps.
AI orchestration guide
A useful AI process often needs more than one model call. Orchestration defines how information is prepared, which service handles each step, where work branches and when a person must decide.
Building blocks
Shape the request and create the structure needed by later steps.
Find approved organisational context before a model prepares a result.
Route each task to a configured local or external model suited to its role.
Run independent work in parallel or choose a path based on process data.
Pause before a consequential step so a person can review and decide.
Use approved service, search or data connections to obtain information or continue an action.
Related terms
| Term | Common emphasis | Useful evaluation question |
|---|---|---|
| AI workflow automation | A defined sequence of AI and non-AI steps | Can the process be versioned, reviewed and operated reliably? |
| AI orchestration | Coordination across models, knowledge, tools and decisions | Are routing, data paths and dependencies visible? |
| AI agent orchestration | Coordination of components that select or perform tasks | How much autonomy is allowed and where are its limits? |
| Human-in-the-loop AI | A person reviews, corrects or approves part of the process | Is human action meaningful, timely and recorded? |
Workflow design
State what the workflow should produce and who remains responsible for using it.
Identify every source, model and external service that can receive or return data.
Add validation, conditions and human approval where the process can become unsuitable or consequential.
Define what happens when a dependency fails and how a new workflow version reaches operation.
Test the complete workflow against representative tasks and explicit acceptance criteria.
Different models can suit different tasks, environments, costs or data paths. Multi-model capability provides choice, but it also requires deliberate evaluation and operational ownership.
Not necessarily. An orchestration workflow can be tightly defined, include fixed branches and pause for people. The permitted autonomy is a design choice and should be explicit.
It means a person participates at a defined point, such as reviewing, correcting, approving or rejecting an output before the process continues.
Pūnaha provides versioned workflows with prompts, retrieval, supported model deployments, parallel stages, approvals, merged outputs and developer-configured backend nodes.
Use the flexible AI workflow tour or request a demonstration focused on your own process.