<?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>Trigger an AEGIS workflow from a signed webhook</title><link>https://100monkeys.ai/blog/trigger-an-aegis-workflow-from-a-webhook</link><guid isPermaLink="true">https://100monkeys.ai/blog/trigger-an-aegis-workflow-from-a-webhook</guid><pubDate>Thu, 29 Oct 2026 01:56:00 +0000</pubDate><description>Set a per-source HMAC secret, route the source to a workflow, sign the raw body, test with curl, and stop duplicate deliveries with an idempotency key.</description></item><item><title>Import a community SKILL.md as an AEGIS agent</title><link>https://100monkeys.ai/blog/import-a-community-skill-into-aegis</link><guid isPermaLink="true">https://100monkeys.ai/blog/import-a-community-skill-into-aegis</guid><pubDate>Thu, 29 Oct 2026 01:55:00 +0000</pubDate><description>Run the AEGIS skill-import workflow on a SKILL.md, pick a security preset, read the safety check, approve at the review gate and find the new agent.</description></item><item><title>AEGIS workflow states and transitions, step by step</title><link>https://100monkeys.ai/blog/aegis-workflow-states-and-transitions</link><guid isPermaLink="true">https://100monkeys.ai/blog/aegis-workflow-states-and-transitions</guid><pubDate>Thu, 29 Oct 2026 00:58:00 +0000</pubDate><description>Write an AEGIS workflow one state at a time: the eight state kinds, transitions tried top to bottom, score branches, loop guards and terminal states.</description></item><item><title>Choose an AEGIS agent runtime from the standard registry</title><link>https://100monkeys.ai/blog/aegis-standard-runtime-registry</link><guid isPermaLink="true">https://100monkeys.ai/blog/aegis-standard-runtime-registry</guid><pubDate>Thu, 29 Oct 2026 00:57:00 +0000</pubDate><description>Pick a language and version for an AEGIS agent from the standard runtime registry, check it with aegis.runtime.list, and see what fails and when.</description></item><item><title>The AEGIS agent manifest: every field and what it enforces</title><link>https://100monkeys.ai/blog/aegis-agent-manifest-fields</link><guid isPermaLink="true">https://100monkeys.ai/blog/aegis-agent-manifest-fields</guid><pubDate>Wed, 28 Oct 2026 23:46:00 +0000</pubDate><description>Every section of an AEGIS agent manifest, what each field enforces, its default, the refusals at deploy, and where a human approval goes instead.</description></item><item><title>How AEGIS seals a tool call: the SEAL gateway, step by step</title><link>https://100monkeys.ai/blog/how-aegis-seals-a-tool-call</link><guid isPermaLink="true">https://100monkeys.ai/blog/how-aegis-seals-a-tool-call</guid><pubDate>Wed, 28 Oct 2026 23:45:00 +0000</pubDate><description>Follow one AEGIS tool call through the SEAL gateway: the per-run session, the signed envelope, the nine checks, the policy decision and the audit event.</description></item><item><title>Self-host AEGIS with Firecracker: the setup the docs describe, and what runs today</title><link>https://100monkeys.ai/blog/aegis-on-firecracker</link><guid isPermaLink="true">https://100monkeys.ai/blog/aegis-on-firecracker</guid><pubDate>Wed, 28 Oct 2026 20:52:00 +0000</pubDate><description>Firecracker support in AEGIS is planned, not shipped. Check a host for KVM, read the documented config, and run the Podman path that works now.</description></item><item><title>Reading an AEGIS execution log: what a sealed tool call records</title><link>https://100monkeys.ai/blog/reading-an-aegis-execution-log</link><guid isPermaLink="true">https://100monkeys.ai/blog/reading-an-aegis-execution-log</guid><pubDate>Wed, 28 Oct 2026 20:51:00 +0000</pubDate><description>Read an AEGIS run from its execution record to its iteration log to the SEAL envelope and audit event behind each tool call, allowed or refused.</description></item><item><title>Run a scheduled agent with AEGIS: schedules, runs and what you see when one fails</title><link>https://100monkeys.ai/blog/run-a-scheduled-agent-with-aegis</link><guid isPermaLink="true">https://100monkeys.ai/blog/run-a-scheduled-agent-with-aegis</guid><pubDate>Wed, 28 Oct 2026 20:50:00 +0000</pubDate><description>Put an AEGIS agent on a timer, fire it once by hand, and read each run: started, skipped, refused or paused. Every field from the public docs.</description></item><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>
