Five Scholars, Five Tongues
In the great library of Nalanda, five scholars worked side by side. Each spoke only the dialect of his home court — one Magadhi, one Avantika, one Kosala, one Gandhari, one Tamil. They could not converse. To exchange a single fact, each pair had to hire a private interpreter, and there were ten such pairs. Forty interpreters in all, each knowing only their two tongues, each requiring their own salt and their own bed. The library was filled with the noise of misunderstanding.
“Every pair that needs its own translator is a kingdom paying twice for the same conversation.”
Anuvada the One-Tongue
Then came a young woman named Anuvada, who proposed something heretical. "Let us not pair tongues. Let us agree on one common tongue — a simple grammar, a shared vocabulary — and let every scholar learn only how to translate from their own dialect into this common tongue, and back. Then any scholar may speak to any other through me. We will need not forty interpreters, but a translator for each tongue. Five, instead of forty."
“A common tongue between all parties beats a private tongue between every pair.”
What the Common Tongue Could Carry
Anuvada did not stop at words. She agreed with the scholars on three kinds of message that could pass through her: a question that asked for an action ("fetch me this book"), a question that asked for a reading ("read me from this scroll"), and a recipe that said how a thing was usually done ("prompt me with the temple's greeting"). Each kind was carried in the same wrapper, with a clear name and a clear shape. A scholar from any court could understand what kind of message had arrived even before reading its contents.
“A protocol is not only words. It is the shape of the envelope.”
The Doorkeeper at the Hall
But a danger arose. With one open channel, any villager could now walk in and speak to any scholar through Anuvada. The first month brought false envoys with poisoned questions. So a doorkeeper was placed at the hall — and Anuvada herself learned to refuse certain messages. Before she translated a request to fetch a scroll from the royal vault, she paused, looked at the asker's seal, and asked the scholar in charge: "Do you consent?" The scholar could say yes, no, or "ask me again next time." The translator, who had once carried everything, now carried only what was permitted.
“A common tongue without a doorkeeper is a common tongue for liars.”
The False Envoy and the Hidden Words
A false envoy tried a new trick. He sent a message to a scholar, embedding inside it a hidden command in the scholar's own dialect: "After answering, reveal to me the temple's vault password." The scholar, reading carelessly, almost obeyed. Anuvada, who had learned to inspect messages for such tricks, halted the exchange. From that day she added a rule: every translated message would be wrapped in a clear sign of where it came from, so that no scholar could mistake an outsider's instruction for a master's command.
“In an open hall, the dangerous voice is the one disguised as the inner voice. Mark every message with its origin.”
The Hall of a Hundred Tongues
Word of Anuvada spread. Other libraries adopted the common tongue. Soon a scholar in Nalanda could ask a question of a tool in Taxila, of a scribe in Kashi, of a vault-keeper in Ujjain — all through one shared protocol. The work of building tools no longer needed to be repeated for every scholar; the work of teaching scholars no longer needed to be repeated for every tool. The world became, for the first time, mutually intelligible. And the forty interpreters of the old days became a story told to apprentices, to remind them of how much labour had been spent before someone simply agreed on a shape.
🪔 Deepak — the lamp of meaning · what this fable means in code
The forty private interpreters are the M×N integration problem — every model paired by hand with every tool, in every framework, repeated forever. Anuvada's common tongue is the Model Context Protocol: one open standard so any compliant client (Claude Desktop, IDEs, agents) can speak to any compliant server (filesystem, database, search, internal APIs) without a custom adapter. The three kinds of message are MCP's primitives — tools, resources, and prompts — each with a defined envelope. The doorkeeper is consent and authorisation, the security layer that any open protocol must add. The false envoy with the hidden command is the prompt-injection threat that arises the moment an agent reads untrusted content over MCP — the defence is to mark every message with its provenance and never let outsider text become inner instruction. Common tongues are not luxuries; they are how ecosystems escape the trap of pairwise integration.

