{
  "example_kind": "invented job and manual worksheet",
  "slug": "follow-the-sun-handoff",
  "title": "Leave the next shift a handoff they can act on without waking you",
  "layout": "handover",
  "story": "When the next owner starts after I log off, I want a usable action boundary so they can progress without guessing or waiting for a meeting.",
  "problem": "Lagos finishes an export check after the receiving team’s workday. Two rows have wrong category labels; the export must not be resent before correction is reviewed.",
  "symptoms": [
    "The receiver gets context but no permitted next action.",
    "A late handoff depends on asking the sender what they meant.",
    "The receiver resends the file instead of correcting the known exceptions."
  ],
  "failed_workaround": "Adding more history to the handoff can still leave the next action and its limits missing.",
  "before": "Export checked. Please take over; details in the thread.",
  "after": "Next-shift brief: use the approved export version and inspect the two marked category rows. Correct labels only; do not resend the export. Return the corrected sample for receiving review, and record any exception that prevents that action. The receiving owner acknowledges the boundary at the start of their shift.",
  "success_check": "The incoming owner can name the version, permitted action and return evidence without asking the outgoing person for the missing instruction.",
  "choices": [
    [
      "The action and boundary are clear",
      "Proceed with the agreed correction",
      "The receiver need not invent scope."
    ],
    [
      "The artifact is inaccessible or ambiguous",
      "Return the specific handoff gap",
      "More background text does not fix access or version uncertainty."
    ],
    [
      "An unplanned exception appears",
      "Record it and seek the appropriate decision",
      "Do not widen permission to keep the shift busy."
    ]
  ],
  "route": [
    {
      "label": "Make the next work owned",
      "capability": "task-record",
      "action": "Identify the receiving correction task and incoming owner.",
      "human_check": "Responsibility is agreed rather than inferred from time-zone coverage."
    },
    {
      "label": "Write the runnable handoff",
      "capability": "task-comment",
      "action": "Name the approved artifact, marked rows, permitted action and prohibited resend.",
      "human_check": "The receiver confirms access and the governing version."
    },
    {
      "label": "Report the return result",
      "capability": "daily-report",
      "action": "Record the corrected sample or the actual blocking exception.",
      "human_check": "A human receiving review decides whether the correction is accepted."
    }
  ],
  "editor": {
    "heading": "Prepare a receiving brief",
    "fields": [
      {
        "key": "artifact",
        "label": "Governing artifact",
        "example": "Approved export version with two marked category rows",
        "help": "Use a version the receiver can access."
      },
      {
        "key": "action",
        "label": "Permitted next action",
        "example": "Correct the marked category labels",
        "help": "Make progress concrete."
      },
      {
        "key": "boundary",
        "label": "Do-not-cross boundary",
        "example": "Do not resend the export before review",
        "help": "State what is not authorized."
      },
      {
        "key": "return",
        "label": "Return evidence",
        "example": "Corrected sample for receiving review",
        "help": "Define what the next owner hands back."
      },
      {
        "key": "ack",
        "label": "Acknowledgment checkpoint",
        "example": "Incoming owner confirms the boundary at shift start",
        "help": "Agree when the receiver establishes understanding."
      }
    ],
    "template": "Next-shift handoff\nUse: {artifact}.\nNext action: {action}.\nBoundary: {boundary}.\nReturn: {return}.\nAcknowledge: {ack}.\nIf the action cannot proceed, record the exact exception instead of guessing."
  },
  "limitations": "The example does not configure shift schedules, automated handoffs or universal file access. Actual ownership and receiving routes need agreement.",
  "tasks": [
    [
      "Identify the governing handoff version",
      "Outgoing owner",
      "The approved file and marked exceptions are accessible to the receiver."
    ],
    [
      "State the next permitted action",
      "Coordinator",
      "Correct category labels is distinguished from resending the export."
    ],
    [
      "Receive the return evidence",
      "Incoming owner",
      "The corrected sample or a specific blocking exception is recorded after acknowledgment."
    ]
  ],
  "faqs": [
    [
      "Do we need a live overlap meeting?",
      "Sometimes, but first make the known action and boundary usable without one."
    ],
    [
      "Should the receiver simply mark the handoff done?",
      "Only after the agreed receiving action and evidence are completed; acknowledgment alone is not correction."
    ],
    [
      "How does TeamBoost support this?",
      "Keep the task owner, handoff context and dated work update together in the documented workflows. This does not promise native shift scheduling, time-zone automation or automatic acknowledgment."
    ]
  ]
}