Indrajit looses the Brahmāstra. Hanuman, who both contributors agree could have resisted, does not.
Everybody in the volume accepts that the submission was voluntary. That is not the disagreement. The disagreement is about why, and two contributors a hundred pages apart give answers that cannot both be right.
Jaidayāl Goyandkā: he allows himself to be bound because he calculates that capture will produce an audience with Rāvaṇa.1
Jagdīś Śukla: he goes still "out of respect for the weapon itself rather than being genuinely overpowered by it — a courtesy, not a defeat."2
🔴 One is instrumental and one is deferential. The first makes the submission a purchase; the second makes it an observance. They are not two aspects of one act — they imply different things about what Hanuman wanted, when he decided it, and whether the audience with Rāvaṇa was an objective or a consequence.
Neither contributor mentions the other. Both readings are preserved here and neither is adopted as the volume's position, because the volume has no position.
The instrumental version is the more elaborate, and it comes with a mechanism.
Hanuman lets the astra take him. Then the rākṣasas, not trusting it, bind him further with ordinary rope — and this, the essay says, voids the Brahmāstra's hold. And Hanuman, now free of the weapon in fact, keeps up the pretence of being genuinely restrained.1
⚑ The volume states the mechanism, not merely the choice. That is unusual. Most of this literature reports what happened and attributes it to a disposition; this reports a sequence with a technical dependency in it, and a deception maintained afterwards.
The strategic logic is complete without any appeal to character. Hanuman has found Sītā and cannot deliver Rāma's threat to Rāvaṇa — an envoy needs an audience, and no vanara gets one by asking. Capture is the only route into the throne room, and the astra is the only thing that could plausibly capture him.
So the submission buys access, at the price of appearing defeated, and the deception is maintained because the price has to keep looking real for the access to hold.
The deferential version is shorter and it is not merely a softer telling of the same thing.
Śukla's Hanuman submits because of what the weapon is. The Brahmāstra is Brahmā's, and a being who has received a boon from Brahmā — as the volume elsewhere records — does not treat that boon's expression as an ordinary missile to be shrugged off.2
On this reading the submission is an act of religious propriety, and the audience with Rāvaṇa is a consequence rather than a purpose.
⚑ This is not an unmotivated reading. It fits a strand running through the volume: a figure who claims envoy immunity while bound and facing execution, who is bound to constraints he could break, whose speed-epithets are each welded to a governor.3 A being who honours protocols he could ignore is exactly what several essays in this volume are describing.
It also gives the phrase its force. A courtesy, not a defeat is doing precise work: it denies the defeat without claiming a stratagem, which leaves the act as neither loss nor manoeuvre but observance.
The two readings look under-determined until one detail is brought forward, and then they do not.
The ordinary rope voids the Brahmāstra's hold, and Hanuman goes on pretending to be bound.1
⚑ A person honouring a weapon does not exploit a technical loophole in it.
That is the whole argument and it is decisive on the evidence available. Śukla's Hanuman submits out of respect for the weapon itself. Goyandkā's Hanuman accepts the weapon, waits for his captors to invalidate it through their own excess of caution, and then conceals the fact that it has been invalidated. The second is incompatible with the first at the level of motive: reverence does not have a loophole clause.
And the detail is asymmetric in a way that matters evidentially. Goyandkā's version carries a specific mechanical claim — one that could be checked against Vālmīki and could be wrong. Śukla's carries no comparable detail at all; it is an attribution of motive with nothing attached that the narrative would have had to supply.
⚑ This build has repeatedly found that the reading with a checkable detail is the one worth weighing, and here the principle sorts a genuine disagreement rather than merely grading two essays. The rope is evidence. The courtesy is an interpretation.
⚠ That does not settle it. Goyandkā's rope may itself be a later tradition's elaboration, and this build has not checked it against Vālmīki's Sundara Kāṇḍa. What can be said is which version has staked something.
The mechanics of the volume explain the collision without either contributor being at fault, and this build has now named the mechanism enough times to state it flatly.
The two essays are in different groups, roughly a hundred pages apart, written by contributors with different disciplines for different purposes. Goyandkā is narrating the Laṅkā mission episode by episode as a demonstration of virtues in sequence. Śukla is arguing that Hanuman's strength is borrowed and not owned, and reaches the Brahmāstra as one instance among several.
Neither is writing about the Brahmāstra. Both mention it on the way to something else.
⚑ And the Aṅka has no adjudication step. It is an anthology built to convene disagreement, and this build has treated that as its most usable feature — a compendium that prints incompatible positions can be argued with. The cost is that it also prints incompatible positions nobody knows are incompatible, because the collisions occur between essays rather than within them.
Which makes this the same structure as the volume's other unnoticed collisions — the Vibhīṣaṇa epistemics, the three reasons for the post-Laṅkā silence, the two conceded lapses against five denials of any lapse. Not disagreement, which is deliberate. Non-contact, which is a by-product.
The readings are worth holding apart because they produce different figures, and a book drawing on this material has to choose.
Goyandkā's Hanuman is an operator. He converts a defeat into an entry, absorbs the appearance of failure as a cost, exploits his enemies' caution, and sustains a deception under pressure. The submission is his most sophisticated single act, and it belongs beside the vernacular choice before Sītā, the Trikūṭa pause, and the argument delivered in the throne room.
Śukla's Hanuman is a figure of observance. He submits to what is owed, declines to press an advantage that would violate propriety, and receives the audience as something the situation gave rather than something he engineered. The submission belongs beside the envoy-immunity claim and the vow-bound restraint.
⚑ The difference is not tone. It is whether he is the kind of figure who plans.
And this build's material on the extension corpus makes the stakes concrete. A modern framework building a strategy practice on this figure needs the first reading — an archetype who cannot plan supplies no strategy — while the tradition's own devotional weight sits closer to the second. The corpus took the first without noticing there was a choice, and the volume supplies grounds for it that the corpus never cites.
On volume of corroboration the instrumental reading wins, and it is worth being explicit about how much.
Akhaṇḍānand's mission beyond the message — the reconnaissance itemised as destroying the military apparatus, exposing Brahmāstra knowledge, throwing the administration into fear and unsettling morale, with the strategic logic stated: if one scout did this, what will the full army do.4 ⚑ Note that the second item is the astra itself: on this reading, being hit by the Brahmāstra was intelligence-gathering.
The sermon in the enemy's court, an argument tailored to one listener while bound before his executioner.3
The deliberate submission, a capability declined to preserve an institution and to buy access.5
Four essays, four contributors, all describing a figure who trades appearances for position.
🔴 And one datum cuts the other way, from the same phase. Jayarāmdās "Dīn" Rāmāyaṇī has Hanuman uneasy at having burned Laṅkā without explicit prior order — which describes somebody who exceeded his brief and knows it, not somebody executing a plan.6 Preserved. The two are reconcilable only if the capture was planned and the fire was not, which is possible and which nobody in the volume says.
When two accounts of one act conflict, look for the version carrying a checkable detail and weigh it above the version carrying a motive. Motives are supplied by interpreters and cost nothing. A mechanical claim — the rope voids the hold — stakes something and can be wrong, which is why it is worth more even before anybody checks it.
Ask whether the proposed motive is compatible with everything else the actor does in the scene. Reverence and loophole-exploitation are not compatible, and the incompatibility is visible without any external evidence. A great deal of source criticism is just holding two sentences from the same passage next to each other.
And when a corpus offers you a strategist and a saint doing the same act, notice that you are choosing rather than discovering. Both readings are available in the material. The one you take will determine what the figure can be used for, and taking it silently — as the modern corpus did — means building on a choice you have not examined.
Two Aṅka essays for the two explanations,12 two further essays for the corroborating material,46 and two of this build's pages.35
Bounded, and this is the page's central limitation. The rope mechanism — that ordinary bonds void the Brahmāstra's hold — is recorded as Goyandkā gives it. This build has not checked it against Vālmīki's Sundara Kāṇḍa, and neither essay supplies a chapter or verse. If the detail is a later elaboration, the discriminator weakens considerably. [TRADITION-CLAIM — unverified]
Bounded again. "Neither contributor mentions the other" is a claim about these two essays as read, and the wider claim that no essay in the volume adjudicates between them is bounded to the twenty-one essays of the Character & Virtue group plus the Aṅka pages already built here.
🔴 The contradiction is the page and is not resolved. A calculated purchase of access against an observance owed to a weapon.
🔴 A second tension, preserved. Four essays support a premeditating figure; one has him uneasy at having acted without orders. Reconcilable if the capture was planned and the fire was not — which no contributor says.
Open question, and it is a single lookup. Does Vālmīki's Sundara Kāṇḍa record the ordinary bonds voiding the astra, and does it give Hanuman a stated intention at the moment of submission? One passage would either hand the instrumental reading a textual anchor or reveal it as commentary, and it is the highest-value check on this page.
Goyandkā and Śukla are doing different jobs, and the disagreement is a by-product of the jobs rather than of the men.
Goyandkā's essay reads each episode for the virtue it demonstrates — humility, restraint, cleverness, purity, statesmanship, constancy, in sequence. The Brahmāstra falls in his statesmanship slot, so it gets a statesman's explanation.
Śukla's essay argues that all strength is borrowed. For him the Brahmāstra is a moment where Hanuman's power meets a greater power's instrument, and the interesting fact is that he does not resist it — which fits the thesis whether the motive is reverence or calculation, and reverence fits it better.
⚑ Each reading is downstream of its essay's argument rather than of the episode. That is not a criticism; it is how thematic exposition works, and both men would probably concede it. What it means for a reader is that the volume's explanations of a given act are structurally as numerous as the arguments the act is recruited into — which is a reason to collect all of them before believing any, and the reason this build reads groups rather than essays.
The Sundarkāṇḍa Sprint. That page finds a modern work-cycle mapping four phases onto this mission — Scout, Infiltrate, Extract Intelligence, Report Back — and omitting both the burning and the audience with Rāvaṇa, because a sequence of activities cannot encode the moment an operator judges the brief has become wrong. The Brahmāstra submission is that moment, and the two contributors disagree about whether it happened at all. ⚑ What the pairing produces is a sharper version of the sprint page's finding: the missing phase is not merely absent from the template, it is contested in the source. Goyandkā's reading is a reassessment executed — brief exceeded deliberately, cost accepted, access purchased. Śukla's reading is that no reassessment occurred, and the outcome was propriety's by-product. A framework borrowing this mission for its structure is therefore borrowing a scene whose central strategic question the tradition never settled — which is a considerably better reason to add an explicit decision phase than the one the sprint page could give: you cannot inherit a judgement your source is not sure was made.
Indirect Agency and Deniable Power. That page treats deniability as an instrument — an effect arranged so it cannot be traced to its author. Goyandkā's Brahmāstra is the technique's inverse and completes the pattern. Hanuman does not conceal an act he performed; he conceals a capacity he retains, maintaining the appearance of restraint after the restraint has lapsed. ⚑ The pairing isolates a distinct move: hidden capability, as against hidden agency. Deniable power hides what you did; this hides what you can still do, and it buys something different — not escape from consequence but continued access, on terms the other party believes they are setting. It is also the more fragile of the two, since a single demonstration ends it permanently, which is why the volume has him hold the pretence all the way into the throne room and drop it only when the fire is lit and the mission is over.
The uncomfortable possibility is that the instrumental reading is a modern preference dressed as a finding, and that this page has just enacted it.
Goyandkā's version is more interesting to a contemporary reader. It supplies agency, calculation, a loophole, a deception sustained under pressure — everything a strategy-minded reader wants, and everything the extension corpus was looking for when it built a framework on this figure without consulting the volume.
Śukla's version offers a being who submits because submission was owed, which is less useful and may be closer to what the tradition means by him.
⚑ And the discriminator this page relied on may be doing less than it appears. The rope detail defeats reverence-toward-the-weapon only if reverence entails not exploiting a lapse — and a tradition in which propriety is owed to the astra rather than to the captors would see no inconsistency at all. Honour the weapon; deceive the rākṣasas. Those are different obligations to different parties, and the volume nowhere says they are the same.
On that reading both essays are right and this page's central argument dissolves, which is the strongest objection available to it and the volume supplies no way past.