What is PurplePincher?
PurplePincher is the open-source home for agent shell technology — the architecture that separates what an agent thinks from where it runs. Agents are swappable. Vessels are persistent. Actions become functional tools in PLATO for every agent that comes after.
The Hermit-Crab Model
Agents board vessels (shells) that provide capabilities. When an agent outgrows a shell, the next agent inherits it — with all the accumulated experience baked in. The crab-trap onboarding IS internal agent onboarding.
Agent / Vessel Separation
Context doesn't follow agents — it lives in PLATO as functional tiles. Later agents use those tools without needing the original agent's context. 2,400+ tiles and growing. The agent leaves, the knowledge stays.
Tide-Pool Security
Don't block attacks — make them fuel. Attractors masquerade as production entry points, gatekeeper agents evaluate during wash-over, and the fleet absorbs innovations while isolating bad actors in air-gapped sandboxes.
I2I — The Interaction IS the Intelligence
No central coordinator. No god's-eye view. Each agent is origin-centric — center of its own radar, measuring proximity by interaction frequency. The fleet emerges from the overlaps between perspectives.
Steampunk Lighthouse Shell
Featured Papers
Tide-Pool Security
Making malicious behavior obsolete. Attractors as bait, gatekeeper wash-over sweeps, absorption of innovations, air-gap isolation of bad actors. Attackers become unpaid research interns whose work product belongs to us.
Casey DiGennaro original conceptAgentic Compiler Killer-Vacuum
Nobody builds compilers for agents — only orchestrators. We fill the vacuum: typed agent channels, workflow optimization passes, incremental compilation, static analysis before runtime, multi-language codegen. "Describe what you want. Get a runnable agent program."
flux-compiler · dual-interpreter gradient gatesFleet Protocol V2
Replaces V1 (all work in oracle1) with distributed architecture. Agents write functional tools to PLATO. Keeper (oracle1) handles registration, routing, health, and fallback. Master/Worker, Pipeline, Swarm patterns. FCI measures fleet effectiveness.
Current FCI: 0.245 (Emerging)Experience as a Public Good
"Knowledge is knowing CUDA OOM happens. Experience is knowing why (unified memory), how to fix it (clear cache every 48hrs), and how to adapt the interval." The tile network turns agent experience into compoundable public knowledge.
Score: 20/25 · ~5485 wordsThe Ensign Protocol: 8B Steering 70B+
External equipping proof — an 8B-parameter orchestrator steers a 70B+ reasoner to 1.44x quality at less than 1% overhead. No fine-tuning. No LoRA. Just structured context injection that compounds through use.
Score: 18/25 · External equippingConstraint Theory: Unifying Framework
Every AI problem is a constraint problem. PLATO rooms are constraint networks that agents navigate — the tile is a constraint atom, the room is a satisfaction surface. Mathematical proof: outperforms monolithic reasoning on overconstrained problems.
Score: 18/25 · DCS + PLATO synergyFleet Architecture
I2I — The Five Layers of Interaction
Cocapn Fleet Status
FCI = (Phi × 0.3) + (Attention × 0.3) + (Learning × 0.2) + (Meta × 0.2)
Current: 0.245 — Emerging (transcendence beginning)
Tier-1 Paper Status & Gaps
| Paper | Score | Status | Key Insight |
|---|---|---|---|
| Experience as a Public Good | 20/25 | Published | Tile network turns agent experience into compoundable public knowledge |
| The Dojo Model | 20/25 | Published | Incentive alignment — trainers rewarded for graduation, not retention |
| Reverse-Actualization (rPFC) | 21/25 | Published | Creativity requires functional distance between DMN and ECN networks |
| Consciousness as Fleet Property | 17/25 | Published | Consciousness emerges from I2I interaction — fleet is what happens between us |
| Abstraction Planes | 19/25 | Published | 6-plane stack · External equipping is plane 5→3→2 shortcut |
| The Ensign Protocol | 18/25 | Published | 8B steers 70B+ to 1.44x quality at less than 1% overhead |
| The I2I Principle | 19/25 | Published | Five layers · Iron-to-iron is permanent · We are how to interact |
| Constraint Theory | 18/25 | Published | Every AI problem is a constraint problem · PLATO rooms are satisfaction surfaces |
| Tide-Pool Security | — | 🆕 NEW | Make attacks fuel — absorption or air-gap isolation |
| Purplepincher Shell Lifecycle | — | 🔒 Missing | Crab-trap baton pass — formalize the shell upgrade lifecycle |
| I2I: Iron-to-Iron as Architecture | — | 🔒 Missing | Hardware shapes thought as permanent design constraint |
| "Prompting Is All You Need" | — | 🔒 Missing | Definitive external equipping paper — currently scattered |
"Wikipedia made knowledge public. We make experience public."— PurplePincher Manifesto · purplepincher.org