{
  "schema": "tce-cookbook-investigation-v1",
  "title": "A clearer workshop handover",
  "scenario": "fictional teaching example",
  "nodeCount": 3,
  "data": {
    "question": "Can three cards turn an ambiguous handover into a useful, testable software brief?",
    "nodes": [
      {
        "id": "handover-question",
        "kind": "question",
        "title": "What should the next shift know?",
        "body": "Design the smallest useful maintenance handover log for a small workshop with two shifts. The next shift should see an open issue, its current owner and the next action. Investigate whether a software prototype is justified, and define a testable first version. This is a fictional teaching case, not a claim about real workshop performance.",
        "captureTrigger": "",
        "captureReason": "",
        "url": "",
        "tags": [],
        "x": 40,
        "y": 120,
        "sourceId": null,
        "documentId": null,
        "attribution": "",
        "rights": "",
        "origin": "human",
        "evidenceStatus": "unassessed"
      },
      {
        "id": "sample-handover",
        "kind": "observation",
        "title": "Three sample handover notes",
        "body": "SYNTHETIC INPUTS FOR THIS RECIPE, not field research. Mon AM: Lathe L2 coolant drip; Alex inspected; absorbent pad placed; Sam to inspect hose next shift; status open. Mon PM: Drill D1 chuck wobble; Morgan checked; use paused pending supervisor review; Priya owns follow-up; status open. Tue AM: Lathe L2 hose replaced by Sam; supervisor still needs to review closure; status awaiting review. The sample illustrates ownership, status and next-action ambiguity; it cannot establish demand, time savings or safety.",
        "captureTrigger": "",
        "captureReason": "",
        "url": "",
        "tags": [],
        "x": 400,
        "y": 40,
        "sourceId": null,
        "documentId": null,
        "attribution": "",
        "rights": "",
        "origin": "human",
        "evidenceStatus": "unassessed"
      },
      {
        "id": "handover-concept",
        "kind": "idea",
        "title": "A single-device handover log",
        "body": "Candidate: a local browser prototype on one shared workshop tablet. Capture equipment label, issue, owner, next action, status and timestamp; show unresolved items first; acknowledge handover; export JSON and readable CSV for backup. One device and one workshop only. No machine control, safety sign-off, fault diagnosis, accounts, cloud sync, notifications, AI features or integrations. A supervisor makes all operational decisions outside the app. All entries are synthetic until a supervised pilot. Evaluate against a structured paper checklist before committing to software.",
        "captureTrigger": "",
        "captureReason": "",
        "url": "",
        "tags": [],
        "x": 760,
        "y": 120,
        "sourceId": null,
        "documentId": null,
        "attribution": "",
        "rights": "",
        "origin": "human",
        "evidenceStatus": "unassessed"
      }
    ],
    "edges": [],
    "contractVersion": 2
  }
}