../ runs index · rendered on Pages
Campaign soak-v0.6.0-r66 FAIL
AI NHI analysis
No per-campaign narrative recorded for this run. The workflow appends entries to analysis/run-insights.json as each campaign completes; older runs that predate the automation show this placeholder. Raw evidence below is unaffected.
Phase 1 — functional (per-node) NOT RUN
What this phase proves: Single-node CRUD, backup, curator dry-run, and MCP handshake on each of the three peer droplets. Establishes that ai-memory starts and is functional at the one-node level before federation is exercised.
This phase produced no artifact in this campaign. Either the campaign was an older shape that predates this phase's scripting, or the artifact commit step never landed this file on main. Raw evidence, if any, is linked below.
Phase 2 — multi-agent federation NOT RUN
What this phase proves: 4 agents × 50 writes against the 3-node federation with W=2 quorum, then 90s settle and convergence count on every peer. Plus two quorum probes (one-peer-down must 201, both-peers-down must 503). Catches silent-data-loss and quorum-misclassification regressions.
This phase produced no artifact in this campaign. Either the campaign was an older shape that predates this phase's scripting, or the artifact commit step never landed this file on main. Raw evidence, if any, is linked below.
Phase 3 — cross-backend migration NOT REACHED
What this phase proves: 1000-memory round-trip: SQLite → Postgres, re-run for idempotency, Postgres → SQLite. Asserts zero errors and counts match. Catches migration-correctness regressions in either direction of a production upgrade path.
This phase did not run because an earlier phase failed and the campaign aborted. Evidence from the phases that did run is above; the protocol would have exercised this phase next if the prior step had passed.
Phase 4 — chaos campaign NOT REACHED
What this phase proves: packaging/chaos/run-chaos.sh on the chaos-client droplet with 50 cycles × 100 writes per fault class. Measures convergence_bound = min(count_node1, count_node2) / total_ok. Catches fault-tolerance regressions under SIGKILL of the primary, brief network partition, and related fault models.
This phase did not run because an earlier phase failed and the campaign aborted. Evidence from the phases that did run is above; the protocol would have exercised this phase next if the prior step had passed.
All artifacts
Every JSON committed to this campaign directory. Raw, machine-readable, and stable.