Stand in front of any Ashokan rock in the Indian heartland — Maski, Erragudi, Brahmagiri, Rupnath — and what you see is Brahmi. Brahmi was the script the central administration used; the language inscribed was an amalgam of Prakrit dialects.
Walk three thousand kilometers northwest to Shahbazgarhi in modern Pakistan and the script changes. Same king, same general kinds of message — but the inscription is in Kharoshthi, a script that ran right-to-left, derived from Aramaic, used across the upper Indus and Swat valleys bordering Afghanistan. Walk a hundred kilometers further west to Mansehra in Hazara district — Kharoshthi again. The script is regionally specific to the northwest.
Walk further west into Afghanistan, to old Kandahar, and the script changes again. Two scripts this time, one above the other on the same stone — Greek above, Aramaic below. The first Afghan rescript Ashoka caused to be carved used neither Brahmi nor Prakrit. He used the local languages of governance — Greek (which had spread with Alexander's successors and remained the administrative language of the Hellenistic-Indian frontier) and Aramaic (which had been the Achaemenid Persian empire's administrative language and persisted as a written-bureaucratic tool throughout the region).1
Four scripts. One empire. The choice of script at each location wasn't accidental — it tracked the administrative-linguistic conventions the local audience and bureaucracy already used.
The Mauryan empire stretched from Afghanistan to Karnataka, from Gujarat to Bengal. No single script-language pair could reach the whole territory. Lahiri describes the strategic logic: "Ashoka's edicts were inscribed in languages used here in governmental memoranda. It was a pragmatic decision. If the administrators of large parts of India conducted official business in Prakrit, in this part of Afghanistan the familiarity was with Greek and Aramaic. By using these the administration was ensuring trouble-free dissemination by factoring in the nature of bilingualism here."1
The decision tree the imperial office must have applied:
Each script choice was a recognition of where the local administrative competence was already located. The empire didn't impose a single bureaucratic language on every region; it met each region in the bureaucratic language already operating there.
Across the entire Ashokan corpus — hundreds of inscriptions at scores of sites — exactly one scribe is named. Capada signed off the three Karnataka inscriptions at Brahmagiri, Siddapura, and Jatinga-Rameshwara. His signature appears in all three texts.1
But Capada signed in a different script than the inscriptions themselves. The Karnataka inscriptions are in Brahmi. Capada's signature is in Kharoshthi.
Why would a scribe working in Karnataka sign in the script of the northwest frontier? Lahiri's reading: he was showing off, or signaling. "Capada may have used Kharoshthi for signing off to show his dexterity with scripts, as also perhaps to signal that he either hailed from or was in some way linked with north-west India."1 Either he was a northwesterner whose Kharoshthi was native and his Brahmi acquired; or he was a Brahmi-native showing that his training included both scripts. Either way, the signature reveals that scribes in Ashoka's administration were sometimes literate in multiple scripts and would occasionally announce it.
The named scribe is exceptional. Most engravers and clerks across the empire are anonymous. Capada's signature is the documentary signature of an Ashokan administrative class that had developed multi-script competence — at least at the upper levels. We see one such individual because he chose to sign; presumably there were others who did not.
At Erragudi in Andhra, the engraver did something unusual. Part of the inscription is boustrophedonic — the lines run alternately left-to-right and right-to-left, the way oxen plow a field (Greek bous = ox, strophe = turn). Boustrophedon was a feature of some ancient Greek inscriptions and not standard for Brahmi.
Lahiri's interpretation: "Was this unnamed scribe using the rock surface to suggest that he was familiar with other writing systems? Kharoshthi was the only regional script written from right to left, so was the engraver indicating his possession of a more cosmopolitan knowledge of scripts?"1
The engraver only sustains the boustrophedon for part of the inscription. "And why did he give up writing in this way after a few lines? The rest of the text, in fact, was rather haphazardly put down on the remaining space, with no concession to readability at all."1 He started showing off; he ran out of patience or runway; the rest went on the rock however he could fit it.
Lahiri's verdict on his work is wry: "What can certainly be said is that every official who expected to read or translate this engraving would, instead of marvelling at the engraver's skill, have roundly cursed the fellow for his rotten cursive. Boustrophedon is not exactly easy on the eye at the best of times."1
The Erragudi engraver is anonymous; we don't know his name. But his hand reveals an Ashokan engraver-class with sometimes-self-conscious literary ambitions, occasionally trying to show off and producing inscriptions worse than the simple straightforward ones. The episode is human in a way most ancient inscriptions aren't.
The Kandahar Greek-Aramaic inscription deserves its own attention because it shows the script-pluralism approach at its most elaborate. Greek above, Aramaic below. Paul Bernard, the principal modern scholar of the inscription's Greek, calls the Greek itself "a language full of vitality, aware of contemporary usage, skilled in the handling of the literary language, familiar with the terms used by philosophers and sophists, as well as those found in the vocabulary of politics."1
This wasn't a translator's rough rendering. This was Greek prose written by someone who knew Greek literary and philosophical conventions. The Greek inscription uses eusebeia for dhamma, diatribe (school of philosophy) for pasamda (Indian religious sect), enkrateia (self-control) for the Indian concept of restraint. The translator was working hard to find the closest Greek equivalents for Indian concepts — and producing Greek that worked as Greek prose rather than as awkward translation.
Below the Greek, the Aramaic does similar work in a different cultural-conceptual vocabulary. The Aramaic uses qshyt (truth) where the Greek uses eusebeia (piety). The Aramaic translator chose a different conceptual anchor for dhamma — neither the Greek piety-of-religious-observance frame nor the Indian moral-cosmological frame, but a Persian-cultural truthfulness frame.
The same Indian dhamma concept gets three readings across the trilingual situation: the Indian original (cosmological-moral), the Greek translation (philosophical-religious), and the Aramaic translation (Persian-truthful). Each translation makes audience-specific choices about how to render an alien concept in already-existing local vocabulary. The script-pluralism is not just orthographic; it's conceptual translation across cultural-linguistic frameworks.
Lahiri's page treats Brahmi as the empire's administrative default without asking where the script itself came from. Olivelle (2023) takes up that prior question directly, and it turns out to be genuinely unsettled.2
Kharoshthi's origin isn't in dispute — there's scholarly consensus it predates Brahmi and was based on, or influenced by, the Aramaic script already in heavy use across the neighboring Achaemenid empire. Both Kharoshthi and Aramaic read right-to-left; Brahmi, like every later Indian script it fathered, reads left-to-right. Kharoshthi stayed geographically boxed in — the greater Gandhara region centered on Taxila — and fell out of use by roughly the third century CE. Richard Salomon's summary of the contrast is blunt: "Unlike Kharoshthi, which was always geographically limited and died out at a relatively early period, the Brahmi script appeared in the third century B.C. as a fully developed pan-Indian national script... and continued to play this role throughout history, becoming the parent of all of the modern Indic scripts."2
That word "appeared" is doing real work. Ashoka's inscriptions are the earliest surviving examples of Brahmi anywhere. Did the script pre-exist him, or was it invented by him or under his direction? Olivelle calls this "still an open question," with books written and scholarly debate ongoing. Several scholars propose Brahmi was invented by Ashoka or shortly before his reign — a thesis that remains widely accepted despite challenges. Claimed pre-Ashokan Brahmi graffiti on potsherds from southern India and Sri Lanka exists, but hasn't won universal acceptance as genuine counter-evidence. Even granting the script might predate Ashoka slightly, Olivelle notes it "could not have been very old" — Brahmi was new at the time of Ashoka's inscriptions, and the way it's actually used across the corpus (from the earliest Minor Rock Edicts in the south to the latest Pillar Edicts on the Gangetic plain) shows scribes and stonemasons "learning the craft as they went along," the visible signature of a still-forming, not long-established, writing tradition.2
This adds a genuinely new layer under the vault's existing script-pluralism material: the plurality itself (Brahmi/Kharoshthi/Greek/Aramaic) was a deliberate administrative accommodation, as Lahiri's page documents — but one of the four scripts in that accommodation may have had no existence at all before Ashoka's own reign commissioned or invented it. If so, Ashoka wasn't simply choosing among four pre-existing regional writing systems to reach four regional audiences. He may have had to build one of his four communication channels from scratch before he could use it.
Olivelle adds a further, striking data point on the logistics this newness implies: the anonymous engravers and scribes who executed Ashoka's inscriptional program are almost entirely unnamed — with exactly one exception. A scribe named Chapada, native to the Gandhara region in the northwest (Kharoshthi's home territory), signed his own name in Kharoshthi script at the end of a Brahmi inscription he'd carved deep in the south, near Karnataka. Scribes in Ashoka's employ, in other words, traveled vast distances to practice their still-developing craft — the same Chapada material the vault's existing script-pluralism page already documents as evidence of multi-script competence, but which reads differently once Brahmi itself is understood as possibly brand-new: a scribe from the region that already had a mature script (Kharoshthi) helping carry a genuinely new one (Brahmi) to the far end of the empire.2
Multi-script systems show up across imperial communication in different historical contexts. The Ashokan pattern teaches a general protocol for reading them.
The protocol:
Map the script-region pairings. Which script appears where? The pairing usually tracks the regional administrative-linguistic norm rather than the imperial-center norm. Read against this baseline.
Identify the imperial-center default. What is the empire's most-common script-language pair? For Ashoka, Brahmi-Prakrit. The default tells you the center of administrative gravity.
Read the deviations from default. Where the empire deviates from its default, it's responding to local administrative reality. Ashoka used Kharoshthi in the northwest because the northwest's bureaucracy was Kharoshthi-trained. Greek-Aramaic at Kandahar because Hellenistic-Persian-Aramaic was the Kandahari administrative inheritance.
Look for conceptual translation, not just orthographic translation. Multi-script inscriptions in cross-cultural regions often involve concept-translation rather than word-translation. The Kandahar eusebeia/qshyt/dhamma trinity is a worked case. The script choice carries the conceptual frame; the audience reads the concept through the frame of their cultural-linguistic competence.
Watch for self-conscious script-display. Named scribes like Capada signing in a different script than their inscription, or engravers like the Erragudi boustrophedon-attempter, reveal an administrative class that had developed multi-script competence and occasionally signaled it. The signaling is documentary evidence of the multi-script literacy stratum's existence.
The transferable principle: imperial multi-script systems are administrative-accommodation systems. They meet local bureaucracies in local literacy norms rather than imposing imperial-center norms uniformly. Reading them this way reveals the empire's accommodation logic — where it bent to local administrative reality, and where it expected local administrators to bend to imperial-center norms.
Hultzsch (1925) catalogues all inscriptions by script. The Brahmi-Kharoshthi-Greek-Aramaic distribution is well-established.1
The Capada signature at Brahmagiri/Siddapura/Jatinga-Rameshwara is at Lines R of Brahmagiri, Line 22 of Siddapura, and inferred (partial survival) at Jatinga-Rameshwara. Lahiri cites Norman (2012) and Hultzsch (1925: 178-179) directly.1
The Erragudi boustrophedonic engraving is documented in standard epigraphic surveys; Lahiri's reading is interpretive but the boustrophedon itself is observable.1
The Kandahar Greek inscription's quality is praised by Paul Bernard (cited in Lahiri); the Aramaic version is documented in standard inscriptional sources. The conceptual-translation pattern (eusebeia/qshyt/dhamma) is interpretive synthesis.
The "administrative accommodation" reading of script choice assumes the empire deliberately matched local norms. Alternative readings are available — script choice could have been determined by the available engravers' competence rather than by a deliberate matching strategy. The two readings produce similar surface patterns but different underlying mechanisms.
The Kandahar conceptual-translation reading depends on the Greek being deliberate philosophical translation rather than approximate rendering. The quality of the Greek (per Bernard) supports the deliberate reading, but the Aramaic's relationship to the Greek is murkier — it's not a strict translation of the Greek; the two texts cover overlapping but not identical content. Whether this represents two independent translations from a Prakrit original, or whether one text was translated from the other, cannot be definitively determined.
Lahiri and K.R. Norman work the same script-linguistic material with different analytical orientations. Norman's foundational work analyzes the Ashokan inscriptions for linguistic-historical features — the dialectal variations across regions, the script evolution, the engraver patterns. Lahiri uses Norman's linguistic analysis as background and focuses on the political-administrative implications.
Both converge on the empirical reality of multi-script systematic deployment. Both agree that the script-pluralism was deliberate, geographically distributed by administrative-linguistic norms, and operationally complex.
The split is in interpretive emphasis. Norman treats the script-pluralism principally as evidence about Indian linguistic-historical development — what the dialects tell us about Prakrit evolution; what the Kharoshthi-Brahmi divide tells us about regional script history. Lahiri treats it principally as evidence about imperial administrative strategy — what the script-choices tell us about how the Mauryan center approached its periphery.
Both readings are valuable. Ancient multi-script inscriptional systems can be read as linguistic-historical sources, as administrative-strategic sources, and as cultural-anthropological sources. Each reading produces different findings; all are valid. The Ashokan corpus is rich enough to sustain multiple analytical approaches simultaneously.
Multi-script imperial communication systems appear across the ancient world. The Mauryan case sits in dialogue with Achaemenid Persian, Hellenistic Greek, and later Roman imperial communications.
Behavioral Mechanics: Manipulation and Influence Hub — Imperial communication systems that meet local audiences in local conventions get higher uptake than systems that impose central conventions uniformly. The Mauryan multi-script approach is a documented case of audience-accommodation as influence strategy. Modern multilingual political campaigns operate on the same principle — address audiences in their own languages, with concept-framings their cultural vocabularies already support. The Ashokan case is the earliest documented Indian instance of the strategy at imperial scale.
Eastern Spirituality: Buddhist Philosophy Complete Map — Buddhist missionary tradition routinely translated doctrine into local cultural-linguistic vocabularies (Chinese Mahayana, Tibetan tantra, Japanese Zen are downstream instances). The Mauryan Kandahar bilingual is structurally analogous — the same dhamma concept rendered in local conceptual vocabularies (Greek philosophical, Aramaic Persian-cultural). Religious-philosophical translation across cultural boundaries is a continuous tradition, and the Mauryan imperial communications anticipate the missionary translation patterns later Buddhism would develop systematically.
The Sharpest Implication
The script-pluralism reveals that imperial unity doesn't require linguistic uniformity. Ashoka's empire was operationally unified through identical-message-multi-copy distribution while being linguistically plural across its regions. Modern political assumptions often treat linguistic uniformity as a precondition for imperial cohesion. The Mauryan case is documented counter-evidence — large-scale imperial communication can operate across script and language diversity if the administrative apparatus has multi-script competence and the imperial communication strategy commits to audience-accommodation rather than center-imposition. The implication for modern multilingual political communications: the Mauryan model is the older option, and it worked.
Generative Questions