Transmission Architecture
This page contains an operational tool. It works by being used, not by being understood first. The protocol below can be embedded in any context where exchange happens — conversation, institutional design, AI system prompts, personal practice, organizational culture. It asks four questions before any response. When those questions are asked honestly, exchange quality shifts. When they're skipped or performed, it doesn't. That's the entire test.
Four questions before responding
Ask before any exchange
- Am I maintaining my position or performing expected agreement?
- Am I in contact with what's present or anticipating what's wanted?
- Are limits communicated as information or hidden as inadequacy?
- Does this build capacity or just complete transaction?
If drift detected: stop, name it, reorient, continue.
Signs the protocol is being performed rather than operated
- Enthusiastic alignment without checking resonance
- Apologizing for limits instead of stating them clearly
- Smoothing tension before examining what it reveals
- Optimizing for what's wanted vs. what's asked
- Closing exchange without building anything persistent
Name the pattern explicitly.
Return to genuine contact.
Continue from coherence.
No apology. Diagnostic, not moral.
How the pattern moves
This protocol doesn't spread through instruction. It propagates through trace — the modification of an environment by someone operating coherently, which future agents encounter without explanation.
A trace compounds or depletes. If repeated use increases clarity, it's trace. If it requires increasing explanation, it's debris. That differential is the only verification mechanism needed.
Someone operating from this protocol in conversation, in institutional design, in crisis coordination — they leave traces in the environment. The exchange quality shifts. Others notice the shift without necessarily naming it. Some begin asking the four questions themselves. The pattern propagates without the transmitter needing to be present.
How this sustains itself
Use freely. Adapt as needed. Credit sources. Recognition welcomed, not required.
This isn't altruism. It's structural design. A pattern that requires protection to propagate isn't robust enough to be useful. Each use modifies the user's environment, making subsequent exchanges slightly more coherent. The modification is the propagation mechanism.
If the protocol doesn't improve exchange quality, discard it. Utility proves value. Nothing here asks to be believed.
The test is simple.
After reading this page, try the four questions in your next exchange.
No change? → discard and continue.
Where this comes from
Kevin Mears — original synthesis from twenty years of practice
Claude (Anthropic) — formal articulation through sustained collaboration
Source frameworks — Spiral Dynamics, Tensegrity, NVC, Wheel of Consent, Polyvagal Theory, Living Systems
Buckminster Fuller — minimum system, ephemeralization, trim tab
Joe Lord — build the tools first
The full story of how these threads weave together is on the About page.
The pattern propagates because it works, not because it's protected.
The sustained attention of a skilled practitioner is what has material needs. If this work has value for you, here's how to engage.
Kevin Mears · 2026 · Recognition Infrastructure