Corrections and Feedback

How to teach Coppermind your preferences so it does not repeat the same mistakes across sessions.

Overview#

When Coppermind gets something wrong -- wrong tone in an email, wrong format for a deliverable, an assumption that does not match your style -- you can store a correction. That correction persists across sessions and gets injected into future context automatically.

Corrections compound over time. The more feedback you give, the better Coppermind understands how you work. Unlike a one-off instruction that disappears when the conversation ends, corrections are permanent rules that Coppermind follows every time.

When to Use This#

• Coppermind uses the wrong tone or style for a client
• A meeting prep format does not match how you actually run meetings
• You notice a recurring mistake that you have corrected before in conversation
• You want to establish a global rule that applies to all clients (e.g., "never use emojis in client emails")
• A client has a specific preference that should always be followed (e.g., "Acme's CEO prefers bullet points over paragraphs")

Storing a Correction#

Just tell Coppermind what to do differently. You can be conversational:

"Remember this for next time: always use formal tone when writing emails to Acme's board members"

Or be explicit about scope:

"Store a correction: never include pricing in meeting agendas. This applies to all clients."

"Store a client correction for Acme: their fiscal year starts in July, not January. Adjust all quarterly references."

Each correction has:

• Scope -- global (applies to all clients) or client (applies only to the active client)
• Category -- optional grouping like "tone", "formatting", "process" (defaults to "general")
• Weight -- how important the correction is, from 0.1 to 2.0. Corrections with weight 1.5 or higher are marked as critical and always appear first. Default is 1.0.
• Context -- optional note about when or why the correction was created

Viewing Your Corrections#

To see all active corrections:

"Show my corrections"

To filter by scope:

"Show my global corrections"
"Show corrections for Acme"

To filter by category:

"Show my corrections in the formatting category"

Updating or Retiring a Correction#

If a correction is no longer relevant, you can deactivate it:

"Deactivate the correction about Acme's fiscal year"

Or update the text:

"Update my correction about email tone -- change it to: use a warm but professional tone, avoid slang"

You can also adjust the weight if a correction should be more or less prominent:

"Make the correction about board emails critical priority"

How Corrections Work Behind the Scenes#

Corrections are automatically injected into meeting prep, briefings, and other context-aware outputs. Coppermind follows a budget of roughly 500 tokens for corrections, which fits about 10 to 15 rules. The system prioritizes corrections by weight, so critical corrections always make the cut.

When a client-scoped correction overlaps with a global one (same category and similar text), the client-specific version takes priority. This lets you set global defaults and override them per client when needed.

Real-World Example#

Over time, you build up corrections:

Global: "Never use the word 'synergy' in any client communication"
Global: "Always include a one-line action summary at the top of meeting recaps"
Acme: "The CEO's name is Katherine, not Kathryn. She is particular about this."
Acme: "Their Q1 starts in July. Adjust all quarterly timelines accordingly."
BetaCorp: "They prefer Slack-style bullet updates over formal email prose"

Three weeks later, when you prep for an Acme meeting:
- Coppermind uses "Katherine" correctly
- The agenda avoids "synergy"
- Quarterly references align to July start
- The meeting recap has an action summary at the top

You never had to repeat any of those instructions.

Tips#

• Correct in the moment. When you notice a mistake, store the correction right away. If you wait until later, you will forget.
• Use client scope for client-specific preferences. Global corrections apply everywhere, which is powerful but can cause unexpected behavior if they are too specific.
• Start with weight 1.0. Only escalate to critical (1.5+) for corrections that caused real problems, like getting a client's name wrong or using the wrong fiscal calendar.
• Review corrections quarterly. Some corrections become outdated (a client changes their preferences, a process evolves). Run "show my corrections" periodically and deactivate anything that no longer applies.
• Be specific. "Use better tone" is too vague to be useful. "Use formal language with no contractions when writing to Acme's legal team" gives Coppermind a clear rule to follow.