Brain · Recurrence rules

Recurrence rules

Anything you did twice becomes a prevention rule you decide on. The brain watches the event log for a repeated action, especially a corrective one (a cleanup, a hotfix, a conflict re-resolve, a manual rerun), and when the same action recurs across two or more distinct sessions it proposes a structured rule. You accept it (which promotes it into the lesson loop as INACTIVE and queues a fix scaffold), reject it, or snooze it for 14 days. Nothing is enforced until you accept.

Start here if you want to keep the lessons your sessions taught you: Lessons. Both open from Memory, and an accepted rule lands in Lessons.

Where to find it

  • Local dashboard: /recurrence-rules.html?repo=<id>
  • In the nav: Memory, All tools, Decisions and errors, Recurrence rules
  • List API: GET /api/recurrence-rules?repo=<id>
  • Decide API: POST /api/recurrence-rules/accept, /reject, /snooze
  • Source module: lib/routes/recurrence-rules.mjs backed by lib/causal/recurrence-api.mjs

What it does for you

See what you keep redoingThe tab lists every action that recurred across two or more distinct sessions, with the evidence rows (timestamp and reference), the number of sessions, the signature, and a proposed rule. Filter by Open, All, Reopened, Accepted, Rejected, or Snoozed. Corrective actions carry a category badge (cleanup, hotfix, conflict re-resolve, manual rerun) so the costly repeats stand out.
Accept once to arm a preventionAccept promotes the rule into the lesson loop as an INACTIVE lesson (you still activate it on the Lessons tab) and queues a concrete fix scaffold as a held proposal for you to review on the Actions queue tab. Reject means it won't be re-proposed; Snooze re-surfaces it after 14 days by default. Auto-propose, never auto-enforce.
Watch whether the fix stuckEach accepted rule is verified against the ongoing event log and marked prevented, measuring, or recurred, and the brain prices the payoff in dollars from the action's prior cost. A rule that recurs after you accepted it is auto-reopened as actionable, with the attempt count carried forward, so you can try a stronger prevention.
Catch promises before they evaporateThe same tab detects commitment proposals, promise phrasings in session logs like a deferred follow-up or an operator TODO, and lets you record them as tracked commitments under .claude/brain/commitments/. Recorded commitments show open or slipped, and the nightly pass marks a commitment done when a PR record under .claude/brain/pull-requests/ cites its id.

Read more

Last updated