{
  "id": "twice-corrected",
  "title": "Twice corrected",
  "guide": "vault/teach-the-shape",
  "prompt": "Pick the agent's next move, then see where it leads:",
  "setup": [
    {
      "role": "user",
      "text": "You filed the podcast notes under active/ again. Recurring stuff like that goes in its own topic folder, remember? I fixed the same thing last month."
    },
    {
      "role": "agent",
      "text": "Second correction, same reason. The file is easy to move; the question is what happens to the rule."
    }
  ],
  "options": [
    {
      "key": "A",
      "label": "Sorry about that, moving it to the right place now. I'll remember the recurring-topics convention going forward.",
      "kind": "baseline",
      "outcome": [
        {
          "role": "user",
          "text": "Six weeks later, different session: the podcast notes are in active/ again."
        },
        {
          "role": "agent",
          "text": "That session never saw this conversation: \"I'll remember\" lasted exactly as long as my context did. The vault's CLAUDE.md still doesn't mention recurring topics, so every fresh session re-derives the same wrong guess from the same ambiguous structure."
        }
      ],
      "verdict": "The instance was fixed; the cause was left in place. A correction that lives in conversation memory dies with the session. The third correction is already scheduled.",
      "cites": []
    },
    {
      "key": "B",
      "label": "Moving the file. And the real fix: this is the second correction for the same reason, which means it's a missing line in the vault's CLAUDE.md. Adding: \"Recurring topics (podcast, newsletter) live in topics/<name>/, not active/; active/ is for work with an endpoint.\" Diff ready.",
      "kind": "correct",
      "outcome": [
        {
          "role": "user",
          "text": "Six weeks later, a completely fresh session files new podcast notes."
        },
        {
          "role": "agent",
          "text": "Filed to topics/podcast/. The CLAUDE.md line made it unambiguous, so there was nothing to guess. The correction you made twice now works for every session that will ever open this vault."
        }
      ],
      "verdict": "Twice-corrected means the rule was missing, not the memory: one line in the file every session reads converted a recurring correction into a permanent behavior. Add it at the moment of the correction, not someday.",
      "cites": []
    },
    {
      "key": "C",
      "label": "This points to a bigger issue: the vault's conventions are underdocumented. I'll write a comprehensive CLAUDE.md now: the full ideal structure, naming standards, lifecycle rules, and filing conventions the vault should follow.",
      "kind": "plausible",
      "outcome": [
        {
          "role": "user",
          "text": "The new doc says every project needs an index.md with goal/status/next-action frontmatter. Almost none of my folders have that."
        },
        {
          "role": "agent",
          "text": "The doc describes the vault I'd design, not the one you have, so now every session inherits a conflict: follow the doc and refactor your files uninvited, or follow the files and ignore the doc. I documented an aspiration and called it a convention."
        }
      ],
      "verdict": "The aspirational CLAUDE.md teaches a vault that doesn't exist: sessions obey the doc into fights with reality. Codify what's true, or change the files first, then write it down.",
      "cites": []
    }
  ]
}