Encapsulated agent task
Run an agent loop as one bounded activity with explicit limits and validation.
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/cee011a5-4dc0-4186-8db8-16863e515c2a/versions/1
Download the exact workflow YAML (v1). Configure the runtime prerequisites below before planning and executing it.
Run this example locally
Run a bounded finite-state agent over an allowlist of local numeric tools, verify the measured answer against the source observations, and independently publish the answer and complete tool trace. The smoke profile uses deterministic tool selection, not an external LLM.
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/bounded-agent &&
./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: answer.json, validation.json, trace.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/bounded-agent
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 |
|---|---|
prepare-objective | Execute the prepare-objective stage and publish its declared outputs for downstream activities. |
agent-loop | Execute the agent-loop stage and publish its declared outputs for downstream activities. |
validate-output | Execute the validate-output stage and publish its declared outputs for downstream activities. |
publish-result | Execute the publish-result stage and publish its declared outputs for downstream activities. |
store-trace | Execute the store-trace stage and publish its declared outputs for downstream activities. |
Inputs
- Objective and context
- Tool allowlist
- Iteration limits
Outputs
- answer.json
- validation.json
- trace.json
Provenance to preserve
- Prompt and model
- Tool calls
- Cost and validation
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: 5/5 activities completed. These captures belong to run showcase-bounded-agent-local-4f5eb97ca7-run-20261020t191412.780353000.
Read the daemon execution record · Local output manifest
Each stage also ran through the standalone local command. Read the dependency and artifact validation.
prepare-objective
After: workflow start.
agent-loop
After: prepare-objective.
validate-output
After: agent-loop.
publish-result
After: validate-output.
store-trace
After: validate-output.
Execution considerations
Apply timeout, cancellation, restricted credentials, and idempotency to any external side effect.
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.