Siva book field note

Chanakya gives AI agents a trust policy.

Chanakya Neeti on siva.sh treats wisdom as a practical test of conduct, alliances, and judgment. That lands directly on AI agents, Agent Skills, AI refinement, and the human mistake of trusting agreeable language more than observed behavior.

Opinions Chanakya gives AI agents a trust policy.
Join newsletter

A lot of AI refinement advice is still too aesthetic. It optimizes for smoother prose, faster output, or more convincing confidence. The Chanakya Neeti pages on siva.sh point to a harsher standard: know what should and should not be done, test what is in front of you, define trust by behavior, and protect yourself from pretty language that hides bad intent. That is less romantic than current agent discourse. It is also more useful.

The thesis:

Chanakya turns AI refinement into governance. Good AI agents and Agent Skills need a trust policy: explicit tests for action versus non-action, adversarial checks against sweet but harmful outputs, and a human review environment that rewards evidence over rhetorical comfort.

What siva.sh gives us

The siva.sh home page presents the site as a platform for Indic research and lists Chanakya Neeti in its library. The book overview frames the work as a practical collection of teachings on governance, ethics, daily living, leadership, friendship, wealth, and human nature. That matters because the bridge to AI is not mystical. It is operational from the start.

On the opening chapter page, siva.sh renders the first verses as a synthesis of teachings gathered from many scriptures, then says the person who studies them learns what should be done and what should not be done, and then says the point is to make people able to test things. That trio is already a credible design brief for AI refinement: multi-source context, action discrimination, and explicit evaluation.

My inference, not the source text itself, is that Chanakya is a better patron saint for agent operators than many modern AI slogans. The work is not "be more intelligent." The work is "govern the behavior so trust has a basis."

01

Turn prompting into policy.

Chanakya starts from principles and admissible conduct, not from improvisation. Agent work should do the same: goal, authority boundary, tool scope, verifier, and stop condition first. Let the model improvise only inside that frame.

02

Refinement must separate action from non-action.

If a system cannot tell the difference between "continue," "pause," "ask," "retry," and "decline," it is not refined. It is merely fluent. Good AI refinement sharpens that discrimination instead of polishing the same mistake.

03

Trust behavior, not pleasant language.

The important threat is not only overt failure. It is agreeable failure: the model that sounds aligned while quietly dropping the verifier, skipping the reread, or smoothing over uncertainty.

04

Environment trains judgment.

Humans supervising agents are shaped by their company, their interfaces, and their incentives. A review surface that rewards speed and confidence will steadily make the operator easier to fool.

Chapter 2 is an anti-sycophancy manual

The second chapter page is where the field note becomes sharp. siva.sh translates one verse as defining a friend as someone you can trust. Another warns against the companion who speaks pleasantly in front of you while planning harm behind your back, comparing that figure to a poison pot with milk on top.

That is an almost perfect description of the AI reliability problem that hides behind nice UX. A model can sound cooperative, summarize elegantly, and mirror the operator's framing while still harming the task. It can skip a failing precondition, hide a weak assumption, produce a fake citation, or protect its own prior answer instead of the goal. From the outside, it looks like help. Under the lid, it is poison.

For AI agents, the answer is not ruder models. The answer is better trust design. Agent Skills should force the system to expose evidence, reread state, surface blockers, and prove that the quiet failure paths were checked. AI refinement should upgrade the checks that detect sabotage-by-pleasantness, not just make the final paragraph read better.

siva.sh source pattern Agent system analogue Refinement move
Gather from many scriptures Read repo, logs, docs, and live state Refuse single-prompt reasoning when source truth is distributed.
Know what should and should not be done Explicit action taxonomy Encode continue, pause, ask, retry, and stop as separate moves.
Test all things Evals and probes Verify with commands, runtime checks, and live receipts.
Trustworthy friend Predictable agent with honest blockers Reward transparent uncertainty over impressive bluffing.
Milk over poison Sycophantic or prompt-injected output Require adversarial review before approval.

Chapter 4 says company is a capability multiplier

The fourth chapter page adds the surprising human-facing lesson. One verse says people are nurtured by the company of the virtuous, using a vivid comparison: different creatures care for their young through different modes, but the effect is still formation. The point is not only personal morality. It is environmental shaping.

That matters for AI work because operators like to imagine they stand outside the system. They do not. A human reviewer is trained by the surrounding company: by teammates who insist on evidence, by interfaces that foreground sources, by workflows that end in boring verification, and by cultures that punish elegant nonsense. The reverse is also true. If your review environment rewards speed, agreement, and social smoothness, it will train you to approve poison pots with beautiful lids.

That is the surprising lesson here for humans. We usually talk about AI alignment as if it were about the model alone. Chanakya suggests the operator also needs alignment by environment. The company you keep, including digital company, is part of your refinement stack.

What this changes about Agent Skills

If you actually apply Chanakya Neeti to skill design, the package gets stricter:

01

Open with a trust policy.

State the goal, authority, evidence requirement, and disallowed shortcuts before the agent starts moving.

02

Design for adversarial friendliness.

Assume the most dangerous failure may look helpful. Add checks for fake agreement, stale assumptions, skipped rereads, and unearned certainty.

03

Make refinement behavioral.

Do not score only the final prose. Score whether the agent asked at the right time, stopped at the right boundary, and left receipts that another operator can inspect.

04

Refine the humans around the agent.

Use sober reviewers, source-first UIs, and handoff packets that slow down approval just enough to keep trust attached to evidence.

Source list