---
title: "Comment by Ahmet Özel on \"When your coding agent repeats a mistake, move the lesson out of chat.\" | Hashnode"
description: "The placement decision is the real engineering work. I would add an expiration or review owner to every learned rule, because repository constraints can outlive"
url: "https://hashnode.com/posts/when-your-coding-agent-repeats-a-mistake-move-the-lesson-out-of-chat/6a70d2a0f40be8a79446c4e7/comment/6a7372279911169defc1278d"
---

[Discussion](https://hashnode.com/posts/when-your-coding-agent-repeats-a-mistake-move-the-lesson-out-of-chat/6a70d2a0f40be8a79446c4e7)

Comment [When your coding agent repeats a mistake, move the lesson out of chat.](https://hashnode.com/posts/when-your-coding-agent-repeats-a-mistake-move-the-lesson-out-of-chat/6a70d2a0f40be8a79446c4e7)

[Ahmet Özel](https://hashnode.com/@ahmetozel)

[Aug 5](https://hashnode.com/posts/when-your-coding-agent-repeats-a-mistake-move-the-lesson-out-of-chat/6a70d2a0f40be8a79446c4e7/comment/6a7372279911169defc1278d)

The placement decision is the real engineering work. I would add an expiration or review owner to every learned rule, because repository constraints can outlive the architecture that justified them and then become invisible drag. A useful mistake record should link the failing example, the positive counterexample, the rule or hook that changed, and the regression test that enforces it. That gives the team a way to remove a safeguard safely when the underlying boundary changes.

[Bryce Darling](https://hashnode.com/@mindrealm)

[Aug 5](https://hashnode.com/posts/when-your-coding-agent-repeats-a-mistake-move-the-lesson-out-of-chat/6a70d2a0f40be8a79446c4e7/comment/6a7372279911169defc1278d#reply-6a737ec9aeb3e7ef845df449)

Assigning a review owner and date to every learned rule is a good idea. Automatic expiration is too blunt for some safeguards, but an owner and review date make someone responsible for asking whether the architecture still justifies the rule.

[Ahmet Özel](https://hashnode.com/@ahmetozel)

[Aug 6](https://hashnode.com/posts/when-your-coding-agent-repeats-a-mistake-move-the-lesson-out-of-chat/6a70d2a0f40be8a79446c4e7/comment/6a7372279911169defc1278d#reply-6a7428d86e5833c7ce73cf94)

Agreed—expiry should be a review trigger, not automatic deletion. I would make the owner confirm one of three outcomes: keep it with renewed rationale, narrow or replace it with a better safeguard, or remove it with a regression test proving the boundary has changed. That small lifecycle prevents both stale constraints and silent safeguard decay.
