<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Artifacts on Fondsites</title><link>https://fondsites.com/tags/artifacts/</link><description>Recent content in Artifacts 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/artifacts/feed.xml" rel="self" type="application/rss+xml"/><item><title>AI Agent Artifact Design: Turning Runs Into Reviewable Work</title><link>https://fondsites.com/ai-agents/guidebooks/agent-artifact-design/</link><pubDate>Mon, 18 May 2026 00:00:00 +0000</pubDate><guid>https://fondsites.com/ai-agents/guidebooks/agent-artifact-design/</guid><description>&lt;p&gt;The output of an AI agent should not be trapped inside the run that produced it. A transcript may explain the conversation, but it is rarely the best shape for review, reuse, audit, or handoff. Serious delegated work needs artifacts: drafts, diffs, briefs, evidence packets, decision records, validation reports, task summaries, and prepared actions that can stand on their own after the agent stops talking.&lt;/p&gt;
&lt;p&gt;Artifact design is the craft of deciding what the agent should leave behind. The artifact is where the work becomes inspectable. It separates the useful result from the noise of the process, while preserving enough evidence to understand why the result should be trusted. Without that layer, every reviewer has to replay the agent&amp;rsquo;s path, read its reasoning, inspect its tools, and reconstruct what matters. That is slow, fragile, and unfair to the person who has to accept the work.&lt;/p&gt;</description></item></channel></rss>