WaagoContent follows the configured route
Waago sends content to an external or local model provider only when the workspace configures and invokes that route. Provider terms and retention practices may also apply.
Governed execution
Agents can execute.
They cannot cross the boundary.
Waago checks the task, route, budget, permission, and risk before work runs. Higher-risk actions pause and return to the accountable person with the evidence needed to decide.
See the control flow- 01Scope
- 02Route
- 03Spend
- 04Judgment
- 05Evidence
- 06Closure
Control flow
Check the boundary before execution. Keep the evidence after it.
One Goal record connects the execution boundary, human decisions, resulting deliverables, and the evidence used to declare the outcome complete.
- 01
Declare the boundary
A Goal defines its outcome, operating mode, participants, task graph, expected artifacts, risk, and acceptance conditions.
- 02
Run policy preflight
Waago can check task readiness, provider route, tools, permissions, budget, dependencies, risk, and required approvals before execution.
- 03
Route accountable work
Each invocation records the task, actor, model route, scoped context, tools, policy result, and measured usage.
- 04
Pause for human judgment
Questions, decisions, reviews, and approvals remain separate objects with an owner, status, rationale, and related work.
- 05
Review the deliverable
Artifacts keep their source, versions, comments, review state, approval state, and export path attached to the Goal.
- 06
Close with evidence
Completion can remain blocked until required work, decisions, approvals, and final artifacts are accounted for.
Provider boundary
Know what Waago controls—and where another provider begins.
This is the current product boundary. Workspace settings and written terms may add controls.
Raw secrets stay outside workspace records
Provider and tool configuration uses credential references. Operators should keep secret values in approved environment, vault, or secret-management systems.
Generated output is not final by default
A model response can become a draft or execution output. Human review and the required final gate still determine whether it becomes an accepted deliverable.
Unknown cost stays unknown
If no active price matches an invocation, Waago presents the estimate as unavailable instead of zero. A later price schedule does not rewrite the completed record.
Operating terms
Review the boundary before consequential use.
The Privacy notice explains data handling. The Terms explain responsibility, third-party services, and private beta availability.
Review a real execution boundary
Define the boundary before agents execute.
Map the scope, model route, budget, risk, human decisions, and completion evidence for one consequential workflow.