Membrane
What it is
A gated community without fences — where you can leave the door unlocked. Not because you're careless, but because the design of the space means you never needed the fence. You built it right once; the community is alive and knows who it is. The unlocked door isn't a risk — it's confidence in what you put in place.
That is what the membrane gives a system designer. Not better locks. Not a smarter gate. A design where you stop thinking about locks.
It is the layer that makes intent transmissible — not a filter, not a gateway, not a smarter wrapper around existing infrastructure.
The internet moves documents — HTTP, email, API calls, all traveling A to B. AI communicates through intent. These are not compatible, and every bridge between them — MCP, OpenAPI, natural-language wrappers — is a translation layer on a broken foundation. You can make the translation better. You cannot make it correct. The membrane does not translate. It carries.
Why existing approaches fail
- MCP — a fuzzy natural-language layer over undocumented systems, interpreted differently by context. Not a contract, not enforced.
- OpenAPI — schema on REST on HTTP. More ornaments on the same tree.
- Raw API docs — unambiguous but unmaintained. Nobody keeps them current.
- Exposing the codebase — unacceptable: security, IP, practicality.
All are documents about what a system can do. The membrane is not a document — it is a surface through which intent flows or does not.
Security as structure
The membrane protects both directions: nothing corrupted enters (injection, manipulation), nothing unintended leaves (leaks, exposure). Not because rules check for it — because there is no path for it. What is not permitted has no path. Not a blocked path. No path.
A filter can be bypassed, a rule argued around, a decision-maker manipulated. The membrane offers none of those: it routes, and the signal finds a permitted path or none.
(The full argument — wall-first, frozen, pattern-only — is in MANIFESTO.md. The one-page model is SYSTEM.md. The mechanics are ARCHITECTURE.md.)
What building it reveals
Defining the membrane forces implicit trust to become explicit. Every system has undocumented trust baked in — assumptions never written down because they never needed to be. Deciding what carries through surfaces those contracts for the first time. Side effect: the best documentation of your system's trust model you have ever had.
Name
Membrane — not a wall, not a door. A living boundary that carries exactly what the system was designed to carry, learns from what flows through it, and protects in both directions.
Pim Bongers, Studio Bonkers, June 2026 With Claude