Claros learns from your overrides, with each rule’s owner approving every change. Nothing about a rule changes on its own: a report is evidence, a suggested change is a draft, and only an expert’s confirm writes the map.

​
Report a check

Any check in the log can be reported, by the agent that was stopped, by the person it acted for, or by an editor reading the log. Three ways in:
  • The guard. Every stop message ends with the command, filled in:
  • The Claros MCP server. report_override(check_id, verdict, reason, rule_id?).
  • The check log. Each rule hit has This was wrong; each check has Missed one. One sentence, in your words.
API: POST /v1/checks/{check_id}/override {verdict, rule_id?, reason?, by?} with an agent key or a capture session. Each report is tied to the check, the rule and the map version the check ran under. The same caller reporting the same thing twice counts once.

​
Counters

Each rule on the map’s rules page shows what the log says about it: how many checks it decided (stop, ask or nudge), how many were overridden, confirmed right and missed. GET /v1/maps/{id}/rules/stats returns the same numbers.

​
Suggested changes

Claros drafts three kinds of change, and none is active until confirmed: Reworded and new rules are drafted by a model from the reports’ reasons only, in the reporters’ words, and checked before they’re shown: they must cite at least two of the reports, the rule fits in one sentence, and a scope is kept only if every part of it is valid. Softening is arithmetic, no model. A suggestion expires after 30 days unconfirmed. Thresholds: CLAROS_DEMOTE_RATIO (0.5), CLAROS_DEMOTE_MIN (4), CLAROS_CANDIDATE_SUPPORT (2), CLAROS_CANDIDATE_TTL_DAYS (30).

​
Confirm, edit, dismiss

The Suggested changes panel on the rules page shows each suggestion with the rule as it is now, the change, and every report behind it (the reason, who sent it, which tool, when). An editor or admin can:
  • Confirm: Claros writes a new map version with that one change. The next check uses it.
  • Edit: put it in your own words (or pick another response) before confirming.
  • Dismiss: nothing changes. The reports behind it won’t bring the same draft back.

​
Versions

Every change to a map is a new version: a confirmed suggestion, a rule edit, a revert. Versions on the rules page lists them with who made the change and why. Revert to version N brings that version’s rules back as a new version, so a revert can itself be reverted.

​
What can’t happen

  • The drafting code can only write suggestions. Only the confirm and revert endpoints write maps, and both need an editor or admin.
  • A model never rewrites a whole map: a confirm changes one rule.
  • The drafter never sees evaluation data; the evaluation set is read only by the eval runner.
  • Every report, suggestion, confirm, dismiss and revert is logged with the map.