The most repeated message in Acme used to be a correction. “Shorter.” “No exclamation marks.” “We say guests, not clients.” People typed the same rule into conversation after conversation, because a correction lived only in the conversation where it was made. From this week it can live in the project instead.
What changed
When you correct a draft, Acme now asks whether the correction is a one-off or a rule. Choose Save to profile and the rule is added to the project profile, in your words. Every request in the project reads the profile first, so the next draft follows the rule without being told.
One-off corrections work exactly as before: they change the current draft and nothing else.
Where the rules go
Saved rules appear in a new Rules section of the profile, newest first. Each one shows the conversation it came from, so you can always see why it is there. Edit a rule to sharpen it, or delete it when it no longer applies — the change takes effect on the next request.
Rules are per project. A tone that is right for one client does not leak into another client’s work, and a copied workflow reads the rules of the project it runs in.
Why we did it this way
We considered learning rules automatically from every edit. In testing it guessed wrong often enough to be annoying: a shortened paragraph became “always be brief”, a removed price became “never mention prices”. Asking once, at the moment of the correction, costs one click and keeps the profile something you can read and trust.
What to try first
Open a project you use every week and look at your last few corrections. Most people find two or three that they make every time. Save those, and the first draft of next week’s work starts closer to done.
The profile itself is explained in Your First Project, and saved rules work on every plan, including the free one.
