{
  "payload": {
    "schema_version": 1,
    "case_id": "SC-5096e3463d284a72928204fe5e46769f",
    "kind": "sanitised-teaching-case",
    "title": "Explain what a capability changes for its user",
    "audience_role": "Product and communication leads reviewing a value proposition",
    "meaning": {
      "communication_job": "Connect a product capability to a useful job.",
      "audience_question": "Why should the audience care what this capability does?",
      "point": "A capability becomes meaningful when its mechanism and intended user benefit are explicit.",
      "reasoning_relation": "One capability maps to one qualified purpose; the mechanism supports the connection.",
      "reader_before": "The reader can repeat a feature list but cannot explain the practical reason to use it.",
      "reader_after": "The reader can connect each feature to a task it may help and identify what proof is still needed.",
      "intended_contribution": "Expose missing value explanations without upgrading proposed benefits into measured outcomes.",
      "required_evidence": [
        "An accurate product capability or a clearly fictional specification.",
        "A plausible mechanism linking that capability to a user task.",
        "Evidence for any claim about actual time, cost or performance gains."
      ],
      "invariants": [
        "Keep every capability paired with its own purpose.",
        "Make the mechanism explicit rather than relying on a benefit adjective.",
        "Label outcomes as intended until tested."
      ],
      "poor_fits": [
        "Benefits that require capabilities the product does not have.",
        "Many-to-many causal dependencies flattened into pairs.",
        "Invented user quotations presented as research."
      ]
    },
    "narrative": {
      "before": "Inspect a real communication specimen and identify what the feature description leaves unexplained.",
      "after": "Demonstrate the most important mechanism and define a test for its intended benefit.",
      "illustrative_flow": [
        "Specimen",
        "Capability-to-purpose map",
        "Mechanism demonstration",
        "Evidence or test"
      ],
      "conditional_branch": "If one feature serves several different jobs, split the case by audience or use a matrix with explicit many-to-many links."
    },
    "layout": {
      "code": "S41",
      "option": "capability-to-purpose",
      "relationship": "existing-arrangement",
      "basis": "Matched-pair family with coupled, detail-bearing rows, informed by the glossary option; quotation styling removed.",
      "editable_pptx": "unverified"
    },
    "slots": [
      {
        "name": "eyebrow",
        "purpose": "Identify this as fictional teaching material.",
        "member_count": 1
      },
      {
        "name": "headline",
        "purpose": "State the communication point and its relevance.",
        "member_count": 1
      },
      {
        "name": "closing",
        "purpose": "Land the implication or prepare the next unit.",
        "member_count": 1
      },
      {
        "name": "qualification",
        "purpose": "Keep evidence status and material limitations visible.",
        "member_count": 1
      },
      {
        "name": "pairs",
        "purpose": "Keep each capability with its intended purpose and supporting mechanism.",
        "member_count": 3
      }
    ],
    "worked_example": {
      "fictional": true,
      "scenario": "A fictional shared-kitchen booking service is explaining three proposed features to community organisers.",
      "decision": "Choose one user task for the next product demonstration and test whether its proposed support works.",
      "slot_fills": [
        {
          "slot": "eyebrow",
          "units": [
            {
              "label": "Status",
              "fields": [
                {
                  "label": "text",
                  "text": "Fictional teaching example / Capability to purpose"
                }
              ]
            }
          ]
        },
        {
          "slot": "headline",
          "units": [
            {
              "label": "Point",
              "fields": [
                {
                  "label": "text",
                  "text": "A feature matters when it helps someone act."
                }
              ]
            }
          ]
        },
        {
          "slot": "closing",
          "units": [
            {
              "label": "Next",
              "fields": [
                {
                  "label": "text",
                  "text": "Choose one mechanism to demonstrate and test."
                }
              ]
            }
          ]
        },
        {
          "slot": "qualification",
          "units": [
            {
              "label": "Limits",
              "fields": [
                {
                  "label": "text",
                  "text": "Fictional teaching scenario, not observed results or an approved operating plan. Benefits are proposed. No measured reduction in travel, mistakes or missed tasks. Mechanism explanations must remain accessible in any final visual adaptation."
                }
              ]
            }
          ]
        },
        {
          "slot": "pairs",
          "units": [
            {
              "label": "Live availability",
              "fields": [
                {
                  "label": "capability",
                  "text": "Display current kitchen availability."
                },
                {
                  "label": "purpose",
                  "text": "Know before travelling."
                },
                {
                  "label": "mechanism",
                  "text": "Current availability lets an organiser check whether a slot is open before leaving."
                }
              ]
            },
            {
              "label": "Shared checklist",
              "fields": [
                {
                  "label": "capability",
                  "text": "Keep one preparation checklist."
                },
                {
                  "label": "purpose",
                  "text": "Spot unfinished preparation."
                },
                {
                  "label": "mechanism",
                  "text": "One shared checklist makes uncompleted tasks visible to the whole organising team."
                }
              ]
            },
            {
              "label": "Role reminders",
              "fields": [
                {
                  "label": "capability",
                  "text": "Send reminders to assigned roles."
                },
                {
                  "label": "purpose",
                  "text": "Reach the responsible person."
                },
                {
                  "label": "mechanism",
                  "text": "A role-specific reminder directs a task to its designated owner instead of the entire group."
                }
              ]
            }
          ]
        }
      ],
      "why_it_works": "The matched pairs identify why each capability matters, while the mechanism fields stop an attractive benefit label from substituting for reasoning.",
      "qualification": "Fictional teaching scenario, not observed results or an approved operating plan. Benefits are proposed. No measured reduction in travel, mistakes or missed tasks. Mechanism explanations must remain accessible in any final visual adaptation."
    },
    "sanitisation": {
      "method": "semantic-abstraction-and-fictional-reconstruction",
      "replaced": [
        "Organisation, people, sector, setting and activities independently reconstructed.",
        "No original names, quotations, figures, dates, screenshots, logos, native notes or links retained.",
        "No persistent client aliases or proportional price transformations used."
      ],
      "preserved": [
        "Keep every capability paired with its own purpose.",
        "Make the mechanism explicit rather than relying on a benefit adjective.",
        "Label outcomes as intended until tested."
      ],
      "losses": [
        "The source specimen and analyst overlays are replaced by a fictional matched-pair explanation.",
        "A pair list is more compact but cannot replace the original specimen as evidence of an actual communication defect."
      ],
      "residual_risk": "Local review found no retained identifying combination in this independently authored example. A generic reasoning relationship may recur elsewhere; this is not formal anonymity or publication clearance.",
      "linkage_boundary": "restricted-bridge-outside-reuse-package"
    }
  },
  "reviews": {
    "privacy": {
      "status": "reviewed",
      "reviewer": "Tessel / production adaptation review",
      "date": "2026-10-14",
      "basis": [
        "Reviewed the complete independently fictional payload and its combinations. No client assets, identifiers, source paths, source hashes or correspondence included.",
        "Adapted copy and new-count scenario reviewed; no claim of formal anonymity."
      ],
      "payload_sha256": "bdba0da222443007b65b8df284b21f1ae4e951856dcaf6a01be8bc2c72dc3fd7"
    },
    "semantic": {
      "status": "reviewed",
      "reviewer": "Tessel / production adaptation review",
      "date": "2026-10-14",
      "basis": [
        "Compared the adaptation with the reviewed fictional preparation: audience change, reasoning, conditions, evidence status and neighbouring dependencies preserved.",
        "Reviewed the exact slot fills and count; separate render and interaction evidence is recorded in batch-02-review.json. Intended contribution is not measured persuasion."
      ],
      "payload_sha256": "bdba0da222443007b65b8df284b21f1ae4e951856dcaf6a01be8bc2c72dc3fd7"
    }
  }
}