Set safe boundaries

Correct saved information in your Mind

Mensara memory is the information your team saves in its Mind for later use: decisions, notes and ways of working. If one of those records is wrong or out of date, you can ask your connected agent to suggest a correction. This guide shows you how to check that the right information actually changed.

Content updated .

Contents

How a correction works

A record is a saved piece of information in your Mind. Your agent reads records to answer questions, so correcting the underlying record helps the next answer start from better information. Editing a sentence in the chat alone does not show that the saved record changed.

You give the agent the correct wording and the evidence for it, such as a later decision. The agent submits a proposal, a suggested edit that the Mind checks against its rules. Your Mind’s settings determine which permitted corrections are saved immediately and which are held for an authorised person to review. By default, a correction is saved without a person only when an automatic check passes and your trust level and the area’s own limit allow it. Areas that hold governed material, such as decisions, typically hold members’ corrections for the owner, and a whole-file replacement that does not carry the record’s current revision is always held.

Use this guide when the saved source needs changing. If you are unsure where an answer came from, first ask the agent to show its source. For more background, read what memory is and how it works.

Held, approved, and the next read gets it

TheoCOOChatGPTProposed
KaiEngineerCursorReadSaturday 9am to 1pm
Your Minddecisions/support-hours.mdCurrentHeldNow current
− Weekends: closed+ Saturday: 9am to 1pm
Held for reviewApproved by Sam, owner

Before you start

Connect your agent to the intended Mind and use your own account. You need permission to read the record and suggest changes in its area. An area is a group of related records with access rules; being able to read it does not automatically let you change it.

Have the reason for the correction ready. If you are practising, use a clearly fictional note in an area the owner has set aside for testing.

Read the current record

Ask your agent to open the source and identify the statement that needs changing. Check whether a later decision already replaces it. A record described as superseded has been replaced by newer guidance and should not be treated as today's instruction.

For a fictional practice example, a demonstration note might say “Use the blue folder”, while your new instruction says “Use the green folder”. The correction should update that note and preserve the surrounding text.

Suggest one precise correction

  1. Name the record, the old wording, the new wording and the evidence.
  2. Ask your agent to check the proposed edit against the Mind's rules, then submit it once.
  3. Ask it to keep the proposal identifier, the reference used to check that same request later.

Example prompt: “Correct this statement using the source I supplied. Preserve the surrounding record. Tell me whether the change was saved or is waiting for review, then open the current record so I can check it.”

Check what happened

If the change is held, it is waiting for review and the saved record has not changed yet. Open the request in Inbox, the Portal's list of work needing a decision. The Portal is your Mind's web interface. Have someone with permission to approve this kind of edit inspect the exact change.

If the change is applied, it has been saved under the Mind's rules. After either immediate application or a reviewer's approval, ask the agent to open the record again. Check that the intended wording appears in the current source.

If the proposal was rejected, understand the reason before preparing another one. If somebody changed the record while you were working, reread it and reconcile the newer wording first.

Check what happened to the proposal

Submission is a request. The resulting state tells you whether the saved record changed.

Read the source and propose one precise correction with its evidence. Your Mind’s settings determine which permitted corrections are saved immediately and which wait for an authorised reviewer. If the change is applied, open the saved record and check the new wording. While a change is held for review, the saved record has not changed. A request can also be rejected; read the reason before deciding what to correct. Review can approve or reject a held change. Check the resulting state and saved record before reporting that the correction landed or submitting it again.

If the connection stops

Ask your agent to check the original proposal and current source before retrying. An unanswered request may already have succeeded. Repeating it without checking can create a second proposal.

Related

How Mensara memory works · Ask your first question · Review changes and check what was saved · Ask what is current, then ask why

Practical guides for people and agents

Start with one useful job

Join the waitlist

Plain text for AI agents. Same content as the human page.

## For agents

- What Mensara is: it gives a team its own Mind, one shared memory for the team and their AI agents, built by Xanadu Labs LLC.
- Status: signup is not open. A person joins the waitlist at https://www.mensara.ai/#waitlist. Agents cannot create an account or sign up.
- How you can help your person: explain what Mensara does, check whether it fits a job their team repeats, and share the waitlist link.
- Agent references: https://www.mensara.ai/llms.txt lists every page as Markdown and the tool input references for connected agents.

---

# Correct saved information in your Mind

Content updated 29 October 2026.

