LearnAI home

Keeping Control ยท Lesson 3

How to Stop AI Forgetting Your Rules

Constraints decay. Here is how to refresh them.

Rules have a half-life

You set the rules at the start of the session, carefully, in one tidy block. Then you did an hour of real work, and the rules did what rules do in a long conversation: they faded. Not all at once, and not because anything went wrong. They simply moved further and further from the sentence being written now.

So stop thinking of your constraints as settings you configured once. Think of them as a signal that weakens with distance, and needs a repeater.

The practical consequence is unintuitive. A rule stated once at message one is weaker than the same rule stated at message one and again at message thirty, even though nothing about the rule changed.

Fix one: restate at decision points

You do not need to repeat everything constantly. You need to repeat the relevant rule at the moment it is about to be tested.

A decision point is any message where the assistant is about to produce something that a colleague might actually see: a draft, a summary of findings, a recommendation, a rewrite, an email. Those are the moments where a forgotten constraint becomes a real mistake rather than a private one.

The move takes one line. Before the request, restate only the rules that bear on this specific output.

Prompt you can copy: the decision point restatement

Before you draft this, the rules that apply here:

  • Findings only. No recommendations, no next steps, no suggestions.
  • Every claim needs a page reference from the material I supplied.
  • If the source does not settle something, write UNCLEAR. Do not estimate.

Now draft: [your request]

Three lines, and they sit immediately next to the work rather than an hour behind it.

Fix two: make it repeat the constraints back

Before anything large or expensive, force the assistant to reconstruct the rules in its own message. This does two things at once. You find out whether the rules survived, and if they did, they are now freshly restated in the most recent part of the conversation, which is exactly where they carry most weight.

Prompt you can copy: read back before a big step

Do not start the task yet.

First, list every rule and constraint currently in force for this piece of work, numbered, in my wording. Include anything I set earlier that still applies. Then state in one line what you understand the task to be.

I will confirm or correct before you begin.

Read what comes back properly. Two things are worth noticing. Missing rules tell you what has already decayed. Invented rules are just as important: an assistant that lists a constraint you never set has started building on its own assumptions, and everything downstream inherits them.

โŒ Weak prompt

Prompt

Remember all the rules I gave you earlier and write the summary.

Output

Of course. Here is the summary, written in line with your earlier requirements. [produces a polished summary that ends with three recommended next steps]

Trusting it to remember is not a check, it is a hope. The word remember produced agreement rather than recall, and the no-recommendations rule died quietly in the last paragraph.

โœ… Good prompt

Prompt

Do not write the summary yet. First list every rule in force, numbered, in my wording. Then state the task in one line and wait for me to confirm.

Output

Rules in force: 1. Findings only, no recommendations. 2. Maximum 400 words. 3. Page reference for every claim. 4. Write UNCLEAR rather than estimating. Task as I understand it: summarise the supplier review findings for the finance director. Confirm and I will proceed.

Now you can see what survived before it costs you a draft, and the act of listing the rules parks them right next to the work instead of an hour behind it.

In plain English

Decision point:
Any moment the assistant is about to produce something a colleague might see, such as a draft or a set of findings.
Read-back:
Asking the assistant to state the rules and task back to you before it starts, so you can catch what has decayed.
Standing brief:
A short block of your fixed rules that you keep outside the chat and paste in again when needed.
Poisoned thread:
A conversation carrying a mistake or bad assumption that keeps resurfacing no matter how often you correct it.

Fix three: keep a standing brief outside the chat

Write your rules once, in a note on your own machine, and paste the block in again whenever a session gets long or whenever you start a new one. Whether you work in Gemini, ChatGPT or Claude, the brief belongs outside the chat window, because that is the only copy that does not decay. Keep it short enough that pasting it never feels like a chore, because a brief you resent pasting is a brief you stop pasting.

Prompt you can copy: your standing brief template

STANDING BRIEF. These rules apply to everything in this conversation and override anything we drifted into earlier.

Role: [what you are acting as, one line] Audience: [who reads the output] Always:

  • [rule]
  • [rule] Never:
  • [rule]
  • [rule] Uncertainty: if the material I supplied does not settle a point, write UNCLEAR and stop. Do not estimate, and do not fill the gap from general knowledge.

Confirm you have these, then continue with: [current task]

The phrase "override anything we drifted into earlier" is doing real work. Without it you have added rules to a pile that already contains contradictions. With it, you have said which version wins.

Fix four: start again, on purpose

Sometimes the thread is poisoned. A wrong figure got into an early answer and now reappears in every draft. A misunderstanding about scope has been quietly baked into six outputs. You correct it, it agrees warmly, and three messages later it is back, because the mistake is still sitting in the conversation being read as history.

Fighting that is a bad trade. You will spend more effort arguing than restarting, and you will never fully trust the result.

Starting fresh is not failure and it is not lost work. Take the standing brief, take the source material, take a clean summary of the decisions you have made, and open a new conversation. The trick is to carry the conclusions across without carrying the contamination.

Do not ask the poisoned thread to summarise itself for the new one. It will faithfully carry the error across, now compressed into an authoritative-sounding paragraph. Write the handover yourself, or have it list only the decisions you can personally confirm.

Checkpoint

Constraints decay with distance. Restate the relevant ones at decision points, make the assistant read the rules back before big steps, keep a short standing brief you can paste again, and start a clean thread rather than fighting a poisoned one.

๐Ÿ“ Quiz

Question 1 of 4

Why is a rule stated once at the start weaker than the same rule stated again later?

Found this useful? Pass it on.