{"id":"f7bd4df7-4411-42d1-9d69-0a3985c6f0e4","slug":"rules-for-workers","category_slug":"workers","order_index":106,"published":true,"created_at":"2026-06-19T14:58:38.774Z","related_slugs":"[\"create-workers\",\"behaviour-studio\",\"workers-self-settings\"]","title_fr":"Les règles (garde-fous)","title_en":"Rules (guardrails)","content_en":"\n\n<blockquote>\n<p><strong>The right picture:</strong> the <strong>initiative</strong> (see the Behavior Studio article) sets the Worker's <em>general temperament</em>. The <strong>rules</strong> are the <em>precise instructions</em> that override it: \"for this, don't ask\" / \"for this, always ask\" / \"this, never\".</p>\n</blockquote>\n\n<h2>What a rule is</h2>\n<p>A rule has a <strong>title</strong>, an optional <strong>description</strong>, and above all a <strong>scope</strong> among three:</p>\n<table>\n<thead>\n<tr>\n<th>Scope</th>\n<th>Worker behavior</th>\n</tr>\n</thead>\n<tbody><tr>\n<td><strong>Always</strong> (<code>always</code>)</td>\n<td>Performs the action <strong>without asking</strong></td>\n</tr>\n<tr>\n<td><strong>Ask</strong> (<code>ask</code>)</td>\n<td><strong>Asks for confirmation</strong> before acting</td>\n</tr>\n<tr>\n<td><strong>Never</strong> (<code>never</code>)</td>\n<td><strong>Refuses</strong> the action</td>\n</tr>\n</tbody></table>\n<p><em>Examples:</em></p>\n<ul>\n<li><em>\"Send external emails\"</em> → <strong>Ask</strong></li>\n<li><em>\"Delete data\"</em> → <strong>Never</strong></li>\n<li><em>\"Create a draft\"</em> → <strong>Always</strong></li>\n</ul>\n\n<h2>Where to create them</h2>\n<ul>\n<li>At the Worker's <strong>creation</strong>: the <em>Skills &amp; Guardrails</em> step.</li>\n<li>Later: the Worker's page → <strong>Behavior Studio</strong> → rules section.</li>\n<li><strong>Worker templates</strong> (admin) can pre-fill rules, which are then copied into each Worker hired from the template.</li>\n</ul>\n<h3>To add a rule</h3>\n<ol class=\"steps\">\n<li>Click <strong>Add a rule</strong></li>\n<li>Enter a clear <strong>title</strong> (the action concerned)</li>\n<li>Choose the <strong>scope</strong>: <em>Always</em> / <em>Ask</em> / <em>Never</em></li>\n<li>Save</li>\n</ol>\n\n<h2>What happens under the hood</h2>\n<ul>\n<li>Your <strong>active</strong> rules are <strong>injected into the Worker's instructions</strong>, in a dedicated <em># RULES</em> section.</li>\n<li>The Worker reads them as behavior instructions:<ul>\n<li><em>ask</em> scope → it calls a <strong>confirmation</strong> tool that pauses the action until you approve;</li>\n<li><em>never</em> scope → it refuses;</li>\n<li><em>always</em> scope → it acts directly.</li>\n</ul>\n</li>\n</ul>\n<blockquote>\n<p><strong>Important — these are instructions, not a technical lock.</strong> Rules strongly guide the Worker, but they're not a code-level permission system. For sensitive actions, combine an <em>ask</em>/<em>never</em> rule with a cautious initiative level.</p>\n</blockquote>\n\n<h2>The limits to know</h2>\n<ol class=\"steps\">\n<li><strong>Maximum 20 active rules</strong> per Worker. Beyond that, you must delete one before adding a new one (explicit error message).</li>\n<li><strong>No explicit priority/order.</strong> Rules are evaluated in the order they appear. Avoid contradictory rules.</li>\n<li><strong>Rules don't automatically propagate to sub-agents.</strong> If your Worker delegates to a sub-agent, you must explicitly restate the constraints in the delegation instructions.</li>\n<li><strong>The <em>ask</em> scope requires a real confirmation.</strong> The Worker calls a confirmation tool that suspends execution — it doesn't just \"hesitate\".</li>\n</ol>\n\n<h2>Rules, instructions, missions: don't mix them up</h2>\n<table>\n<thead>\n<tr>\n<th>Concept</th>\n<th>Role</th>\n<th>When it acts</th>\n</tr>\n</thead>\n<tbody><tr>\n<td><strong>Rule</strong></td>\n<td>Per-action guardrail (always / ask / never)</td>\n<td>At each decision to act</td>\n</tr>\n<tr>\n<td><strong>Onboarding instructions</strong></td>\n<td>Framing text given at hire</td>\n<td>Continuously, as context</td>\n</tr>\n<tr>\n<td><strong>Initiative</strong></td>\n<td>General temperament (passive → autonomous)</td>\n<td>At each decision to act</td>\n</tr>\n<tr>\n<td><strong>Mission / Task</strong></td>\n<td>Triggered work (recurring, scheduled, on event)</td>\n<td>When the trigger fires</td>\n</tr>\n</tbody></table>\n\n<h2>In summary</h2>\n<ul>\n<li><strong>Rules</strong> = precise, per-action guardrails, in three scopes.</li>\n<li>They are <strong>injected into the Worker's behavior</strong> (strong instructions, not a lock).</li>\n<li><strong>Cap of 20</strong>, no priority, <strong>must be restated to sub-agents</strong>.</li>\n<li>Combine them with the right <strong>initiative level</strong> for a Worker that's both autonomous and safe.</li>\n</ul>","tags_fr":null,"tags_en":null,"intro_fr":"Les règles sont les garde-fous de ton Worker : elles disent, action par action, ce qu'il peut faire seul, ce pour quoi il doit demander, et ce qu'il ne doit jamais faire.","intro_en":"Rules are your Worker's guardrails: they state, action by action, what it can do on its own, what it must ask about, and what it must never do.","prerequisites_fr":null,"prerequisites_en":null}