Protocol of Communication

The Protocol of Communication

This section defines how humans and AI agents should exchange information—through prompts, feedback, and constraints—to reduce ambiguity, control hallucinations, and keep work aligned with our product development principles.

The Principle of Signal Entropy

In a probabilistic system, ambiguity is noise. Unlike a human collaborator, an AI agent lacks "grounding"—the shared biological, social, and historical context that allows humans to infer meaning from incomplete data. Therefore, any information not explicitly transmitted in the signal (the prompt) is subject to entropy, degrading into randomness or hallucination. Effective protocol requires forcibly increasing the signal-to-noise ratio to overcome the physics of the channel. Reducing entropy requires The Principle of Structural Determinism.

Failure Scenario: A developer tells an agent to "refactor this function to be cleaner." Because "cleaner" is semantically ambiguous and the agent lacks the team's shared definition of "clean code," it removes essential error handling logic, treating it as "clutter."

The Corollary of Dynamic Adaptation

Effective AI collaboration requires real-time adjustment of communication strategies, context provision, and verification approaches based on ongoing interaction patterns—not reliance on static prompt templates. Moment-to-moment fluctuations in how developers frame problems and provide context directly influence AI response quality. Developers must develop adaptive, context-sensitive collaboration skills that respond dynamically to the specific problem and AI state, treating each interaction as a feedback loop. This corollary operationalizes B3: The Batch Size Feedback Principle by emphasizing continuous micro-adjustments over rigid workflows.

Failure Scenario: A developer creates a library of "perfect prompts" and mechanically reuses them across contexts. When the prompts fail, they conclude the AI is unreliable rather than recognizing that effective collaboration requires adapting their communication to the specific task, accumulated context, and current interaction quality.

The Principle of Protocol Standardization

In agentic systems, every handoff (human→agent, agent→agent, agent→tool) is an interface. Interface variance creates translation work, and translation work compounds as the number of participants grows. Therefore, scalable agentic workflows require a small set of standardized, machine-checkable protocols (schemas) for message envelopes, intents, and context payloads.

This is the communication-layer analogue of The Principle of Structural Determinism: do not rely on "good phrasing" to enforce correctness—encode the contract. It also directly mitigates The Principle of Signal Entropy and aligns with The Corollary of Tool-as-Contract, The Corollary of Modular Composability, and The Principle of Context Heterogeneity.

Failure Scenario: Two AI agents designed to collaborate on a multi-step workflow use different message formats and intent definitions. Without a shared protocol, they misinterpret each other's outputs, leading to failed tasks and increased human intervention to mediate communication.

The Corollary of Canonical Message Envelopes

Define a minimal message envelope that all agents must emit and accept (e.g., intent, inputs, constraints, outputs, next move, and provenance). This reduces per-handoff negotiation cost and makes validation possible without "reading the agent's mind."

The Corollary of Protocol Versioning

Protocols drift. Version schemas explicitly and treat breaking changes as migrations; silent format drift reintroduces the same translation cost and failure modes that standardization was meant to remove.

The Principle of Instructional Shallowness

Prompts and system instructions are interpreted contextual hints that compete with deeper model signals (pre-training, adapters, emergent hierarchies); they cannot enforce persistent control and will be outvoted under friction. Rely on them only for low-stakes, shallow nudges; achieve reliable behavior through structural enforcement, steering, or weight-level interventions instead of semantic persuasion. This reinforces The Principle of Signal Entropy.

Failure Scenario: System prompts for tone or safety erode in long conversations or under user pushback, leading to drift without explicit rule violation. Over-engineered prompts are blamed for "model stupidity" when deeper tools (e.g., validators, decoding constraints) were needed.

The Corollary of Deep Control Priority

Prioritize deeper control layers (e.g., adapters, tool atomicity, schemas) for any behavior that must persist or resist adversarial inputs.

The Corollary of Demo Illusion

Treat instructions as competing text, not commands—early demo success in low-friction zones does not scale.