{
  "schema": "tce-cookbook-canvas-presentation-v1",
  "title": "A clearer workshop handover",
  "sourceFile": "final-investigation.json",
  "sourceSha256": "3a7a301bfaf124d35720fe76f0bc22f98f8d507bd37e58295670e084325860c1",
  "authorship": "Codex-authored layout and relationships added for cookbook presentation after the recorded investigation. No model generation or investigation rerun.",
  "preserved": "Exactly the three original node IDs and every original node field except x/y. The original run, package, investigation and captures are unchanged.",
  "semantics": "The forward-flow connection expresses how the question informs the candidate. The association expresses contextual qualification or a design limit; it is not an executable second input or proof of evidence.",
  "nodeCount": 3,
  "relationshipCount": 2,
  "providerCalls": 0,
  "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": 0,
        "y": 0,
        "sourceId": null,
        "documentId": null,
        "attribution": "",
        "rights": "",
        "origin": "human",
        "evidenceStatus": "unassessed",
        "contentRevision": 1
      },
      {
        "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": 620,
        "y": 0,
        "sourceId": null,
        "documentId": null,
        "attribution": "",
        "rights": "",
        "origin": "human",
        "evidenceStatus": "unassessed",
        "contentRevision": 1
      },
      {
        "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": 310,
        "y": 350,
        "sourceId": null,
        "documentId": null,
        "attribution": "",
        "rights": "",
        "origin": "human",
        "evidenceStatus": "unassessed",
        "contentRevision": 1
      }
    ],
    "edges": [
      {
        "id": "presentation-handover-question-scope",
        "from": "handover-question",
        "to": "handover-concept",
        "channel": "flow",
        "relation": "informs",
        "rationale": "The question makes current owner, next action and unresolved issues the scope of the proposed single-device handover log.",
        "origin": "agent",
        "assessment": "unassessed",
        "fromPort": "out",
        "toPort": "in",
        "fromSide": "bottom",
        "toSide": "top",
        "executable": false,
        "weight": 2,
        "revision": 1,
        "metadata": {
          "purpose": "cookbook-presentation",
          "author": "Codex presentation editor",
          "generatedByRecordedRun": false
        }
      },
      {
        "id": "presentation-sample-handover-constraint",
        "from": "sample-handover",
        "to": "handover-concept",
        "channel": "association",
        "relation": "qualifies",
        "rationale": "The three synthetic notes expose ownership and closure ambiguity and therefore qualify which fields and review states the candidate needs. They do not establish real demand or performance.",
        "origin": "agent",
        "assessment": "unassessed",
        "fromPort": "out",
        "toPort": "in",
        "fromSide": "bottom",
        "toSide": "top",
        "executable": false,
        "weight": 2,
        "revision": 1,
        "metadata": {
          "purpose": "cookbook-presentation",
          "author": "Codex presentation editor",
          "generatedByRecordedRun": false
        }
      }
    ],
    "contractVersion": 2,
    "viewport": {
      "x": 210,
      "y": 170,
      "zoom": 1
    }
  }
}