{
  "ok": true,
  "data": {
    "entry": {
      "id": "glossary-before-demo",
      "kind": "tip",
      "kindLabel": "Tip",
      "title": "Put the glossary before the demo",
      "body": "A live demo creates cognitive load. Do the vocabulary work first so readers can spend the demo watching the model behavior instead of decoding the guide's words.",
      "tag": "dictionary",
      "date": "2026 · 06 · 28",
      "publishedAt": "2026-06-28",
      "note": null,
      "insight": {
        "aha": "The demo is where readers should watch behavior, not decode vocabulary under pressure.",
        "tryThis": "List the walkthrough glossary before the first live output and link each term to Dictionary when a public definition exists.",
        "watchFor": [
          "Cognitive overload from new terms during the demo",
          "Guide-specific jargon that has no shared reference",
          "Terms explained differently in slides, notes, and discussion"
        ]
      },
      "extended": [
        "Before a retrieval demo, define retrieval, relevance, chunk, contradiction, and receipt. Before a tool demo, define dry run, target id, protected action, and rollback.",
        "The definitions do not need to be long. They need to be visible and shared.",
        "This is where a Dictionary link does real work. It gives the group a stable reference outside the slide, the notebook entry, and the guide's memory."
      ],
      "url": "https://tips.platphormnews.com/entries/glossary-before-demo"
    }
  }
}