{
  "schemaVersion": 1,
  "name": "Beacon / Q4 planning room",
  "period": "October–December 2026",
  "unit": "person-days",
  "reachWindow": "Eligible fictional workspaces per quarter",
  "teams": [
    {
      "id": "engineering",
      "name": "Engineering"
    },
    {
      "id": "design",
      "name": "Design"
    }
  ],
  "goals": [
    {
      "id": "activation",
      "title": "Get teams to a first useful result",
      "metric": "First-result rate within 7 days",
      "baseline": "Fictional baseline: 38%",
      "target": "Hypothesis: 50% after the pilot",
      "measurement": "Cohort comparison over 4 weeks; exclude internal accounts"
    },
    {
      "id": "trust",
      "title": "Make collaboration dependable",
      "metric": "Successful review and export tasks",
      "baseline": "Fictional usability benchmark: 7/12 successful tasks",
      "target": "Hypothesis: 10/12 tasks in the next usability round",
      "measurement": "Moderated 12-task study; report unique participants and failures"
    }
  ],
  "releases": [
    {
      "id": "now",
      "name": "Now · Foundation",
      "capacity": {
        "engineering": 16,
        "design": 8
      }
    },
    {
      "id": "next",
      "name": "Next · First value",
      "capacity": {
        "engineering": 22,
        "design": 7
      }
    },
    {
      "id": "later",
      "name": "Later · Expansion",
      "capacity": {
        "engineering": 18,
        "design": 5
      }
    }
  ],
  "evidence": [
    {
      "id": "e1",
      "source": "Fictional usability notes / session 01",
      "observation": "Two first-time teams started with an empty board and could not identify the next action."
    },
    {
      "id": "e2",
      "source": "Fictional support review / week 40",
      "observation": "Three export tickets described missing Unicode labels in CSV handoffs."
    },
    {
      "id": "e3",
      "source": "Fictional research / session 03",
      "observation": "A project lead asked for a durable shared review state, rather than another notification."
    },
    {
      "id": "e4",
      "source": "Fictional discovery / session 04",
      "observation": "A specialist needs keyboard navigation and a clear focus indicator on the board."
    },
    {
      "id": "e5",
      "source": "Fictional opportunity note / 05",
      "observation": "Two team leads requested reusable templates; each already has a different workflow."
    },
    {
      "id": "e6",
      "source": "Fictional engineering spike / 06",
      "observation": "An API requires stable permissions and versioned export schemas first."
    },
    {
      "id": "e7",
      "source": "Fictional analytics review / 07",
      "observation": "The activation event name is ambiguous and does not distinguish generated versus saved output."
    },
    {
      "id": "e8",
      "source": "Fictional mobile observation / 08",
      "observation": "Capturing a short note on a phone failed after an interrupted connection."
    }
  ],
  "initiatives": [
    {
      "id": "accessible-foundation",
      "title": "Keyboard-first component foundation",
      "team": "design",
      "owner": "Mara",
      "goalId": "trust",
      "users": "Project leads and contributors in small product teams",
      "problem": "Board interactions lack consistent focus and keyboard behavior.",
      "reach": 500,
      "impact": 1,
      "confidence": 1,
      "effort": 6,
      "dependsOn": [],
      "status": "done",
      "evidenceIds": [
        "e4"
      ],
      "decision": "Create a documented focus and tab-order contract.",
      "nonGoals": [
        "No automatic external publication in this release",
        "No expansion to unvalidated personas"
      ],
      "requirements": [
        {
          "id": "core-flow",
          "priority": "P0",
          "text": "Create a documented focus and tab-order contract.",
          "acceptance": [
            "An explicit keyboard interaction map exists for tabs, lists and dialogs.",
            "Given a keyboard-only session, every primary action is reachable without a trap."
          ]
        },
        {
          "id": "recovery",
          "priority": "P1",
          "text": "Document recovery, ownership and accessibility for this flow.",
          "acceptance": [
            "The handoff identifies an owner and the exact release scope.",
            "Given an unavailable service, the user can preserve their work and understand the next step."
          ]
        }
      ],
      "risks": [
        "Reach and impact are estimates from a fictional discovery set; confirm before committing."
      ],
      "openQuestions": [
        "Who will review the pilot outcome and decide whether to expand?"
      ]
    },
    {
      "id": "starter-templates",
      "title": "Opinionated starter templates",
      "team": "design",
      "owner": "Mara",
      "goalId": "activation",
      "users": "Project leads and contributors in small product teams",
      "problem": "Teams need a useful starting point without a long setup.",
      "reach": 640,
      "impact": 2,
      "confidence": 0.8,
      "effort": 7,
      "dependsOn": [
        "accessible-foundation"
      ],
      "status": "planned",
      "evidenceIds": [
        "e1",
        "e5"
      ],
      "decision": "Provide three editable starting workflows and explain who each is for.",
      "nonGoals": [
        "No automatic external publication in this release",
        "No expansion to unvalidated personas"
      ],
      "requirements": [
        {
          "id": "core-flow",
          "priority": "P0",
          "text": "Provide three editable starting workflows and explain who each is for.",
          "acceptance": [
            "Templates preserve original content and support an empty-start option.",
            "Given an existing workspace, applying a template creates a separate draft rather than overwriting it."
          ]
        },
        {
          "id": "recovery",
          "priority": "P1",
          "text": "Document recovery, ownership and accessibility for this flow.",
          "acceptance": [
            "The handoff identifies an owner and the exact release scope.",
            "Given an unavailable service, the user can preserve their work and understand the next step."
          ]
        }
      ],
      "risks": [
        "Reach and impact are estimates from a fictional discovery set; confirm before committing."
      ],
      "openQuestions": [
        "Who will review the pilot outcome and decide whether to expand?"
      ],
      "deadlineRelease": "now"
    },
    {
      "id": "guided-first-run",
      "title": "A guided first useful result",
      "team": "engineering",
      "owner": "Jules",
      "goalId": "activation",
      "users": "Project leads and contributors in small product teams",
      "problem": "New teams do not know how to progress from the first screen.",
      "reach": 620,
      "impact": 2,
      "confidence": 0.8,
      "effort": 12,
      "dependsOn": [
        "starter-templates"
      ],
      "status": "planned",
      "evidenceIds": [
        "e1",
        "e7"
      ],
      "decision": "Guide the user through one complete save-and-share task.",
      "nonGoals": [
        "No automatic external publication in this release",
        "No expansion to unvalidated personas"
      ],
      "requirements": [
        {
          "id": "core-flow",
          "priority": "P0",
          "text": "Guide the user through one complete save-and-share task.",
          "acceptance": [
            "Progress survives a reload and the user can skip or resume.",
            "Given a failed save, the UI retains the draft and offers a retry without duplicating the result."
          ]
        },
        {
          "id": "recovery",
          "priority": "P1",
          "text": "Document recovery, ownership and accessibility for this flow.",
          "acceptance": [
            "The handoff identifies an owner and the exact release scope.",
            "Given an unavailable service, the user can preserve their work and understand the next step."
          ]
        }
      ],
      "risks": [
        "Reach and impact are estimates from a fictional discovery set; confirm before committing."
      ],
      "openQuestions": [
        "Who will review the pilot outcome and decide whether to expand?"
      ],
      "deadlineRelease": "next"
    },
    {
      "id": "export-integrity",
      "title": "Exports that survive the handoff",
      "team": "engineering",
      "owner": "Jules",
      "goalId": "trust",
      "users": "Project leads and contributors in small product teams",
      "problem": "Exported records lose important labels at handoff.",
      "reach": 420,
      "impact": 2,
      "confidence": 1,
      "effort": 8,
      "dependsOn": [],
      "status": "in-progress",
      "evidenceIds": [
        "e2"
      ],
      "decision": "Preserve Unicode text, stable IDs and explicit column semantics.",
      "nonGoals": [
        "No automatic external publication in this release",
        "No expansion to unvalidated personas"
      ],
      "requirements": [
        {
          "id": "core-flow",
          "priority": "P0",
          "text": "Preserve Unicode text, stable IDs and explicit column semantics.",
          "acceptance": [
            "A CSV export re-imports Unicode and quoted delimiters without changes.",
            "Given a formula-looking label, spreadsheet export treats it as text."
          ]
        },
        {
          "id": "recovery",
          "priority": "P1",
          "text": "Document recovery, ownership and accessibility for this flow.",
          "acceptance": [
            "The handoff identifies an owner and the exact release scope.",
            "Given an unavailable service, the user can preserve their work and understand the next step."
          ]
        }
      ],
      "risks": [
        "Reach and impact are estimates from a fictional discovery set; confirm before committing."
      ],
      "openQuestions": [
        "Who will review the pilot outcome and decide whether to expand?"
      ],
      "deadlineRelease": "now"
    },
    {
      "id": "review-room",
      "title": "One shared review room",
      "team": "engineering",
      "owner": "Noor",
      "goalId": "trust",
      "users": "Project leads and contributors in small product teams",
      "problem": "Reviewers cannot tell which saved version a comment refers to.",
      "reach": 310,
      "impact": 2,
      "confidence": 0.8,
      "effort": 11,
      "dependsOn": [
        "export-integrity"
      ],
      "status": "planned",
      "evidenceIds": [
        "e3"
      ],
      "decision": "Tie feedback to a version and provide an explicit approval state.",
      "nonGoals": [
        "No automatic external publication in this release",
        "No expansion to unvalidated personas"
      ],
      "requirements": [
        {
          "id": "core-flow",
          "priority": "P0",
          "text": "Tie feedback to a version and provide an explicit approval state.",
          "acceptance": [
            "Feedback retains the reviewed artifact ID and its version.",
            "Given two parallel reviews, approvals refer to the correct version and do not silently overwrite each other."
          ]
        },
        {
          "id": "recovery",
          "priority": "P1",
          "text": "Document recovery, ownership and accessibility for this flow.",
          "acceptance": [
            "The handoff identifies an owner and the exact release scope.",
            "Given an unavailable service, the user can preserve their work and understand the next step."
          ]
        }
      ],
      "risks": [
        "Reach and impact are estimates from a fictional discovery set; confirm before committing."
      ],
      "openQuestions": [
        "Who will review the pilot outcome and decide whether to expand?"
      ],
      "deadlineRelease": "next"
    },
    {
      "id": "activation-events",
      "title": "An unambiguous activation event",
      "team": "engineering",
      "owner": "Noor",
      "goalId": "activation",
      "users": "Project leads and contributors in small product teams",
      "problem": "The team cannot distinguish starting a task from delivering value.",
      "reach": 800,
      "impact": 1,
      "confidence": 0.8,
      "effort": 5,
      "dependsOn": [],
      "status": "planned",
      "evidenceIds": [
        "e7"
      ],
      "decision": "Define generated, saved and shared events with an event contract.",
      "nonGoals": [
        "No automatic external publication in this release",
        "No expansion to unvalidated personas"
      ],
      "requirements": [
        {
          "id": "core-flow",
          "priority": "P0",
          "text": "Define generated, saved and shared events with an event contract.",
          "acceptance": [
            "The event dictionary separates draft generation from successful persistence.",
            "Given repeated retries, the first-success metric counts one successful save per workspace."
          ]
        },
        {
          "id": "recovery",
          "priority": "P1",
          "text": "Document recovery, ownership and accessibility for this flow.",
          "acceptance": [
            "The handoff identifies an owner and the exact release scope.",
            "Given an unavailable service, the user can preserve their work and understand the next step."
          ]
        }
      ],
      "risks": [
        "Reach and impact are estimates from a fictional discovery set; confirm before committing."
      ],
      "openQuestions": [
        "Who will review the pilot outcome and decide whether to expand?"
      ],
      "deadlineRelease": "now"
    },
    {
      "id": "public-api",
      "title": "The first portable API surface",
      "team": "engineering",
      "owner": "Jules",
      "goalId": "trust",
      "users": "Project leads and contributors in small product teams",
      "problem": "Integrations need a stable permission and export model.",
      "reach": 120,
      "impact": 2,
      "confidence": 0.5,
      "effort": 20,
      "dependsOn": [
        "export-integrity",
        "review-room"
      ],
      "status": "planned",
      "evidenceIds": [
        "e6"
      ],
      "decision": "Ship a read-only API after the handoff contract is stable.",
      "nonGoals": [
        "No automatic external publication in this release",
        "No expansion to unvalidated personas"
      ],
      "requirements": [
        {
          "id": "core-flow",
          "priority": "P0",
          "text": "Ship a read-only API after the handoff contract is stable.",
          "acceptance": [
            "All read endpoints enforce the documented workspace permissions.",
            "Given a revoked token, the API denies access without disclosing another workspace."
          ]
        },
        {
          "id": "recovery",
          "priority": "P1",
          "text": "Document recovery, ownership and accessibility for this flow.",
          "acceptance": [
            "The handoff identifies an owner and the exact release scope.",
            "Given an unavailable service, the user can preserve their work and understand the next step."
          ]
        }
      ],
      "risks": [
        "Reach and impact are estimates from a fictional discovery set; confirm before committing."
      ],
      "openQuestions": [
        "Who will review the pilot outcome and decide whether to expand?"
      ]
    },
    {
      "id": "mobile-capture",
      "title": "Reliable notes on the move",
      "team": "engineering",
      "owner": "Noor",
      "goalId": "activation",
      "users": "Project leads and contributors in small product teams",
      "problem": "Interrupted mobile connections can lose a short note.",
      "reach": 200,
      "impact": 1,
      "confidence": 0.5,
      "effort": 13,
      "dependsOn": [],
      "status": "blocked",
      "evidenceIds": [
        "e8"
      ],
      "decision": "Prototype a recoverable draft and test the conflict behavior.",
      "nonGoals": [
        "No automatic external publication in this release",
        "No expansion to unvalidated personas"
      ],
      "requirements": [
        {
          "id": "core-flow",
          "priority": "P0",
          "text": "Prototype a recoverable draft and test the conflict behavior.",
          "acceptance": [
            "A local draft is recoverable after a simulated interrupted save.",
            "Given two drafts for the same note, the user can inspect both before choosing."
          ]
        },
        {
          "id": "recovery",
          "priority": "P1",
          "text": "Document recovery, ownership and accessibility for this flow.",
          "acceptance": [
            "The handoff identifies an owner and the exact release scope.",
            "Given an unavailable service, the user can preserve their work and understand the next step."
          ]
        }
      ],
      "risks": [
        "Reach and impact are estimates from a fictional discovery set; confirm before committing."
      ],
      "openQuestions": [
        "Who will review the pilot outcome and decide whether to expand?"
      ]
    },
    {
      "id": "executive-summary",
      "title": "A weekly executive summary",
      "team": "design",
      "owner": "Mara",
      "goalId": "trust",
      "users": "Project leads and contributors in small product teams",
      "problem": "A summary request has no evidence of recurring usage.",
      "reach": 60,
      "impact": 0.5,
      "confidence": 0.3,
      "effort": 5,
      "dependsOn": [],
      "status": "deferred",
      "evidenceIds": [],
      "decision": "Interview two intended readers before designing another report.",
      "nonGoals": [
        "No automatic external publication in this release",
        "No expansion to unvalidated personas"
      ],
      "requirements": [
        {
          "id": "core-flow",
          "priority": "P0",
          "text": "Interview two intended readers before designing another report.",
          "acceptance": [
            "The discovery record identifies a real decision and required source data.",
            "Given insufficient evidence, the roadmap keeps the idea outside committed capacity."
          ]
        },
        {
          "id": "recovery",
          "priority": "P1",
          "text": "Document recovery, ownership and accessibility for this flow.",
          "acceptance": [
            "The handoff identifies an owner and the exact release scope.",
            "Given an unavailable service, the user can preserve their work and understand the next step."
          ]
        }
      ],
      "risks": [
        "Reach and impact are estimates from a fictional discovery set; confirm before committing."
      ],
      "openQuestions": [
        "Who will review the pilot outcome and decide whether to expand?"
      ]
    }
  ]
}