{
  "example_kind": "invented job and manual worksheet",
  "slug": "decision-owner-unavailable",
  "title": "Keep an approval moving when the decision owner is away",
  "layout": "decision",
  "story": "When the approver is unavailable, I want to identify a valid decision route so the team can move without inventing authority.",
  "problem": "Release review falls during Ada’s leave. Ben can approve only a rollback-ready patch under the recorded delegation. The packet has no rollback demonstration.",
  "symptoms": [
    "A task owner is assumed to inherit approval authority.",
    "The substitute is named without the delegation’s conditions.",
    "Pressure to keep moving hides the evidence still required."
  ],
  "failed_workaround": "Assigning the task to whoever is online does not extend their decision authority or make the missing proof appear.",
  "before": "Ada is away. Ben is now the owner, so we can approve the release.",
  "after": "Approval route: Ben may review the rollback-ready patch within the recorded delegation. Rollback proof is still missing, so approval remains open. The patch owner must provide the agreed demonstration. The broader rollout waits for Ada or another expressly authorized route; reassignment alone does not approve it.",
  "success_check": "The coordinator can state who may decide what, which proof is needed and which work remains outside the substitute’s scope.",
  "choices": [
    [
      "A substitute is authorized within limits",
      "Prepare the in-scope packet",
      "The limits travel with the request."
    ],
    [
      "Required proof is missing",
      "Keep approval open and assign proof work",
      "An available approver does not waive the requirement."
    ],
    [
      "No valid substitute exists",
      "Agree a revised decision route or checkpoint",
      "Task reassignment is not an authority workaround."
    ]
  ],
  "route": [
    {
      "label": "Keep preparation owned",
      "capability": "task-record",
      "action": "Assign the missing proof preparation to its delivery owner.",
      "human_check": "Assignment does not confer approval authority."
    },
    {
      "label": "Record the decision route",
      "capability": "task-comment",
      "action": "Name the substitute, permitted scope and required evidence in the task context.",
      "human_check": "Verify the actual delegation outside this worksheet."
    },
    {
      "label": "Report the approval state",
      "capability": "daily-report",
      "action": "State that approval is waiting for rollback proof, not simply for any available person.",
      "human_check": "The authorized approver supplies the verdict."
    }
  ],
  "editor": {
    "heading": "Prepare a decision request",
    "fields": [
      {
        "key": "scope",
        "label": "Decision scope",
        "example": "Rollback-ready patch only",
        "help": "Retain the actual authorized boundary."
      },
      {
        "key": "approver",
        "label": "Permitted decision owner",
        "example": "Ben under the recorded delegation",
        "help": "Use a verified route, not an available name."
      },
      {
        "key": "missing",
        "label": "Missing evidence",
        "example": "Patch-specific rollback demonstration",
        "help": "Name the prerequisite for a verdict."
      },
      {
        "key": "owner",
        "label": "Preparation owner",
        "example": "Patch owner",
        "help": "Keep delivery and approval separate."
      },
      {
        "key": "next",
        "label": "Next check",
        "example": "Review proof before requesting the patch verdict",
        "help": "State the actionable checkpoint."
      }
    ],
    "template": "Approval packet\nScope: {scope}.\nDecision route: {approver}.\nStill required: {missing}.\nPreparation owner: {owner}.\nNext check: {next}.\nAnything outside the recorded route remains undecided."
  },
  "limitations": "The delegation and release scenario are fictional. The worksheet does not grant authority or implement native approval enforcement.",
  "tasks": [
    [
      "Confirm the delegation boundary",
      "Coordinator",
      "The allowed patch class, substitute and proof requirement are recorded."
    ],
    [
      "Prepare the missing proof",
      "Patch owner",
      "The rollback demonstration addresses this patch and can be inspected."
    ],
    [
      "Request the bounded verdict",
      "Release coordinator",
      "The substitute accepts, holds or declines only the authorized scope."
    ]
  ],
  "faqs": [
    [
      "Can a reassigned owner approve the outcome?",
      "Only if the actual decision process grants that authority. Delivery assignment and approval are different responsibilities."
    ],
    [
      "What if no substitute is authorized?",
      "Keep the decision open, explain the impact and agree a revised checkpoint; do not invent a delegation."
    ],
    [
      "Does TeamBoost enforce this delegation?",
      "No enforcement is established here. Use documented assignment and task-note workflows to record the route, while the real authorization and approval remain separate."
    ]
  ]
}