banthislisted

# Banthis — durable behavioral bans Extend the local instruction surface with a named prohibition. The op-cell is **extend**: add one hard rule, keep existing project memory intact, and make the rule visible to future sessions. Banthis is for user frustration or correction that should persist. It is not a notes system, preference logger, or policy engine. --- ## When to Apply Apply immediately when the user signals a behavior should never recur: - “stop doing X” - “never do that again” - “ban this” - “remember not to …” - “add a project rule …” - repeated frustration with a specific agent behavior Certainty: - **HIGH** — explicit ban language or direct instruction to remember a prohibition. - **MEDIUM** — frustration plus a concrete repeated behavior. Ask only if the rule boundary is ambiguous. - **LOW** — stylistic preference, local task constraint, or one-off correction. Do not persist unless the user asks. --- ## When NOT Do not write a ban when: - the constraint applies only to the current command or current file; - the request is a normal implementation requirement; - the rule would be vague (“be better”, “stop being annoying”); - the rule duplicates an existing ban with no stronger wording; - the rule is unsafe, impossible, or conflicts with a higher-priority instruction. If a requested ban conflicts with an existing ban, surface the conflict instead of rewriting history. --- ## Workflow 1. **Extract the invariant.** Identify the forbidden behavior and t