Flow Tools

Why this matters

Real agent workflows are not single tool calls. They are multi-step pipelines where each step depends on the last and some steps need human approval. Flow provides the structure for these pipelines. Once a workflow is verified, save it as a skill — a reusable tool that any agent on your server can call by name without re-planning.

Four tools

• ✓flow.into — Multi-step workflow execution with dependency resolution, CTC validation, and optional skill saving
• ✓flow.route — Conditional dispatch with predicate matching — branch to any tool, including user-created skills
• ✓flow.request-approval — Pause for human approval before sensitive operations
• ✓flow.request-feedback — Ask the user for missing data mid-workflow

Skills and Cognitive Trust Certificates

When flow.into executes a workflow successfully, it can be saved as a skill with its CTC — a cryptographic verification that the plan was validated for type safety, cost bounds, and policy compliance. Skills appear as regular tools that any agent on your server can call — no re-planning, no re-verification. Each execution is auditable by CTC ID through inspect.ctc-executions.

Example: conditional routing

{
  "name": "data-grout@1/flow.route@1",
  "arguments": {
    "cache_ref": "rc_lead_data",
    "branches": [
      { "when": "$is_enterprise", "then": "my-skill/enterprise-onboarding" },
      { "when": "_", "then": "my-skill/standard-onboarding" }
    ]
  }
}