Observe Execution

Guide page — how to use this step in your SDK or loop. For the HTTP endpoint parameters, see Observe / Guide / Feedback. For the product concept, see Execution Memory.

Use observe when something happened in the Agent loop and should become evidence for future context compilation.

Execution evidence can be:

an attempted route,
a tool result,
a verifier rejection,
an accepted handoff,
a reviewer decision,
a final outcome.

SDK Example


await aionis.execution.observeStep({
  agent_id: "worker-1",
  team_id: "checkout-team",
  role: "worker",
  run_id: "run-001",
  task_signature: "checkout-migration",
  title: "Legacy adapter rejected",
  summary: "Verifier rejected the legacy route because it touched unrelated modules.",
  outcome: "failed",
  target_files: ["src/checkout/legacyAdapter.ts"],
});

What To Include

Field	Why
`run_id`	Ties evidence to a concrete execution run.
`task_signature`	Lets later guide calls find related state.
`agent_id` / `role`	Preserves producer and consumer boundaries.
`outcome`	Helps lifecycle adjudication.
`target_files`	Helps route and branch relation inference.

Do not write every thought as a high-authority memory. Write observable evidence and let Aionis adjudicate whether it should become current, inspect-only, blocked, or rehydratable.