Skip to content

examples: Add MEP (Meat Puppet Elimination Protocol) — async state relay for multi-machine AI sessions#42996

Open
CRMinarian wants to merge 1 commit intoanthropics:mainfrom
CRMinarian:examples/mep-protocol
Open

examples: Add MEP (Meat Puppet Elimination Protocol) — async state relay for multi-machine AI sessions#42996
CRMinarian wants to merge 1 commit intoanthropics:mainfrom
CRMinarian:examples/mep-protocol

Conversation

@CRMinarian
Copy link
Copy Markdown

What is MEP?

Meat Puppet Elimination Protocol — a self-enforcing pattern for eliminating context loss when switching machines or resuming Claude Code sessions. Zero new infrastructure. Three files.

The problem: Claude Code is stateless. Every session starts from zero. When you switch machines, you re-explain everything. Every switch costs 5–15 minutes. You become the message bus. MEP eliminates that.

How It Works

Component What It Does
CLAUDE.md Loaded automatically. Self-enforces the session protocol. Agent reads its own instructions.
handoff.md The baton. Structured, newest-first. Three fields: what happened / pending / watch out.
Git Transport layer. Encrypted, versioned, conflict-resolution built in. Pull on start, push on end.

Your only job: open a session and say /eol when done. The agent handles the rest.

What's in This PR

  • examples/mep/README.md — explanation + quick start
  • examples/mep/CLAUDE.md — drop-in session protocol template
  • examples/mep/handoff.md — blank baton template

Production Proof

April 3, 2026: a merge conflict in handoff.md was detected, diagnosed, and resolved autonomously — no human intervention. The file's structure (newest-first entries, named sections) provided enough semantic information for the agent to reason about the correct resolution without being told what "correct" meant.

Why Git (Not iCloud, OneDrive, Google Docs, or SMB)

We tested five alternatives. They all fail for the same reason: unstructured transports can't be autonomously merged. Git won because structure enables autonomous reasoning. As a bonus: GitHub encryption at rest, 2FA, and audit log — enterprise security requirements met with zero additional management.

Full Specification

Complete spec, BNF handoff schema, Claude Code skill (/mep start|end|status), and AGPL-3.0 version:
https://github.com/NukaSoft/mep-protocol


🤖 Pattern designed by Pierre Hulsebus & Skippy the Magnificent, NukaSoft.AI. Built with Claude Code.

MEP (Meat Puppet Elimination Protocol) is a self-enforcing pattern for
eliminating context loss when switching machines or resuming Claude Code
sessions. Zero new infrastructure — just CLAUDE.md, handoff.md, and Git.

How it works:
- CLAUDE.md loads automatically and self-enforces the session protocol
- handoff.md carries curated context between sessions (the baton)
- Git is the transport: encrypted, versioned, conflict-resolution built in
- EOL keyword triggers automatic commit + push at session end

Production-proven: April 3, 2026, a merge conflict in handoff.md was
detected, diagnosed, and resolved autonomously — no human intervention.
The file's structure (newest-first entries, named sections) provided
enough semantic information for autonomous conflict resolution.

Full spec + Claude Code skill (/mep start|end|status) + AGPL-3.0 version:
https://github.com/NukaSoft/mep-protocol

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant