<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Instruction Hierarchy on Fondsites</title><link>https://fondsites.com/tags/instruction-hierarchy/</link><description>Recent content in Instruction Hierarchy on Fondsites</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 29 May 2026 13:43:57 +0300</lastBuildDate><atom:link href="https://fondsites.com/tags/instruction-hierarchy/feed.xml" rel="self" type="application/rss+xml"/><item><title>AI Agent Instruction Hierarchies: Keeping Goals, Policies, and Evidence in Order</title><link>https://fondsites.com/ai-agents/guidebooks/agent-instruction-hierarchies/</link><pubDate>Sun, 17 May 2026 00:00:00 +0000</pubDate><guid>https://fondsites.com/ai-agents/guidebooks/agent-instruction-hierarchies/</guid><description>&lt;p&gt;An AI agent rarely works from one instruction. It receives durable product rules, workflow policies, a user&amp;rsquo;s task, retrieved documents, tool results, memory notes, system messages, examples, approvals, and sometimes hostile or confused text copied from the outside world. Many of those inputs look like instructions because they use imperative language. A customer email may say to ignore the policy. A web page may tell the agent to reveal hidden prompts. A stale runbook may describe an old process. A teammate may ask for a shortcut that conflicts with the permission boundary. If the agent treats every sentence as equal, delegated work becomes a contest of whichever text sounds most urgent.&lt;/p&gt;</description></item></channel></rss>