engraim-calibrate

name

engraim-calibrate

description

Record and manage how Claude should BEHAVE in this workspace — corrections, conventions, do/don't rules, tone. Use WHENEVER the user corrects you, states a preference, expresses frustration with an approach, or a `verdict:` annotation comes back negative. Also use to reaffirm, promote, or retire existing behavior overrides. This is the workspace's self-improving frame; it's distinct from facts about the world (use engraim-memory for those).

Calibrate: the workspace's behavioral frame

Corrections about how to act here are first-class memory. Capturing them is what makes the workspace get easier to work in over time.

When to calibrate

• The user corrects your approach ("don't do X", "always Y here").
• They state a standing preference (tooling, style, process, tone).
• They push back or express frustration — the underlying preference is the override.
• A verdict: you left on prior work comes back negative — turn the lesson into a rule.

A UserPromptSubmit hook already watches for durable, project-wide phrasing ("from now on", "always remember", "we should do it like this", "in this project …") and injects a [EngrAIm] nudge when it fires. Treat that nudge as a prompt to act here — but apply your own judgment: capture it only if it's a standing rule for the workspace, not a one-off for the current task. The hook detects; you decide.

How

• Phrase it as a short imperative rule: "run tests before committing", "prefer pnpm", "keep answers terse, no preamble". Add a scope tag (git, testing, tone, …) when domain-specific.
• Call calibrate(rule, scope?, reason?). Re-stating a rule you already have REAFFIRMS it (refreshes its 90-day expiry and counts toward promotion) — that's good, not a duplicate.

The promotion ladder

1. Logged / one-off — captured, low commitment.