Federation

Omnipotent separates private work from collaborative work at the protocol level. Your secrets stay local. Your shared plans travel through the Airlock.

Two Domains

The Keep (Sovereign Domain)

Your private workspace. Sensitive data, proprietary patterns, and personal session history stay here. Anything within this domain is physically isolated from any external service.

• Scope: Local-only infrastructure
• Privacy: Cryptographically isolated session logs
• Rationale: By enforcing a local-first boundary for the Keep, the system ensures that sovereign logic never touches a network adapter unless explicitly promoted to collaborative scope.

The Commons (Alliance Domain)

The shared workspace for team collaboration. Shared strategic goals, architectural patterns, and collective documentation live here.

• Scope: Shared organizational environment
• Collaboration: Multi-agent synchronization of strategic artifacts
• Rationale: Provides a "neutral ground" where multiple realms can synchronize state without compromising the security of their individual sovereign domains.

The Diplomat Agent

The Diplomat is the specialized custodian responsible for managing the secure transition of artifacts across the Airlock boundary. It ensures signal integrity and handles conflict resolution during synchronization events.

How Synchronization Works

1. Validate Boundary. The system verifies the integrity of the Airlock before any data movement occurs.
2. Pull Collective State. Fetches the latest architectural patterns and strategic goals from the shared domain.
3. Resolve Conflicts. Applies incoming updates. Any logic collisions are flagged for human-in-the-loop review.
4. Push Promoted Artifacts. Any local artifacts explicitly promoted to the shared scope are synchronized.
5. Audit. The entire event is cryptographically logged to the system's permanent audit trail.

Airlock Crossing Rules

The Airlock is a hard architectural boundary enforced by the Kernel.

1. Explicit promotion required. Artifacts must be manually moved from the private Keep to the shared Commons.
2. Uni-directional visibility. The synchronization layer has zero visibility into the private Keep.
3. Immutable audit trail. Every transition across the boundary is logged and verified by the security layer.
4. Atomicity. Strategic goals are synchronized as complete executable units to prevent logic fragmentation.

Setting Up Federation

# Initialize in alliance mode with a Commons URL
omnipotent init \
  --federation https://github.com/your-org/commons.git \
  --mode alliance

# Run initial sync
omnipotent diplomat

# Enable continuous background sync
omnipotent diplomat --watch --interval 60

Related

• Airlock Protocol — Technical details of the boundary enforcement
• Diplomat Protocol — Sync lifecycle and running modes
• Agents — The Diplomat agent profile