He has carried whole ranges to the causeway. Then he goes north for one more peak and, ⭐ *"astonishingly, with the whole of his strength applied, it did not shift at all."*1
The mountain is Govardhan.
⚑ What follows is the only episode in this build where the obstacle is not defeated, out-thought or endured — it is asked. ⭐ And the promise he makes while asking goes on to reorganise a future incarnation.
⚠ The volume also tells this story a second time, in a different section, with a different cause, a different mover and a different obligation.2 Neither telling knows the other exists, and both are printed. This page holds both.
The diagnosis takes one thought and it is not about weight.
⭐ *"This is the Lord's own form, and every rock of it is equivalent to a śālagrāma."*1
⚑ So the immovability is not resistance. It is category. ⭐ He has been handling terrain; this is not terrain.
And the change in his behaviour is immediate and total. ⚠ He salutes it, and then he asks — "most holy king of mountains, I want to bring you to the Lord's feet — why will you not come? There you will not merely get the rare sight of his auspicious form; the Lord will set his own feet on you as he crosses the ocean into Laṅkā."1
⭐⭐ The request is an offer, and the offer is precisely calibrated to what the mountain is. Not come, you are needed — but come, and be stood on by the person you are made of.
Govardhan then "lifted like a flower on Hanumān's left hand."1
⭐ The build notes the hand. ⚑ He is carrying a form of the Lord in his left, and the volume's own etiquette material would have something to say about that if anyone had noticed. Nobody does.
The complication arrives from his own side, and it is administrative.
On day five the last twenty-three yojanas close, and the order goes out that everyone should drop whatever they are carrying where they stand.1 ⭐ The bridge is finished; the material is surplus.
⚑ "Those dropped mountains, the Carit notes, are the ones standing in south India today, the region's own having already gone into the bridge."1
⚠ Hanumān had reached Braj carrying Govardhan when the order reached him.
⭐⭐ He sets it down — "but he had given his word, and he saw Govardhan looking at him with disappointment and hope at once."1
And his response is not to apologise and not to appeal. ⭐ He tells the mountain not to worry, "since his own Lord would certainly protect his servant's promise" — and flies to Rāma to ask.1
⚑ Note the order of confidence: he states the guarantee to the mountain before obtaining it. ⚠ Which is either serene trust or an agent committing his principal twice over, and the Carit does not distinguish them.
Rāma's answer is one line and it is the doctrine the whole episode exists to state.
⭐⭐⭐ *"Your assurance and your word are my own assurance and my own word."*1
⚑⚑ That is a delegation of the principal's own credit to the agent, stated without limit, after the fact, on a commitment the principal never authorised and had in fact countermanded.
⭐ Work through what it costs him, because the Carit had already made it explicit. Before the settlement, Rāma states the difficulty himself: "Govardhan is the unrivalled devotee of my Kṛṣṇa form in Goloka; if he asks here to be shown that form, then out of regard for his true well-wisher Hanumān I will have to break my own avatār's proper bounds. What is to be done?"1
⚠ So the conflict is named in advance and it is a real one. ⭐ An avatāra has bounds — a form it may show, a register it may work in — and honouring the servant's promise would breach them.
⭐⭐ The resolution does not choose between the two. ⚑ It moves the payment into a later incarnation, where the bounds are different: *"the form dear to him is the peacock-crowned, flute-bearing one. So tell him that when I descend in Dvāpara on the land of Braj in that very form, he will not only see me; I will play upon him with the cowherd boys, using his fruit, flowers, and grasses, and I will hold him up on one finger for seven days together."*1
⭐⭐⭐ And the Carit states the causal claim outright: *"that place was granted by the flute-bearing Rāma of Dvāpara specifically to protect his devotee Hanumān's own word."*1
⚑ On this telling, the most famous act of the Kṛṣṇa avatāra — the lifting of Govardhan — happens because a servant made a promise he could not keep.
The volume's Braj temples survey gives the same episode and disagrees on every structural point.2
In the temples version:
The cause is not immovability. ⭐ Rāma simply orders every unused peak set down wherever it stands, and this one lands in Braj. There is no failure to lift it, no śālagrāma reading, no request.
The grievance is Girirāj's, not Hanumān's. ⚑ *"Girirāj protested that he had now lost his closeness to Śiva without gaining Rāma's presence either."*
And the promise is Hanumān's answer to a complaint rather than a commitment he made in advance: "if not in Rāma's form, then in Kṛṣṇa's, the Lord himself would one day lift this very mountain in his hands."2
⭐⭐ Then a detail the Carit does not have at all: Girirāj asks one more thing — that Hanumān himself stay close by when that day comes — and Hanumān agrees, promising to witness Kṛṣṇa's play in the mountain's own caves.2
⚠ And the temples essay supplies a different reason for the whole settlement: it reads the episode as Rāma discharging a debt he had left open, citing his own Mānas admission that nobody has ever done him a favour he could really repay.2
⚑⚑ Different cause, different mover, different obligation. 🔴 Carit: the mountain could not be moved, Hanumān promised, Rāma honoured a servant's word. 🔴 Temples: the mountain was set down by order, Girirāj complained, Hanumān consoled him, and Rāma was settling his own debt.
The disagreement is not decorative, and naming what it turns on is the useful part.
⭐ They disagree about who owes what.
On the Carit's account, the obligation runs from Rāma to Hanumān. ⚑ The servant's word binds the master, and the doctrine is stated as a general principle — your word is my word. Govardhan is the beneficiary of somebody else's relationship.
On the temples account, the obligation runs from Rāma to Govardhan, ⭐ and Hanumān is a messenger who happened to be standing there. ⚑ The Mānas debt-line makes the creditor the mountain, not the servant.
⚠ These cannot both be the reason Kṛṣṇa lifts Govardhan, and the volume asserts both causally.
⭐⭐ What is common to both is the mechanism, and it survives the disagreement: an obligation incurred in one incarnation is discharged in a later one, in a form where discharging it is permissible. ⚑ That is a genuinely unusual piece of machinery — a deferral across avatāras, used to reconcile a commitment with a constraint — and both contributors reach for it independently.
⚠ The build states the convergence at its actual strength. [n=2] Two tellings in one volume converge on the deferral device and diverge on everything else.
Three problems, and the first is the one a reader should carry away.
The delegation is stated without any limit whatever. ⚠ Your assurance and your word are my own. ⭐ No scope, no ceiling, no condition, no revocation — and it is granted retroactively on a promise made in defiance of a standing order. ⚑ A doctrine of unlimited agent authority is exactly what the volume's envoy material spends four essays trying to bound, and none of them cites this.3
And the promise was made to a party who could not have been harmed by refusal. ⭐ Govardhan is a mountain that is also a form of the Lord. ⚠ The stakes are entirely reputational — he saw Govardhan looking at him with disappointment and hope at once — which makes this the weakest possible case on which to establish an unlimited principle, and the strongest possible case for stating it warmly.
The Carit's causal claim about Braj is unfalsifiable and enormous. ⭐ That place was granted… specifically to protect his devotee Hanumān's own word. ⚑ A whole devotional geography re-attributed to one servant's promise, asserted with no source, in a Hanumān-devoted volume. ⚠ The build records the claim as the volume's and marks the motivated-reasoning risk plainly.
When something will not move, check whether you have misclassified it before applying more force. ⭐ The diagnosis here takes one thought and changes the whole approach: this is not a heavy object, it is a different kind of object. ⚑ The tell is that maximal effort produced no movement rather than insufficient movement — resistance and category-error look different, and the second one does not respond to effort at all.
Then make the request in the currency of what the thing actually is. ⚠ He does not say you are needed for the bridge. ⭐ He offers the one thing a form of the Lord would want — the Lord's own feet. A request calibrated to your purpose gets refused; a request calibrated to theirs is not really a request.
Do not guarantee your principal's performance before obtaining it. ⚑ He tells the mountain the Lord will protect his servant's promise, and only then goes to ask. ⚠ It works here because the principal is God. ⭐ In every other setting this is the move that destroys agents — and the Carit gives no warrant for it beyond the outcome.
And when a commitment collides with a constraint, look for the deferral before looking for a winner. ⭐ Both versions of this story resolve the same way: not by breaking the promise and not by breaking the bounds, but by moving the payment to a context where both hold. ⚑ That is the transferable device on this page — when something is delivered is a variable most people treat as fixed.
The Carit's bridge chapter for the immovability, the countermand and the settlement,1 the Braj temples essay for the incompatible version,2 and three of this build's pages for the envoy-mandate material and the foreman's account of the same five days.345
Bounded. ⚠ Neither telling cites a text. ⭐ The Carit is a 1975 serialised devotional biography; the temples piece is a regional survey by a different contributor. Neither is a Vālmīki narrative, and the build claims nothing about the episode's antiquity. [PLAUSIBLE — needs corroboration] [RENDERING — verify against Hindi] 🚩 MOTIVATED REASONING — a Hanumān-devoted volume attributing the Govardhan-lifting to a Hanumān promise is exactly the claim such a volume would produce, and the build marks it rather than discounting it.
🔴 The contradiction is preserved and is the page's core. Cause (immovable versus set down by order), mover (Hanumān's promise versus Girirāj's complaint), and obligation (Rāma to Hanumān versus Rāma to Govardhan) all differ. ⚑ The temples version also carries a second promise the Carit lacks entirely — that Hanumān would stay nearby for the Kṛṣṇa-līlā. Neither author cites the other. Both are printed in one volume.
⚠ A tension the Carit creates against the volume's own envoy doctrine. ⭐ Your assurance and your word are my own is an unlimited grant of principal authority to an agent. ⚑ Four contributors elsewhere in the volume set out envoy standards concerned precisely with how far an agent may commit his master, and none of them cites this line.3
Open question, and it is checkable. ⭐ Does any Kṛṣṇa-tradition source attribute the Govardhan-lifting to a promise made by Hanumān? ⚑ If the attribution appears only in Hanumān-centred material, the build has caught a devotional volume writing its subject into another tradition's central episode — which is a different and more interesting finding than a variant.
Two contributors, one volume, one episode, and their disagreement is diagnostic of how this material is assembled.
Dubey is writing a continuous biography, and needs the promise to matter — ⭐ so the mountain is immovable, the promise is his hero's, and the payoff is a doctrine about a servant's word.
Rāmdās Śāstrī is writing a temple survey, and needs to explain why this place is honoured — ⭐ so the mountain is set down by routine order, the grievance is local, and the payoff is a claim about Girirāj's standing.
⚑ Each version is shaped by what its author's genre has to deliver, and neither is checking the other. ⚠ This is the same mechanism the build has recorded three times now: the volume's narrative section and its thematic sections develop the same material independently, and the divergences are never reconciled because nobody reads across.
⭐⭐ What survives the disagreement is worth more than either version: the deferral device, reached independently by two contributors with different aims. [n=2] ⚑ An obligation that cannot be honoured under current constraints is not cancelled and not forced — it is rescheduled into a context where it becomes permissible. Both authors treat that as obvious, which is the best evidence that it is the tradition's own move rather than either one's invention.
Reciprocity. That page records the obligation Rāvaṇa's ten severed heads created and the eleventh form it did not reach. This episode is reciprocity running on a debt that cannot be discharged in kind, and the machinery it produces is the finding. ⭐ The temples version states the problem exactly — Rāma's own admission that nobody has done him a favour he could really repay. ⚑ An unrepayable debt is normally treated as a bond that simply persists; here it is discharged by changing the terms of the transaction — different incarnation, different form, different currency. **What the pairing produces is a third option beside repay-and-clear or remain-obligated: defer into a context where the repayment becomes possible. ⚠ And it names the precondition, which reciprocity theory usually leaves implicit. ⭐ Deferral only works where the parties expect to meet again under different rules — which is trivially true for avatāras and rare everywhere else, and explains why most unrepayable obligations in ordinary life simply calcify.
The Envoy Sent Without Instructions. That page holds the corpus's doctrine of improvisation within a mandate — how far an agent may act on judgement toward an unstated goal. This episode supplies the extreme case the doctrine has no room for: an agent committing his principal against a standing order, and being ratified. ⭐ The order was explicit — set down whatever you are carrying — and he had already given his word. ⚑ What the pairing yields is that the corpus's mandate question is framed one step too early. It asks how far an agent may go before acting; this asks what happens when he has already gone too far and the commitment is live. ⚠ And the volume's answer — your word is my word, unlimited and retroactive — is unusable as doctrine, because it makes ratification automatic and therefore makes the mandate meaningless. ⭐ The usable form is narrower and the episode contains it: the promise was made to a party the principal already valued, in the principal's own interest, and the agent went and asked immediately. Three conditions, none of them stated, all three present.
Sharpest implication. ⭐ A servant's unauthorised promise, made in defiance of an explicit order, is honoured by rescheduling a future incarnation — and the volume states this as doctrine rather than as an exception. ⚑ For a project extending what bhakti can be made to do, the interesting object is not the devotional warmth of your word is my word but the machinery underneath it: a system in which commitments outrank instructions, and in which the constraint that blocks a commitment is answered by moving the delivery rather than by cancelling it. ⚠ Neither the volume's envoy doctrine nor the modern corpus's mandate material can accommodate that, and both would be sharper for having to.
Generative questions.
What are the three conditions that make retroactive ratification safe? ⭐ The episode contains them and states none: the beneficiary was already valued by the principal, the commitment served the principal's interest, and the agent disclosed immediately. ⚑ Stated as a rule, that is a usable doctrine of agent authority — and it is exactly what four essays of envoy standards failed to produce.
Which version does the Kṛṣṇa tradition itself tell? ⚠ Both accounts here are from a Hanumān-devoted volume, and both make a Hanumān promise the cause of Govardhan's honour. ⭐ If Kṛṣṇa sources give the episode without any Hanumān involvement, the build has a clean instance of a devotional tradition inserting its subject into another's central story — and that would be worth far more to the book than the variant itself.