Bindusara had many sons. Susima was the eldest and the heir-apparent. Ashoka was one of the others — and across every legend tradition that survived, Bindusara is shown disliking him. The Ashokavadana names the reason: Ashoka's skin was "rough and unpleasant to the touch." The texture itself bothered the father.1
Pingalavatsajiva, an Ajivika ascetic visiting the court, was asked by Bindusara to examine the sons and determine which would best succeed him. Ashoka was initially unwilling to be examined. He knew his father disliked him; he expected the examination to confirm what everyone already understood. His mother persuaded him to participate. He came along with the other princes and let the ascetic look at him.
The Ajivika saw it immediately. This was the son who would rule. But Pingalavatsajiva also saw something else — Bindusara would not accept the answer if it came as Ashoka's name. So he gave the answer in code. "The one who has the best mount, seat, drink, vessel and food will become the emperor." The criteria were generic-sounding enough that Bindusara couldn't identify Ashoka in them. The princes left.
Ashoka, walking away, translated the code for his mother. "The back of an elephant was my mount, the earth was my seat, my vessel was made of clay, boiled rice with curds was my food, and water was my drink; therefore, I know I shall be king." He had ridden an elephant. He had sat on the earth instead of on cushions. He had eaten simple food, drunk water, used a clay vessel. The Ajivika had seen what the others hadn't — Ashoka's princely conduct was unpretentious in a way his rivals' wasn't. The simplicity was the sign.1
The Ajivika then left the kingdom. Pingalavatsajiva knew that if Bindusara asked him directly, he'd have to say Ashoka's name, and that the dying king would refuse the verdict and punish the ascetic for delivering it. So the ascetic disappeared. He returned to Magadha only after Bindusara was dead. The prophecy held; the prophet hid until the prophet's reading became safe to confirm.1
Some years after the examination, Taxila — the major city on the empire's north-western frontier, two thousand kilometers from Pataliputra in modern Pakistan — broke into rebellion against Bindusara's local administrators. The Ashokavadana records what happened next: Bindusara sent Ashoka to put down the rebellion.
But he sent him without weapons.
The text frames the supply shortage as setup for a miracle. Ashoka's servants tell him on his departure: "Prince, we don't have any weapons of war; how and with what shall we do battle?" Ashoka declares: "If my merit is such that I am to become king, may weapons of war appear before me!" The earth opens and deities bring forth weapons. The army is supplied.1
Lahiri reads this differently. Three possible interpretations of the no-weapons detail:
First, hagiographic exaggeration of an inadequate supply. The expedition was probably under-supplied; the text inflated under-supply into total absence to set up the miracle.
Second, Bindusara engineering Ashoka's failure. The father who disliked the son could send him on a frontier mission with insufficient resources, hoping the mission would fail and conveniently remove the son from succession contention. This reads against the Arthashastra's frontier-rotation solution for disaffected princes — except inverted. The frontier-rotation solution worked when the prince was sent to be far from the king; the no-weapons version worked when the prince was sent to be far from victory.
Third, prefiguration of Ashoka as the "iron-wheeled monarch" (ayashcakravartin) — the later texts' framing of Ashoka as a king who ruled by threat-of-sword rather than by actual sword. The legend of Taxila pacification without weapons becomes the foundation-story for the later moral kingship: even in rebellion, Ashoka subdues without bloodshed.
The reality the text frames around: Ashoka reached Taxila and the citizens did not resist. The Ashokavadana has them welcoming him on the roads, saying "We did not want to rebel against the prince... nor even against King Bindusara; but evil ministers came and oppressed us."1 The rebellion turns out to have been against local administrators, not against the dynasty. Ashoka — without using force — accepts the surrender and re-establishes Mauryan governance. The mission Bindusara may have hoped would fail succeeds. The disliked son returns credentialed.
The Ashokavadana is hagiographic, but Lahiri identifies one piece of archaeological corroboration. At Taxila, on an octagonal pillar of white marble, an Aramaic inscription mentions "our lord Priyardarshi." Priyadarshi is Ashoka's title across the empire (Devanampiya Priyadarshi, Beloved of the Gods, Who Looks Amiably). The inscription's content speaks of non-injury to creatures and obedience to the aged — themes that match Ashoka's later edicts.1
The inscription doesn't prove the legend's specific story. It establishes that Ashoka had a real, documented presence at Taxila, with a real-titled Aramaic inscription consistent with the rest of his epigraphic program. The Ashokavadana's claim that Ashoka was at Taxila isn't pure invention. The mission happened; the form it took in the legend tradition is what's open to question.
The other Ashokan presence at Taxila — the great Dharmarajika stupa, built outside the Bhir mound city — is documented as later, post-conversion. But its location at Taxila isn't accidental either. If Ashoka had visited Taxila as a prince before his conversion, the city would have remained meaningful to him as he chose where to invest his post-conversion patronage.
After Taxila, Bindusara sent Ashoka to Avanti — the central Indian region around modern Madhya Pradesh — as viceroy. The administrative center was Ujjayini, which Hindu astronomers later treated as the prime meridian for Indian time-reckoning. Ashoka spent roughly ten years there (~282-272 BCE).1
The Avanti posting reads differently from the Taxila dispatch. Ten years is too long to be a remove-the-son-from-succession mission. It looks like a genuine viceroyalty — the empire-managing apprenticeship that the Arthashastra prescribes for trusted princes. Either Bindusara revised his opinion of his disliked son after the Taxila success, or the regional administration of a wealthy commercial province (Avanti was strategically important for political and trade reasons) was understood as a way to keep the disliked-but-competent son productively away from Pataliputra.
In Ujjayini, Ashoka met Devi — the daughter of a Vidisha merchant — and they had two children, Mahinda and Sanghamitra. Both children would later become Buddhist religious figures (Mahinda the missionary who brought Buddhism to Sri Lanka; Sanghamitra the nun who brought the Bodhi-tree sapling). The Avanti posting wasn't just political; it produced the family connections that would later carry Ashoka's Buddhism across the subcontinent and beyond.
The Bindusara-Ashoka-Taxila dynamic illustrates a general pattern: any royal dispatch to a difficult frontier is doing political work that may not be visible in the surface narrative. The protocol for reading dispatches:
Map the formal mission. What is the dispatched figure supposed to accomplish? Quell rebellion, govern province, complete a delicate negotiation, lead an army. The surface-level mission is the legible task.
Identify the resource configuration. Are they being sent with the resources the mission requires? Or are they being under-supplied in ways that make the mission harder than it looks? The Taxila no-weapons detail is the textbook indicator — a mission whose supply chain doesn't match the mission's stated difficulty is doing more than the stated mission.
Read the dispatcher's prior relationship with the dispatched. Bindusara disliked Ashoka. Dispatcher-bias against dispatched is a signal that the mission may include hidden purposes. Modern equivalents: an executive sent to head a struggling subsidiary by a CEO who has been publicly skeptical of them.
Watch what happens on the ground. The Taxila citizens welcomed Ashoka. The rebellion turned out to be against local administrators, not against Bindusara. The on-ground reality made the under-supplied mission tractable in ways neither Bindusara nor the dispatched prince could have predicted. Outcomes often diverge from intent in ways that reveal the underlying situation.
Read the post-mission trajectory. Did the dispatched figure return with new credibility? Did they fade into administrative obscurity? Were they given a follow-up mission, or sidelined? Ashoka's post-Taxila Avanti viceroyalty suggests his Taxila success forced Bindusara to revise — slightly — the prior dislike, or at least to use his disliked son's competence productively.
The transferable principle: royal dispatches in courts with active succession dynamics are rarely just mission-assignments. They're strategic moves in ongoing succession negotiations. Reading them as just-the-mission misses what the dispatcher is actually doing.
The Ashokavadana's Taxila-no-weapons sequence is Strong (1989): 218-225. The Pingalavatsajiva examination with the "best mount, seat, drink, vessel, food" cipher is Ashokavadana, also covered in Strong.1
The Aramaic Priyadarshi inscription at Taxila is documented in standard epigraphic publications; Lahiri references it via Hultzsch (1925) and via later Taxila archaeological reports.1
The Avanti viceroyalty is referenced in multiple legend traditions (Mahavamsa, Dipavamsa) and indirectly in Ashoka's own later edicts (which mention his son's viceroyalty at Ujjayini following his own pattern).1
The Ashokavadana's specific story of the Taxila pacification is hagiography. Whether Ashoka actually went to Taxila as a prince, or whether the Aramaic Priyadarshi inscription dates to his post-coronation period only, cannot be definitively settled. Lahiri's reading treats the pre-coronation Taxila trip as plausible but acknowledges the textual evidence is weak.
The Bindusara-engineered-failure interpretation of the no-weapons dispatch is interpretive. The Mauryan dynastic record doesn't directly support it; it depends on the dislike-of-son detail (which is unanimous across legend traditions) combined with the no-weapons detail (which is Ashokavadana-specific). The combination produces a coherent reading but cannot be proven.
The "iron-wheeled monarch" framing — that Ashoka would rule by threat-of-sword rather than by sword — is a back-reading from later Buddhist political theology. It would not have been operative for Bindusara or for the young Ashoka. The Ashokavadana imposes the framing retroactively.
Lahiri and John Strong (who produced the principal scholarly translation and commentary on the Ashokavadana) converge on treating the Taxila narrative as hagiographic but residue-bearing. Strong's reading is more focused on the religious-narrative function — the Taxila story sets up Ashoka's later "iron-wheeled monarch" framing. Lahiri's reading is more focused on the political-biographical residue — what the story tells us about the Bindusara-Ashoka relationship beyond the legend's surface.
Where they split: what each emphasizes. Strong reads the dirt-offering, the Buddha's prophecy, the no-weapons miracle, the cave-donation pattern as components of a coherent Buddhist political theology built around Ashoka's figure. The components are doing theological work and the historical-residue question is secondary. Lahiri reads the same components asymmetrically — some pass the historical-residue filter (the dislike-of-son, the Champa origin, the Ajivika court connection, the Aramaic inscription corroboration) and some don't (the dirt-offering Buddha-prophecy is pure theology).
Both readings are necessary. Strong's theological reading explains why the Ashokavadana exists in the form it does — what the second-century-CE Buddhist tradition needed Ashoka to mean. Lahiri's residue reading explains what the Ashokavadana inadvertently preserves about the historical Ashoka. Together they produce a fuller account of the relationship between the historical figure and the religious-narrative apparatus built around him.
Where they share method — read skeptically first, look for residue second, never accept the narrative surface as evidence — is the more important point. Both treat the Ashokavadana as a text that requires staged reading, not direct acceptance. Where they differ is in what they read it for. Reading them together reveals that the same hagiographic text serves at least two distinct historical purposes: it tells us about post-Mauryan Buddhist political theology AND it tells us (in its awkward residue) about the historical Ashoka. The text was not written to do either, but it can be made to yield both.
A prince sent on a difficult mission by a father who dislikes him is a story-structure that appears across mythology, history, and modern organizational politics. The Mauryan case has documented archaeological corroboration that's rare in the broader pattern, but the structure itself is general.
Behavioral Mechanics: Power, Authority & Social Hub — The under-supplied difficult mission is a classical organizational sidelining technique. Send the rival to head the failing subsidiary; give them just enough resources that the failure can be attributed to their incompetence; recall them after the failure to formally sideline them. The technique works when the rival is incompetent enough to fail without sufficient resources. It fails when the rival is competent enough to succeed despite under-supply — at which point the dispatcher has accidentally credentialed the rival they were trying to remove. Bindusara's Taxila dispatch produced exactly this inversion. Any organization with active succession dynamics produces the same pattern. The under-supplied difficult mission is the most-recognizable elite-management technique because it's also the most likely to backfire. Modern corporate parallels: the head-of-international-expansion role used as exit-track for executives the CEO can't openly fire. Sometimes the executive succeeds wildly and returns more powerful. The mechanism is structural.
Psychology: Identity Architecture and Defense Hub — A son who knows his father wants him to fail develops specific psychological architecture. He cannot trust that resources will be provided; he cannot trust that success will be acknowledged; he cannot trust that the dispatcher's stated mission is the actual one. The Ashoka who survived the Taxila dispatch — assuming the legend preserves something of his actual experience — would have come back to Pataliputra with a particular cognitive equipment: read the father's actual intent, not the stated mission; trust local subjects (who welcomed him) more than the home-court ministers; build alternative power bases (the Ujjayini Avanti posting; the Vidisha-Devi family connections) outside the dispatcher's direct control. The psychological architecture of the disfavored son who survives elite-management techniques is recognizably specific. They develop a particular kind of strategic competence — high distrust of stated intentions, high investment in alternative power bases, high facility with reading dispatcher psychology. The pattern shows up in modern corporate survivors of organizational sidelining who eventually return to take over.
Eastern Spirituality: Buddhist Philosophy Complete Map — The Ashokavadana's narrative arc — disfavored son sent to difficult frontier; subjects welcome him; he succeeds without violence; he returns transformed by the experience — is structurally a Buddhist conversion-pre-figuration. The Taxila mission isn't yet the Buddhist conversion (Ashoka isn't yet a Buddhist), but the narrative shape is the same: a person sent into a situation that should produce force-and-violence finds another path. The later Kalinga moment will repeat the pattern with conversion-explicit framing. Buddhist hagiographic narratives often establish the conversion-shape pre-narratively, in episodes that anticipate the later transformation. The Taxila no-weapons miracle teaches the reader to expect, later, the Kalinga regret. Buddhist political theology builds the narrative through anticipatory rehearsal. The structural integrity of the conversion-arc depends on the prior episodes prefiguring it.
The Sharpest Implication
The disliked son who survives elite-management techniques accumulates a specific kind of credibility — not the credibility of beloved-heir-apparent, which depends on dispatcher endorsement, but the credibility of having succeeded despite the dispatcher's intent. This is a different kind of legitimacy. It's tied to demonstrated capability rather than inherited position. The implication: in courts with active succession dynamics, the most-likely-to-actually-succeed contender is often the disfavored prince who survives the apparatus designed to remove them. The favored heir-apparent has had everything handed to them; the disfavored survivor has had to develop the competencies the favored heir didn't need. When the moment of succession arrives, capability matters more than endorsement. Ashoka's accession against Susima's heir-apparent status is the textbook case. The dispatched-to-frontier prince came back with administrative competence and provincial networks. The endorsed heir-apparent had courtly favor and senior officials who had insulted him.
Generative Questions