A commercial team let an assistant draft routine agreements from past deals. It was fast, and for a while it was fine. Then a one-time concession from a bad quarter started showing up as the suggested default. Nobody had voted for that. The model had noticed a pattern and promoted it. The reviewer, moving quickly, accepted drafts that looked familiar.
Familiar is not the same as decided.
a pattern is not a decision
Separate what the company has agreed, on purpose, from what has merely happened. The first belongs in a playbook a person maintains. The second is history. A model may read history. It should not be allowed to rewrite the playbook because a pattern got thick.
When a draft wants to depart from the playbook, the screen should say so in the first line, not in a highlight three pages down.
Repetition is not approval. Someone has to mean it.
change the standard on purpose
If the last five deals suggest a new position, that is a change request. Name an owner. Write what would change. Decide whether the next draft uses it. Shipping the new position silently, because the model averaged it in, is how a standard dissolves.
The same habit applies when a vendor changes a model under you. Notice, test, then go. A living system with no release is just drift with a nicer interface.