Workflows & tools
Stable contracts between a model’s request and an operation’s effects.
A tool is an entry point
The model sees a tool declaration adapted to its protocol. Atreyu maps the emitted call back to a canonical workflow and checks authorization before execution. Visibility to a model is not itself permission to perform an action.
Workflows coordinate work
A workflow defines a versioned sequence of steps. Steps can call models, invoke primitive functions, and coordinate results. Durable execution records allow callers to inspect progress and distinguish accepted work from completed work.
Two provider boundaries
Model providers generate content and tool requests. Effect providers execute the underlying operation, such as a scoped file action, web lookup, or media task. Keeping these boundaries separate lets a stable workflow survive a change of model or execution host.
Long-running operations
Submission, execution, artifact creation, and delivery are separate milestones. A queued job is not a finished result. Recovery should inspect the existing execution and its effects before retrying an operation that might already have succeeded.
Media and external capabilities
Atreyu can coordinate image, video, music, speech, and other tool-backed workflows where configured. Actual models, input schemas, quotas, and permissions are environment-specific. Integrators should discover the current contract rather than infer it from a model name.