Protocols

Omnipotent's behavior is governed by four core protocols. Each defines rules that agents must follow — no exceptions, no overrides.

Mnemosyne Protocol

The tiered memory system that prevents context drift and hallucination. Named after the Greek titaness of memory.

Memory Tiers

The Menoms Review

At the end of every milestone, the Mnemon agent triggers this ritual:

1. Read raw logs from the session
2. Synthesize a "Wisdom Block" (condensed lessons learned)
3. Append to wisdom.md (The Scroll of Truth)
4. Archive raw logs to Cold Memory via pgvector embeddings

Context-Slicing (Mnemon Protocol)

The system employs a high-density information pipeline for processing complex strategic goals. Instead of saturating model context windows, Omnipotent segments data into executable atoms.

Airlock Protocol

Enforces "Church & State" separation between your Sovereign Domain (private) and the Alliance Domain (shared).

The Keep (Sovereign Domain)

• Scope: Local infrastructure only
• Memory: Private session history and local vector stores
• Rationale: Physical isolation ensures that private logic and sensitive keys are cryptographically unreachable from any external network sync.

The Commons (Alliance Domain)

• Scope: Shared organizational repository
• Memory: Collaborative plans and pattern libraries
• Rationale: Provides a controlled environment for team collaboration where artifacts are explicitly promoted from private to shared scope.

Crossing Rules

Data never "leaks" between domains. It must be explicitly promoted:

• To share: promote a strategic plan from the sovereign path to the alliance path.
• The system monitors only the alliance-scope directories, maintaining zero visibility into the private Keep.

Swarm Protocol

Agent coordination via the blackboard pattern. All agents synchronize through a shared state repository.

The Blackboard

This centralized state file serves as the system's "nervous system," tracking:

• Current execution phase and multi-agent milestones
• Task-to-role mapping and individual agent status
• System health signals and inter-agent coordination tokens
• Critical blockers and parallel workstream dependencies

Concurrency: The Sharded Swarm

1. Branch Locking: Before an agent starts a task, it checks for a remote branch feat/{task_id}. If it exists, the task is locked by an ally.
2. Worktree Isolation: Complex tasks run in isolated Git worktrees to prevent file-lock collisions on your local machine.

Diplomat Protocol

Git-based federation sync. The Diplomat agent is the only entity allowed to cross the Airlock boundary.

Sync Lifecycle

1. Diplomat checks .realm/federation.json for the Commons URL
2. Pulls latest from the Commons remote
3. Merges Alliance-side changes into local state
4. Pushes local Alliance changes back to Commons
5. Logs the sync event to the audit trail

Running Modes

Related

• Architecture — System overview and memory tier details
• Federation — Deep dive into Sovereign vs Alliance
• Agents — Mnemon, Diplomat, and other protocol custodians