Pluribus

Privacy-safe context receipts for AI coding agents — plus audits/sync for the instruction files they actually load.

Pluribus (pluribus-context on npm, pluribus on the command line) is a CLI for agent context evidence. It helps teams answer: what instruction file, skill, MCP/tool schema, memory/RAG result, compaction, pruning step, or generated rule actually crossed an agent boundary — without logging raw prompts, source code, tool output, paths, transcripts, secrets, or customer data.

The original sync workflow is still useful: Pluribus can keep project instructions, conventions, constraints, and team context in one versioned pluribus.md source of truth, then generate native files for Claude Code, Cursor, GitHub Copilot, OpenClaw, Windsurf, Continue, Zed, and Bob. The sharper wedge is evidence: read-only audits and receipts show where context keeps fidelity, downgrades to a generic fallback, duplicates, stays deferred, hydrates, gets pruned, or rolls back after failed compaction.

It is not a persistent memory layer, retrieval system, agent orchestrator, enterprise ContextOps platform, or agent-merging framework. Think evidence for context boundaries: CLAUDE.md, .cursorrules, copilot-instructions.md, AGENTS.md, MCP Tool Search, Agent Skills, RAG/code-search, pruning, and compaction — with privacy-safe receipts instead of raw content dumps.

Pluribus sits beside context layers rather than replacing them. The boundary is easiest to see by comparing the jobs:

Layer	Question it answers	Example
Storage + retrieval	What memory should an agent recall?	ContextVault and MCP/RAG memory systems
Behavioral ablation	Did removing one rule change behavior in this harness?	rulecov
Cross-tool boundary evidence	Which exact source/target was configured, observed by the native loader, and tied to an accepted or reverted outcome?	Pluribus

Pluribus does not replace memory ranking or causal rule experiments; it can preserve their outputs as evidence at the next boundary. A useful receipt separates configured, visible, loaded, invoked, and accepted_or_reverted so a team can tell the difference between “this context exists somewhere,” “this harness reacted to it,” and “this exact context governed a useful run.”

See the core workflow in 30 seconds: open the browser-only context sync demo, edit one rule, preview CLAUDE.md, AGENTS.md, or .cursorrules, and inspect the source/output hashes. It makes the boundary explicit: generation is proven; runtime load and task outcome remain unknown until the client supplies evidence.

Field evidence: the public evidence ledger separates maintainer-shipped outcomes, independently reviewed contributions, and directory distribution across trace privacy, handoff continuity, skill use, runtime authority, freshness, and mutation safety. It says exactly what each result proves—and does not call it Pluribus adoption.

Project transparency and continuity