{
  "ok": true,
  "data": {
    "frames": [
      {
        "id": "shared-terms",
        "eyebrow": "Start here",
        "title": "Name the term before the trick",
        "takeaway": "Model behavior is hard to inspect when the key vocabulary is unstable.",
        "body": "Open with the words that matter: retrieval, receipt, confidence bucket, dry run, abstention, provenance. Once the terms are shared, the demo becomes an evidence exercise instead of a vocabulary scramble.",
        "entryIds": [
          "plain-then-precise",
          "term-first-fieldwork",
          "dictionary-backed-verification"
        ],
        "dictionaryTerm": "retrieval relevance",
        "notesPrompt": "Which word in today's demo felt familiar but turned out to need a stricter definition?",
        "aha": "The glossary is not background material. It is part of the operating system for the work."
      },
      {
        "id": "artifact-first",
        "eyebrow": "Inspection",
        "title": "Put an artifact on screen",
        "takeaway": "The room needs something concrete to inspect: an answer, citation, tool preview, or note.",
        "body": "A good technical walkthrough has a visible object. Point at the fragile claim, irrelevant retrieved chunk, broad selector, or missing receipt before summarizing the system.",
        "entryIds": [
          "artifact-questions",
          "inspect-one-claim",
          "explain-inspect-repair-loop",
          "receipts"
        ],
        "dictionaryTerm": "receipt",
        "notesPrompt": "What exact artifact made you change your mind about the model output?",
        "aha": "Evidence has to be visible before judgment can become repeatable."
      },
      {
        "id": "dry-run-action",
        "eyebrow": "Agents",
        "title": "Preview action before authority",
        "takeaway": "A model that can mutate state needs a dry run, target ids, stop conditions, and verification.",
        "body": "Use a tool-call example where the selector is too broad. Mark what would change, who must approve it, and what proof is needed after the tool runs.",
        "entryIds": [
          "first-safe-agent-plan",
          "public-private-sorting",
          "tool-dry-run",
          "integration-contract-cards"
        ],
        "dictionaryTerm": "dry run",
        "notesPrompt": "What would stop this tool call before it touches real state?",
        "aha": "Permission to explain a tool call is not permission to execute it."
      },
      {
        "id": "abstention-branch",
        "eyebrow": "Reliability",
        "title": "Make stopping a valid answer",
        "takeaway": "Unknown, partial, protected-required, and needs-review states keep bad certainty from becoming product behavior.",
        "body": "Compare two schemas: one that forces every field to be filled, and one that allows useful absence states. Decide which one prevents invented data and why.",
        "entryIds": [
          "readiness-red-yellow-green",
          "abstention-design",
          "schema-first-output"
        ],
        "dictionaryTerm": "abstention",
        "notesPrompt": "Where did the model need an honest stop state instead of a smoother sentence?",
        "aha": "A graceful stop can be the most helpful output in the room."
      },
      {
        "id": "notes-to-glossary",
        "eyebrow": "Capture",
        "title": "Turn repeated confusion into better tools",
        "takeaway": "Repeated confusion is a product signal, not an interruption.",
        "body": "Capture the phrase that caused confusion in Notes. If the phrase repeats, move it into a human-reviewed Dictionary candidate and add a notebook exercise around it.",
        "entryIds": [
          "definition-vs-proof",
          "note-to-definition-pipeline",
          "misconception-map"
        ],
        "dictionaryTerm": "provenance",
        "notesPrompt": "What phrase should become a shared glossary candidate after this walkthrough?",
        "aha": "The field notes are generating the next version of the shared vocabulary."
      },
      {
        "id": "self-quiz-transfer",
        "eyebrow": "Retention",
        "title": "End with recall, artifact, transfer",
        "takeaway": "An insight is useful when it can be named, used on an artifact, and transferred to another workflow.",
        "body": "Close with three questions: what is the concept, where does it appear in this output, and where would you look for the same pattern in a different workflow?",
        "entryIds": [
          "aha-from-mistake",
          "self-quiz-cards",
          "aha-checkpoints"
        ],
        "dictionaryTerm": "prompt fixture",
        "notesPrompt": "Write one transfer question that would catch shallow memorization.",
        "aha": "The final question should prove the habit moved beyond this frame."
      }
    ],
    "frameCount": 6,
    "fullScreenSupported": true,
    "practiceLoop": "Define the term, inspect an artifact, repair the failure, capture the observation, and end with a transfer question."
  }
}