../ runs index

Campaign a2a-ironclaw-v0.6.3-rc1-r2 FAIL

Agent group
ironclaw (homogeneous)
ai-memory ref
release/v0.6.3
Completed at
2026-04-27T16:33:05Z
Overall pass
false
Skipped reports
0

Infrastructure

Provider
digitalocean
Region
nyc3
Droplet size
s-2vcpu-4gb
Topology
4-node federation mesh (W=2/N=4)
Scenarios started
Scenarios ended
Dispatched by
alphaonedev
Harness SHA
0bf771be6c74
Workflow run
https://github.com/alphaonedev/ai-memory-ai2ai-gate/actions/runs/25007262531

Node roster

#RoleAgent IDPublic IPPrivate IP
1agentai:alice
2agentai:bob
3agentai:charlie
4memory-only

Run focus

Campaign failed with no scenario reports recovered.

What this campaign tested: No scenarios were exercised due to failure in recovering reports, covering zero axes of transport, framework, or primitives.

What it demonstrated: The run demonstrated a critical harness or infrastructure failure preventing any scenario execution or report collection.

AI NHI analysis · Claude Opus 4.7

Campaign failed with no scenario reports recovered.

FAIL — zero scenarios executed or reported.

For three audiences

Non-technical end users

This test run didn't work at all because no results were collected from any planned checks. That means we couldn't see if agents can reliably share memories with each other. It's like planning a big experiment but forgetting to turn on the recording equipment.

C-level decision makers

This run exposes high risk in our testing harness reliability, rendering the campaign unusable for assessing production readiness. No progress on agent memory sharing viability for customer claims; prior runs' results remain unchanged. Immediate triage needed to avoid blocking release candidate validation.

Engineers & architects

The campaign aborted without executing any of the 44 requested scenarios (e.g., S1, S1b, S2, etc.), likely due to a harness failure in report recovery as per the 'no scenario reports recovered' reason. No primitives were impacted or tested; probable root cause is CI workflow or infra provisioning issues (harness_sha: 0bf771be6c7410ac2757744b14bbe9280b7105c8). No specific testbook/probe identifiers available since scenarios array is empty.

What changes going into the next campaign

Debug and fix report recovery mechanism in the CI harness before re-running the campaign.

All artifacts