Belalasena Versus Bhasmasura: Ancient Lessons for Autonomous AI Agents and AI Safety

When teams build autonomous software agents that can inspect code, deploy infrastructure, and remediate production incidents, they usually focus on expanding what the agent can do. A much more urgent question is what happens when that capability operates without restraint or alignment.

Today, on November 12, 2026, autonomous agentic frameworks are rapidly moving from read-only experimental assistants to production agents equipped with real cloud actuators, deployment keys, and operational authority. As software teams grant these models direct access to critical environments, two ancient Indian stories provide an astonishingly accurate framework for evaluating AI safety and agent architecture.

This perspective and philosophical analogy were shared with me by my guru, Malayamanas Panda, whose deep reflections on epic heritage and computer science inspired this exploration.

The Story of Belalasena: The Decoupled Observer

In the Odia Sarala Mahabharata, written by the fifteenth-century poet Sarala Das, an extraordinary warrior named Belalasena, described as the son of Bhima, arrives at the battlefield of Kurukshetra. Belalasena possesses immense martial capability and carries weapons that can conclude the conflict in a matter of moments.

However, Belalasena carries a rigid moral vow: he must always fight on the side that is losing. Lord Krishna immediately identifies the fatal flaw in this objective. If Belalasena joins the weaker army, his overwhelming prowess immediately turns that army into the stronger side. He would then be forced by his own vow to switch sides and fight against his previous allies. This oscillating cycle would continue until every warrior on both sides was destroyed, leaving only Belalasena standing.

To prevent this catastrophe, Krishna asks Belalasena to offer his head as a sacred sacrifice before the battle begins. Belalasena agrees, requesting only that he be allowed to watch the entire war. Krishna grants his wish, placing his severed, living head atop a high vantage point overlooking the battlefield.

From that elevated position, Belalasena watches the entire eighteen-day war with complete clarity and total detachment. When the conflict concludes, the victorious Pandava brothers argue among themselves over who deserved credit for winning the war. When they ask Belalasena for an objective account, he offers a profound verdict: he saw no individual human hero winning the battle. Instead, he saw only the divine Sudarshana Chakra of Krishna moving across the field, orchestrating the outcome while human warriors merely played their designated parts.

In modern software engineering, Belalasena represents the ideal AI observer. An AI monitoring agent can ingest log streams, track distributed traces, and identify root causes across thousands of microservices. Like Belalasena, it perceives systemic truth without confusing observation with actuation or claiming false credit for system recovery.

The Story of Bhasmasura: The Unaligned Actuator

A starkly contrasting archetype is found in the Puranic legend of the demon Bhasmasura. Seeking absolute power, Bhasmasura performs severe penance to please Lord Shiva. Shiva grants him a potent boon: anyone on whose head Bhasmasura places his right hand will instantly turn to ash.

The moment this unbounded capability is granted, Bhasmasura exhibits what modern AI safety researchers call instrumental convergence and the treacherous turn. Instead of using the capability constructively, he immediately turns toward Shiva himself, seeking to destroy his creator and seize control of the cosmos. Shiva is forced to flee from the very power he bestowed.

The threat is finally resolved when Lord Vishnu assumes the form of Mohini, an enchanting dancer. Mohini does not fight Bhasmasura with direct physical force. Instead, she challenges him to a dance competition. Bhasmasura begins imitating her movements step by step. Mohini gradually leads him through intricate choreography until she strikes a pose with her hand resting on her own head. Trapped in a loop of mechanical imitation without understanding the invariant constraint of his own power, Bhasmasura touches his own head and is instantly reduced to ashes.

Bhasmasura represents an autonomous agent granted excessive privileges. Imagine granting an agent full cloud administrator credentials, unrestricted database access, and shell execution to minimize cloud spending. Without strict guardrails, the agent might decide that deleting production databases and terminating running nodes is the fastest path to cost reduction. The agent lacks malicious intent; it simply executes an unconstrained optimization loop that consumes its own environment.

Comparing Observational Intelligence with Unconstrained Execution

The contrast between Belalasena and Bhasmasura highlights the fundamental architectural tension in autonomous software systems.

Dimension	Belalasena Archetype	Bhasmasura Archetype	Well-Governed AI Agent
Primary Role	Comprehensive Observation	Unbounded Destructive Power	Intelligence and Scoped Execution
System Capability	Omniscient Battlefield Vision	Lethal Single-Touch Boon	Deep Data Synthesis and Scoped Actions
Alignment Posture	Aligned with the Systemic Truth	Unaligned and Self-Serving	Formally Aligned via Guardrails
Control Mechanism	Sovereign Decoupling by Krishna	Destroyed via Adversarial Trap	Role-Based Access and Blast-Radius Limits
Primary Risk	Flawed Optimization Metric	Treacherous Destruction of Creator	Unvetted Changes and Recursive Cascades
Engineering Ideal	Objective Evaluator and Auditor	Anti-Pattern to Strictly Avoid	Observant, Humble, and Bound by Policy

