[
  {
    "scenario_id": "sprint_025",
    "difficulty": "hard",
    "transcript": "For the fintech treasury workspace, we need wire approvals, cash positioning, FX exposure alerts, settlement reconciliation, role-based approvals, liquidity dashboards, bank statement ingestion, and treasury audit trails. Assume treasury ops will pull people away and change compliance sequencing more than once during the sprint.",
    "developers": [
      {"id": "D1", "name": "Ishaan Rao", "capacity": 8, "skill": 0.94, "specializations": ["backend", "payments", "security"]},
      {"id": "D2", "name": "Clara Stein", "capacity": 7, "skill": 0.9, "specializations": ["frontend", "ui", "analytics"]},
      {"id": "D3", "name": "Mateo Silva", "capacity": 8, "skill": 0.91, "specializations": ["backend", "database", "integration"]},
      {"id": "D4", "name": "Jia Lin", "capacity": 6, "skill": 0.88, "specializations": ["testing", "qa", "compliance"]}
    ],
    "items": [
      {"task": "Build wire approval workflow", "description": "Implement multi-step review and approval for outgoing wires", "deadline": 4, "priority": 4, "category": "feature", "tags": ["payments", "backend"], "acceptance_criteria": ["Approval chain enforced", "Dual authorization supported", "Audit log captured"], "dependency_hints": [], "owner_hint": "backend", "urgency_reason": "Treasury launch blocker", "raw_text": "we need wire approvals"},
      {"task": "Create cash positioning service", "description": "Aggregate balances from bank accounts and intraday movements", "deadline": 4, "priority": 4, "category": "data", "tags": ["backend", "analytics"], "acceptance_criteria": ["Balances aggregated", "Intraday changes applied", "Historical snapshots retained"], "dependency_hints": [], "owner_hint": "backend", "urgency_reason": "Core treasury visibility", "raw_text": "cash positioning"},
      {"task": "Add FX exposure alerts", "description": "Warn when currency positions breach configured exposure thresholds", "deadline": 5, "priority": 3, "category": "feature", "tags": ["analytics", "backend"], "acceptance_criteria": ["Thresholds configurable", "Alerts sent", "Exposure drill-down works"], "dependency_hints": ["depends on cash positioning"], "owner_hint": "backend", "urgency_reason": "", "raw_text": "FX exposure alerts"},
      {"task": "Implement settlement reconciliation", "description": "Match wires and settlements against bank confirmations", "deadline": 6, "priority": 4, "category": "data", "tags": ["backend", "database"], "acceptance_criteria": ["Matches detected", "Breaks surfaced", "Manual review supported"], "dependency_hints": ["depends on bank statement ingestion"], "owner_hint": "backend", "urgency_reason": "Reduces settlement risk", "raw_text": "settlement reconciliation"},
      {"task": "Add role-based approval controls", "description": "Restrict approval actions by treasury role and limit", "deadline": 5, "priority": 4, "category": "security", "tags": ["security", "auth"], "acceptance_criteria": ["Role rules enforced", "Limits configurable", "Unauthorized attempts logged"], "dependency_hints": ["depends on wire approval workflow"], "owner_hint": "backend", "urgency_reason": "Compliance requirement", "raw_text": "role-based approvals"},
      {"task": "Build liquidity dashboard", "description": "Visualize balances, outflows, and upcoming settlement pressure", "deadline": 7, "priority": 3, "category": "feature", "tags": ["frontend", "analytics"], "acceptance_criteria": ["Metrics correct", "Filters work", "Refresh time under 5 seconds"], "dependency_hints": ["depends on cash positioning"], "owner_hint": "frontend", "urgency_reason": "", "raw_text": "liquidity dashboards"},
      {"task": "Implement bank statement ingestion", "description": "Ingest end-of-day statement files from banking partners", "deadline": 5, "priority": 4, "category": "integration", "tags": ["backend", "integration"], "acceptance_criteria": ["Files parsed", "Duplicates ignored", "Schema errors surfaced"], "dependency_hints": [], "owner_hint": "backend", "urgency_reason": "Required for reconciliation", "raw_text": "bank statement ingestion"},
      {"task": "Create treasury audit trail export", "description": "Export approval and settlement activity for audit review", "deadline": 7, "priority": 3, "category": "documentation", "tags": ["security", "backend"], "acceptance_criteria": ["Export generated", "Date filters supported", "Actor metadata included"], "dependency_hints": ["depends on role-based approval controls"], "owner_hint": "backend", "urgency_reason": "", "raw_text": "treasury audit trails"}
    ],
    "events": [
      {"day": 2, "type": "capacity_change", "title": "Ishaan pulled into bank escalation", "description": "Lead payments engineer loses substantial time to a live treasury issue", "payload": {"developer_id": "D1", "new_capacity": 5, "reason": "Bank escalation"}},
      {"day": 3, "type": "add_task", "title": "SWIFT rejection hotfix", "description": "Treasury discovers some wire payloads fail SWIFT validation", "payload": {"task": "Patch SWIFT validation rules", "description": "Validate outgoing wire payloads against SWIFT-required fields and formats", "deadline": 4, "priority": 4, "category": "bugfix", "tags": ["payments", "backend"], "acceptance_criteria": ["Invalid payloads rejected", "Field-level errors shown", "Tests added for SWIFT cases"], "dependency_hints": ["depends on wire approval workflow"], "owner_hint": "backend", "urgency_reason": "Production payment risk"}},
      {"day": 4, "type": "add_dependency", "title": "FX alerts now require role controls", "description": "Treasury wants exposure alerts restricted by approval entitlements", "payload": {"task": "Add FX exposure alerts", "depends_on": "Add role-based approval controls"}},
      {"day": 6, "type": "remove_dependency", "title": "Audit export can ship before dashboard", "description": "Audit accepts raw exports before treasury visualizations are complete", "payload": {"task": "Create treasury audit trail export", "depends_on": "Build liquidity dashboard"}},
      {"day": 7, "type": "capacity_change", "title": "Jia covering a release audit", "description": "QA and compliance bandwidth drop late in the sprint", "payload": {"developer_id": "D4", "new_capacity": 4, "reason": "Release audit"}}
    ]
  },
  {
    "scenario_id": "sprint_026",
    "difficulty": "hard",
    "transcript": "This sprint is for the marketplace trust platform. We need seller onboarding checks, dispute workflows, listing moderation, refund rules, risky order scoring, abuse dashboards, review integrity, and admin investigation tools. Trust and operations are likely to change dependencies and pull engineers into incidents as we go.",
    "developers": [
      {"id": "D1", "name": "Avery Cole", "capacity": 8, "skill": 0.93, "specializations": ["backend", "security", "analytics"]},
      {"id": "D2", "name": "Neha Kapoor", "capacity": 7, "skill": 0.9, "specializations": ["frontend", "ui", "testing"]},
      {"id": "D3", "name": "Bruno Costa", "capacity": 8, "skill": 0.9, "specializations": ["backend", "integration", "database"]},
      {"id": "D4", "name": "Sofia Marin", "capacity": 6, "skill": 0.87, "specializations": ["qa", "infra", "performance"]}
    ],
    "items": [
      {"task": "Build seller onboarding checks", "description": "Validate business identity, tax details, and required documents", "deadline": 4, "priority": 4, "category": "security", "tags": ["backend", "integration"], "acceptance_criteria": ["Documents validated", "KYC failures surfaced", "Retry flow supported"], "dependency_hints": [], "owner_hint": "backend", "urgency_reason": "Risk control blocker", "raw_text": "seller onboarding checks"},
      {"task": "Implement dispute workflow", "description": "Allow buyers and sellers to open and resolve order disputes", "deadline": 5, "priority": 4, "category": "feature", "tags": ["frontend", "backend"], "acceptance_criteria": ["Cases created", "State changes tracked", "Notifications sent"], "dependency_hints": [], "owner_hint": "frontend", "urgency_reason": "Support escalation", "raw_text": "dispute workflows"},
      {"task": "Add listing moderation service", "description": "Queue suspicious listings for moderation review and blocking", "deadline": 4, "priority": 4, "category": "security", "tags": ["backend", "analytics"], "acceptance_criteria": ["Queue populated", "Moderator actions persisted", "Block reason recorded"], "dependency_hints": [], "owner_hint": "backend", "urgency_reason": "Marketplace safety", "raw_text": "listing moderation"},
      {"task": "Implement refund eligibility rules", "description": "Apply category-specific refund windows and exceptions", "deadline": 6, "priority": 3, "category": "feature", "tags": ["backend", "payments"], "acceptance_criteria": ["Rules enforced", "Exceptions configurable", "Reason codes surfaced"], "dependency_hints": ["depends on dispute workflow"], "owner_hint": "backend", "urgency_reason": "", "raw_text": "refund rules"},
      {"task": "Build risky order scoring", "description": "Score orders using account, device, and payment risk signals", "deadline": 5, "priority": 4, "category": "security", "tags": ["backend", "analytics"], "acceptance_criteria": ["Scores computed", "Feature breakdown visible", "Thresholds configurable"], "dependency_hints": [], "owner_hint": "backend", "urgency_reason": "Fraud prevention", "raw_text": "risky order scoring"},
      {"task": "Create abuse operations dashboard", "description": "Show risky orders, disputes, and moderation volume to trust ops", "deadline": 7, "priority": 3, "category": "feature", "tags": ["frontend", "analytics"], "acceptance_criteria": ["Data accurate", "Filters work", "Investigations link correctly"], "dependency_hints": ["depends on risky order scoring"], "owner_hint": "frontend", "urgency_reason": "", "raw_text": "abuse dashboards"},
      {"task": "Protect review integrity", "description": "Detect and suppress coordinated fake review campaigns", "deadline": 7, "priority": 3, "category": "security", "tags": ["analytics", "backend"], "acceptance_criteria": ["Suspicious reviews flagged", "Bulk suppression possible", "Investigation notes saved"], "dependency_hints": [], "owner_hint": "backend", "urgency_reason": "", "raw_text": "review integrity"},
      {"task": "Build admin investigation tools", "description": "Provide internal tooling for trust analysts to inspect abuse cases", "deadline": 8, "priority": 2, "category": "feature", "tags": ["frontend", "backend"], "acceptance_criteria": ["Case detail view works", "Evidence panel available", "Internal notes persisted"], "dependency_hints": ["depends on abuse operations dashboard"], "owner_hint": "frontend", "urgency_reason": "", "raw_text": "admin investigation tools"}
    ],
    "events": [
      {"day": 2, "type": "add_task", "title": "Refund exploit discovered", "description": "Trust identifies an exploit in refund abuse handling", "payload": {"task": "Patch refund abuse loophole", "description": "Block repeated refund claims using duplicate evidence and device reuse", "deadline": 4, "priority": 4, "category": "bugfix", "tags": ["security", "payments"], "acceptance_criteria": ["Exploit blocked", "False positives reviewed", "Audit notes captured"], "dependency_hints": ["depends on implement refund eligibility rules"], "owner_hint": "backend", "urgency_reason": "High-loss exploit"}},
      {"day": 3, "type": "capacity_change", "title": "Avery on fraud incident response", "description": "Lead trust engineer loses substantial backend time", "payload": {"developer_id": "D1", "new_capacity": 4, "reason": "Fraud incident response"}},
      {"day": 4, "type": "add_dependency", "title": "Dashboard needs moderation data", "description": "Ops wants abuse dashboards tied directly to moderation outcomes", "payload": {"task": "Create abuse operations dashboard", "depends_on": "Add listing moderation service"}},
      {"day": 5, "type": "add_task", "title": "Chargeback evidence request", "description": "Payments partner requires better evidence packaging for disputes", "payload": {"task": "Generate chargeback evidence packs", "description": "Compile order, delivery, and dispute evidence into partner-specific packets", "deadline": 7, "priority": 4, "category": "feature", "tags": ["payments", "backend"], "acceptance_criteria": ["Evidence packet generated", "Required fields complete", "Manual resubmission supported"], "dependency_hints": ["depends on dispute workflow"], "owner_hint": "backend", "urgency_reason": "Partner deadline"}},
      {"day": 7, "type": "remove_dependency", "title": "Investigation tools can ship before dashboard polish", "description": "Trust ops agrees to use a minimal internal view", "payload": {"task": "Build admin investigation tools", "depends_on": "Create abuse operations dashboard"}}
    ]
  },
  {
    "scenario_id": "sprint_027",
    "difficulty": "hard",
    "transcript": "We are building the cloud observability workspace this sprint. Finish service health views, alert routing, incident timelines, SSO access, log retention controls, noisy alert suppression, on-call reports, and runbook linking. Reliability and security are both in motion, so expect capacity shifts and dependency changes during execution.",
    "developers": [
      {"id": "D1", "name": "Harper Nguyen", "capacity": 8, "skill": 0.94, "specializations": ["backend", "infra", "security"]},
      {"id": "D2", "name": "Rohan Mehta", "capacity": 7, "skill": 0.89, "specializations": ["frontend", "ui", "analytics"]},
      {"id": "D3", "name": "Lucia Romero", "capacity": 8, "skill": 0.9, "specializations": ["backend", "database", "performance"]},
      {"id": "D4", "name": "Tariq Abdullah", "capacity": 6, "skill": 0.88, "specializations": ["qa", "testing", "devops"]}
    ],
    "items": [
      {"task": "Build service health overview", "description": "Summarize service status, error rates, and incident counts", "deadline": 4, "priority": 4, "category": "feature", "tags": ["frontend", "analytics"], "acceptance_criteria": ["Health tiles accurate", "Service filters work", "Refresh under 5 seconds"], "dependency_hints": [], "owner_hint": "frontend", "urgency_reason": "Core observability surface", "raw_text": "service health views"},
      {"task": "Implement alert routing rules", "description": "Route alerts to teams based on ownership, severity, and schedule", "deadline": 4, "priority": 4, "category": "feature", "tags": ["backend", "infra"], "acceptance_criteria": ["Routing rules persisted", "Escalations work", "Override paths supported"], "dependency_hints": [], "owner_hint": "backend", "urgency_reason": "Needed for on-call operations", "raw_text": "alert routing"},
      {"task": "Create incident timeline view", "description": "Show incident events, alerts, and operator actions chronologically", "deadline": 5, "priority": 4, "category": "feature", "tags": ["frontend", "backend"], "acceptance_criteria": ["Timeline renders correctly", "Events ordered properly", "Annotations supported"], "dependency_hints": ["depends on alert routing rules"], "owner_hint": "frontend", "urgency_reason": "", "raw_text": "incident timelines"},
      {"task": "Add SSO access controls", "description": "Restrict observability access by team and role through SSO groups", "deadline": 5, "priority": 4, "category": "security", "tags": ["auth", "backend"], "acceptance_criteria": ["Group mapping works", "Access restricted by role", "Deprovisioning tested"], "dependency_hints": [], "owner_hint": "backend", "urgency_reason": "Enterprise access blocker", "raw_text": "SSO access"},
      {"task": "Implement log retention controls", "description": "Apply retention policies by service tier and compliance setting", "deadline": 6, "priority": 3, "category": "security", "tags": ["backend", "database"], "acceptance_criteria": ["Retention rules enforced", "Overrides audited", "Expiry jobs tested"], "dependency_hints": [], "owner_hint": "backend", "urgency_reason": "", "raw_text": "log retention controls"},
      {"task": "Build noisy alert suppression", "description": "Suppress repeated low-value alerts without hiding major incidents", "deadline": 6, "priority": 4, "category": "quality", "tags": ["backend", "analytics"], "acceptance_criteria": ["Suppression works", "Thresholds configurable", "Suppressed alerts still searchable"], "dependency_hints": ["depends on alert routing rules"], "owner_hint": "backend", "urgency_reason": "Reduces operator overload", "raw_text": "noisy alert suppression"},
      {"task": "Create on-call reports", "description": "Report after-hours pages, acknowledgements, and resolution times", "deadline": 7, "priority": 3, "category": "analytics", "tags": ["analytics", "backend"], "acceptance_criteria": ["Metrics correct", "Team filters work", "Export available"], "dependency_hints": ["depends on alert routing rules"], "owner_hint": "backend", "urgency_reason": "", "raw_text": "on-call reports"},
      {"task": "Link runbooks to alerts", "description": "Attach runbooks to matching alerts and incidents", "deadline": 7, "priority": 3, "category": "documentation", "tags": ["backend", "frontend"], "acceptance_criteria": ["Runbooks linked", "Fallback suggestions shown", "Missing runbooks highlighted"], "dependency_hints": ["depends on incident timeline view"], "owner_hint": "frontend", "urgency_reason": "", "raw_text": "runbook linking"}
    ],
    "events": [
      {"day": 2, "type": "capacity_change", "title": "Harper on sev-one support", "description": "Infra lead loses time to a production incident", "payload": {"developer_id": "D1", "new_capacity": 5, "reason": "Sev-one incident"}},
      {"day": 3, "type": "add_dependency", "title": "Timeline now requires SSO gating", "description": "Security wants incident timelines behind role controls", "payload": {"task": "Create incident timeline view", "depends_on": "Add SSO access controls"}},
      {"day": 4, "type": "add_task", "title": "Pager routing bug", "description": "Alerts are misrouting to the wrong rotation after schedule changes", "payload": {"task": "Fix pager routing mismatch", "description": "Correct alert routing when team schedules rotate mid-week", "deadline": 5, "priority": 4, "category": "bugfix", "tags": ["infra", "backend"], "acceptance_criteria": ["Correct team paged", "Schedule cache refreshed", "Regression tests added"], "dependency_hints": ["depends on implement alert routing rules"], "owner_hint": "backend", "urgency_reason": "On-call outage risk"}},
      {"day": 6, "type": "capacity_change", "title": "Tariq covering release verification", "description": "Testing capacity shrinks before rollout", "payload": {"developer_id": "D4", "new_capacity": 4, "reason": "Release verification"}},
      {"day": 7, "type": "remove_dependency", "title": "Runbooks can ship without timeline integration", "description": "Ops agrees to attach runbooks directly on alerts first", "payload": {"task": "Link runbooks to alerts", "depends_on": "Create incident timeline view"}}
    ]
  }
]