federation-sync

Synchronize claims and hypotheses across peer vaults via a shared exchange directory.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/achousal/EngramR --skill federation-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: federation-sync
Source: https://github.com/achousal/EngramR/tree/main/.claude/skills/federation-sync
Command: npx skills add https://github.com/achousal/EngramR --skill federation-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Synchronize and federate claims and hypotheses across peer vaults using a shared exchange directory to maintain consistency without deploying servers.

Core Features & Use Cases

  • File-based federation exchange with no server infrastructure required.
  • Respect for trust levels and quarantine policies during exports and imports.
  • Export of claims from notes/ and export of hypotheses from _research/hypotheses/, with manifests tracking identity and timestamp.
  • Import and export workflows with per-peer synchronization and provenance logging.
  • Support for configurable export/import filters and federated Elo fields for cross-vault ranking.

Quick Start

Configure ops/federation.yaml and run the federation-sync agent to begin exchanging claims and hypotheses with peers.

Frequently Asked Questions about federation-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I synchronize claims across peer vaults without deploying a server?

You can synchronize claims across peer vaults without a server by using a file-based exchange directory. The system applies trust levels and quarantine policies to control imports and exports while tracking file manifests.

How does file-based federation exchange handle trust levels and quarantine policies?

File-based federation exchange enforces trust levels and quarantine policies during imports and exports. This ensures that only compliant claims and hypotheses are transferred between peer vaults via the shared directory.

Can I configure export and import filters for federated vault synchronization?

Yes, you can configure export and import filters for federated vault synchronization. The system supports per-peer synchronization, provenance logging, and federated Elo fields for cross-vault ranking.

What is the best way to track provenance when importing hypotheses from peer vaults?

The best way to track provenance when importing hypotheses is through manifest tracking. Manifests record identity and timestamp data during exports from _research/hypotheses/ and subsequent peer imports.

How do I start syncing claims using the federation exchange directory?

To start syncing claims, configure the ops/federation.yaml file and run the federation-sync agent. This initiates the exchange of claims and hypotheses with peers using your shared directory.