<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ai-Harnesses on AI For Human Expertise</title><link>https://aiforhumanexpertise.com/tags/ai-harnesses/</link><description>Recent content in Ai-Harnesses on AI For Human Expertise</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Mon, 06 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aiforhumanexpertise.com/tags/ai-harnesses/index.xml" rel="self" type="application/rss+xml"/><item><title>Constrained Generation Is Symbolic AI Smuggled Into LLMs</title><link>https://aiforhumanexpertise.com/blog/constrained-generation-is-symbolic-ai/</link><pubDate>Mon, 06 Jul 2026 00:00:00 +0000</pubDate><guid>https://aiforhumanexpertise.com/blog/constrained-generation-is-symbolic-ai/</guid><description>&lt;h2 id="the-toolkit-most-practitioners-already-reach-for"&gt;The Toolkit Most Practitioners Already Reach For&lt;/h2&gt;
&lt;p&gt;Anyone who has shipped a language-model application beyond the prototype stage has, at some point, used constrained generation. The shape of the encounter is consistent. The model produces text that is almost right and occasionally wrong in ways the consumer cannot tolerate. Someone on the team reaches for one of a small set of tools: Outlines, lm-format-enforcer, the JSON-schema mode in their model API, a regex post-filter, a structured-output decoder. The wrong answers stop. The system ships.&lt;/p&gt;</description></item><item><title>A Five-Role Diagnostic For Any AI Agent</title><link>https://aiforhumanexpertise.com/blog/a-five-role-diagnostic-for-any-ai-agent/</link><pubDate>Mon, 22 Jun 2026 00:00:00 +0000</pubDate><guid>https://aiforhumanexpertise.com/blog/a-five-role-diagnostic-for-any-ai-agent/</guid><description>&lt;h2 id="most-agent-problems-have-a-diagnostic"&gt;Most Agent Problems Have A Diagnostic&lt;/h2&gt;
&lt;p&gt;When an AI agent fails in production, the conversation almost always turns to the model. The team waits for a bigger model, a better-tuned variant, a different vendor, a new context window. Sometimes the team turns to prompts instead: more careful instructions, more examples, a sharper system message. Most failures are neither. They are failures of structure, and the structure question is a thirty-year-old framework most engineers have never read.&lt;/p&gt;</description></item><item><title>The Harness Is Where Symbolic AI Returned</title><link>https://aiforhumanexpertise.com/blog/the-harness-is-where-symbolic-ai-returned/</link><pubDate>Mon, 15 Jun 2026 00:00:00 +0000</pubDate><guid>https://aiforhumanexpertise.com/blog/the-harness-is-where-symbolic-ai-returned/</guid><description>&lt;h2 id="the-standard-story-about-ai-agents-misses-half-the-system"&gt;The Standard Story About AI Agents Misses Half The System&lt;/h2&gt;
&lt;p&gt;The dominant story about building AI agents is straightforward: take a language model, prompt it well, give it tools, and let it loop. The model is doing the work. Everything else is plumbing.&lt;/p&gt;
&lt;p&gt;This story is incomplete in a way that has practical consequences. The plumbing is not plumbing. It is a body of design decisions that determines whether the agent works in production, fails silently, or quietly degrades over time. And some of it, the parts that earn the name, is doing what symbolic AI has always tried to do: making reasoning explicit, checkable, and tied to a model of the world.&lt;/p&gt;</description></item></channel></rss>