Docs · LLMs and developers
Reviewed2026-06-20Version3.12.0Your Automation Rules
How Achiral AI keeps a private, per-person view of automation rules — learning what works for you, and letting you pause a rule or require your own approval without affecting your teammates.
Automation performance explains how Achiral AI scores each automation rule for your whole organisation. On top of that shared score, Chiro also keeps a private, per-person view: when an automation run can be attributed to you, it remembers how that rule has worked for you specifically, and lets you tune the rule for your own account without changing anything for anyone else.
You manage this from your own Account → Memories page, in the Automation Rules panel. Everything there is scoped to you: you only ever see rules that have run on your behalf, never another person's history.
Two levels of rule memory
Achiral AI keeps a rule's learning at two separate, independent levels:
- Org-level memory. One shared utility per rule for the whole organisation, folding in everyone's outcomes together. It is visible to owners and admins and is described in Automation Performance.
- Member-level memory (this page). Your own private utility for a rule, kept only for runs attributed to you and visible only to you.
The two never overwrite each other: your private score is never changed by other people's runs, and your pause or approval choices never change the shared organisation rule or anyone else's experience. Everything below describes the member-level layer.
What "for you" means
A run is attributed to you when you are the person it acted for:
- You ran it — you triggered the automation manually.
- You approved or rejected it — you were the approver on a step that required approval.
- An event you caused — an incoming business event whose actor resolves to your account.
- A scheduled rule that names you — a scheduled automation that is explicitly configured to act on your behalf.
When a run can't be tied to an individual (for example, a general scheduled job), it stays organisation-only and simply doesn't create any personal memory.
Your personal score
Your per-rule score works exactly like the organisation score, just measured from your own outcomes:
- It is a value between 0 and 1, starting from a neutral 0.5.
- Your successful runs raise it; your failed runs lower it.
- Older outcomes fade over time, so it reflects your recent experience with the rule.
Until a rule has actually run for you, you have no personal history yet, so the panel shows the organisation default score and marks the row using org default. Once you accumulate your own outcomes, the panel switches to your score.
How your score affects firing
When a run is attributed to you, Chiro ranks the matching rules using a blend of the organisation score and your personal score — weighted mostly toward the organisation (the personal signal contributes a smaller share by default). A brand-new personal history doesn't count against a rule: with no outcomes of your own yet, ranking falls back to the organisation score, so the rule is still given a fair chance for you.
Your personal pause and approval choices, described below, only ever change your runs of a rule. They never affect the organisation rule or any teammate.
The panel
Each rule in the Automation Rules panel shows:
- The rule's name and trigger type (Manual, Schedule, Insight, or Event).
- A state badge (see below).
- Your utility for the rule (or the org default, when you have no personal history yet).
- Your success rate and a breakdown of your outcomes (successes / failures, and neutral runs if any).
- The last outcome and when it happened.
State badges
| Badge | Meaning |
|---|---|
| Active | Running for you normally. |
| Learning | Too few of your own runs to personalise yet — still exploring. |
| Approval required for me | This rule asks for your approval before it runs for you. |
| Paused for me | Paused from auto-running for your account during a cooldown. |
| Paused by your org | An admin paused it for everyone — only an admin can resume it. |
When a rule is paused for the whole organisation, that takes precedence over your personal state: you'll see Paused by your org, and the personal controls are unavailable until an admin resumes it.
What you can do
The panel gives you two member-scoped controls. Both apply only to your own runs of the rule:
- Un-pause for me — if a rule has been paused for your account (because it kept failing for you), this clears your pause and lets it run for you again. A later poor outcome can pause it for you again, just like before.
- Require my approval / Allow auto-run — toggle whether this rule must ask for your approval before running for you. Requiring approval is treated as a deliberate, lasting preference, so it stays in place through later automatic recalculations until you turn it off again with Allow auto-run.
These controls never touch the organisation-level rule. Lifting or changing the organisation pause is still an admin action on the Automation Performance panel.
Managing your rules via the API
Two endpoints back the panel. Both act only on the signed-in member's own rule memory and can never change organisation-level state:
POST /api/user/memory/automation-rules/:templateId/unsuppress— clears your personal pause for one rule.POST /api/user/memory/automation-rules/:templateId/require-approval— opts your runs of one rule into an approval gate. Send{ "enabled": false }to opt back out.
If you have no personal memory for the given rule — which is also what a request for someone else's rule looks like — the endpoint returns 404, so one member can never read or change another member's rule memory.
Privacy
Your automation rule memory is private to you. The panel and the endpoints above only ever return or modify rows that belong to your account within your current organisation; any row that doesn't match is dropped. Your personal pause and approval choices are invisible to other members and never alter the shared organisation rule.
Reviewed 2026-06-20 for Achiral AI v3.12.0.