<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>100monkeys.ai blog</title><link>https://100monkeys.ai/blog/</link><atom:link href="https://100monkeys.ai/blog/rss.xml" rel="self" type="application/rss+xml" /><description>Essays from 100monkeys.ai on AI agents, source control, approvals and accountability.</description><language>en</language><item><title>How to give an orchestrator an approval step: a pattern, with AEGIS as the worked example</title><link>https://100monkeys.ai/blog/approval-step-for-an-agent-orchestrator</link><guid isPermaLink="true">https://100monkeys.ai/blog/approval-step-for-an-agent-orchestrator</guid><pubDate>Wed, 28 Oct 2026 20:32:00 +0000</pubDate><description>A pattern for human approval gates in agent workflows: where the gate goes, what the reviewer sees, what silence means, with AEGIS as the worked example.</description></item><item><title>A traceability checklist for AI agents in production: what to log, what to sign, what to show the reviewer</title><link>https://100monkeys.ai/blog/ai-agent-traceability-checklist</link><guid isPermaLink="true">https://100monkeys.ai/blog/ai-agent-traceability-checklist</guid><pubDate>Wed, 28 Oct 2026 20:31:00 +0000</pubDate><description>What to log on every agent run, what to sign so the log can be trusted, and what to show the reviewer. Vendor-neutral, with open standards for each step.</description></item><item><title>Install AEGIS on a fresh Ubuntu VPS and run your first approved task</title><link>https://100monkeys.ai/blog/install-aegis-on-ubuntu-vps</link><guid isPermaLink="true">https://100monkeys.ai/blog/install-aegis-on-ubuntu-vps</guid><pubDate>Wed, 28 Oct 2026 20:30:00 +0000</pubDate><description>Install AEGIS on a fresh Ubuntu server with one command, run an agent, then gate its result behind a human approval. Every step from the public docs.</description></item><item><title>Blame that remembers why: what a change should carry when the author was an agent</title><link>https://100monkeys.ai/blog/blame-that-remembers-why</link><guid isPermaLink="true">https://100monkeys.ai/blog/blame-that-remembers-why</guid><pubDate>Wed, 28 Oct 2026 18:00:00 +0000</pubDate><description>When the author of a change is an agent, blame can no longer point at a person who remembers. What a change should carry instead: the reason, the whole change, no silent merges, a history that cannot be rewritten, and approval bound to what was approved.</description></item><item><title>The approval is the product: why an agent orchestrator should make you say yes</title><link>https://100monkeys.ai/blog/the-approval-is-the-product</link><guid isPermaLink="true">https://100monkeys.ai/blog/the-approval-is-the-product</guid><pubDate>Wed, 28 Oct 2026 17:59:00 +0000</pubDate><description>Two kinds of yes, and why both belong outside the model: a deny-by-default policy in the runtime, and an approval bound to the exact act.</description></item></channel></rss>