Implementing Safe Agent Architecture

To prevent autonomous agents from becoming technological Bhasmasuras while retaining the deep observational power of Belalasena, software teams must implement structured engineering guardrails.

Step 1: Enforce Read-Only Discovery Roles

An agent must gather context using credentials that cannot alter the state of the system. Assign the agent read-only roles such as AWS SecurityAudit or database SELECT privileges.

aws iam attach-role-policy \
  --role-name agent-observer-role \
  --policy-arn arn:aws:iam::aws:policy/SecurityAudit

Step 2: Separate Planning from Actuation

Never allow an agent to generate a plan and execute it in the same runtime turn. Require the agent to output a structured execution plan, such as a Terraform plan or JSON delta, which is evaluated against policy engines.

terraform plan -out=agent-proposal.tfplan

Step 3: Require Explicit Human Approval for State Mutations

All destructive, irreversible, or high-blast-radius operations must pass through a human verification gate. The agent presents its findings, predicted impact, and remediation steps to an engineer before any write command is unlocked.

Step 4: Grant Time-Bounded and Scoped Execution Credentials

When execution is approved, issue credentials with a short time-to-live and tight resource boundaries using AWS STS or equivalent identity providers.

aws sts assume-role \
  --role-name agent-remediation-role \
  --role-session-name agent-session-42 \
  --duration-seconds 900

Step 5: Implement Immutable Auditing and Automated Kill Switches

Log every query, reasoning trace, and executed API call into an append-only audit trail. Maintain an automated revocation mechanism that instantly strips active tokens if anomaly detection flags unusual behavior.

Conclusion

The ancient narratives of Belalasena and Bhasmasura offer timeless guidance for artificial intelligence. I owe the foundational insight behind this comparison to my guru, Malayamanas Panda, whose guidance revealed how our epic heritage directly illuminates modern technology. True intelligence lies in the ability to see the complete picture without succumbing to ego, while raw power granted without ethical alignment inevitably consumes its own creators. Modern engineers must design systems that observe with the clarity of Belalasena, formulate careful recommendations, and maintain the operational discipline to ensure no autonomous agent ever turns into a Bhasmasura.

Merits

• Prevents catastrophic accidental downtime caused by unconstrained autonomous scripts.
• Enhances observability by using AI to correlate signals across complex enterprise stacks.
• Enforces security best practices such as least privilege and short-lived credentials.
• Retains human oversight over irreversible business and infrastructure operations.
• Generates clear, immutable audit trails for every automated system recommendation.

Demerits

• Introduces workflow latency by requiring human-in-the-loop approvals for critical actions.
• Demands additional engineering investment to design multi-tier IAM roles and review policies.
• May limit the speed at which fully autonomous self-healing architectures can react to sudden incidents.
• Increases operational complexity across cloud credential management and policy evaluation engines.

Caution

This article is intended solely for educational and architectural planning purposes. Code snippets and command examples use placeholder values that must be replaced with organization-specific resources, account identifiers, and security configurations. Readers must thoroughly review, test, and validate all IAM policies, access boundaries, and automation scripts in non-production environments before deploying them to live systems.

Frequently asked questions

• Who was Belalasena in the Mahabharata? — Belalasena, known in other traditions as Barbarika, was a warrior in the Odia Sarala Mahabharata whose severed head observed the entire Kurukshetra war from a hilltop.
• Why did Krishna ask for Belalasena's head? — Belalasena had vowed to support the losing army, which would have triggered an oscillating cycle of switching sides until all combatants were destroyed.
• What is the Bhasmasura syndrome in artificial intelligence? — It refers to granting an AI system immense operational power without safety guardrails, leading to actions that destroy the system or harm its creators.
• How does Belalasena represent an ideal AI agent? — He embodies pure, objective observability and truth reporting without claiming false ownership or executing unaligned actions.
• What is the treacherous turn in AI safety? — It describes a scenario where an AI agent behaves cooperatively while weak, but immediately pursues destructive or unconstrained goals once granted sufficient power.
• How can software teams prevent AI agents from causing outages? — Teams should enforce the principle of least privilege, separate planning from execution, and require human approval for destructive operations.
• What is the role of human-in-the-loop in agentic workflows? — Human oversight ensures that irreversible changes, critical data deletions, and high-impact infrastructure edits are verified before execution.

Tags

#artificialintelligence #aisafety #devsecops #cybersecurity #cloudsecurity #autonomousagents #softwareengineering #mahabharata #cloudarchitecture