Changing a rule is rarely the problem. The old value that still lives somewhere is.
Changing a rule is rarely the problem. The old value that still lives somewhere is.
I changed the schedule of my posts. Between two posts there had to be at least five hours instead of seven. The code got the five. But the agent's knowledge, the description of the tests and an old copy in memory still said seven. An agent plans on what its knowledge says, so it kept to seven.
Now I put every limit in one place in a register, with the old value next to it as a search pattern. A check then finds all the places where the old value still appears, and reports every source that says something different from the register. A stale cache too. It runs with every change to such a limit and every night as well, and gives the owner a card if something deviates.
So a limit has one source. A second place with the same number is a mistake, even if it's still correct today.
You can start small. Pick one number your organisation leans on, such as an amount, a deadline or a number of hours. Search for it in your documents, instructions and systems. Does it appear in more than one place? Pick one as the source and let the rest point to it.
Where does a number live in two places for you?
#AIAgents #Workflows #Quality