Rules change: an owner keeps approving the same kind of action, a rule turns out too strict, a rule stops mattering. Claros keeps every version, proposes changes from the owner’s own answers, and lets a new rule run silently before it stops anything.

​
Rule versions

Each change to a rule is a new version. Nothing is deleted. Every check stores the version id of each rule it hit, so the check log shows the rule as it read then. To see why a rule changed, open it on the map’s Rules page (History) or call GET /api/maps/{id}/rules/{rule}/versions. Each version lists the answers or reports behind it.

​
The owner’s answers become a rule

Every answer to an ask is a precedent on the rule. When the owner has answered the same way on the same kind of action three times (CLAROS_PRECEDENT_SUPPORT), Claros proposes a refined rule:
  • Approved each time: the rule with an exception for what those actions had in common, so they stop asking. It replaces the rule once it leaves watch.
  • Said no each time: a new rule that stops what those actions had in common.
The proposal shows on Home as a card: “3 times you approved … Make it a rule?”, with the proposed wording and Confirm, Edit or Dismiss. An LLM writes the wording only from what the actions and the owner’s reasons say. Without an LLM, the wording is the rule plus the details every one of those actions shared. If the owner answered both ways, there’s no proposal. The card says “You’ve answered both ways” instead.

​
Watch mode

A rule in watch is evaluated on every check like any other rule, but never enforced. The check returns allowed, and the log records what the rule would have done (would: stop, ask or nudge). Rules confirmed from the owner’s answers or from reports start in watch, and so do mined rules confirmed from connectors and drafted rules approved from a policy (unless approved with Approve and enforce now). A rule a person adds themselves keeps the response they set when it’s personal or added by an editor; a member’s team rule runs in watch until an editor confirms it (Add a rule). The same holds when Claros guides a person live in an app: a rule in watch never interrupts or nudges them; each time it would have fired on a record is logged as a check (source tutor, from the live voice session) and counted under watched. On the map, a rule in watch shows “Would have fired N times in watch”. Promote it to nudge, ask first or stop in one tap. A refinement replaces the rule it refines when you promote it.

​
Per-rule counts

GET /v1/maps/{id}/rules/stats and the Rules page show, per rule: The page also shows when the rule last fired. A rule that is served often and never fires is one to retire. Retiring removes it from the map and closes its last version with no successor, so its history and the checks it ran on stay.