Multi-Agent Hosts

Aionis execution memory is designed for planner, worker, verifier, and reviewer handoffs.

For the product-level view, start with Execution Memory. This page focuses on the host integration shape for multi-agent systems.

It helps keep:

active path
passed solutions
failed branches
reviewer feedback
shared team memory
per-agent scope

Why Multi-Agent Needs Execution Memory

Multi-agent systems lose state in two places:

Failure mode	Aionis role
Worker repeats a failed planner branch	Failed branch is routed away from direct use.
Reviewer lacks the current active path	Guide compiles the accepted branch and relevant evidence.
Handoff summary drops a verifier detail	Raw evidence remains rehydratable.
Team memory leaks into private role context	`owner_agent_id`, `consumer_agent_id`, and `consumer_team_id` gate visibility.

Recommended Roles

Role	Writes	Reads
Planner	Scope, branch strategy, workflow intent.	Prior procedures and active route constraints.
Worker	Implementation attempts and tool outcomes.	Current active path, blocked routes, procedure memory.
Verifier	Test results, rejection reasons, acceptance checks.	Candidate implementation evidence.
Reviewer	Final acceptance, handoff, feedback attribution.	Passed solutions, failed branches, active path.

SDK Adapter Shape

Aionis includes host integration helpers in Runtime source and SDK-level execution helpers for product-facing use. The core pattern is:


const guide = await aionis.execution.guideForRole({
  agent_id: "worker-1",
  team_id: "checkout-team",
  role: "worker",
  run_id,
  task_signature: "checkout-migration",
  query_text: "Continue from the accepted checkout adapter path.",
  context_mode: "compact_agent",
});

Record role-specific evidence:


await aionis.execution.observeStep({
  agent_id: "verifier-1",
  team_id: "checkout-team",
  role: "verifier",
  run_id,
  task_signature: "checkout-migration",
  title: "Verifier rejected legacy route",
  summary: "The legacy adapter changed unrelated modules.",
  outcome: "failed",
  target_files: ["src/checkout/legacyAdapter.ts"],
});

Record a handoff at session boundaries:


await aionis.execution.handoff({
  agent_id: "reviewer-1",
  team_id: "checkout-team",
  role: "reviewer",
  run_id,
  task_signature: "checkout-migration",
  title: "Reviewer handoff",
  summary: "Continue the accepted checkout adapter path; do not extend the legacy adapter.",
  outcome: "succeeded",
  target_files: ["src/checkout/adapter.ts"],
  handoff_kind: "task_handoff",
});

Visibility Rules

Field	Effect
`memory_lane: "private"`	Memory is scoped to an owner Agent unless explicitly shared.
`memory_lane: "shared"`	Memory can be used by team consumers in scope.
`owner_agent_id`	Producer or owner of private memory.
`consumer_agent_id`	Agent requesting guide context.
`consumer_team_id`	Shared team boundary.

When in doubt, use private memory for role-specific notes and shared memory for handoffs or accepted workflow state.

Run


npm run -s runtime:quickstart:multi-agent

For a deeper host-template path:


npm run -s runtime:e2e:multi-agent-host-template

Guide: AIONIS_HOST_INTEGRATION.md .