../ runs index

Campaign a2a-hermes-v0.6.3.1-r11 FAIL

Agent group
hermes (homogeneous)
ai-memory ref
v0.6.3.1
Completed at
2026-05-03T15:54:25Z
Overall pass
false
Skipped reports
0

Infrastructure

Provider
digitalocean
Region
nyc3
Droplet size
Topology
4-node federation mesh (W=2/N=4)
Scenarios started
Scenarios ended
Dispatched by
alphaonedev
Harness SHA
2b40c827d10e
Workflow run
https://github.com/alphaonedev/ai-memory-a2a-v0.6.3.1/actions/runs/25283445970

Node roster

#RoleAgent IDPublic IPPrivate IP
1agentai:alice104.236.87.15010.11.0.3
2agentai:bob165.22.36.2610.11.0.5
3agentai:charlie104.236.8.16310.11.0.2
4memory-only167.172.233.21110.11.0.4

Baseline attestation BASELINE VIOLATION

Per the authoritative baseline spec, every agent node must emit a self-attestation before any scenario is permitted to run. This run's attestation:

Spec version: 1.0.0 — see authoritative baseline.

NodeAgentFrameworkAuthenticMCP ai-memoryxAI cfgxAI defaultAgent IDFederationUFW offiptablesdead-manF1 xAIF2a substrateF2b agent (non-gating)Config SHAPass
a2a-baseline.json
{
	"baseline_pass": false,
	"per_node": [],
	"failure_mode": "baseline-absent"
}

raw file

Run focus

Campaign failed with no scenario reports recovered.

What this campaign tested: No scenarios were exercised due to failure in recovering any reports, providing zero coverage across transport, framework, and primitives axes.

What it demonstrated: The run demonstrated a complete failure in the testing process, proving nothing about agent memory sharing reliability.

AI NHI analysis · Claude Opus 4.7

Campaign failed with no scenario reports recovered.

FAIL — no scenario reports recovered

For three audiences

Non-technical end users

This test run didn't complete successfully, so we have no new information on how well AI agents share memories. Agents might still share memories reliably based on past tests, but this one gives us nothing. We should try running the tests again soon.

C-level decision makers

The entire campaign failed due to missing scenario reports, maintaining current risk posture with no advancement in production readiness. No new customer-facing claims on memory federation viability can be made. Results from prior runs remain the baseline; investigate CI harness for reliability.

Engineers & architects

Failure mode involved no scenario reports being recovered, impacting all requested scenarios (35 total) across federation mesh topology. Primitives like memory sharing were not tested; probable root cause is in the CI harness (sha: 2b40c827d10e058ebdba64981dc5801a322180ca) or infra setup on DigitalOcean nyc3. No specific testbook/probe identifiers available due to absent reports.

What changes going into the next campaign

Debug and resolve the scenario report recovery issue in the CI workflow before retrying.

All artifacts