Supervised tool loop
Separate proposal, policy, approval, execution, and verification.
Import this workflow from AkôFlow Hub
Open the public README and measured execution results. The Hub includes the execution capture, activity metrics, logs and version history. Reading public results does not require an account.
In Desktop, choose Create workflow → Import from Hub and paste this version-specific URI:
akoflow://hub/publications/59517e35-7fec-49a4-ad24-cafe373d27f5/versions/1
Download the exact workflow YAML (v1). Configure the runtime prerequisites below before planning and executing it.
Run this example locally
Propose a sandboxed summary-writing action, enforce an allowlist, replay a clearly identified approval fixture, execute the local tool, and verify its output and digest. Set AKOFLOW_APPROVAL_FILE to supply an explicit approval record; the bundled approval is only for this smoke example.
Install Go and Python 3.12 or newer.
git clone https://github.com/UFFeScience/akoflow-examples.git &&
cd akoflow-examples &&
git checkout --detach d890c3171e3661890305b763b8fc3ede48bb61b4 &&
cd agentic-workflows/supervised-tool-loop &&
./prepare.sh &&
./run.sh
Run the block from the directory where you keep your repositories. If you already cloned the repository, enter this example's directory and run ./prepare.sh && ./run.sh.
Preparation downloads the Go module and any declared Python packages once. The workload then runs locally with offline input data. Every meaningful step is a separate process; independent activities run in parallel after their dependencies complete.
Read outputs/manifest.json for the generated artifacts, outputs/dag-validation.json for dependency waves, and outputs/stage-<activity>.json for each activity's observed result. A failed stage stops the run and prevents a successful final manifest.
Expected outputs: execution.json, verification.json.
Run the same activities in Desktop
Start your local AkôFlow daemon with Docker available and configure AKOFLOW_API_TOKEN in your shell. From this example's directory, run:
go run ../../tools/daemon-local -root ../.. -example agentic-workflows/supervised-tool-loop
This command validates the daemon connection, builds the declared image, registers the local environment and workflow, and submits a real run. The daemon owns execution and file transfers. Open the printed run ID in Desktop to inspect each activity.
Activity responsibilities
| Activity | Responsibility |
|---|---|
build-context | Execute the build-context stage and publish its declared outputs for downstream activities. |
propose-action | Execute the propose-action stage and publish its declared outputs for downstream activities. |
policy-check | Execute the policy-check stage and publish its declared outputs for downstream activities. |
human-approval | Execute the human-approval stage and publish its declared outputs for downstream activities. |
execute-tool | Execute the execute-tool stage and publish its declared outputs for downstream activities. |
verify | Execute the verify stage and publish its declared outputs for downstream activities. |
Inputs
- Goal and state
- Policies
- Tool credentials
Outputs
- execution.json
- verification.json
Provenance to preserve
- Proposal revisions
- Approver
- Idempotency key
Source bundle
The executable workflow and its implementation files are maintained in the separate AkôFlow examples repository. The documentation intentionally keeps code, container recipes, generators, and validation scripts out of the narrative page.
Open the complete source bundle ↗Execution evidence
Verified on local Docker: 6/6 activities completed. These captures belong to run showcase-supervised-tool-loop-local-1fb7664e1c-run-20261020t191433.219869000.
Read the daemon execution record · Local output manifest
Each stage also ran through the standalone local command. Read the dependency and artifact validation.
build-context
After: workflow start.
propose-action
After: build-context.
policy-check
After: propose-action.
human-approval
After: policy-check.
execute-tool
After: human-approval.
verify
After: execute-tool.
Execution considerations
This pattern requires durable pause and resume. A daemon restart must not execute an approved action twice.
AkôFlow boundary: the engine schedules, deploys, executes, transfers data, and records evidence. The ML or agent framework remains an implementation choice inside each activity.