Governance Season: An Open-Source Retrospective for MCP and Multi-Agent Memory

Description and use

An open‑source governance framework for MCP and multi‑agent memory that uses signed capabilities, provenance metadata, and dry‑run rsync checks to prevent accidental deletions and enable rapid remediation of poisoned data.

Problem

A rsync job with a deleted exclusion list removed 70+ private modules, revealing that agent stacks can silently propagate poisoned data through shared memory and unscoped tools.

Outcome

The system now prevents accidental deletions, tracks provenance of memory writes, and provides a governance framework that surfaces and resolves conflicts before they become incidents.

Workflow

• Rebuild exclusion list and manually restore missing modules
• Add signed capability files to MCP servers and reject unsigned or overly privileged tools
• Add provenance metadata to every memory write
• Implement dry-run rsync checks before deletion
• Establish incident ledger and governance artifacts
• Use council arbitration for conflicting memory claims

Evidence

rsync pulling modules off a dev box into a working tree, --delete on, an exclusion list deciding what survived the pass.

Source

Every server ships a signed capability file — tool names, input and output schemas, the scopes it claims, and an owner key on it.

Source

Every write into shared long-term memory now carries agent_id, tool_call_id, source_hash, timestamp, and a confidence value.

Source

The fix that came out of the sync incident had nothing to do with the exclusion list. Every run now does a dry pass first: the same rsync invocation with --dry-run.

Source