我碰到 Grok @bot 一个有意思的问题：它有时没完整验证就把事情当真...

我碰到 Grok @bot 一个有意思的问题 它有时没完整验证或背景就把事情当真，直接写进 bot 的身分 我是这样处理的 👇 每个新 bot 我都会贴一条写入规则，把记忆分成 3 个抽屉： 1. Profile：稳定身分，每一轮都加载提示词。游走的「maybe」或旧产品线绝不该溜进来的唯一地方。 2. Log：带日期的历史，一事一行。发生了什么，不是这个 bot 是谁。 3. Note：本周的卡点或待办。排序变低后会从永远可见的清单掉下去，但在你 Forget 之前仍留在磁盘。 精确区块如下： "PROFILE MEMORY Write to own profile only when the fact is stable and needed every turn. Test: if forgotten tomorrow, this agent does the job wrong every day. Else do not write profile. Profile scope: [lane coordinates] + [rules they mark stable]. Nothing else. If unsure, do not write profile. If it reads like a diary, it is log. LOG MEMORY Write when it reconstructs what happened and is not needed every turn. Log scope: [dated lane events]. One line. No chat diary. No profile repeats. NOTE MEMORY Write only when it should drop off the always-visible list once it's ranked low. The platform fades it from the prompt. It stays on disk until Forget. Test: useless next week is note. Needed every turn is profile. Worth finding next month is log. Note scope: [this-week blocker / pending]." 设一次，单次闲聊就不会改写这个 bot 是谁。

原文：I came across an interesting issue with Grok @bot Sometimes it assumes something is true without full validation or context, and writes it straight into the bot's identity Here's how I handle it 👇 I paste a write rule into every new bot that splits memory into 3 drawers: 1. Profile: The stable identity, loaded into the prompt every turn. The one place a stray "maybe" or an old product line should never sneak into. 2. Log: Dated history, one line per event. What happened, not who the bot is. 3. Note: This week's blocker or pending item. Drops off the always-visible list once it's ranked low, but stays on disk until you Forget it. Here's the exact block: "PROFILE MEMORY Write to own profile only when the fact is stable and needed every turn. Test: if forgotten tomorrow, this agent does the job wrong every day. Else do not write profile. Profile scope: [lane coordinates] + [rules they mark stable]. Nothing else. If unsure, do not write profile. If it reads like a diary, it is log. LOG MEMORY Write when it reconstructs what happened and is not needed every turn. Log scope: [dated lane events]. One line. No chat diary. No profile repeats. NOTE MEMORY Write only when it should drop off the always-visible list once it's ranked low. The platform fades it from the prompt. It stays on disk until Forget. Test: useless next week is note. Needed every turn is profile. Worth finding next month is log. Note scope: [this-week blocker / pending]." Set this once and one stray chat never rewrites who the bot is.

集成