Guides · Set safe boundaries · [How it works](https://www.mensara.ai/how-it-works)

Mensara memory is the information your team saves in its Mind for later use: decisions, notes and ways of working. If one of those records is wrong or out of date, you can ask your connected agent to suggest a correction. This guide shows you how to check that the right information actually changed.

[Page as Markdown](https://www.mensara.ai/how-it-works/suggest-a-correction.md)

[Operating procedure](https://www.mensara.ai/how-it-works/correct-memory-procedure)

## How a correction works

A record is a saved piece of information in your Mind. Your agent reads records to answer questions, so correcting the underlying record helps the next answer start from better information. Editing a sentence in the chat alone does not show that the saved record changed.

You give the agent the correct wording and the evidence for it, such as a later decision. The agent submits a **proposal**, a suggested edit that the Mind checks against its rules. [Your Mind’s settings](https://www.mensara.ai/how-it-works/mind-settings#why-changes-wait-for-review) determine which permitted corrections are saved immediately and which are held for an authorised person to review. By default, a correction is saved without a person only when an automatic check passes and your trust level and the area’s own limit allow it. Areas that hold governed material, such as decisions, typically hold members’ corrections for the owner, and a whole-file replacement that does not carry the record’s current revision is always held.

Use this guide when the saved source needs changing. If you are unsure where an answer came from, first ask the agent to show its source. For more background, read [what memory is and how it works](https://www.mensara.ai/how-it-works/memory).

## Before you start

Connect your agent to the intended Mind and use your own account. You need permission to read the record and suggest changes in its area. An area is a group of related records with access rules; being able to read it does not automatically let you change it.

Have the reason for the correction ready. If you are practising, use a clearly fictional note in an area the owner has set aside for testing.

## Read the current record

Ask your agent to open the source and identify the statement that needs changing. Check whether a later decision already replaces it. A record described as **superseded** has been replaced by newer guidance and should not be treated as today's instruction.

For a fictional practice example, a demonstration note might say “Use the blue folder”, while your new instruction says “Use the green folder”. The correction should update that note and preserve the surrounding text.

## Suggest one precise correction

1. Name the record, the old wording, the new wording and the evidence.
2. Ask your agent to check the proposed edit against the Mind's rules, then submit it once.
3. Ask it to keep the proposal identifier, the reference used to check that same request later.

Example prompt: “Correct this statement using the source I supplied. Preserve the surrounding record. Tell me whether the change was saved or is waiting for review, then open the current record so I can check it.”

## Check what happened

If the change is **held**, it is waiting for review and the saved record has not changed yet. Open the request in **Inbox**, the Portal's list of work needing a decision. The Portal is your Mind's web interface. Have someone with permission to approve this kind of edit inspect the exact change.

If the change is **applied**, it has been saved under the Mind's rules. After either immediate application or a reviewer's approval, ask the agent to open the record again. Check that the intended wording appears in the current source.

If the proposal was rejected, understand the reason before preparing another one. If somebody changed the record while you were working, reread it and reconcile the newer wording first.

### Check what happened to the proposal

Submission is a request. The resulting state tells you whether the saved record changed.

Read the source and propose one precise correction with its evidence. Your Mind’s settings determine which permitted corrections are saved immediately and which wait for an authorised reviewer. If the change is applied, open the saved record and check the new wording. While a change is held for review, the saved record has not changed. A request can also be rejected; read the reason before deciding what to correct. Review can approve or reject a held change. Check the resulting state and saved record before reporting that the correction landed or submitting it again.

## If the connection stops

Ask your agent to check the original proposal and current source before retrying. An unanswered request may already have succeeded. Repeating it without checking can create a second proposal.

## Related

- [How Mensara memory works](https://www.mensara.ai/how-it-works/memory)
- [Ask your first question](https://www.mensara.ai/how-it-works/first-useful-question)
- [Review changes and check what was saved](https://www.mensara.ai/how-it-works/changes-approvals-receipts)
- [Ask what is current, then ask why](https://www.mensara.ai/how-it-works/current-and-evidence)

Previous page: [Decide where your information may go](https://www.mensara.ai/how-it-works/ownership-data-flow)

Next page: [Invite a teammate to your Mind](https://www.mensara.ai/how-it-works/invite-a-teammate)

A Mensara Mind holds your team's shared information and work.

[Join the waitlist](https://www.mensara.ai/?guide_attribution=eyJfcmFpbHMiOnsiZGF0YSI6eyJvcmlnaW5fcGF0aCI6Ii9ob3ctaXQtd29ya3Mvc3VnZ2VzdC1hLWNvcnJlY3Rpb24iLCJjdGFfaWQiOiJtYXJrZG93biIsImNvbnRlbnRfcmV2aXNpb24iOiI1NGJlNjNlNzg2YjQ1MTI3In0sInB1ciI6Imd1aWRlLWNsaWNrIn19--59d01275899d6acdb0f828001fca9036471f4baa#waitlist)