Repository navigation
examples: Add MEP (Meat Puppet Elimination Protocol) — async state relay for multi-machine AI sessions - #42996
CRMinarian wants to merge 3 commits into
Conversation
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 <[email protected]>
MEP was relicensed upstream on 2026-08-11. AGPL made this contribution unmergeable into a permissively licensed repository, which was never the intent: the whole point of publishing the protocol is that people can implement it freely. Code, templates, and skills are now Apache 2.0. The specification documents are CC BY 4.0. Implementing MEP requires no permission and imposes no obligation.
|
Bumping this with a change that matters. This PR was filed under AGPL-3.0, which made it unmergeable into a permissively licensed repo regardless of merit. That was my mistake and it has been fixed upstream. MEP is now Apache 2.0 for code, templates, and skills, and CC BY 4.0 for the specification documents. Implementing it requires no permission and imposes no obligation. Pushed the corrected licence line to this branch. The contribution is three files and 133 additive lines under examples/, no changes to anything existing. It documents a pattern for carrying context between stateless Claude Code sessions across machines, which is a problem people hit constantly and currently solve by hand. Happy to adjust scope, placement, or wording if examples/ is not the right home for it. Full spec: https://github.com/NukaSoft/mep-protocol |
1 participant
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
CLAUDE.mdhandoff.mdYour only job: open a session and say
/eolwhen done. The agent handles the rest.What's in This PR
examples/mep/README.md— explanation + quick startexamples/mep/CLAUDE.md— drop-in session protocol templateexamples/mep/handoff.md— blank baton templateProduction Proof
April 3, 2026: a merge conflict in
handoff.mdwas 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.