{
  "copyright": "\u00a9 2026 Matthew Breen. Licensed under CC BY 4.0. See LICENSE-CONTENT.md.",
  "_version": "1.0",
  "_description": "Per-use-case scoring map. Each UC has a static blockchainFit (1-5) and P2 signal mappings that drive need/scale/readiness scores independently per UC. This replaces the category-level scoring that gave all UCs in the same category identical scores.",
  "_signalRoles": {
    "need": "High severity on this question = org genuinely needs this UC. Weighted average becomes needScore.",
    "scale": "High severity = volume/complexity justifies blockchain overhead. Weighted average becomes scaleScore.",
    "readiness": "High severity = org LACKS readiness (inverted for final score). Can be compensated by high need+scale.",
    "fit_boost": "High severity amplifies blockchainFit \u2014 reveals multi-party trust problems where blockchain shines."
  },
  "UC-A-001": {
    "name": "Cross-border beneficiary payments",
    "blockchainFit": 4.5,
    "rationale": "Multi-party cross-border transfers with no single trusted intermediary. Strong blockchain case when corridors are difficult.",
    "signals": [
      {
        "q": "NGO-P2-CatA-Q2",
        "w": 1,
        "role": "need",
        "why": "More intermediaries = more friction blockchain can remove"
      },
      {
        "q": "NGO-P2-CatA-Q4",
        "w": 0.9,
        "role": "need",
        "why": "High fees = direct cost blockchain can reduce"
      },
      {
        "q": "NGO-P2-CatA-Q5",
        "w": 1,
        "role": "need",
        "why": "Sanctions/de-risked corridors = traditional banking failing"
      },
      {
        "q": "NGO-P2-CatA-Q6",
        "w": 0.9,
        "role": "need",
        "why": "Frequent blocks = urgent need for alternative rail"
      },
      {
        "q": "NGO-P2-CatA-Q3",
        "w": 0.8,
        "role": "need",
        "why": "Slow transfers = beneficiaries waiting"
      },
      {
        "q": "NGO-P2-CatA-Q31",
        "w": 0.6,
        "role": "fit_boost",
        "why": "Cash scarcity in communities amplifies blockchain payment case"
      },
      {
        "q": "NGO-P2-CatA-Q8b",
        "w": 0.5,
        "role": "scale",
        "why": "High discrepancy rate = more transactions needing reconciliation"
      },
      {
        "q": "NGO-P2-CatA-Q1",
        "w": 0.4,
        "role": "readiness",
        "why": "Complex existing process = harder to implement but also more to gain"
      }
    ],
    "fitGate": 3,
    "readinessGate": 2.5
  },
  "UC-A-002": {
    "name": "Staff salary payments across jurisdictions",
    "blockchainFit": 2,
    "rationale": "Mostly internal single-org payments. Payroll software handles this well. Blockchain only adds value if operating in sanctioned/de-risked corridors.",
    "signals": [
      {
        "q": "NGO-P2-CatA-Q5",
        "w": 1,
        "role": "need",
        "why": "Only justified if corridors are genuinely blocked"
      },
      {
        "q": "NGO-P2-CatA-Q4",
        "w": 0.5,
        "role": "need",
        "why": "High fees on salary transfers"
      },
      {
        "q": "NGO-P2-CatA-Q3",
        "w": 0.4,
        "role": "need",
        "why": "Staff waiting weeks for salary is a retention problem"
      },
      {
        "q": "NGO-P2-CatA-Q6",
        "w": 0.6,
        "role": "need",
        "why": "Blocked salary payments = staff crisis"
      },
      {
        "q": "NGO-P2-CatA-Q1",
        "w": 0.3,
        "role": "readiness",
        "why": "Process complexity indicates existing capability"
      }
    ],
    "fitGate": 3.5,
    "readinessGate": 2
  },
  "UC-A-003": {
    "name": "Vendor and supplier payments in remote locations",
    "blockchainFit": 3.2,
    "rationale": "Multi-party (org + vendor + agent). Relevant when vendors are in areas with poor banking. Mobile money often sufficient alternative.",
    "signals": [
      {
        "q": "NGO-P2-CatA-Q5",
        "w": 0.9,
        "role": "need",
        "why": "Difficult corridors affect vendor payments"
      },
      {
        "q": "NGO-P2-CatA-Q4",
        "w": 0.8,
        "role": "need",
        "why": "High payment costs to remote vendors"
      },
      {
        "q": "NGO-P2-CatA-Q31",
        "w": 0.8,
        "role": "need",
        "why": "Cash scarcity = vendors can't receive traditional payment"
      },
      {
        "q": "NGO-P2-CatA-Q2",
        "w": 0.6,
        "role": "need",
        "why": "Intermediaries in vendor payment chain"
      },
      {
        "q": "NGO-P2-CatA-Q8b",
        "w": 0.5,
        "role": "scale",
        "why": "Payment discrepancies with vendors"
      }
    ],
    "fitGate": 3,
    "readinessGate": 2
  },
  "UC-A-004": {
    "name": "Inter-office fund transfers across country programmes",
    "blockchainFit": 1.8,
    "rationale": "Internal transfers within single org. ERP/banking handles this. Only relevant if operating across highly restricted corridors.",
    "signals": [
      {
        "q": "NGO-P2-CatA-Q5",
        "w": 1,
        "role": "need",
        "why": "Only justified with sanctioned/restricted corridors"
      },
      {
        "q": "NGO-P2-CatA-Q3",
        "w": 0.5,
        "role": "need",
        "why": "Slow inter-office transfers"
      },
      {
        "q": "NGO-P2-CatA-Q4",
        "w": 0.4,
        "role": "need",
        "why": "Cost of moving funds between offices"
      },
      {
        "q": "NGO-P2-CatA-Q8a",
        "w": 0.3,
        "role": "scale",
        "why": "Infrequent reconciliation suggests low volume"
      }
    ],
    "fitGate": 3.5,
    "readinessGate": 1.5
  },
  "UC-A-005": {
    "name": "Emergency rapid-disbursement payments",
    "blockchainFit": 4,
    "rationale": "Speed + accountability + multi-party coordination in crisis. Pre-positioned smart contracts can release funds automatically based on triggers.",
    "signals": [
      {
        "q": "NGO-P2-CatA-Q3",
        "w": 1,
        "role": "need",
        "why": "Slow transfers in emergencies = lives at risk"
      },
      {
        "q": "NGO-P2-CatA-Q6",
        "w": 1,
        "role": "need",
        "why": "Blocked transfers during crisis = critical"
      },
      {
        "q": "NGO-P2-CatA-Q6-followup",
        "w": 0.9,
        "role": "need",
        "why": "Severe disruption impact amplifies urgency"
      },
      {
        "q": "NGO-P2-CatA-Q5",
        "w": 0.8,
        "role": "need",
        "why": "Difficult corridors block emergency funds"
      },
      {
        "q": "NGO-P2-CatA-Q30",
        "w": 0.7,
        "role": "fit_boost",
        "why": "Critical failure points = need for resilient alternative"
      },
      {
        "q": "NGO-P2-CatA-Q31",
        "w": 0.5,
        "role": "scale",
        "why": "Cash scarcity in target communities"
      }
    ],
    "fitGate": 3,
    "readinessGate": 2.5
  },
  "UC-A-006": {
    "name": "Multi-currency treasury management and currency hedging",
    "blockchainFit": 2.8,
    "rationale": "DeFi protocols offer alternatives but require significant technical sophistication. Traditional treasury management tools exist.",
    "signals": [
      {
        "q": "NGO-P2-CatA-Q4",
        "w": 0.8,
        "role": "need",
        "why": "High FX costs indicate currency management pain"
      },
      {
        "q": "NGO-P2-CatA-Q5",
        "w": 0.7,
        "role": "need",
        "why": "FX controls and capital restrictions"
      },
      {
        "q": "NGO-P2-CatA-Q2",
        "w": 0.5,
        "role": "scale",
        "why": "Multiple intermediaries = complex treasury"
      },
      {
        "q": "NGO-P2-CatA-Q1",
        "w": 0.6,
        "role": "readiness",
        "why": "Complex process indicates treasury sophistication needed"
      }
    ],
    "fitGate": 3,
    "readinessGate": 3
  },
  "UC-A-007": {
    "name": "Donor fund reconciliation and tracking",
    "blockchainFit": 3.8,
    "rationale": "Multi-party (org + donors + auditors). Immutable ledger provides trusted audit trail. Strong case when multiple donors require different reporting.",
    "signals": [
      {
        "q": "NGO-P2-CatA-Q8a",
        "w": 0.8,
        "role": "need",
        "why": "Infrequent reconciliation = tracking gaps"
      },
      {
        "q": "NGO-P2-CatA-Q8b",
        "w": 1,
        "role": "need",
        "why": "High discrepancy rate = reconciliation failing"
      },
      {
        "q": "NGO-P2-CatA-Q29",
        "w": 0.7,
        "role": "fit_boost",
        "why": "Desire for real-time donor visibility = blockchain natural fit"
      },
      {
        "q": "NGO-P2-CatA-Q7",
        "w": 0.6,
        "role": "need",
        "why": "Compliance burden indicates reporting complexity"
      },
      {
        "q": "NGO-P2-CatA-Q2",
        "w": 0.4,
        "role": "scale",
        "why": "More intermediaries = more reconciliation points"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 2.5
  },
  "UC-A-008": {
    "name": "Real-time financial reporting across programmes",
    "blockchainFit": 3,
    "rationale": "Centralised dashboards can do this. Blockchain adds value when multiple independent parties need to trust the same data.",
    "signals": [
      {
        "q": "NGO-P2-CatA-Q8a",
        "w": 0.9,
        "role": "need",
        "why": "Infrequent reconciliation = no real-time visibility"
      },
      {
        "q": "NGO-P2-CatA-Q8b",
        "w": 0.7,
        "role": "need",
        "why": "Discrepancies = unreliable current reporting"
      },
      {
        "q": "NGO-P2-CatA-Q29",
        "w": 0.8,
        "role": "fit_boost",
        "why": "Excitement about real-time donor visibility"
      },
      {
        "q": "NGO-P2-CatA-Q1",
        "w": 0.4,
        "role": "readiness",
        "why": "Process complexity indicates reporting maturity"
      }
    ],
    "fitGate": 3,
    "readinessGate": 2.5
  },
  "UC-A-009": {
    "name": "Automated compliance reporting to donors",
    "blockchainFit": 3.2,
    "rationale": "Smart contracts can automate report generation from on-chain data. Most valuable when multiple donors have different requirements.",
    "signals": [
      {
        "q": "NGO-P2-CatA-Q7",
        "w": 1,
        "role": "need",
        "why": "High compliance burden = automation opportunity"
      },
      {
        "q": "NGO-P2-CatA-Q8b",
        "w": 0.7,
        "role": "need",
        "why": "Discrepancies in reporting data"
      },
      {
        "q": "NGO-P2-CatA-Q29",
        "w": 0.6,
        "role": "fit_boost",
        "why": "Donor desire for transparency"
      },
      {
        "q": "NGO-P2-CatA-Q1",
        "w": 0.5,
        "role": "readiness",
        "why": "Process complexity indicates compliance sophistication"
      }
    ],
    "fitGate": 3,
    "readinessGate": 2.5
  },
  "UC-A-010": {
    "name": "Petty cash and field office expense management",
    "blockchainFit": 1.5,
    "rationale": "Single-org, low-value transactions. Mobile money or expense management apps are simpler. Blockchain is overkill.",
    "signals": [
      {
        "q": "NGO-P2-CatA-Q31",
        "w": 0.7,
        "role": "need",
        "why": "Cash scarcity makes petty cash management harder"
      },
      {
        "q": "NGO-P2-CatA-Q8b",
        "w": 0.4,
        "role": "need",
        "why": "Expense discrepancies"
      },
      {
        "q": "NGO-P2-CatA-Q1",
        "w": 0.3,
        "role": "readiness",
        "why": "Process maturity"
      }
    ],
    "fitGate": 3.5,
    "readinessGate": 1.5
  },
  "UC-A-011": {
    "name": "Procurement process transparency and audit trails",
    "blockchainFit": 3.5,
    "rationale": "Multi-party (org + vendors + auditors + donors). Immutable procurement records reduce fraud. Strong when procurement spans multiple jurisdictions.",
    "signals": [
      {
        "q": "NGO-P2-CatA-Q8b",
        "w": 0.8,
        "role": "need",
        "why": "Discrepancies indicate procurement opacity"
      },
      {
        "q": "NGO-P2-CatA-Q7",
        "w": 0.7,
        "role": "need",
        "why": "Compliance checking time burden"
      },
      {
        "q": "NGO-P2-CatA-Q30",
        "w": 0.6,
        "role": "fit_boost",
        "why": "Procurement fraud as failure point"
      },
      {
        "q": "NGO-P2-CatA-Q29",
        "w": 0.5,
        "role": "fit_boost",
        "why": "Donor desire for procurement visibility"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 2.5
  },
  "UC-A-012": {
    "name": "Smart contract-based vendor payment terms",
    "blockchainFit": 3.8,
    "rationale": "Automated conditional payments on delivery verification. Strong multi-party trust case with vendors.",
    "signals": [
      {
        "q": "NGO-P2-CatA-Q4",
        "w": 0.7,
        "role": "need",
        "why": "High cost = incentive for automation"
      },
      {
        "q": "NGO-P2-CatA-Q8b",
        "w": 0.9,
        "role": "need",
        "why": "Payment-delivery discrepancies"
      },
      {
        "q": "NGO-P2-CatA-Q2",
        "w": 0.6,
        "role": "scale",
        "why": "Multiple intermediaries in payment chain"
      },
      {
        "q": "NGO-P2-CatA-Q1",
        "w": 0.5,
        "role": "readiness",
        "why": "Process sophistication for smart contracts"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 3
  },
  "UC-A-013": {
    "name": "Multi-party approval workflows across time zones",
    "blockchainFit": 2.5,
    "rationale": "E-signature and workflow tools handle this well. Blockchain adds immutability but most orgs don't need it for approvals.",
    "signals": [
      {
        "q": "NGO-P2-CatA-Q1",
        "w": 0.8,
        "role": "need",
        "why": "Complex processes = multi-party approval needs"
      },
      {
        "q": "NGO-P2-CatA-Q7",
        "w": 0.6,
        "role": "need",
        "why": "Compliance requires documented approvals"
      },
      {
        "q": "NGO-P2-CatA-Q30",
        "w": 0.4,
        "role": "fit_boost",
        "why": "Key person departure as failure point = need for decentralised approval"
      }
    ],
    "fitGate": 3,
    "readinessGate": 2.5
  },
  "UC-A-014": {
    "name": "Restricted vs unrestricted fund segregation and tracking",
    "blockchainFit": 3.5,
    "rationale": "Critical for donor compliance. Blockchain provides provable fund segregation that auditors can verify independently.",
    "signals": [
      {
        "q": "NGO-P2-CatA-Q7",
        "w": 1,
        "role": "need",
        "why": "Compliance time = fund tracking burden"
      },
      {
        "q": "NGO-P2-CatA-Q8b",
        "w": 0.9,
        "role": "need",
        "why": "Discrepancies in fund tracking"
      },
      {
        "q": "NGO-P2-CatA-Q8a",
        "w": 0.6,
        "role": "need",
        "why": "Infrequent reconciliation = fund mix-up risk"
      },
      {
        "q": "NGO-P2-CatA-Q29",
        "w": 0.7,
        "role": "fit_boost",
        "why": "Donor desire for fund visibility"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 2.5
  },
  "UC-A-015": {
    "name": "Multi-year grant milestone-based disbursement automation",
    "blockchainFit": 4,
    "rationale": "Smart contracts releasing funds on verified milestone completion. Multi-party (donor + org + verifier). Strong blockchain case.",
    "signals": [
      {
        "q": "NGO-P2-CatA-Q7",
        "w": 0.9,
        "role": "need",
        "why": "Compliance documentation for milestones"
      },
      {
        "q": "NGO-P2-CatA-Q3",
        "w": 0.7,
        "role": "need",
        "why": "Slow disbursement delays programmes"
      },
      {
        "q": "NGO-P2-CatA-Q29",
        "w": 0.8,
        "role": "fit_boost",
        "why": "Real-time milestone tracking for donors"
      },
      {
        "q": "NGO-P2-CatA-Q8b",
        "w": 0.5,
        "role": "scale",
        "why": "Discrepancies in milestone verification"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 3
  },
  "UC-A-016": {
    "name": "Sub-grantee fund disbursement and tracking",
    "blockchainFit": 4,
    "rationale": "Multi-party (primary + sub-grantees + donor). Tracking funds through sub-granting chain is a trust problem blockchain solves well.",
    "signals": [
      {
        "q": "NGO-P2-CatA-Q2",
        "w": 0.8,
        "role": "need",
        "why": "Intermediaries in sub-granting chain"
      },
      {
        "q": "NGO-P2-CatA-Q8b",
        "w": 0.9,
        "role": "need",
        "why": "Discrepancies in sub-grantee reporting"
      },
      {
        "q": "NGO-P2-CatA-Q7",
        "w": 0.8,
        "role": "need",
        "why": "Compliance burden for sub-grants"
      },
      {
        "q": "NGO-P2-CatA-Q29",
        "w": 0.7,
        "role": "fit_boost",
        "why": "Donor visibility into sub-grantee spending"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 2.5,
    "interagency": true
  },
  "UC-A-017": {
    "name": "Proof of funds deployment (donor accountability)",
    "blockchainFit": 4.2,
    "rationale": "Core blockchain value prop: immutable proof that funds went where claimed. Multi-party verification.",
    "signals": [
      {
        "q": "NGO-P2-CatA-Q29",
        "w": 1,
        "role": "need",
        "why": "Direct donor accountability need"
      },
      {
        "q": "NGO-P2-CatA-Q8b",
        "w": 0.8,
        "role": "need",
        "why": "Discrepancies undermine donor trust"
      },
      {
        "q": "NGO-P2-CatA-Q7",
        "w": 0.7,
        "role": "need",
        "why": "Compliance burden for proof generation"
      },
      {
        "q": "NGO-P2-CatA-Q8a",
        "w": 0.5,
        "role": "scale",
        "why": "Reconciliation frequency indicates reporting volume"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 2.5
  },
  "UC-A-018": {
    "name": "Real-time expenditure tracking for donors",
    "blockchainFit": 3.5,
    "rationale": "Dashboard solutions exist but blockchain adds independent verifiability. Strong when multiple donors track same programmes.",
    "signals": [
      {
        "q": "NGO-P2-CatA-Q29",
        "w": 1,
        "role": "need",
        "why": "Direct donor visibility requirement"
      },
      {
        "q": "NGO-P2-CatA-Q8a",
        "w": 0.7,
        "role": "need",
        "why": "Infrequent reconciliation = no real-time view"
      },
      {
        "q": "NGO-P2-CatA-Q8b",
        "w": 0.6,
        "role": "need",
        "why": "Expenditure discrepancies"
      },
      {
        "q": "NGO-P2-CatA-Q7",
        "w": 0.5,
        "role": "scale",
        "why": "Compliance time indicates reporting complexity"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 2.5
  },
  "UC-A-019": {
    "name": "Microfinance and lending to underbanked beneficiaries",
    "blockchainFit": 3.8,
    "rationale": "Multi-party (lender + borrower + guarantor). Blockchain enables transparent lending without traditional banking infrastructure.",
    "signals": [
      {
        "q": "NGO-P2-CatA-Q31",
        "w": 1,
        "role": "need",
        "why": "Cash/banking scarcity = underbanked population"
      },
      {
        "q": "NGO-P2-CatA-Q5",
        "w": 0.8,
        "role": "need",
        "why": "Difficult corridors indicate no banking access"
      },
      {
        "q": "NGO-P2-CatA-Q4",
        "w": 0.6,
        "role": "need",
        "why": "High transaction costs for small loans"
      },
      {
        "q": "NGO-P2-CatA-Q1",
        "w": 0.5,
        "role": "readiness",
        "why": "Existing financial process maturity"
      }
    ],
    "fitGate": 3,
    "readinessGate": 3
  },
  "UC-A-020": {
    "name": "Savings group management and record-keeping",
    "blockchainFit": 2.5,
    "rationale": "Community-level record keeping. Mobile apps work well. Blockchain adds value only for cross-group federation or auditor access.",
    "signals": [
      {
        "q": "NGO-P2-CatA-Q31",
        "w": 0.9,
        "role": "need",
        "why": "Cash scarcity drives savings group importance"
      },
      {
        "q": "NGO-P2-CatA-Q8b",
        "w": 0.5,
        "role": "need",
        "why": "Record discrepancies in savings groups"
      },
      {
        "q": "NGO-P2-CatA-Q1",
        "w": 0.3,
        "role": "readiness",
        "why": "Financial process maturity"
      }
    ],
    "fitGate": 3,
    "readinessGate": 2
  },
  "UC-A-021": {
    "name": "Forecast-based financing (anticipatory action)",
    "blockchainFit": 4.2,
    "rationale": "Smart contracts that auto-release funds based on external data triggers (weather, conflict indicators). Strong multi-party automation case.",
    "signals": [
      {
        "q": "NGO-P2-CatA-Q3",
        "w": 0.9,
        "role": "need",
        "why": "Slow funds = too late for anticipatory action"
      },
      {
        "q": "NGO-P2-CatA-Q6",
        "w": 0.8,
        "role": "need",
        "why": "Blocked transfers undermine pre-positioning"
      },
      {
        "q": "NGO-P2-CatA-Q30",
        "w": 0.7,
        "role": "fit_boost",
        "why": "Financial system failure points = need for automated resilience"
      },
      {
        "q": "NGO-P2-CatA-Q5",
        "w": 0.6,
        "role": "need",
        "why": "Difficult corridors block anticipatory funds"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 3
  },
  "UC-A-022": {
    "name": "Parametric insurance for beneficiaries",
    "blockchainFit": 4.5,
    "rationale": "Oracle-triggered smart contract payouts. Classic blockchain use case \u2014 automated, trustless, multi-party.",
    "signals": [
      {
        "q": "NGO-P2-CatA-Q31",
        "w": 0.9,
        "role": "need",
        "why": "Cash scarcity = insurance payouts critical"
      },
      {
        "q": "NGO-P2-CatA-Q30",
        "w": 0.8,
        "role": "fit_boost",
        "why": "Financial failure points = insurance need"
      },
      {
        "q": "NGO-P2-CatA-Q5",
        "w": 0.7,
        "role": "need",
        "why": "Difficult corridors affect insurance payouts"
      },
      {
        "q": "NGO-P2-CatA-Q1",
        "w": 0.6,
        "role": "readiness",
        "why": "Sophisticated financial process needed"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 3
  },
  "UC-A-023": {
    "name": "Community currencies and complementary currency systems",
    "blockchainFit": 4,
    "rationale": "Token-based community exchange. Natural blockchain application for creating trusted local currencies without central authority.",
    "signals": [
      {
        "q": "NGO-P2-CatA-Q31",
        "w": 1,
        "role": "need",
        "why": "Severe cash scarcity = community currency need"
      },
      {
        "q": "NGO-P2-CatA-Q5",
        "w": 0.7,
        "role": "need",
        "why": "No banking infrastructure = alternative needed"
      },
      {
        "q": "NGO-P2-CatA-Q4",
        "w": 0.5,
        "role": "need",
        "why": "High transaction costs justify alternatives"
      },
      {
        "q": "NGO-P2-CatA-Q1",
        "w": 0.5,
        "role": "readiness",
        "why": "Financial sophistication for currency design"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 3
  },
  "UC-B-024": {
    "name": "Beneficiary registration (refugees, stateless, undocumented)",
    "blockchainFit": 4.5,
    "rationale": "Multi-party (multiple NGOs + host govt + UNHCR). No single authority trusted. Cross-border portability. Classic decentralised identity case.",
    "signals": [
      {
        "q": "NGO-P2-CatB-Q1",
        "w": 1,
        "role": "need",
        "why": "% lacking ID = direct measure of registration gap"
      },
      {
        "q": "NGO-P2-CatB-Q1a",
        "w": 0.9,
        "role": "scale",
        "why": "Volume of beneficiaries to register"
      },
      {
        "q": "NGO-P2-CatB-Q1c",
        "w": 0.9,
        "role": "need",
        "why": "Duplicate rate = registration system failing"
      },
      {
        "q": "NGO-P2-CatB-Q9",
        "w": 0.8,
        "role": "need",
        "why": "Record continuity for displaced = portability need"
      },
      {
        "q": "NGO-P2-CatB-Q10",
        "w": 0.7,
        "role": "fit_boost",
        "why": "Cross-NGO data sharing = multi-party trust problem"
      },
      {
        "q": "NGO-P2-CatB-Q1b",
        "w": 0.6,
        "role": "need",
        "why": "Many systems = fragmented identity data"
      },
      {
        "q": "NGO-P2-CatB-Q3",
        "w": 0.5,
        "role": "readiness",
        "why": "Registration process maturity \u2014 but compensated by high need+scale"
      },
      {
        "q": "NGO-P2-CatB-Q8",
        "w": 0.7,
        "role": "need",
        "why": "High duplicate rate = deduplication needed"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 3
  },
  "UC-B-025": {
    "name": "Birth registration for children born in displacement",
    "blockchainFit": 4.3,
    "rationale": "Government systems inaccessible for displaced. Blockchain provides portable, verifiable birth record that transcends jurisdictions.",
    "signals": [
      {
        "q": "NGO-P2-CatB-Q1",
        "w": 0.9,
        "role": "need",
        "why": "High % lacking ID correlates with unregistered births"
      },
      {
        "q": "NGO-P2-CatB-Q9",
        "w": 1,
        "role": "need",
        "why": "Record portability critical for displaced children"
      },
      {
        "q": "NGO-P2-CatB-Q1a",
        "w": 0.6,
        "role": "scale",
        "why": "Population size indicates birth registration volume"
      },
      {
        "q": "NGO-P2-CatB-Q3",
        "w": 0.4,
        "role": "readiness",
        "why": "Digital process maturity for registration"
      },
      {
        "q": "NGO-P2-CatB-Q10",
        "w": 0.7,
        "role": "fit_boost",
        "why": "Cross-org sharing of birth records"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 2.5
  },
  "UC-B-026": {
    "name": "Death registration and inheritance documentation",
    "blockchainFit": 3.5,
    "rationale": "Important for inheritance/property but lower urgency than birth/beneficiary registration. Immutability valuable for legal claims.",
    "signals": [
      {
        "q": "NGO-P2-CatB-Q1",
        "w": 0.6,
        "role": "need",
        "why": "ID gap correlates with death registration gaps"
      },
      {
        "q": "NGO-P2-CatB-Q9",
        "w": 0.8,
        "role": "need",
        "why": "Portable records for inheritance claims across borders"
      },
      {
        "q": "NGO-P2-CatB-Q1b",
        "w": 0.5,
        "role": "need",
        "why": "Fragmented systems lose death records"
      },
      {
        "q": "NGO-P2-CatB-Q3",
        "w": 0.4,
        "role": "readiness",
        "why": "Registration process maturity"
      }
    ],
    "fitGate": 3,
    "readinessGate": 2
  },
  "UC-B-027": {
    "name": "Marriage and family status documentation",
    "blockchainFit": 3.2,
    "rationale": "Portable family status records for displaced populations. Useful but less urgent than core identity/registration.",
    "signals": [
      {
        "q": "NGO-P2-CatB-Q1",
        "w": 0.5,
        "role": "need",
        "why": "ID gap includes family documentation"
      },
      {
        "q": "NGO-P2-CatB-Q9",
        "w": 0.9,
        "role": "need",
        "why": "Family records lost in displacement"
      },
      {
        "q": "NGO-P2-CatB-Q1a",
        "w": 0.4,
        "role": "scale",
        "why": "Population size"
      },
      {
        "q": "NGO-P2-CatB-Q3",
        "w": 0.3,
        "role": "readiness",
        "why": "Process maturity"
      }
    ],
    "fitGate": 3,
    "readinessGate": 2
  },
  "UC-B-028": {
    "name": "Portable service history across borders and organisations",
    "blockchainFit": 4.5,
    "rationale": "Core decentralised identity use case \u2014 individual controls their service record, verifiable by any org without central database.",
    "signals": [
      {
        "q": "NGO-P2-CatB-Q9",
        "w": 1,
        "role": "need",
        "why": "Direct measure of record portability gap"
      },
      {
        "q": "NGO-P2-CatB-Q10",
        "w": 1,
        "role": "fit_boost",
        "why": "Cross-NGO sharing = multi-party trust problem"
      },
      {
        "q": "NGO-P2-CatB-Q10-FU",
        "w": 0.7,
        "role": "fit_boost",
        "why": "Sharing method problems"
      },
      {
        "q": "NGO-P2-CatB-Q1c",
        "w": 0.8,
        "role": "need",
        "why": "Duplicates across systems = no shared history"
      },
      {
        "q": "NGO-P2-CatB-Q1b",
        "w": 0.7,
        "role": "need",
        "why": "Multiple systems = fragmented service records"
      },
      {
        "q": "NGO-P2-CatB-Q1a",
        "w": 0.6,
        "role": "scale",
        "why": "Population size needing portable records"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 3
  },
  "UC-B-029": {
    "name": "Staff credential verification across jurisdictions",
    "blockchainFit": 3,
    "rationale": "Verifiable credentials for staff across countries. Useful but traditional HR systems handle this for single-org. Multi-org federations benefit more.",
    "signals": [
      {
        "q": "NGO-P2-CatB-Q28",
        "w": 0.7,
        "role": "need",
        "why": "Key staff departure as failure point = credential continuity need"
      },
      {
        "q": "NGO-P2-CatB-Q1b",
        "w": 0.5,
        "role": "need",
        "why": "Multiple systems = fragmented staff records"
      },
      {
        "q": "NGO-P2-CatB-Q10",
        "w": 0.6,
        "role": "fit_boost",
        "why": "Cross-org credential sharing"
      },
      {
        "q": "NGO-P2-CatB-Q3",
        "w": 0.4,
        "role": "readiness",
        "why": "Digital process maturity"
      }
    ],
    "fitGate": 3,
    "readinessGate": 2
  },
  "UC-B-030": {
    "name": "Volunteer identity and background verification",
    "blockchainFit": 2.8,
    "rationale": "Background checks can be centralized. Blockchain adds value for cross-org volunteer verification but most orgs manage internally.",
    "signals": [
      {
        "q": "NGO-P2-CatB-Q1b",
        "w": 0.5,
        "role": "need",
        "why": "Multiple systems = no unified volunteer record"
      },
      {
        "q": "NGO-P2-CatB-Q28",
        "w": 0.5,
        "role": "need",
        "why": "System failure could lose volunteer records"
      },
      {
        "q": "NGO-P2-CatB-Q10",
        "w": 0.5,
        "role": "fit_boost",
        "why": "Cross-org volunteer sharing"
      },
      {
        "q": "NGO-P2-CatB-Q3",
        "w": 0.3,
        "role": "readiness",
        "why": "Digital verification capability"
      }
    ],
    "fitGate": 3,
    "readinessGate": 1.5
  },
  "UC-B-031": {
    "name": "Health worker and teacher certification verification",
    "blockchainFit": 3.5,
    "rationale": "Verifiable credentials across borders. Strong case when health workers/teachers move between countries and credentials aren't recognized.",
    "signals": [
      {
        "q": "NGO-P2-CatB-Q9",
        "w": 0.9,
        "role": "need",
        "why": "Credential portability across borders"
      },
      {
        "q": "NGO-P2-CatB-Q28",
        "w": 0.6,
        "role": "need",
        "why": "System failure risks credential loss"
      },
      {
        "q": "NGO-P2-CatB-Q10",
        "w": 0.7,
        "role": "fit_boost",
        "why": "Cross-org credential verification"
      },
      {
        "q": "NGO-P2-CatB-Q1a",
        "w": 0.4,
        "role": "scale",
        "why": "Scale indicates number of credentials"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 2.5
  },
  "UC-B-032": {
    "name": "Implementing partner staff verification",
    "blockchainFit": 3.2,
    "rationale": "Verifying partner staff credentials and safeguarding clearances. Multi-party trust relevant when partners operate independently.",
    "signals": [
      {
        "q": "NGO-P2-CatB-Q10",
        "w": 0.8,
        "role": "need",
        "why": "Partner coordination = need for shared verification"
      },
      {
        "q": "NGO-P2-CatB-Q10-FU",
        "w": 0.7,
        "role": "need",
        "why": "Data sharing challenges with partners"
      },
      {
        "q": "NGO-P2-CatB-Q28",
        "w": 0.5,
        "role": "need",
        "why": "System failure risks"
      },
      {
        "q": "NGO-P2-CatB-Q1b",
        "w": 0.4,
        "role": "scale",
        "why": "Multiple systems = verification complexity"
      }
    ],
    "fitGate": 3,
    "readinessGate": 2,
    "interagency": true
  },
  "UC-B-033": {
    "name": "Educational credentials for displaced students",
    "blockchainFit": 4.2,
    "rationale": "Students crossing borders lose educational records. Blockchain provides portable, verifiable credentials that any institution can check.",
    "signals": [
      {
        "q": "NGO-P2-CatB-Q9",
        "w": 1,
        "role": "need",
        "why": "Record portability for displaced students"
      },
      {
        "q": "NGO-P2-CatB-Q1",
        "w": 0.7,
        "role": "need",
        "why": "ID gap affects credential recognition"
      },
      {
        "q": "NGO-P2-CatB-Q10",
        "w": 0.8,
        "role": "fit_boost",
        "why": "Cross-institution credential verification"
      },
      {
        "q": "NGO-P2-CatB-Q1a",
        "w": 0.5,
        "role": "scale",
        "why": "Number of displaced students"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 2.5
  },
  "UC-B-034": {
    "name": "Vocational training certificates",
    "blockchainFit": 3.5,
    "rationale": "Portable verifiable certificates. Blockchain ensures certificates can't be forged and are verifiable by any employer.",
    "signals": [
      {
        "q": "NGO-P2-CatB-Q9",
        "w": 0.9,
        "role": "need",
        "why": "Certificate portability across borders"
      },
      {
        "q": "NGO-P2-CatB-Q10",
        "w": 0.7,
        "role": "fit_boost",
        "why": "Cross-org certificate verification"
      },
      {
        "q": "NGO-P2-CatB-Q1a",
        "w": 0.4,
        "role": "scale",
        "why": "Number of trainees"
      },
      {
        "q": "NGO-P2-CatB-Q3",
        "w": 0.3,
        "role": "readiness",
        "why": "Digital certificate issuance capability"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 2
  },
  "UC-B-035": {
    "name": "Skills attestation and competency verification",
    "blockchainFit": 3.3,
    "rationale": "Verifiable skills records. Similar to vocational certs but more granular. Valuable in refugee employment contexts.",
    "signals": [
      {
        "q": "NGO-P2-CatB-Q9",
        "w": 0.8,
        "role": "need",
        "why": "Skills records lost in displacement"
      },
      {
        "q": "NGO-P2-CatB-Q1",
        "w": 0.5,
        "role": "need",
        "why": "ID gap affects skill recognition"
      },
      {
        "q": "NGO-P2-CatB-Q10",
        "w": 0.6,
        "role": "fit_boost",
        "why": "Cross-org skills verification"
      },
      {
        "q": "NGO-P2-CatB-Q1a",
        "w": 0.4,
        "role": "scale",
        "why": "Population needing attestation"
      }
    ],
    "fitGate": 3,
    "readinessGate": 2
  },
  "UC-B-036": {
    "name": "Community governance participation eligibility",
    "blockchainFit": 3,
    "rationale": "Proving community membership/eligibility for governance roles. Blockchain prevents double-voting and ensures transparency.",
    "signals": [
      {
        "q": "NGO-P2-CatB-Q1",
        "w": 0.6,
        "role": "need",
        "why": "ID gap affects governance participation"
      },
      {
        "q": "NGO-P2-CatB-Q1c",
        "w": 0.7,
        "role": "need",
        "why": "Duplicates enable governance manipulation"
      },
      {
        "q": "NGO-P2-CatB-Q10",
        "w": 0.5,
        "role": "fit_boost",
        "why": "Multi-party governance verification"
      },
      {
        "q": "NGO-P2-CatB-Q3",
        "w": 0.3,
        "role": "readiness",
        "why": "Digital registration capability"
      }
    ],
    "fitGate": 3,
    "readinessGate": 2
  },
  "UC-B-037": {
    "name": "Consent records and data sharing permissions",
    "blockchainFit": 3.8,
    "rationale": "Beneficiary-controlled consent that multiple orgs can check without central authority. Strong blockchain case for GDPR/data protection compliance.",
    "signals": [
      {
        "q": "NGO-P2-CatB-Q10",
        "w": 1,
        "role": "need",
        "why": "Data sharing with other NGOs = consent management critical"
      },
      {
        "q": "NGO-P2-CatB-Q6",
        "w": 0.7,
        "role": "need",
        "why": "Biometric data use heightens consent importance"
      },
      {
        "q": "NGO-P2-CatB-Q6-FU",
        "w": 0.8,
        "role": "need",
        "why": "Data protection concerns = consent management gap"
      },
      {
        "q": "NGO-P2-CatB-Q1b",
        "w": 0.6,
        "role": "fit_boost",
        "why": "Multiple systems = consent needs to span systems"
      },
      {
        "q": "NGO-P2-CatB-Q1a",
        "w": 0.5,
        "role": "scale",
        "why": "Volume of consent records to manage"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 3
  },
  "UC-B-038": {
    "name": "Age verification for child protection programmes",
    "blockchainFit": 3.5,
    "rationale": "Privacy-preserving age verification without revealing full identity. Zero-knowledge proofs on blockchain.",
    "signals": [
      {
        "q": "NGO-P2-CatB-Q1",
        "w": 0.8,
        "role": "need",
        "why": "ID gap = no reliable age documents"
      },
      {
        "q": "NGO-P2-CatB-Q1a",
        "w": 0.5,
        "role": "scale",
        "why": "Number of children in programmes"
      },
      {
        "q": "NGO-P2-CatB-Q6",
        "w": 0.6,
        "role": "fit_boost",
        "why": "Biometric use for age verification"
      },
      {
        "q": "NGO-P2-CatB-Q3",
        "w": 0.4,
        "role": "readiness",
        "why": "Digital verification capability"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 2.5
  },
  "UC-C-039": {
    "name": "Medical records (private but verifiable)",
    "blockchainFit": 4,
    "rationale": "Patient controls access to records. Multiple healthcare providers need to verify without central database. Privacy + multi-party.",
    "signals": [
      {
        "q": "NGO-P2-CatC-Q1",
        "w": 0.9,
        "role": "need",
        "why": "Fragmented data governance = records scattered"
      },
      {
        "q": "NGO-P2-CatC-Q3",
        "w": 0.8,
        "role": "need",
        "why": "Multiple systems = fragmented medical records"
      },
      {
        "q": "NGO-P2-CatC-Q8",
        "w": 0.9,
        "role": "need",
        "why": "Poor audit visibility = data access risks"
      },
      {
        "q": "NGO-P2-CatC-Q4",
        "w": 0.7,
        "role": "need",
        "why": "Conflicting data resolution = records unreliable"
      },
      {
        "q": "NGO-P2-CatC-Q7",
        "w": 0.6,
        "role": "fit_boost",
        "why": "Partner data reconciliation = multi-party challenge"
      },
      {
        "q": "NGO-P2-CatC-Q9",
        "w": 0.5,
        "role": "fit_boost",
        "why": "Data management failure points"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 3
  },
  "UC-C-040": {
    "name": "Vaccination history and immunisation records",
    "blockchainFit": 4.2,
    "rationale": "Portable vaccination records that any healthcare provider can verify. WHO Digital Health initiatives align. Cross-border critical.",
    "signals": [
      {
        "q": "NGO-P2-CatC-Q1",
        "w": 0.8,
        "role": "need",
        "why": "Fragmented data = lost vaccination records"
      },
      {
        "q": "NGO-P2-CatC-Q3",
        "w": 0.9,
        "role": "need",
        "why": "Multiple systems = immunization records scattered"
      },
      {
        "q": "NGO-P2-CatC-Q7",
        "w": 0.8,
        "role": "fit_boost",
        "why": "Partner data sharing for immunization campaigns"
      },
      {
        "q": "NGO-P2-CatC-Q5",
        "w": 0.6,
        "role": "need",
        "why": "Duplicate detection = double-vaccination risk"
      },
      {
        "q": "NGO-P2-CatC-Q8",
        "w": 0.5,
        "role": "need",
        "why": "Audit trail for vaccine administration"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 2.5
  },
  "UC-C-041": {
    "name": "Mental health and psychosocial support records",
    "blockchainFit": 3.5,
    "rationale": "Highly sensitive data requiring strong privacy controls. Blockchain adds encryption + access control but fewer multi-party needs than medical records.",
    "signals": [
      {
        "q": "NGO-P2-CatC-Q8",
        "w": 1,
        "role": "need",
        "why": "Data access visibility critical for sensitive MHPSS data"
      },
      {
        "q": "NGO-P2-CatC-Q1",
        "w": 0.7,
        "role": "need",
        "why": "Governance approach for sensitive data"
      },
      {
        "q": "NGO-P2-CatC-Q9",
        "w": 0.7,
        "role": "fit_boost",
        "why": "Data breach/cyber risk for MHPSS records"
      },
      {
        "q": "NGO-P2-CatC-Q4",
        "w": 0.5,
        "role": "need",
        "why": "Conflicting records = treatment continuity risks"
      }
    ],
    "fitGate": 3,
    "readinessGate": 3
  },
  "UC-C-042": {
    "name": "GBV and protection case data",
    "blockchainFit": 3.8,
    "rationale": "Extremely sensitive. Immutable audit trail critical for accountability. Access control essential. Multi-org referral chains.",
    "signals": [
      {
        "q": "NGO-P2-CatC-Q8",
        "w": 1,
        "role": "need",
        "why": "Audit visibility critical \u2014 who accessed GBV data"
      },
      {
        "q": "NGO-P2-CatC-Q1",
        "w": 0.8,
        "role": "need",
        "why": "Data governance for protection data"
      },
      {
        "q": "NGO-P2-CatC-Q7",
        "w": 0.7,
        "role": "fit_boost",
        "why": "Inter-agency referral data sharing"
      },
      {
        "q": "NGO-P2-CatC-Q9",
        "w": 0.8,
        "role": "fit_boost",
        "why": "Failure point = catastrophic for protection data"
      },
      {
        "q": "NGO-P2-CatC-Q4",
        "w": 0.6,
        "role": "need",
        "why": "Conflicting case data across providers"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 3.5
  },
  "UC-C-043": {
    "name": "Beneficiary deduplication across programmes and organisations",
    "blockchainFit": 4.5,
    "rationale": "Core multi-party problem \u2014 orgs need to dedup without sharing full datasets. Privacy-preserving matching on blockchain is ideal.",
    "signals": [
      {
        "q": "NGO-P2-CatC-Q5",
        "w": 1,
        "role": "need",
        "why": "Duplicate detection frequency = direct dedup need"
      },
      {
        "q": "NGO-P2-CatC-Q3",
        "w": 0.9,
        "role": "need",
        "why": "Multiple systems = dedup across systems needed"
      },
      {
        "q": "NGO-P2-CatC-Q7",
        "w": 0.9,
        "role": "fit_boost",
        "why": "Partner data reconciliation = cross-org dedup"
      },
      {
        "q": "NGO-P2-CatC-Q1",
        "w": 0.7,
        "role": "need",
        "why": "Fragmented governance = duplicates proliferate"
      },
      {
        "q": "NGO-P2-CatC-Q4",
        "w": 0.8,
        "role": "need",
        "why": "Conflicting data = dedup resolution hard"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 3,
    "interagency": true
  },
  "UC-C-044": {
    "name": "Impact data integrity and verification",
    "blockchainFit": 3.8,
    "rationale": "Donors need to trust impact data. Blockchain timestamps and immutability prevent retroactive manipulation.",
    "signals": [
      {
        "q": "NGO-P2-CatC-Q8",
        "w": 0.9,
        "role": "need",
        "why": "Poor audit trail = impact data unreliable"
      },
      {
        "q": "NGO-P2-CatC-Q7",
        "w": 0.8,
        "role": "need",
        "why": "Donor data reconciliation challenges"
      },
      {
        "q": "NGO-P2-CatC-Q7-FU",
        "w": 0.7,
        "role": "need",
        "why": "Specific reconciliation challenge types"
      },
      {
        "q": "NGO-P2-CatC-Q1",
        "w": 0.6,
        "role": "need",
        "why": "Data governance for impact metrics"
      },
      {
        "q": "NGO-P2-CatC-Q4",
        "w": 0.5,
        "role": "need",
        "why": "Conflicting impact data across sources"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 2.5
  },
  "UC-C-045": {
    "name": "Consent management and audit trails",
    "blockchainFit": 4,
    "rationale": "Beneficiary-controlled consent records. Multiple orgs check consent without central authority. GDPR alignment.",
    "signals": [
      {
        "q": "NGO-P2-CatC-Q8",
        "w": 1,
        "role": "need",
        "why": "Audit visibility = who accessed what with what consent"
      },
      {
        "q": "NGO-P2-CatC-Q7",
        "w": 0.8,
        "role": "fit_boost",
        "why": "Partner data sharing requires consent tracking"
      },
      {
        "q": "NGO-P2-CatC-Q1",
        "w": 0.7,
        "role": "need",
        "why": "Data governance maturity for consent"
      },
      {
        "q": "NGO-P2-CatC-Q3",
        "w": 0.5,
        "role": "need",
        "why": "Multiple systems need coordinated consent"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 3
  },
  "UC-C-046": {
    "name": "Inter-agency data sharing without centralisation",
    "blockchainFit": 4.8,
    "rationale": "THE blockchain sweet spot \u2014 multiple independent agencies share data without any one controlling it. Decentralisation is the whole point.",
    "signals": [
      {
        "q": "NGO-P2-CatC-Q3",
        "w": 1,
        "role": "need",
        "why": "Multiple systems with no shared truth \u2014 strong inter-agency surfacing signal even when partner reconciliation isn't acknowledged explicitly"
      },
      {
        "q": "NGO-P2-CatC-Q7",
        "w": 0.8,
        "role": "fit_boost",
        "why": "Partner data reconciliation acknowledged \u2014 amplifies fit when present but does not gate surfacing (UN/mature agencies often answer 'No' even when friction exists underneath)"
      },
      {
        "q": "NGO-P2-CatC-Q7-FU",
        "w": 0.9,
        "role": "need",
        "why": "Specific sharing challenges"
      },
      {
        "q": "NGO-P2-CatC-Q1",
        "w": 0.7,
        "role": "need",
        "why": "Fragmented governance = need for shared layer"
      },
      {
        "q": "NGO-P2-CatC-Q8",
        "w": 0.6,
        "role": "need",
        "why": "Audit trail for shared data access"
      },
      {
        "q": "NGO-P2-CatC-Q9",
        "w": 0.5,
        "role": "fit_boost",
        "why": "Single point of failure = decentralisation case"
      }
    ],
    "fitGate": 1.5,
    "readinessGate": 3.5,
    "interagency": true
  },
  "UC-C-047": {
    "name": "Referral pathway tracking across service providers",
    "blockchainFit": 4,
    "rationale": "Multi-provider referral chains where each provider needs to verify referral source and update status. Multi-party workflow.",
    "signals": [
      {
        "q": "NGO-P2-CatC-Q7",
        "w": 0.9,
        "role": "need",
        "why": "Partner coordination for referrals"
      },
      {
        "q": "NGO-P2-CatC-Q4",
        "w": 0.8,
        "role": "need",
        "why": "Conflicting referral data across providers"
      },
      {
        "q": "NGO-P2-CatC-Q3",
        "w": 0.7,
        "role": "need",
        "why": "Multiple systems = referrals get lost"
      },
      {
        "q": "NGO-P2-CatC-Q5",
        "w": 0.6,
        "role": "need",
        "why": "Duplicate detection in referral chains"
      },
      {
        "q": "NGO-P2-CatC-Q8",
        "w": 0.5,
        "role": "need",
        "why": "Audit trail for referral outcomes"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 3,
    "interagency": true
  },
  "UC-C-048": {
    "name": "Audit trail maintenance for compliance",
    "blockchainFit": 3.5,
    "rationale": "Immutable audit logs. Blockchain ensures logs can't be tampered with retroactively. Valuable for regulated environments.",
    "signals": [
      {
        "q": "NGO-P2-CatC-Q8",
        "w": 1,
        "role": "need",
        "why": "Direct audit visibility gap"
      },
      {
        "q": "NGO-P2-CatC-Q1",
        "w": 0.6,
        "role": "need",
        "why": "Governance approach affects audit capability"
      },
      {
        "q": "NGO-P2-CatC-Q9",
        "w": 0.7,
        "role": "fit_boost",
        "why": "Data failure points = audit trail critical"
      },
      {
        "q": "NGO-P2-CatC-Q7",
        "w": 0.4,
        "role": "scale",
        "why": "Partner compliance adds audit complexity"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 2.5
  },
  "UC-C-049": {
    "name": "Research data with beneficiary privacy protection",
    "blockchainFit": 3,
    "rationale": "Privacy-preserving research data. Blockchain can enable controlled access without full data exposure. Niche use case.",
    "signals": [
      {
        "q": "NGO-P2-CatC-Q8",
        "w": 0.8,
        "role": "need",
        "why": "Research data access control"
      },
      {
        "q": "NGO-P2-CatC-Q1",
        "w": 0.6,
        "role": "need",
        "why": "Data governance for research data"
      },
      {
        "q": "NGO-P2-CatC-Q7",
        "w": 0.5,
        "role": "fit_boost",
        "why": "Research data sharing with external parties"
      },
      {
        "q": "NGO-P2-CatC-Q9",
        "w": 0.4,
        "role": "need",
        "why": "Research data vulnerability"
      }
    ],
    "fitGate": 3,
    "readinessGate": 3
  },
  "UC-C-050": {
    "name": "Beneficiary feedback data integrity",
    "blockchainFit": 3.2,
    "rationale": "Immutable feedback records that can't be manipulated by staff. Valuable for accountability but lower priority than core data management.",
    "signals": [
      {
        "q": "NGO-P2-CatC-Q8",
        "w": 0.8,
        "role": "need",
        "why": "Audit trail for feedback = prevent manipulation"
      },
      {
        "q": "NGO-P2-CatC-Q4",
        "w": 0.6,
        "role": "need",
        "why": "Conflicting feedback data"
      },
      {
        "q": "NGO-P2-CatC-Q1",
        "w": 0.5,
        "role": "need",
        "why": "Data governance for feedback"
      },
      {
        "q": "NGO-P2-CatC-Q7",
        "w": 0.4,
        "role": "fit_boost",
        "why": "Feedback shared with partners/donors"
      }
    ],
    "fitGate": 3,
    "readinessGate": 2
  },
  "UC-C-051": {
    "name": "Needs assessment data integrity",
    "blockchainFit": 3,
    "rationale": "Preventing manipulation of needs assessments that drive resource allocation. Important but centralised solutions often sufficient.",
    "signals": [
      {
        "q": "NGO-P2-CatC-Q8",
        "w": 0.7,
        "role": "need",
        "why": "Audit trail for assessment data"
      },
      {
        "q": "NGO-P2-CatC-Q4",
        "w": 0.7,
        "role": "need",
        "why": "Conflicting assessment data"
      },
      {
        "q": "NGO-P2-CatC-Q7",
        "w": 0.6,
        "role": "fit_boost",
        "why": "Assessment data shared across agencies"
      },
      {
        "q": "NGO-P2-CatC-Q1",
        "w": 0.5,
        "role": "need",
        "why": "Data governance for assessments"
      }
    ],
    "fitGate": 3,
    "readinessGate": 2
  },
  "UC-D-052": {
    "name": "Medicine authenticity verification (anti-counterfeiting)",
    "blockchainFit": 4.5,
    "rationale": "Multi-party supply chain \u2014 manufacturer, distributor, warehouse, field. Blockchain provenance prevents counterfeit medicines entering supply chain.",
    "signals": [
      {
        "q": "NGO-P2-CatD-Q5",
        "w": 1,
        "role": "need",
        "why": "Counterfeit/quality issues = direct need for authentication"
      },
      {
        "q": "NGO-P2-CatD-Q5-FU",
        "w": 0.9,
        "role": "need",
        "why": "Severity of quality/counterfeit incidents"
      },
      {
        "q": "NGO-P2-CatD-Q4",
        "w": 0.8,
        "role": "need",
        "why": "Poor tracking = can't verify medicine journey"
      },
      {
        "q": "NGO-P2-CatD-Q1",
        "w": 0.6,
        "role": "scale",
        "why": "More supply chain tiers = more counterfeit entry points"
      },
      {
        "q": "NGO-P2-CatD-Q1a",
        "w": 0.7,
        "role": "scale",
        "why": "Transaction volume"
      },
      {
        "q": "NGO-P2-CatD-Q7",
        "w": 0.5,
        "role": "need",
        "why": "Cold chain capability affects medicine handling"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 2.5
  },
  "UC-D-053": {
    "name": "Vaccine cold chain monitoring and verification",
    "blockchainFit": 4.3,
    "rationale": "IoT sensors + blockchain = immutable temperature records through supply chain. Multi-party verification of cold chain integrity.",
    "signals": [
      {
        "q": "NGO-P2-CatD-Q7",
        "w": 1,
        "role": "need",
        "why": "Cold chain capability gap = direct need"
      },
      {
        "q": "NGO-P2-CatD-Q7-FU",
        "w": 0.9,
        "role": "need",
        "why": "Cold chain capability details"
      },
      {
        "q": "NGO-P2-CatD-Q4",
        "w": 0.7,
        "role": "need",
        "why": "Tracking gaps = temperature excursions undetected"
      },
      {
        "q": "NGO-P2-CatD-Q5",
        "w": 0.6,
        "role": "need",
        "why": "Quality failures from cold chain breaks"
      },
      {
        "q": "NGO-P2-CatD-Q1a",
        "w": 0.5,
        "role": "scale",
        "why": "Volume of cold chain shipments"
      },
      {
        "q": "NGO-P2-CatD-Q1b",
        "w": 0.6,
        "role": "need",
        "why": "High problem rate = cold chain failing"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 3
  },
  "UC-D-055": {
    "name": "Nutrition supplement tracking",
    "blockchainFit": 3.5,
    "rationale": "Sensitive supplements require provenance verification and expiry tracking. Multi-party when distributed through partners.",
    "signals": [
      {
        "q": "NGO-P2-CatD-Q5",
        "w": 0.9,
        "role": "need",
        "why": "Quality/counterfeit risk for nutritional products"
      },
      {
        "q": "NGO-P2-CatD-Q4",
        "w": 0.7,
        "role": "need",
        "why": "Tracking gaps in supplement distribution"
      },
      {
        "q": "NGO-P2-CatD-Q7",
        "w": 0.6,
        "role": "need",
        "why": "Temperature sensitivity of some supplements"
      },
      {
        "q": "NGO-P2-CatD-Q1b",
        "w": 0.5,
        "role": "need",
        "why": "Distribution problem rate"
      }
    ],
    "fitGate": 3,
    "readinessGate": 2
  },
  "UC-D-056": {
    "name": "Food aid tracking from source to beneficiary",
    "blockchainFit": 4,
    "rationale": "Multi-party chain (donor + procurement + warehouse + transport + distribution). Diversion is a major problem. Blockchain provides verifiable trail.",
    "signals": [
      {
        "q": "NGO-P2-CatD-Q4",
        "w": 1,
        "role": "need",
        "why": "Tracking gaps = food aid diversion undetected"
      },
      {
        "q": "NGO-P2-CatD-Q1b",
        "w": 0.9,
        "role": "need",
        "why": "High loss/damage rate = diversion or mishandling"
      },
      {
        "q": "NGO-P2-CatD-Q8",
        "w": 0.8,
        "role": "fit_boost",
        "why": "Last-mile delivery failure = accountability gap"
      },
      {
        "q": "NGO-P2-CatD-Q1a",
        "w": 0.7,
        "role": "scale",
        "why": "Volume of food distributions"
      },
      {
        "q": "NGO-P2-CatD-Q1",
        "w": 0.6,
        "role": "scale",
        "why": "Supply chain tiers for food"
      },
      {
        "q": "NGO-P2-CatD-Q1c",
        "w": 0.5,
        "role": "scale",
        "why": "Number of partners in food chain"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 2.5,
    "interagency": true
  },
  "UC-D-057": {
    "name": "Donated goods provenance verification",
    "blockchainFit": 3.8,
    "rationale": "Proving donated goods came from claimed source. Relevant for compliance and donor accountability.",
    "signals": [
      {
        "q": "NGO-P2-CatD-Q5",
        "w": 0.9,
        "role": "need",
        "why": "Counterfeit/quality concerns in donations"
      },
      {
        "q": "NGO-P2-CatD-Q4",
        "w": 0.8,
        "role": "need",
        "why": "Tracking gap = can't verify provenance"
      },
      {
        "q": "NGO-P2-CatD-Q1",
        "w": 0.5,
        "role": "scale",
        "why": "Supply chain depth"
      },
      {
        "q": "NGO-P2-CatD-Q1c",
        "w": 0.5,
        "role": "fit_boost",
        "why": "Multiple partners in donation chain"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 2
  },
  "UC-D-058": {
    "name": "In-kind donation tracking and valuation",
    "blockchainFit": 3.2,
    "rationale": "Immutable record of donated goods values. Useful for tax receipts and donor reporting. Lower multi-party complexity.",
    "signals": [
      {
        "q": "NGO-P2-CatD-Q4",
        "w": 0.7,
        "role": "need",
        "why": "Tracking gaps in donations"
      },
      {
        "q": "NGO-P2-CatD-Q1a",
        "w": 0.5,
        "role": "scale",
        "why": "Volume of donations"
      },
      {
        "q": "NGO-P2-CatD-Q8",
        "w": 0.4,
        "role": "need",
        "why": "Failure point in donation chain"
      }
    ],
    "fitGate": 3,
    "readinessGate": 2
  },
  "UC-D-059": {
    "name": "Shelter materials and NFI tracking",
    "blockchainFit": 3.5,
    "rationale": "Non-food item tracking through multi-org distribution. Blockchain ensures accountability in NFI supply chain.",
    "signals": [
      {
        "q": "NGO-P2-CatD-Q4",
        "w": 0.8,
        "role": "need",
        "why": "NFI tracking gaps"
      },
      {
        "q": "NGO-P2-CatD-Q1b",
        "w": 0.7,
        "role": "need",
        "why": "Loss/damage rate for shelter materials"
      },
      {
        "q": "NGO-P2-CatD-Q8",
        "w": 0.6,
        "role": "fit_boost",
        "why": "Last-mile delivery verification"
      },
      {
        "q": "NGO-P2-CatD-Q1a",
        "w": 0.5,
        "role": "scale",
        "why": "Volume of NFI distributions"
      }
    ],
    "fitGate": 3,
    "readinessGate": 2
  },
  "UC-D-060": {
    "name": "WASH supplies verification",
    "blockchainFit": 3.5,
    "rationale": "Water/sanitation supply authenticity. Counterfeit water purification products are dangerous. Multi-party supply chain.",
    "signals": [
      {
        "q": "NGO-P2-CatD-Q5",
        "w": 1,
        "role": "need",
        "why": "Counterfeit WASH supplies are health-critical"
      },
      {
        "q": "NGO-P2-CatD-Q4",
        "w": 0.7,
        "role": "need",
        "why": "Tracking WASH supply journey"
      },
      {
        "q": "NGO-P2-CatD-Q5-FU",
        "w": 0.8,
        "role": "need",
        "why": "Quality failure details for WASH"
      },
      {
        "q": "NGO-P2-CatD-Q1b",
        "w": 0.5,
        "role": "need",
        "why": "Problem rate in WASH supply chain"
      }
    ],
    "fitGate": 3,
    "readinessGate": 2
  },
  "UC-D-061": {
    "name": "Equipment and asset lifecycle tracking",
    "blockchainFit": 2.5,
    "rationale": "Single-org asset management. ERP systems handle this. Blockchain only adds value for multi-org shared equipment.",
    "signals": [
      {
        "q": "NGO-P2-CatD-Q4",
        "w": 0.6,
        "role": "need",
        "why": "Equipment tracking gaps"
      },
      {
        "q": "NGO-P2-CatD-Q1a",
        "w": 0.4,
        "role": "scale",
        "why": "Volume of assets"
      },
      {
        "q": "NGO-P2-CatD-Q8",
        "w": 0.4,
        "role": "need",
        "why": "Asset loss as failure point"
      },
      {
        "q": "NGO-P2-CatD-Q1c",
        "w": 0.3,
        "role": "fit_boost",
        "why": "Shared equipment across partners"
      }
    ],
    "fitGate": 3.5,
    "readinessGate": 2
  },
  "UC-D-062": {
    "name": "Fleet and vehicle management",
    "blockchainFit": 2,
    "rationale": "Internal fleet tracking. GPS and fleet management software handles this well. Low multi-party need.",
    "signals": [
      {
        "q": "NGO-P2-CatD-Q4",
        "w": 0.5,
        "role": "need",
        "why": "Vehicle tracking gaps"
      },
      {
        "q": "NGO-P2-CatD-Q8",
        "w": 0.4,
        "role": "need",
        "why": "Fleet as failure point"
      },
      {
        "q": "NGO-P2-CatD-Q1a",
        "w": 0.3,
        "role": "scale",
        "why": "Fleet size proxy"
      }
    ],
    "fitGate": 3.5,
    "readinessGate": 2
  },
  "UC-D-063": {
    "name": "Last-mile delivery verification",
    "blockchainFit": 4.2,
    "rationale": "Critical accountability gap \u2014 proving goods actually reached beneficiaries. Multi-party (org + transporter + community leader + beneficiary).",
    "signals": [
      {
        "q": "NGO-P2-CatD-Q8",
        "w": 1,
        "role": "need",
        "why": "Last-mile delivery as biggest failure point"
      },
      {
        "q": "NGO-P2-CatD-Q4",
        "w": 0.9,
        "role": "need",
        "why": "Tracking gap at last mile"
      },
      {
        "q": "NGO-P2-CatD-Q1b",
        "w": 0.8,
        "role": "need",
        "why": "High problem rate at delivery"
      },
      {
        "q": "NGO-P2-CatD-Q1a",
        "w": 0.6,
        "role": "scale",
        "why": "Volume of last-mile deliveries"
      },
      {
        "q": "NGO-P2-CatD-Q1c",
        "w": 0.5,
        "role": "fit_boost",
        "why": "Multiple partners in delivery chain"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 2.5
  },
  "UC-D-064": {
    "name": "Local procurement verification",
    "blockchainFit": 3.5,
    "rationale": "Verifying locally procured goods meet standards. Multi-party (local vendors + org + quality inspectors).",
    "signals": [
      {
        "q": "NGO-P2-CatD-Q5",
        "w": 0.9,
        "role": "need",
        "why": "Quality/counterfeit in local procurement"
      },
      {
        "q": "NGO-P2-CatD-Q9",
        "w": 0.7,
        "role": "need",
        "why": "Local producer verification"
      },
      {
        "q": "NGO-P2-CatD-Q4",
        "w": 0.6,
        "role": "need",
        "why": "Procurement tracking gaps"
      },
      {
        "q": "NGO-P2-CatD-Q8",
        "w": 0.5,
        "role": "fit_boost",
        "why": "Procurement fraud as failure point"
      }
    ],
    "fitGate": 3,
    "readinessGate": 2
  },
  "UC-D-065": {
    "name": "Warehouse inventory management",
    "blockchainFit": 2.2,
    "rationale": "Single-location inventory management. WMS software handles this. Blockchain only relevant for multi-party shared warehouses.",
    "signals": [
      {
        "q": "NGO-P2-CatD-Q4",
        "w": 0.6,
        "role": "need",
        "why": "Inventory tracking capability"
      },
      {
        "q": "NGO-P2-CatD-Q8",
        "w": 0.5,
        "role": "need",
        "why": "Warehouse loss as failure point"
      },
      {
        "q": "NGO-P2-CatD-Q1a",
        "w": 0.4,
        "role": "scale",
        "why": "Inventory volume"
      },
      {
        "q": "NGO-P2-CatD-Q1c",
        "w": 0.4,
        "role": "fit_boost",
        "why": "Shared warehouse with partners"
      }
    ],
    "fitGate": 3.5,
    "readinessGate": 2
  },
  "UC-D-066": {
    "name": "Expiry tracking and waste reduction",
    "blockchainFit": 2.8,
    "rationale": "FIFO/FEFO management. Standard supply chain tools handle this but blockchain adds cross-org coordination for surplus redistribution.",
    "signals": [
      {
        "q": "NGO-P2-CatD-Q4",
        "w": 0.7,
        "role": "need",
        "why": "Tracking gaps lead to expired stock"
      },
      {
        "q": "NGO-P2-CatD-Q7",
        "w": 0.6,
        "role": "need",
        "why": "Cold chain gaps accelerate expiry"
      },
      {
        "q": "NGO-P2-CatD-Q1a",
        "w": 0.5,
        "role": "scale",
        "why": "Volume of perishable supplies"
      },
      {
        "q": "NGO-P2-CatD-Q1c",
        "w": 0.4,
        "role": "fit_boost",
        "why": "Multiple partners for surplus redistribution"
      }
    ],
    "fitGate": 3,
    "readinessGate": 2
  },
  "UC-D-067": {
    "name": "Smallholder farmer market access and fair trade verification",
    "blockchainFit": 4.3,
    "rationale": "Multi-party provenance chain (farmer + cooperative + buyer + certifier). Blockchain enables direct market access with verifiable fair trade claims.",
    "signals": [
      {
        "q": "NGO-P2-CatD-Q9",
        "w": 1,
        "role": "need",
        "why": "Direct smallholder producer verification need"
      },
      {
        "q": "NGO-P2-CatD-Q5",
        "w": 0.8,
        "role": "need",
        "why": "Quality/authenticity issues in ag products"
      },
      {
        "q": "NGO-P2-CatD-Q4",
        "w": 0.7,
        "role": "need",
        "why": "Farm-to-market tracking gaps"
      },
      {
        "q": "NGO-P2-CatD-Q1",
        "w": 0.6,
        "role": "scale",
        "why": "Supply chain depth for agricultural products"
      },
      {
        "q": "NGO-P2-CatD-Q1c",
        "w": 0.7,
        "role": "scale",
        "why": "Number of farmers/cooperatives"
      },
      {
        "q": "NGO-P2-CatD-Q1a",
        "w": 0.5,
        "role": "scale",
        "why": "Agricultural transaction volume"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 3
  },
  "UC-E-068": {
    "name": "Transparent voting and consensus mechanisms",
    "blockchainFit": 4.5,
    "rationale": "Tamper-proof voting. Multi-party where no single org controls the outcome. Classic blockchain governance use case.",
    "signals": [
      {
        "q": "NGO-P2-CatE-Q11",
        "w": 0.9,
        "role": "need",
        "why": "Slow/unclear decision-making = governance gap"
      },
      {
        "q": "NGO-P2-CatE-Q13",
        "w": 0.8,
        "role": "need",
        "why": "Unclear accountability = voting transparency needed"
      },
      {
        "q": "NGO-P2-CatE-Q1",
        "w": 0.7,
        "role": "scale",
        "why": "Number of participating orgs"
      },
      {
        "q": "NGO-P2-CatE-Q12",
        "w": 0.6,
        "role": "fit_boost",
        "why": "Trust deficit as coordination breakdown cause"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 3,
    "interagency": true
  },
  "UC-E-069": {
    "name": "Community-based targeting verification",
    "blockchainFit": 3.8,
    "rationale": "Multi-party verification that targeting criteria were applied fairly. Community + org + oversight body.",
    "signals": [
      {
        "q": "NGO-P2-CatE-Q14",
        "w": 1,
        "role": "need",
        "why": "Milestone verification = targeting verification need"
      },
      {
        "q": "NGO-P2-CatE-Q13",
        "w": 0.8,
        "role": "need",
        "why": "Accountability for targeting decisions"
      },
      {
        "q": "NGO-P2-CatE-Q3",
        "w": 0.7,
        "role": "need",
        "why": "Eligibility disputes = targeting contested"
      },
      {
        "q": "NGO-P2-CatE-Q4",
        "w": 0.6,
        "role": "need",
        "why": "Referral process problems affect targeting"
      }
    ],
    "fitGate": 3,
    "readinessGate": 2.5
  },
  "UC-E-070": {
    "name": "Grant allocation across multiple partners",
    "blockchainFit": 4,
    "rationale": "Transparent allocation when multiple partners compete for limited funds. Smart contracts for rule-based allocation.",
    "signals": [
      {
        "q": "NGO-P2-CatE-Q13",
        "w": 0.9,
        "role": "need",
        "why": "Accountability for allocation decisions"
      },
      {
        "q": "NGO-P2-CatE-Q11",
        "w": 0.8,
        "role": "need",
        "why": "Decision-making speed for allocations"
      },
      {
        "q": "NGO-P2-CatE-Q1a",
        "w": 0.7,
        "role": "scale",
        "why": "Number of partner organisations"
      },
      {
        "q": "NGO-P2-CatE-Q12",
        "w": 0.6,
        "role": "fit_boost",
        "why": "Trust deficit in allocation decisions"
      },
      {
        "q": "NGO-P2-CatE-Q10",
        "w": 0.5,
        "role": "readiness",
        "why": "Technology platform for coordination"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 3,
    "interagency": true
  },
  "UC-E-071": {
    "name": "Partner performance verification",
    "blockchainFit": 3.5,
    "rationale": "Immutable records of partner deliverables. Multi-party verification of claimed outputs.",
    "signals": [
      {
        "q": "NGO-P2-CatE-Q14",
        "w": 1,
        "role": "need",
        "why": "Milestone verification = partner performance tracking"
      },
      {
        "q": "NGO-P2-CatE-Q13",
        "w": 0.7,
        "role": "need",
        "why": "Accountability framework for partners"
      },
      {
        "q": "NGO-P2-CatE-Q1a",
        "w": 0.6,
        "role": "scale",
        "why": "Number of partners to verify"
      },
      {
        "q": "NGO-P2-CatE-Q12",
        "w": 0.5,
        "role": "fit_boost",
        "why": "Trust deficit with partners"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 2.5
  },
  "UC-E-072": {
    "name": "Whistleblower protection mechanisms",
    "blockchainFit": 4,
    "rationale": "Anonymous, immutable reporting. Blockchain ensures reports can't be deleted or traced back. Strong privacy + immutability case.",
    "signals": [
      {
        "q": "NGO-P2-CatE-Q12",
        "w": 0.9,
        "role": "need",
        "why": "Trust deficit = whistleblowing environment"
      },
      {
        "q": "NGO-P2-CatE-Q13",
        "w": 0.8,
        "role": "need",
        "why": "Unclear accountability = oversight needed"
      },
      {
        "q": "NGO-P2-CatE-Q9",
        "w": 0.7,
        "role": "fit_boost",
        "why": "Political interference as failure point"
      },
      {
        "q": "NGO-P2-CatE-Q10",
        "w": 0.4,
        "role": "readiness",
        "why": "Technology capability for secure reporting"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 3
  },
  "UC-E-073": {
    "name": "Cross-NGO beneficiary coordination (avoiding gaps and overlaps)",
    "blockchainFit": 4.5,
    "rationale": "THE coordination problem \u2014 multiple NGOs serving same population need shared view without central controller. Core blockchain value.",
    "signals": [
      {
        "q": "NGO-P2-CatE-Q7",
        "w": 1,
        "role": "need",
        "why": "Duplicate service prevention = direct coordination need"
      },
      {
        "q": "NGO-P2-CatE-Q8",
        "w": 0.9,
        "role": "need",
        "why": "Duplicate services discovered"
      },
      {
        "q": "NGO-P2-CatE-Q8-FU",
        "w": 0.8,
        "role": "need",
        "why": "Frequency of duplicate services"
      },
      {
        "q": "NGO-P2-CatE-Q4",
        "w": 0.7,
        "role": "need",
        "why": "Referral process gaps = coordination failure"
      },
      {
        "q": "NGO-P2-CatE-Q3",
        "w": 0.6,
        "role": "need",
        "why": "Eligibility disputes between NGOs"
      },
      {
        "q": "NGO-P2-CatE-Q1a",
        "w": 0.7,
        "role": "scale",
        "why": "More coordination partners = bigger problem"
      },
      {
        "q": "NGO-P2-CatE-Q12",
        "w": 0.5,
        "role": "fit_boost",
        "why": "Trust deficit between agencies"
      }
    ],
    "fitGate": 1.5,
    "readinessGate": 3.5,
    "interagency": true
  },
  "UC-E-074": {
    "name": "Cluster coordination record-keeping",
    "blockchainFit": 3.5,
    "rationale": "UN cluster system record-keeping. Multi-party but existing reporting platforms work. Blockchain adds immutability.",
    "signals": [
      {
        "q": "NGO-P2-CatE-Q1",
        "w": 0.7,
        "role": "scale",
        "why": "Forum size indicates cluster complexity"
      },
      {
        "q": "NGO-P2-CatE-Q1b",
        "w": 0.6,
        "role": "need",
        "why": "Data exchange frequency with cluster partners"
      },
      {
        "q": "NGO-P2-CatE-Q10",
        "w": 0.7,
        "role": "need",
        "why": "Platform dependency = vendor lock-in risk"
      },
      {
        "q": "NGO-P2-CatE-Q12",
        "w": 0.5,
        "role": "need",
        "why": "Coordination breakdown causes"
      }
    ],
    "fitGate": 3,
    "readinessGate": 2.5,
    "interagency": true
  },
  "UC-E-075": {
    "name": "Community feedback mechanisms",
    "blockchainFit": 3,
    "rationale": "Immutable community feedback. Prevents feedback manipulation but simpler tools often suffice.",
    "signals": [
      {
        "q": "NGO-P2-CatE-Q13",
        "w": 0.7,
        "role": "need",
        "why": "Accountability requires genuine feedback"
      },
      {
        "q": "NGO-P2-CatE-Q14",
        "w": 0.6,
        "role": "need",
        "why": "Verification of community input"
      },
      {
        "q": "NGO-P2-CatE-Q12",
        "w": 0.5,
        "role": "fit_boost",
        "why": "Trust deficit = feedback integrity matters"
      },
      {
        "q": "NGO-P2-CatE-Q10",
        "w": 0.3,
        "role": "readiness",
        "why": "Technology for feedback collection"
      }
    ],
    "fitGate": 3,
    "readinessGate": 2
  },
  "UC-E-076": {
    "name": "Local partner capacity verification",
    "blockchainFit": 3.2,
    "rationale": "Verifying partner capacity claims. Multi-party (primary + partner + evaluator). Useful for due diligence.",
    "signals": [
      {
        "q": "NGO-P2-CatE-Q14",
        "w": 0.9,
        "role": "need",
        "why": "Verification of partner claims"
      },
      {
        "q": "NGO-P2-CatE-Q1a",
        "w": 0.6,
        "role": "scale",
        "why": "Number of partners to verify"
      },
      {
        "q": "NGO-P2-CatE-Q12",
        "w": 0.6,
        "role": "fit_boost",
        "why": "Trust issues with partner claims"
      },
      {
        "q": "NGO-P2-CatE-Q13",
        "w": 0.5,
        "role": "need",
        "why": "Accountability for partner capacity"
      }
    ],
    "fitGate": 3,
    "readinessGate": 2,
    "interagency": true
  },
  "UC-E-077": {
    "name": "Consortium fund allocation tracking",
    "blockchainFit": 4.2,
    "rationale": "Multi-party fund flow through consortium. Each partner sees the same ledger. Smart contracts enforce allocation rules.",
    "signals": [
      {
        "q": "NGO-P2-CatE-Q13",
        "w": 0.9,
        "role": "need",
        "why": "Fund allocation accountability"
      },
      {
        "q": "NGO-P2-CatE-Q1a",
        "w": 0.8,
        "role": "scale",
        "why": "Consortium partner count"
      },
      {
        "q": "NGO-P2-CatE-Q12",
        "w": 0.7,
        "role": "fit_boost",
        "why": "Trust deficit in fund allocation"
      },
      {
        "q": "NGO-P2-CatE-Q11",
        "w": 0.6,
        "role": "need",
        "why": "Decision-making speed for allocations"
      },
      {
        "q": "NGO-P2-CatE-Q10",
        "w": 0.5,
        "role": "readiness",
        "why": "Current coordination technology"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 3,
    "interagency": true
  },
  "UC-E-078": {
    "name": "Inter-agency coordination layer",
    "blockchainFit": 4.5,
    "rationale": "Shared coordination infrastructure that no single agency controls. Decentralised by design. Core blockchain governance value.",
    "signals": [
      {
        "q": "NGO-P2-CatE-Q10",
        "w": 1,
        "role": "need",
        "why": "Vendor lock-in = need for decentralised platform"
      },
      {
        "q": "NGO-P2-CatE-Q1a",
        "w": 0.8,
        "role": "scale",
        "why": "Number of agencies to coordinate"
      },
      {
        "q": "NGO-P2-CatE-Q12",
        "w": 0.9,
        "role": "fit_boost",
        "why": "Trust deficit = decentralisation imperative"
      },
      {
        "q": "NGO-P2-CatE-Q1b",
        "w": 0.7,
        "role": "need",
        "why": "Data exchange frequency indicates coordination volume"
      },
      {
        "q": "NGO-P2-CatE-Q7",
        "w": 0.6,
        "role": "need",
        "why": "Duplicate service visibility gap"
      },
      {
        "q": "NGO-P2-CatE-Q11",
        "w": 0.5,
        "role": "need",
        "why": "Decision-making structure"
      }
    ],
    "fitGate": 2,
    "readinessGate": 3.5,
    "interagency": true
  },
  "UC-E-079": {
    "name": "Digital public goods infrastructure",
    "blockchainFit": 4,
    "rationale": "Open-source shared infrastructure for public benefit. Blockchain as neutral coordination layer for digital public goods.",
    "signals": [
      {
        "q": "NGO-P2-CatE-Q10",
        "w": 1,
        "role": "need",
        "why": "Platform ownership = need for public goods approach"
      },
      {
        "q": "NGO-P2-CatE-Q12",
        "w": 0.7,
        "role": "fit_boost",
        "why": "Data silos + no shared system = public goods case"
      },
      {
        "q": "NGO-P2-CatE-Q1a",
        "w": 0.6,
        "role": "scale",
        "why": "Number of potential users/contributors"
      },
      {
        "q": "NGO-P2-CatE-Q9",
        "w": 0.5,
        "role": "need",
        "why": "Current system failure points justify alternatives"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 3,
    "interagency": true
  },
  "_catF_header": "=== CATEGORY F: Fundraising and Donor Relations (cross-category signals from A + E) ===",
  "UC-F-080": {
    "name": "Transparent fund flow tracking",
    "blockchainFit": 4.2,
    "rationale": "Multi-stakeholder transparency (donors, HQ, field). Blockchain's immutable audit trail directly solves trust deficit between donors and implementers.",
    "signals": [
      {
        "q": "NGO-P2-CatA-Q29",
        "w": 1,
        "role": "need",
        "why": "Lack of real-time donor visibility = direct need for transparent tracking"
      },
      {
        "q": "NGO-P2-CatA-Q8b",
        "w": 0.8,
        "role": "need",
        "why": "High discrepancy rate = funds unaccounted for"
      },
      {
        "q": "NGO-P2-CatA-Q30",
        "w": 0.7,
        "role": "need",
        "why": "Financial failure points = trust gaps"
      },
      {
        "q": "NGO-P2-CatE-Q13",
        "w": 0.8,
        "role": "fit_boost",
        "why": "Unclear accountability = multi-party trust problem"
      },
      {
        "q": "NGO-P2-CatE-Q6",
        "w": 0.6,
        "role": "readiness",
        "why": "Existing evidence/verification capability"
      },
      {
        "q": "NGO-P2-CatA-Q2",
        "w": 0.5,
        "role": "scale",
        "why": "More intermediaries = more points needing transparency"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 2.5,
    "interagency": true
  },
  "UC-F-081": {
    "name": "Fractional and micro-donation enabling",
    "blockchainFit": 3.5,
    "rationale": "Low-value transactions where traditional payment rails are too expensive. Blockchain reduces per-transaction cost for micro-amounts.",
    "signals": [
      {
        "q": "NGO-P2-CatA-Q4",
        "w": 1,
        "role": "need",
        "why": "High transfer fees make micro-donations uneconomical"
      },
      {
        "q": "NGO-P2-CatA-Q31",
        "w": 0.7,
        "role": "need",
        "why": "Cash-scarce communities need digital micro-payments"
      },
      {
        "q": "NGO-P2-CatA-Q2",
        "w": 0.6,
        "role": "need",
        "why": "Many intermediaries inflate micro-payment costs"
      },
      {
        "q": "NGO-P2-CatA-Q1",
        "w": 0.4,
        "role": "readiness",
        "why": "Process complexity indicates digital payment maturity"
      }
    ],
    "fitGate": 3,
    "readinessGate": 2
  },
  "UC-F-082": {
    "name": "Cryptocurrency and digital asset donations",
    "blockchainFit": 4.8,
    "rationale": "Inherently blockchain-native. If org receives crypto, they need blockchain infrastructure by definition.",
    "signals": [
      {
        "q": "NGO-P2-CatA-Q5",
        "w": 0.8,
        "role": "need",
        "why": "Restricted corridors push donors toward crypto alternatives"
      },
      {
        "q": "NGO-P2-CatA-Q6",
        "w": 0.7,
        "role": "need",
        "why": "Blocked transfers motivate crypto donation acceptance"
      },
      {
        "q": "NGO-P2-CatA-Q4",
        "w": 0.5,
        "role": "need",
        "why": "High fees push toward crypto rails"
      },
      {
        "q": "NGO-P2-CatA-Q1",
        "w": 0.4,
        "role": "readiness",
        "why": "Process sophistication for handling digital assets"
      }
    ],
    "fitGate": 2,
    "readinessGate": 3
  },
  "UC-F-083": {
    "name": "Impact verification tied to specific donations",
    "blockchainFit": 4,
    "rationale": "Links specific donor funds to verified outcomes. Multi-party verification chain (donor \u2192 org \u2192 field \u2192 beneficiary) is a trust problem blockchain addresses.",
    "signals": [
      {
        "q": "NGO-P2-CatA-Q29",
        "w": 1,
        "role": "need",
        "why": "No real-time donor visibility = donors can't see impact"
      },
      {
        "q": "NGO-P2-CatE-Q14",
        "w": 0.9,
        "role": "need",
        "why": "Milestone verification = direct impact tracking need"
      },
      {
        "q": "NGO-P2-CatE-Q6",
        "w": 0.7,
        "role": "readiness",
        "why": "Existing evidence types = data collection capability"
      },
      {
        "q": "NGO-P2-CatE-Q13",
        "w": 0.8,
        "role": "fit_boost",
        "why": "Unclear accountability between parties = trust problem"
      },
      {
        "q": "NGO-P2-CatA-Q8b",
        "w": 0.5,
        "role": "need",
        "why": "Discrepancies = impact claims unverifiable"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 2.5
  },
  "UC-F-084": {
    "name": "Automated donor reporting",
    "blockchainFit": 3.2,
    "rationale": "Automates reporting from immutable records. Useful but traditional reporting tools often sufficient unless multi-donor coordination required.",
    "signals": [
      {
        "q": "NGO-P2-CatA-Q29",
        "w": 0.9,
        "role": "need",
        "why": "Poor donor visibility = manual reporting burden"
      },
      {
        "q": "NGO-P2-CatA-Q7",
        "w": 0.7,
        "role": "need",
        "why": "Heavy compliance burden = reporting overhead"
      },
      {
        "q": "NGO-P2-CatE-Q1a",
        "w": 0.6,
        "role": "scale",
        "why": "More partners = more reporting requirements"
      },
      {
        "q": "NGO-P2-CatA-Q8a",
        "w": 0.5,
        "role": "readiness",
        "why": "Reconciliation frequency = data readiness for automation"
      }
    ],
    "fitGate": 3,
    "readinessGate": 2.5
  },
  "UC-F-085": {
    "name": "Crowdfunding with built-in accountability",
    "blockchainFit": 3.8,
    "rationale": "Public-facing accountability for many small donors. Blockchain provides verifiable receipts and fund tracking at scale.",
    "signals": [
      {
        "q": "NGO-P2-CatA-Q29",
        "w": 0.9,
        "role": "need",
        "why": "Donors want visibility into where funds go"
      },
      {
        "q": "NGO-P2-CatA-Q4",
        "w": 0.7,
        "role": "need",
        "why": "High fees eat into small donations"
      },
      {
        "q": "NGO-P2-CatE-Q14",
        "w": 0.6,
        "role": "fit_boost",
        "why": "Milestone-based verification for campaign goals"
      },
      {
        "q": "NGO-P2-CatA-Q2",
        "w": 0.5,
        "role": "scale",
        "why": "Many intermediaries in donation pipeline"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 2.5
  },
  "UC-F-086": {
    "name": "Corporate giving with verified impact metrics",
    "blockchainFit": 3.8,
    "rationale": "Corporate donors require auditable impact evidence. Blockchain provides tamper-proof impact records for ESG reporting.",
    "signals": [
      {
        "q": "NGO-P2-CatE-Q14",
        "w": 1,
        "role": "need",
        "why": "Milestone verification = core of impact reporting"
      },
      {
        "q": "NGO-P2-CatA-Q29",
        "w": 0.8,
        "role": "need",
        "why": "Donor visibility needs for corporate giving"
      },
      {
        "q": "NGO-P2-CatE-Q6",
        "w": 0.7,
        "role": "readiness",
        "why": "Existing evidence collection = data availability"
      },
      {
        "q": "NGO-P2-CatA-Q7",
        "w": 0.6,
        "role": "need",
        "why": "Compliance burden correlates with corporate reporting needs"
      },
      {
        "q": "NGO-P2-CatE-Q13",
        "w": 0.5,
        "role": "fit_boost",
        "why": "Accountability gaps = verified metrics needed"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 2.5
  },
  "UC-F-087": {
    "name": "Recurring donation automation",
    "blockchainFit": 2.5,
    "rationale": "Traditional payment processors handle recurring donations well. Blockchain only adds value if operating in restricted corridors or needing immutable receipts.",
    "signals": [
      {
        "q": "NGO-P2-CatA-Q5",
        "w": 0.8,
        "role": "need",
        "why": "Only justified if corridors restrict traditional recurring payments"
      },
      {
        "q": "NGO-P2-CatA-Q6",
        "w": 0.7,
        "role": "need",
        "why": "Payment blocks disrupt recurring giving"
      },
      {
        "q": "NGO-P2-CatA-Q4",
        "w": 0.5,
        "role": "need",
        "why": "High fees erode recurring micro-donations"
      },
      {
        "q": "NGO-P2-CatA-Q1",
        "w": 0.3,
        "role": "readiness",
        "why": "Payment process maturity"
      }
    ],
    "fitGate": 3.5,
    "readinessGate": 1.5
  },
  "UC-F-088": {
    "name": "Donor-advised fund integration",
    "blockchainFit": 2.8,
    "rationale": "Niche use case. Smart contracts can automate DAF disbursement rules, but traditional DAF platforms handle this adequately.",
    "signals": [
      {
        "q": "NGO-P2-CatA-Q29",
        "w": 0.7,
        "role": "need",
        "why": "Fund visibility for donor advisors"
      },
      {
        "q": "NGO-P2-CatA-Q7",
        "w": 0.5,
        "role": "need",
        "why": "Compliance overhead in fund allocation"
      },
      {
        "q": "NGO-P2-CatE-Q14",
        "w": 0.6,
        "role": "fit_boost",
        "why": "Milestone-based disbursement from DAFs"
      },
      {
        "q": "NGO-P2-CatA-Q1",
        "w": 0.3,
        "role": "readiness",
        "why": "Financial process sophistication"
      }
    ],
    "fitGate": 3,
    "readinessGate": 2.5
  },
  "UC-F-089": {
    "name": "Gift matching verification",
    "blockchainFit": 3,
    "rationale": "Multi-party verification (donor, matcher, org). Blockchain provides proof that matching commitments were honoured. Traditional systems can do this with audits.",
    "signals": [
      {
        "q": "NGO-P2-CatE-Q14",
        "w": 0.9,
        "role": "need",
        "why": "Milestone/condition verification = matching trigger verification"
      },
      {
        "q": "NGO-P2-CatA-Q29",
        "w": 0.7,
        "role": "need",
        "why": "Donor needs proof matches were applied"
      },
      {
        "q": "NGO-P2-CatE-Q13",
        "w": 0.6,
        "role": "fit_boost",
        "why": "Accountability between matcher and org = trust problem"
      },
      {
        "q": "NGO-P2-CatA-Q8b",
        "w": 0.4,
        "role": "scale",
        "why": "Discrepancy rate signals volume of matching"
      }
    ],
    "fitGate": 3,
    "readinessGate": 2
  },
  "_catG_header": "=== CATEGORY G: Resilience and Risk Management (cross-category signals from A + B + C + D) ===",
  "UC-G-090": {
    "name": "Early warning systems with automated fund release triggers",
    "blockchainFit": 4.5,
    "rationale": "Parametric triggers releasing pre-positioned funds. Smart contracts execute based on verified external data. Multi-party trust between data source, funder, implementer.",
    "signals": [
      {
        "q": "NGO-P2-CatA-Q3",
        "w": 1,
        "role": "need",
        "why": "Slow transfers = early warning loses value without rapid disbursement"
      },
      {
        "q": "NGO-P2-CatA-Q6",
        "w": 0.9,
        "role": "need",
        "why": "Blocked transfers = early warning useless without alternative rails"
      },
      {
        "q": "NGO-P2-CatA-Q30",
        "w": 0.8,
        "role": "need",
        "why": "Financial failure points = need for automated fallback"
      },
      {
        "q": "NGO-P2-CatE-Q11",
        "w": 0.7,
        "role": "need",
        "why": "Slow decision-making = need for automated triggers"
      },
      {
        "q": "NGO-P2-CatE-Q14",
        "w": 0.8,
        "role": "fit_boost",
        "why": "Condition verification = parametric trigger validation"
      },
      {
        "q": "NGO-P2-CatA-Q1",
        "w": 0.4,
        "role": "readiness",
        "why": "Process complexity = integration challenge"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 3.5
  },
  "UC-G-091": {
    "name": "Disaster response fund pre-positioning",
    "blockchainFit": 4.2,
    "rationale": "Pre-positioned smart contracts release funds on verified disaster triggers. Removes approval delays. Multi-party coordination between donors and responders.",
    "signals": [
      {
        "q": "NGO-P2-CatA-Q3",
        "w": 1,
        "role": "need",
        "why": "Slow transfers in disaster context = critical delay"
      },
      {
        "q": "NGO-P2-CatA-Q5",
        "w": 0.9,
        "role": "need",
        "why": "Disaster zones often in restricted corridors"
      },
      {
        "q": "NGO-P2-CatA-Q6",
        "w": 0.9,
        "role": "need",
        "why": "Blocked transfers during disaster = lives lost"
      },
      {
        "q": "NGO-P2-CatA-Q30",
        "w": 0.7,
        "role": "fit_boost",
        "why": "Financial failure in disaster = case for pre-positioning"
      },
      {
        "q": "NGO-P2-CatE-Q1a",
        "w": 0.5,
        "role": "scale",
        "why": "Multi-partner disaster response coordination"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 3,
    "interagency": true
  },
  "UC-G-092": {
    "name": "Anticipatory action fund release mechanisms",
    "blockchainFit": 4.3,
    "rationale": "Smart contracts triggered by forecast thresholds. Multi-party agreement on triggers and disbursement rules. Strong blockchain case for removing bureaucratic delays.",
    "signals": [
      {
        "q": "NGO-P2-CatA-Q3",
        "w": 1,
        "role": "need",
        "why": "Transfer speed critical for anticipatory action"
      },
      {
        "q": "NGO-P2-CatE-Q11",
        "w": 0.9,
        "role": "need",
        "why": "Slow decision-making defeats anticipatory purpose"
      },
      {
        "q": "NGO-P2-CatE-Q14",
        "w": 0.9,
        "role": "fit_boost",
        "why": "Condition-based verification = parametric triggers"
      },
      {
        "q": "NGO-P2-CatA-Q6",
        "w": 0.8,
        "role": "need",
        "why": "Payment blocks undermine anticipatory action"
      },
      {
        "q": "NGO-P2-CatA-Q5",
        "w": 0.7,
        "role": "need",
        "why": "Restricted corridors in vulnerable regions"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 3.5
  },
  "UC-G-093": {
    "name": "Climate adaptation financing",
    "blockchainFit": 3.5,
    "rationale": "Multi-stakeholder climate finance with verification requirements. Blockchain provides transparent tracking but traditional grant management may suffice for bilateral arrangements.",
    "signals": [
      {
        "q": "NGO-P2-CatE-Q14",
        "w": 0.9,
        "role": "need",
        "why": "Climate milestones need verification for continued funding"
      },
      {
        "q": "NGO-P2-CatA-Q29",
        "w": 0.8,
        "role": "need",
        "why": "Funders need visibility into climate adaptation spend"
      },
      {
        "q": "NGO-P2-CatE-Q1a",
        "w": 0.7,
        "role": "scale",
        "why": "Multi-partner climate programmes"
      },
      {
        "q": "NGO-P2-CatE-Q13",
        "w": 0.6,
        "role": "fit_boost",
        "why": "Accountability gaps in climate finance"
      },
      {
        "q": "NGO-P2-CatA-Q7",
        "w": 0.5,
        "role": "readiness",
        "why": "Compliance capability for climate finance reporting"
      }
    ],
    "fitGate": 3,
    "readinessGate": 3
  },
  "UC-G-094": {
    "name": "Conflict-sensitive resource allocation",
    "blockchainFit": 3.8,
    "rationale": "Multi-party coordination in conflict zones where trust is low. Blockchain ensures transparent, auditable allocation preventing bias accusations.",
    "signals": [
      {
        "q": "NGO-P2-CatE-Q3",
        "w": 1,
        "role": "need",
        "why": "Eligibility disputes = resource allocation contested"
      },
      {
        "q": "NGO-P2-CatE-Q4",
        "w": 0.9,
        "role": "need",
        "why": "Service overlap = resource duplication in conflict"
      },
      {
        "q": "NGO-P2-CatE-Q13",
        "w": 0.9,
        "role": "fit_boost",
        "why": "Unclear accountability in conflict = trust crisis"
      },
      {
        "q": "NGO-P2-CatE-Q1a",
        "w": 0.7,
        "role": "scale",
        "why": "Many partners operating in conflict zone"
      },
      {
        "q": "NGO-P2-CatE-Q11",
        "w": 0.5,
        "role": "readiness",
        "why": "Decision-making speed and structure indicates capacity"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 3,
    "interagency": true
  },
  "UC-G-095": {
    "name": "Evidence preservation for human rights documentation",
    "blockchainFit": 4.5,
    "rationale": "Immutable timestamps and chain of custody for legal proceedings. Blockchain's core tamper-resistance property directly solves this problem.",
    "signals": [
      {
        "q": "NGO-P2-CatC-Q8",
        "w": 1,
        "role": "need",
        "why": "No audit trail = evidence tampering risk"
      },
      {
        "q": "NGO-P2-CatC-Q6",
        "w": 0.8,
        "role": "readiness",
        "why": "Existing data integrity methods"
      },
      {
        "q": "NGO-P2-CatC-Q9",
        "w": 0.9,
        "role": "need",
        "why": "Data management failures = evidence loss"
      },
      {
        "q": "NGO-P2-CatC-Q4",
        "w": 0.7,
        "role": "need",
        "why": "Conflicting data = evidence credibility problem"
      },
      {
        "q": "NGO-P2-CatC-Q1",
        "w": 0.5,
        "role": "fit_boost",
        "why": "Weak data governance = tamper risk blockchain addresses"
      }
    ],
    "fitGate": 2,
    "readinessGate": 2.5
  },
  "UC-G-096": {
    "name": "Atrocity documentation with chain of custody",
    "blockchainFit": 4.7,
    "rationale": "Legal proceedings require proven chain of custody. Blockchain provides cryptographic proof of when evidence was captured and that it hasn't been altered.",
    "signals": [
      {
        "q": "NGO-P2-CatC-Q8",
        "w": 1,
        "role": "need",
        "why": "Audit visibility = chain of custody capability"
      },
      {
        "q": "NGO-P2-CatC-Q9",
        "w": 0.9,
        "role": "need",
        "why": "Data failure = evidence loss for prosecution"
      },
      {
        "q": "NGO-P2-CatC-Q4",
        "w": 0.8,
        "role": "need",
        "why": "Conflicting data undermines evidence credibility"
      },
      {
        "q": "NGO-P2-CatC-Q6",
        "w": 0.7,
        "role": "readiness",
        "why": "Existing integrity methods = data handling capability"
      },
      {
        "q": "NGO-P2-CatC-Q1",
        "w": 0.6,
        "role": "fit_boost",
        "why": "Weak governance = evidence tampering risk"
      }
    ],
    "fitGate": 2,
    "readinessGate": 3
  },
  "UC-G-097": {
    "name": "Witness testimony timestamping",
    "blockchainFit": 4.3,
    "rationale": "Immutable timestamp proves when testimony was recorded. Critical for legal credibility. Blockchain's core immutability property.",
    "signals": [
      {
        "q": "NGO-P2-CatC-Q8",
        "w": 1,
        "role": "need",
        "why": "No audit trail = no proof of when testimony recorded"
      },
      {
        "q": "NGO-P2-CatC-Q9",
        "w": 0.8,
        "role": "need",
        "why": "System failures could lose testimony records"
      },
      {
        "q": "NGO-P2-CatC-Q1",
        "w": 0.6,
        "role": "fit_boost",
        "why": "Weak governance = testimony credibility risk"
      },
      {
        "q": "NGO-P2-CatB-Q9",
        "w": 0.5,
        "role": "need",
        "why": "Record continuity for displaced witnesses"
      },
      {
        "q": "NGO-P2-CatC-Q6",
        "w": 0.5,
        "role": "readiness",
        "why": "Existing data integrity capability"
      }
    ],
    "fitGate": 2,
    "readinessGate": 2.5
  },
  "UC-G-098": {
    "name": "Displacement tracking and verification",
    "blockchainFit": 4,
    "rationale": "Multi-agency tracking of displaced populations. No single authority trusted. Cross-border portability of displacement status.",
    "signals": [
      {
        "q": "NGO-P2-CatB-Q1",
        "w": 1,
        "role": "need",
        "why": "Lack of ID = displaced people invisible to systems"
      },
      {
        "q": "NGO-P2-CatB-Q9",
        "w": 0.9,
        "role": "need",
        "why": "Record continuity for displaced = displacement tracking"
      },
      {
        "q": "NGO-P2-CatB-Q10",
        "w": 0.8,
        "role": "fit_boost",
        "why": "Multi-agency data sharing = multi-party trust"
      },
      {
        "q": "NGO-P2-CatB-Q1a",
        "w": 0.7,
        "role": "scale",
        "why": "Volume of displaced population"
      },
      {
        "q": "NGO-P2-CatB-Q1c",
        "w": 0.6,
        "role": "need",
        "why": "Duplicate rate = same displaced person counted multiple times"
      },
      {
        "q": "NGO-P2-CatB-Q3",
        "w": 0.4,
        "role": "readiness",
        "why": "Registration process maturity"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 3
  },
  "_catH_header": "=== CATEGORY H: Land, Property and Natural Resources (cross-category signals from B + C + D + E) ===",
  "UC-H-099": {
    "name": "Land registry and title documentation (post-conflict/disaster)",
    "blockchainFit": 4.5,
    "rationale": "Destroyed or corrupted land registries. No single trusted authority to adjudicate claims. Blockchain provides immutable title records.",
    "signals": [
      {
        "q": "NGO-P2-CatC-Q9",
        "w": 1,
        "role": "need",
        "why": "Data failure = lost land records"
      },
      {
        "q": "NGO-P2-CatC-Q1",
        "w": 0.9,
        "role": "need",
        "why": "Weak data governance = vulnerable registries"
      },
      {
        "q": "NGO-P2-CatC-Q8",
        "w": 0.8,
        "role": "need",
        "why": "No audit trail = disputed ownership claims"
      },
      {
        "q": "NGO-P2-CatB-Q1",
        "w": 0.7,
        "role": "need",
        "why": "ID gap correlates with missing property documentation"
      },
      {
        "q": "NGO-P2-CatE-Q3",
        "w": 0.6,
        "role": "fit_boost",
        "why": "Eligibility disputes = contested land claims"
      },
      {
        "q": "NGO-P2-CatC-Q6",
        "w": 0.5,
        "role": "readiness",
        "why": "Existing data integrity methods"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 3.5
  },
  "UC-H-100": {
    "name": "Property rights documentation for displaced populations",
    "blockchainFit": 4.3,
    "rationale": "Displaced populations need portable proof of property ownership. Multi-party (displaced person, government, NGO, host country).",
    "signals": [
      {
        "q": "NGO-P2-CatB-Q9",
        "w": 1,
        "role": "need",
        "why": "Record continuity = portable property proof"
      },
      {
        "q": "NGO-P2-CatB-Q1",
        "w": 0.9,
        "role": "need",
        "why": "No ID = can't prove property ownership"
      },
      {
        "q": "NGO-P2-CatC-Q9",
        "w": 0.8,
        "role": "need",
        "why": "System failure = lost property records"
      },
      {
        "q": "NGO-P2-CatB-Q10",
        "w": 0.7,
        "role": "fit_boost",
        "why": "Cross-org data sharing for property claims"
      },
      {
        "q": "NGO-P2-CatB-Q1a",
        "w": 0.6,
        "role": "scale",
        "why": "Volume of displaced population with property claims"
      },
      {
        "q": "NGO-P2-CatC-Q6",
        "w": 0.4,
        "role": "readiness",
        "why": "Data integrity capability"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 3
  },
  "UC-H-101": {
    "name": "Housing, land, and property (HLP) claims tracking",
    "blockchainFit": 4.2,
    "rationale": "Multi-party dispute resolution. Tracking claims across multiple authorities. Blockchain provides shared tamper-proof claims ledger.",
    "signals": [
      {
        "q": "NGO-P2-CatE-Q3",
        "w": 1,
        "role": "need",
        "why": "Eligibility disputes = contested HLP claims"
      },
      {
        "q": "NGO-P2-CatC-Q8",
        "w": 0.9,
        "role": "need",
        "why": "Audit trail needed for claims adjudication"
      },
      {
        "q": "NGO-P2-CatE-Q1a",
        "w": 0.7,
        "role": "scale",
        "why": "Multiple agencies processing claims"
      },
      {
        "q": "NGO-P2-CatE-Q13",
        "w": 0.8,
        "role": "fit_boost",
        "why": "Unclear accountability = disputed decisions"
      },
      {
        "q": "NGO-P2-CatC-Q4",
        "w": 0.6,
        "role": "need",
        "why": "Conflicting records on property claims"
      },
      {
        "q": "NGO-P2-CatE-Q11",
        "w": 0.4,
        "role": "readiness",
        "why": "Decision-making process maturity"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 3.5
  },
  "UC-H-102": {
    "name": "Customary land rights documentation",
    "blockchainFit": 3.8,
    "rationale": "Community-based land rights that aren't captured in formal systems. Blockchain provides community-controlled registry that doesn't depend on government.",
    "signals": [
      {
        "q": "NGO-P2-CatC-Q1",
        "w": 0.9,
        "role": "need",
        "why": "Weak formal governance = customary rights undocumented"
      },
      {
        "q": "NGO-P2-CatE-Q10",
        "w": 0.8,
        "role": "fit_boost",
        "why": "Platform ownership question = who controls the registry"
      },
      {
        "q": "NGO-P2-CatC-Q9",
        "w": 0.7,
        "role": "need",
        "why": "System failure = lost customary records"
      },
      {
        "q": "NGO-P2-CatE-Q1a",
        "w": 0.5,
        "role": "scale",
        "why": "Community size and complexity"
      },
      {
        "q": "NGO-P2-CatC-Q6",
        "w": 0.4,
        "role": "readiness",
        "why": "Data integrity capability for documentation"
      }
    ],
    "fitGate": 3,
    "readinessGate": 3
  },
  "UC-H-103": {
    "name": "Natural resource extraction tracking",
    "blockchainFit": 4,
    "rationale": "Multi-stakeholder supply chain from extraction to export. Prevents conflict mineral issues. Blockchain tracks provenance.",
    "signals": [
      {
        "q": "NGO-P2-CatD-Q1",
        "w": 1,
        "role": "need",
        "why": "Deep supply chain tiers = extraction tracking complexity"
      },
      {
        "q": "NGO-P2-CatD-Q4",
        "w": 0.9,
        "role": "need",
        "why": "Long item journey = many points to track"
      },
      {
        "q": "NGO-P2-CatD-Q6",
        "w": 0.8,
        "role": "need",
        "why": "Visibility gaps in extraction chain"
      },
      {
        "q": "NGO-P2-CatD-Q1c",
        "w": 0.7,
        "role": "scale",
        "why": "Many supply chain partners in extraction"
      },
      {
        "q": "NGO-P2-CatD-Q5",
        "w": 0.6,
        "role": "fit_boost",
        "why": "Quality/authenticity issues = provenance needed"
      },
      {
        "q": "NGO-P2-CatD-Q3",
        "w": 0.4,
        "role": "readiness",
        "why": "Existing verification methods"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 3
  },
  "UC-H-104": {
    "name": "Community benefit sharing from resources",
    "blockchainFit": 3.5,
    "rationale": "Transparent revenue sharing between extractors and communities. Smart contracts can automate royalty payments. Trust deficit between parties.",
    "signals": [
      {
        "q": "NGO-P2-CatE-Q13",
        "w": 1,
        "role": "need",
        "why": "Accountability gaps = communities don't trust benefit sharing"
      },
      {
        "q": "NGO-P2-CatA-Q29",
        "w": 0.8,
        "role": "need",
        "why": "No visibility into fund flows to communities"
      },
      {
        "q": "NGO-P2-CatE-Q14",
        "w": 0.7,
        "role": "fit_boost",
        "why": "Milestone verification for benefit triggers"
      },
      {
        "q": "NGO-P2-CatE-Q1a",
        "w": 0.6,
        "role": "scale",
        "why": "Number of stakeholder communities"
      },
      {
        "q": "NGO-P2-CatA-Q8b",
        "w": 0.5,
        "role": "need",
        "why": "Discrepancies in benefit payments"
      }
    ],
    "fitGate": 3,
    "readinessGate": 2.5
  },
  "UC-H-105": {
    "name": "Water rights management",
    "blockchainFit": 3.5,
    "rationale": "Multi-stakeholder resource allocation. Shared ledger for water usage rights. Blockchain useful where multiple users compete for scarce resource.",
    "signals": [
      {
        "q": "NGO-P2-CatE-Q3",
        "w": 0.9,
        "role": "need",
        "why": "Eligibility disputes = water rights contested"
      },
      {
        "q": "NGO-P2-CatE-Q4",
        "w": 0.8,
        "role": "need",
        "why": "Service overlap = over-allocation of water"
      },
      {
        "q": "NGO-P2-CatE-Q10",
        "w": 0.7,
        "role": "fit_boost",
        "why": "Platform ownership = who controls water allocation system"
      },
      {
        "q": "NGO-P2-CatE-Q1a",
        "w": 0.6,
        "role": "scale",
        "why": "Number of competing water users"
      },
      {
        "q": "NGO-P2-CatE-Q11",
        "w": 0.4,
        "role": "readiness",
        "why": "Decision-making structure for allocation"
      }
    ],
    "fitGate": 3,
    "readinessGate": 2.5
  },
  "UC-H-106": {
    "name": "Fishing rights and marine resource access",
    "blockchainFit": 3.5,
    "rationale": "Multi-stakeholder management of marine resources. Tracking catch quotas and access permits across jurisdictions.",
    "signals": [
      {
        "q": "NGO-P2-CatD-Q1",
        "w": 0.8,
        "role": "need",
        "why": "Supply chain depth = fishing industry tiers"
      },
      {
        "q": "NGO-P2-CatE-Q3",
        "w": 0.8,
        "role": "need",
        "why": "Eligibility disputes = fishing rights contested"
      },
      {
        "q": "NGO-P2-CatD-Q6",
        "w": 0.7,
        "role": "need",
        "why": "Visibility gaps in fishing supply chain"
      },
      {
        "q": "NGO-P2-CatD-Q9",
        "w": 0.6,
        "role": "fit_boost",
        "why": "Smallholder provenance = artisanal fishing tracking"
      },
      {
        "q": "NGO-P2-CatE-Q1a",
        "w": 0.5,
        "role": "scale",
        "why": "Multiple fishing communities/jurisdictions"
      }
    ],
    "fitGate": 3,
    "readinessGate": 2.5
  },
  "_catI_header": "=== CATEGORY I: Energy and Environment (cross-category signals from C + D + E) ===",
  "UC-I-107": {
    "name": "Renewable energy certificate tracking and trading",
    "blockchainFit": 4.5,
    "rationale": "Multi-party marketplace for RECs. Blockchain prevents double-counting and provides transparent trading. Strong fit for token-based certificates.",
    "signals": [
      {
        "q": "NGO-P2-CatC-Q5",
        "w": 0.9,
        "role": "need",
        "why": "Duplicate detection = double-counting prevention for RECs"
      },
      {
        "q": "NGO-P2-CatC-Q8",
        "w": 0.8,
        "role": "need",
        "why": "Audit trail needed for certificate provenance"
      },
      {
        "q": "NGO-P2-CatE-Q1a",
        "w": 0.8,
        "role": "scale",
        "why": "Many market participants trading certificates"
      },
      {
        "q": "NGO-P2-CatE-Q10",
        "w": 0.7,
        "role": "fit_boost",
        "why": "No single party should control the registry"
      },
      {
        "q": "NGO-P2-CatC-Q6",
        "w": 0.5,
        "role": "readiness",
        "why": "Data integrity practices for certificate management"
      }
    ],
    "fitGate": 2,
    "readinessGate": 3
  },
  "UC-I-108": {
    "name": "Carbon credit registry and marketplace",
    "blockchainFit": 4.5,
    "rationale": "Tokenized carbon credits on shared ledger. Prevents double-counting. Multi-party verification. Already seeing real-world blockchain adoption.",
    "signals": [
      {
        "q": "NGO-P2-CatC-Q5",
        "w": 1,
        "role": "need",
        "why": "Duplicate detection = double-counting prevention for credits"
      },
      {
        "q": "NGO-P2-CatC-Q8",
        "w": 0.9,
        "role": "need",
        "why": "Audit trail for credit provenance and retirement"
      },
      {
        "q": "NGO-P2-CatE-Q1a",
        "w": 0.8,
        "role": "scale",
        "why": "Many market participants"
      },
      {
        "q": "NGO-P2-CatE-Q14",
        "w": 0.7,
        "role": "fit_boost",
        "why": "Verification of carbon reduction milestones"
      },
      {
        "q": "NGO-P2-CatE-Q10",
        "w": 0.7,
        "role": "fit_boost",
        "why": "Neutral registry ownership critical"
      }
    ],
    "fitGate": 2,
    "readinessGate": 3
  },
  "UC-I-109": {
    "name": "Green energy provenance for climate finance",
    "blockchainFit": 4,
    "rationale": "Proving energy source for climate finance eligibility. Chain of custody from generation to claim. Multi-party verification.",
    "signals": [
      {
        "q": "NGO-P2-CatD-Q4",
        "w": 0.9,
        "role": "need",
        "why": "Item journey tracking = energy provenance chain"
      },
      {
        "q": "NGO-P2-CatC-Q8",
        "w": 0.8,
        "role": "need",
        "why": "Audit trail for provenance claims"
      },
      {
        "q": "NGO-P2-CatE-Q14",
        "w": 0.8,
        "role": "fit_boost",
        "why": "Verification of green energy milestones"
      },
      {
        "q": "NGO-P2-CatD-Q6",
        "w": 0.7,
        "role": "need",
        "why": "Visibility gaps in energy supply chain"
      },
      {
        "q": "NGO-P2-CatC-Q6",
        "w": 0.5,
        "role": "readiness",
        "why": "Data integrity for provenance claims"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 3
  },
  "UC-I-110": {
    "name": "Environmental monitoring data integrity",
    "blockchainFit": 4,
    "rationale": "Distributed sensor data from many sources. Blockchain provides tamper-proof data aggregation. Critical for environmental compliance.",
    "signals": [
      {
        "q": "NGO-P2-CatC-Q4",
        "w": 1,
        "role": "need",
        "why": "Conflicting data = sensor disagreements need resolution"
      },
      {
        "q": "NGO-P2-CatC-Q8",
        "w": 0.9,
        "role": "need",
        "why": "Audit visibility for monitoring data"
      },
      {
        "q": "NGO-P2-CatC-Q3",
        "w": 0.7,
        "role": "scale",
        "why": "Many data systems = distributed monitoring"
      },
      {
        "q": "NGO-P2-CatC-Q1",
        "w": 0.6,
        "role": "fit_boost",
        "why": "Weak governance = data manipulation risk"
      },
      {
        "q": "NGO-P2-CatC-Q6",
        "w": 0.5,
        "role": "readiness",
        "why": "Existing data integrity methods"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 3
  },
  "UC-I-111": {
    "name": "Circular economy and waste tracking",
    "blockchainFit": 3.5,
    "rationale": "Material tracking through lifecycle. Multi-party supply chain (producer \u2192 consumer \u2192 recycler). Blockchain provides shared product passport.",
    "signals": [
      {
        "q": "NGO-P2-CatD-Q4",
        "w": 1,
        "role": "need",
        "why": "Long item journey = material lifecycle tracking"
      },
      {
        "q": "NGO-P2-CatD-Q6",
        "w": 0.9,
        "role": "need",
        "why": "Visibility gaps = waste leakage from circular system"
      },
      {
        "q": "NGO-P2-CatD-Q1",
        "w": 0.7,
        "role": "scale",
        "why": "Supply chain depth = more tracking points"
      },
      {
        "q": "NGO-P2-CatD-Q1c",
        "w": 0.6,
        "role": "scale",
        "why": "Many partners in circular chain"
      },
      {
        "q": "NGO-P2-CatD-Q3",
        "w": 0.4,
        "role": "readiness",
        "why": "Existing verification methods for materials"
      }
    ],
    "fitGate": 3,
    "readinessGate": 2.5
  },
  "UC-I-112": {
    "name": "Reforestation verification",
    "blockchainFit": 4,
    "rationale": "Immutable record of tree planting and survival. Multi-party verification (planter, auditor, funder). Prevents greenwashing.",
    "signals": [
      {
        "q": "NGO-P2-CatE-Q14",
        "w": 1,
        "role": "need",
        "why": "Milestone verification = tree planting and survival verification"
      },
      {
        "q": "NGO-P2-CatE-Q6",
        "w": 0.7,
        "role": "readiness",
        "why": "Existing evidence collection for verification"
      },
      {
        "q": "NGO-P2-CatE-Q13",
        "w": 0.8,
        "role": "fit_boost",
        "why": "Accountability gaps in reforestation claims"
      },
      {
        "q": "NGO-P2-CatC-Q8",
        "w": 0.7,
        "role": "need",
        "why": "Audit trail for planting records"
      },
      {
        "q": "NGO-P2-CatE-Q1a",
        "w": 0.5,
        "role": "scale",
        "why": "Number of planting partners/communities"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 2.5
  },
  "UC-I-113": {
    "name": "Biodiversity conservation tracking",
    "blockchainFit": 3.5,
    "rationale": "Multi-source monitoring data. Shared ledger across conservation agencies. Blockchain ensures data integrity for policy decisions.",
    "signals": [
      {
        "q": "NGO-P2-CatC-Q4",
        "w": 0.9,
        "role": "need",
        "why": "Conflicting data from multiple monitoring sources"
      },
      {
        "q": "NGO-P2-CatC-Q3",
        "w": 0.7,
        "role": "scale",
        "why": "Multiple data systems = distributed monitoring"
      },
      {
        "q": "NGO-P2-CatC-Q8",
        "w": 0.8,
        "role": "need",
        "why": "Audit trail for conservation records"
      },
      {
        "q": "NGO-P2-CatE-Q1a",
        "w": 0.6,
        "role": "scale",
        "why": "Number of conservation partners"
      },
      {
        "q": "NGO-P2-CatC-Q6",
        "w": 0.4,
        "role": "readiness",
        "why": "Existing data integrity methods"
      }
    ],
    "fitGate": 3,
    "readinessGate": 2.5
  },
  "UC-I-114": {
    "name": "Clean cookstove distribution and usage verification",
    "blockchainFit": 3.8,
    "rationale": "Distribution tracking + usage verification for carbon credits. Multi-party (manufacturer, distributor, household, carbon credit buyer). Blockchain links distribution to verified usage.",
    "signals": [
      {
        "q": "NGO-P2-CatD-Q4",
        "w": 0.9,
        "role": "need",
        "why": "Item journey = cookstove distribution chain"
      },
      {
        "q": "NGO-P2-CatE-Q14",
        "w": 0.8,
        "role": "need",
        "why": "Usage milestone verification for carbon credits"
      },
      {
        "q": "NGO-P2-CatD-Q6",
        "w": 0.7,
        "role": "need",
        "why": "Visibility gaps = are cookstoves actually being used?"
      },
      {
        "q": "NGO-P2-CatD-Q1c",
        "w": 0.6,
        "role": "scale",
        "why": "Distribution partner network size"
      },
      {
        "q": "NGO-P2-CatD-Q3",
        "w": 0.4,
        "role": "readiness",
        "why": "Existing verification methods for distribution"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 2.5
  },
  "_catJ_header": "=== CATEGORY J: Workforce and Operations (cross-category signals from B + C + E) ===",
  "UC-J-115": {
    "name": "Volunteer management and hour tracking",
    "blockchainFit": 2,
    "rationale": "Single-org internal operation. Traditional HR/volunteer management tools handle this. Only adds value for multi-org volunteer sharing.",
    "signals": [
      {
        "q": "NGO-P2-CatB-Q1b",
        "w": 0.6,
        "role": "need",
        "why": "Multiple systems = fragmented volunteer records"
      },
      {
        "q": "NGO-P2-CatE-Q1a",
        "w": 0.5,
        "role": "scale",
        "why": "Multi-org volunteer coordination"
      },
      {
        "q": "NGO-P2-CatB-Q10",
        "w": 0.5,
        "role": "fit_boost",
        "why": "Cross-org data sharing for volunteer verification"
      },
      {
        "q": "NGO-P2-CatB-Q3",
        "w": 0.3,
        "role": "readiness",
        "why": "Digital registration process maturity"
      }
    ],
    "fitGate": 3.5,
    "readinessGate": 1.5
  },
  "UC-J-116": {
    "name": "Staff deployment records across locations",
    "blockchainFit": 2.5,
    "rationale": "Cross-location staff tracking. Mostly internal HR. Blockchain adds value only for multi-org deployment coordination in humanitarian contexts.",
    "signals": [
      {
        "q": "NGO-P2-CatB-Q28",
        "w": 0.7,
        "role": "need",
        "why": "Staff system failure = deployment records lost"
      },
      {
        "q": "NGO-P2-CatB-Q1b",
        "w": 0.6,
        "role": "need",
        "why": "Multiple systems = staff tracked in different places"
      },
      {
        "q": "NGO-P2-CatE-Q1a",
        "w": 0.6,
        "role": "scale",
        "why": "Multi-location/multi-org deployments"
      },
      {
        "q": "NGO-P2-CatB-Q10",
        "w": 0.4,
        "role": "fit_boost",
        "why": "Cross-org staff sharing"
      },
      {
        "q": "NGO-P2-CatC-Q3",
        "w": 0.3,
        "role": "readiness",
        "why": "Number of data systems = integration readiness"
      }
    ],
    "fitGate": 3.5,
    "readinessGate": 2
  },
  "UC-J-117": {
    "name": "Training completion records",
    "blockchainFit": 2.8,
    "rationale": "Verifiable credentials for training. Blockchain adds value when credentials need to be portable across orgs or jurisdictions.",
    "signals": [
      {
        "q": "NGO-P2-CatB-Q10",
        "w": 0.8,
        "role": "fit_boost",
        "why": "Cross-org credential sharing = blockchain case"
      },
      {
        "q": "NGO-P2-CatB-Q1b",
        "w": 0.6,
        "role": "need",
        "why": "Multiple systems = training records fragmented"
      },
      {
        "q": "NGO-P2-CatB-Q28",
        "w": 0.5,
        "role": "need",
        "why": "System failure = lost training records"
      },
      {
        "q": "NGO-P2-CatE-Q1a",
        "w": 0.5,
        "role": "scale",
        "why": "Multi-org credential recognition"
      },
      {
        "q": "NGO-P2-CatB-Q3",
        "w": 0.3,
        "role": "readiness",
        "why": "Digital process maturity"
      }
    ],
    "fitGate": 3,
    "readinessGate": 2
  },
  "UC-J-118": {
    "name": "Safeguarding training verification",
    "blockchainFit": 3.5,
    "rationale": "Critical compliance requirement. Immutable proof of training completion. Particularly valuable for cross-org staff movement where safeguarding verification must be portable.",
    "signals": [
      {
        "q": "NGO-P2-CatB-Q10",
        "w": 0.9,
        "role": "fit_boost",
        "why": "Cross-org verification = blockchain's multi-party trust"
      },
      {
        "q": "NGO-P2-CatB-Q28",
        "w": 0.8,
        "role": "need",
        "why": "System failure = lost safeguarding records = risk"
      },
      {
        "q": "NGO-P2-CatE-Q13",
        "w": 0.7,
        "role": "need",
        "why": "Accountability gaps = safeguarding compliance gaps"
      },
      {
        "q": "NGO-P2-CatE-Q1a",
        "w": 0.6,
        "role": "scale",
        "why": "Multi-org safeguarding coordination"
      },
      {
        "q": "NGO-P2-CatC-Q8",
        "w": 0.5,
        "role": "need",
        "why": "Audit trail for training compliance"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 2.5
  },
  "UC-J-119": {
    "name": "Security clearance and access management",
    "blockchainFit": 3,
    "rationale": "Verifiable security clearances across locations. Blockchain prevents credential fraud. Most valuable in multi-org or multi-jurisdiction contexts.",
    "signals": [
      {
        "q": "NGO-P2-CatC-Q8",
        "w": 0.9,
        "role": "need",
        "why": "Audit trail = who accessed what and when"
      },
      {
        "q": "NGO-P2-CatB-Q28",
        "w": 0.7,
        "role": "need",
        "why": "System failure = security records compromised"
      },
      {
        "q": "NGO-P2-CatB-Q10",
        "w": 0.6,
        "role": "fit_boost",
        "why": "Cross-org clearance verification"
      },
      {
        "q": "NGO-P2-CatC-Q1",
        "w": 0.5,
        "role": "need",
        "why": "Weak governance = security access unclear"
      },
      {
        "q": "NGO-P2-CatC-Q6",
        "w": 0.4,
        "role": "readiness",
        "why": "Existing security data integrity methods"
      }
    ],
    "fitGate": 3,
    "readinessGate": 2.5
  },
  "UC-J-120": {
    "name": "Duty of care / staff location tracking in emergencies",
    "blockchainFit": 2.5,
    "rationale": "Real-time location tracking in emergencies. Traditional systems (GPS, apps) handle this. Blockchain adds value for immutable audit trail of duty of care compliance.",
    "signals": [
      {
        "q": "NGO-P2-CatA-Q30",
        "w": 0.8,
        "role": "need",
        "why": "Financial failure points correlate with operational crisis risk"
      },
      {
        "q": "NGO-P2-CatB-Q28",
        "w": 0.7,
        "role": "need",
        "why": "Identity system failure = can't track staff in crisis"
      },
      {
        "q": "NGO-P2-CatC-Q8",
        "w": 0.6,
        "role": "need",
        "why": "Audit trail for duty of care compliance"
      },
      {
        "q": "NGO-P2-CatE-Q1a",
        "w": 0.5,
        "role": "scale",
        "why": "Multi-location staff across crisis zones"
      },
      {
        "q": "NGO-P2-CatC-Q6",
        "w": 0.3,
        "role": "readiness",
        "why": "Data integrity for location tracking"
      }
    ],
    "fitGate": 3.5,
    "readinessGate": 2
  },
  "UC-J-121": {
    "name": "Contractor and consultant verification",
    "blockchainFit": 2.8,
    "rationale": "Verifiable credentials and performance records for contractors. Useful when multiple orgs share contractors and need trust in credentials.",
    "signals": [
      {
        "q": "NGO-P2-CatB-Q10",
        "w": 0.8,
        "role": "fit_boost",
        "why": "Cross-org contractor verification = multi-party trust"
      },
      {
        "q": "NGO-P2-CatB-Q1b",
        "w": 0.6,
        "role": "need",
        "why": "Multiple systems = fragmented contractor records"
      },
      {
        "q": "NGO-P2-CatB-Q28",
        "w": 0.6,
        "role": "need",
        "why": "System failure = lost contractor credentials"
      },
      {
        "q": "NGO-P2-CatE-Q1a",
        "w": 0.5,
        "role": "scale",
        "why": "Multi-org contractor pool"
      },
      {
        "q": "NGO-P2-CatC-Q8",
        "w": 0.4,
        "role": "need",
        "why": "Audit trail for contractor compliance"
      }
    ],
    "fitGate": 3,
    "readinessGate": 2
  },
  "UC-D-068": {
    "name": "Aid diversion detection and prevention",
    "blockchainFit": 4.3,
    "rationale": "Classic fit. Multi-party chain with adversarial actors, losses triggered irreversibly once goods leave custody, detection latency is a direct loss multiplier. Immutable handoff records + anomaly surfacing + partner attribution is a strong B3/B2/B7 case.",
    "signals": [
      {
        "q": "NGO-P2-CatD-Q8",
        "w": 1.0,
        "role": "need",
        "why": "Biggest failure point \u2014 last-mile diversion is option 1"
      },
      {
        "q": "NGO-P2-CatD-Q1b",
        "w": 0.9,
        "role": "need",
        "why": "Share of distributions with problems \u2014 direct severity signal"
      },
      {
        "q": "NGO-P2-CatD-Q6",
        "w": 0.8,
        "role": "need",
        "why": "Visibility gaps in transit / field distribution / partner handover"
      },
      {
        "q": "NGO-P2-CatD-Q1c",
        "w": 0.7,
        "role": "fit_boost",
        "why": "Number of partners and intermediaries \u2014 more partners, stronger fit for shared ledger"
      },
      {
        "q": "NGO-P2-CatD-Q1a",
        "w": 0.5,
        "role": "scale",
        "why": "Monthly distribution volume \u2014 scale of the problem"
      },
      {
        "q": "NGO-P2-CatD-Q5",
        "w": 0.6,
        "role": "need",
        "why": "Recurring counterfeit / quality failures reinforce the fraud-control framing"
      }
    ],
    "fitGate": 3.0,
    "readinessGate": 2.5,
    "interagency": true
  },
  "UC-D-069": {
    "name": "Beneficiary receipt confirmation (proof of delivery)",
    "blockchainFit": 4.0,
    "rationale": "Beneficiary-attested proof of delivery is a strong B3/B2 case when receipts must be verifiable by external parties (donors, auditors) and the org is one of the parties being audited. B5 becomes active when receipts trigger irreversible fund flow. Lower than UC-D-068 because the attacker surface is narrower (receipt fabrication rather than multi-actor diversion).",
    "signals": [
      {
        "q": "NGO-P2-CatD-Q4",
        "w": 1.0,
        "role": "need",
        "why": "Tracking gap at last mile \u2014 directly the problem proof-of-delivery solves"
      },
      {
        "q": "NGO-P2-CatD-Q8",
        "w": 0.9,
        "role": "need",
        "why": "Last-mile delivery as biggest failure point"
      },
      {
        "q": "NGO-P2-CatD-Q1b",
        "w": 0.8,
        "role": "need",
        "why": "Share of distributions with problems \u2014 receipt confirmation is the primary control"
      },
      {
        "q": "NGO-P2-CatD-Q2",
        "w": 0.7,
        "role": "need",
        "why": "Strength of current beneficiary verification \u2014 weaker current state, stronger fit"
      },
      {
        "q": "NGO-P2-CatD-Q1a",
        "w": 0.6,
        "role": "scale",
        "why": "Volume of deliveries \u2014 scale justifies investment in cryptographic receipts"
      },
      {
        "q": "NGO-P2-CatD-Q1c",
        "w": 0.5,
        "role": "fit_boost",
        "why": "Multi-partner chains amplify value of tamper-evident receipts"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 2.5
  },
  "UC-D-070": {
    "name": "Conflict mineral and material tracking",
    "blockchainFit": 4.2,
    "rationale": "Classic regulated supply-chain case. Multi-tier actors, no shared trust anchor, strong external verifier needs, hard regulatory requirements, existing industry precedent for blockchain-anchored provenance. B1/B3/B6/B7 all active. Higher complexity moderates the fit slightly.",
    "signals": [
      {
        "q": "NGO-P2-CatD-Q1",
        "w": 1.0,
        "role": "need",
        "why": "Supplier-tier depth \u2014 more tiers between org and origin, stronger fit for shared provenance ledger"
      },
      {
        "q": "NGO-P2-CatD-Q1c",
        "w": 0.9,
        "role": "fit_boost",
        "why": "Distinct suppliers and intermediaries \u2014 multi-party B1 case"
      },
      {
        "q": "NGO-P2-CatD-Q3",
        "w": 0.8,
        "role": "need",
        "why": "Current verification methods \u2014 weaker verification = stronger fit for provable integrity"
      },
      {
        "q": "NGO-P2-CatD-Q5",
        "w": 0.8,
        "role": "need",
        "why": "Counterfeit / quality-failure incidents \u2014 direct provenance-dispute signal"
      },
      {
        "q": "NGO-P2-CatD-Q6",
        "w": 0.7,
        "role": "need",
        "why": "Visibility gaps in the upstream chain \u2014 provenance ledger value"
      },
      {
        "q": "NGO-P2-CatD-Q1a",
        "w": 0.6,
        "role": "scale",
        "why": "Procurement volume \u2014 justifies per-batch tracking overhead"
      },
      {
        "q": "NGO-P2-CatF-Q16",
        "w": 0.7,
        "role": "fit_boost",
        "why": "Donor-driven transparency / technology requirements \u2014 ESG sourcing clauses originate here"
      },
      {
        "q": "NGO-P2-CatF-Q5",
        "w": 0.5,
        "role": "fit_boost",
        "why": "Donor proof requirements \u2014 what donors accept as evidence of compliance"
      }
    ],
    "fitGate": 3.0,
    "readinessGate": 3.0
  },
  "UC-D-071": {
    "name": "Customs and import documentation",
    "blockchainFit": 3.8,
    "rationale": "Strong B1/B3/B4 case on paper \u2014 multi-party, trust-sensitive, document-centric. Moderated by ecosystem adoption reality (a major shipping-consortium platform shut down in 2022; customs authorities often mandate proprietary systems). B7 active when duty-exemption is programmable. Lower than UC-D-070 because the adoption path is more constrained.",
    "signals": [
      {
        "q": "NGO-P2-CatD-Q1",
        "w": 0.9,
        "role": "need",
        "why": "Supplier-tier depth \u2014 more tiers often means more cross-border movements"
      },
      {
        "q": "NGO-P2-CatD-Q4",
        "w": 1.0,
        "role": "need",
        "why": "End-to-end shipment journey \u2014 customs is where visibility commonly breaks"
      },
      {
        "q": "NGO-P2-CatD-Q6",
        "w": 0.8,
        "role": "need",
        "why": "Visibility gaps \u2014 customs is a classic gap point"
      },
      {
        "q": "NGO-P2-CatD-Q1a",
        "w": 0.7,
        "role": "scale",
        "why": "Transaction volume \u2014 high volume makes per-shipment automation valuable"
      },
      {
        "q": "NGO-P2-CatD-Q1c",
        "w": 0.6,
        "role": "fit_boost",
        "why": "Distinct intermediaries \u2014 brokers, freight forwarders, customs authorities"
      },
      {
        "q": "NGO-P2-CatF-Q5",
        "w": 0.5,
        "role": "fit_boost",
        "why": "Donor proof-of-fund-deployment \u2014 in-kind imports require customs documentation for donor audit"
      }
    ],
    "fitGate": 2.75,
    "readinessGate": 3.0
  },
  "UC-A-024": {
    "name": "Currency hedging and stability (stablecoin alternatives)",
    "blockchainFit": 4.4,
    "rationale": "Native blockchain use case \u2014 stablecoin-based treasury is inherently on-chain, with B4 (disintermediation of banking/FX infrastructure), B5 (settlement finality), and B7 (programmable allocation) all strongly active. B6 relevant where treasury-to-beneficiary flows carry sensitive metadata. Moderated by regulatory fit and donor acceptance rather than technical fit.",
    "signals": [
      {
        "q": "NGO-P2-CatA-Q5",
        "w": 1.0,
        "role": "need",
        "why": "Countries/corridors where traditional banking struggles \u2014 direct driver for stablecoin alternatives"
      },
      {
        "q": "NGO-P2-CatA-Q6",
        "w": 0.9,
        "role": "need",
        "why": "Frequency of blocked / frozen / delayed transfers \u2014 B4 value proposition"
      },
      {
        "q": "NGO-P2-CatA-Q4",
        "w": 0.8,
        "role": "need",
        "why": "Cost per transfer \u2014 stablecoin rails typically reduce cost materially"
      },
      {
        "q": "NGO-P2-CatA-Q3",
        "w": 0.7,
        "role": "need",
        "why": "Time from initiate to in-country availability \u2014 B5 settlement finality driver"
      },
      {
        "q": "NGO-P2-CatA-Q7",
        "w": 0.6,
        "role": "need",
        "why": "Compliance-check overhead on transfers \u2014 programmable compliance (B7) signal"
      },
      {
        "q": "NGO-P2-CatA-Q2",
        "w": 0.5,
        "role": "fit_boost",
        "why": "Intermediary count \u2014 more intermediaries amplify disintermediation value"
      },
      {
        "q": "NGO-P2-CatA-Q31",
        "w": 0.4,
        "role": "fit_boost",
        "why": "Community cash availability \u2014 affects viability of stablecoin-to-cash on/off ramps"
      }
    ],
    "fitGate": 3.0,
    "readinessGate": 3.0
  },
  "UC-F-090": {
    "name": "Donor identity verification for AML compliance",
    "blockchainFit": 4.0,
    "rationale": "Strong B2/B3/B6 case for verifiable-credential-based donor KYC with reusable proofs across NGOs; B7 active when AML rules gate donation acceptance programmatically. Particularly strong for crypto-donation flows where on-chain sanctions screening is already native. Moderated by the fact that most established NGOs already use commercial KYC vendors for fiat donors \u2014 blockchain's added value is strongest at the margins (crypto, cross-NGO reuse, donor privacy).",
    "signals": [
      {
        "q": "NGO-P2-CatF-Q1",
        "w": 0.8,
        "role": "scale",
        "why": "Donor count and mix \u2014 more donors, more KYC automation value"
      },
      {
        "q": "NGO-P2-CatA-Q7",
        "w": 0.9,
        "role": "need",
        "why": "Time spent on compliance / sanctions screening for transfers \u2014 direct AML overhead signal"
      },
      {
        "q": "NGO-P2-CatF-Q9",
        "w": 0.8,
        "role": "need",
        "why": "Independent verification / audit requests from donors \u2014 drives evidence model"
      },
      {
        "q": "NGO-P2-CatF-Q7",
        "w": 0.7,
        "role": "need",
        "why": "Lost donors due to transparency \u2014 KYC is a trust anchor"
      },
      {
        "q": "NGO-P2-CatF-Q16",
        "w": 0.7,
        "role": "fit_boost",
        "why": "Donor technology preferences \u2014 alignment with blockchain approaches"
      },
      {
        "q": "NGO-P2-CatA-Q27",
        "w": 0.5,
        "role": "fit_boost",
        "why": "Friction / fee / delay pain across payment flows \u2014 AML friction is part of this"
      }
    ],
    "fitGate": 2.75,
    "readinessGate": 3.0
  },
  "UC-A-025": {
    "name": "Insurance for field staff and organisational assets",
    "blockchainFit": 4.1,
    "rationale": "Strong B5/B7 case for parametric staff and asset insurance - smart-contract payouts on objective triggers collapse settlement time from weeks to hours. B4 active when an NGO-mutual or DeFi-capital pool disintermediates traditional broker+reinsurer chains, which is especially valuable in fragile-state markets where commercial capacity is scarce. B3 gives tamper-evident claim evidence - critical in contested K&R or asset-loss claims. Moderated by insurance being heavily regulated: fully on-chain structures can be non-compliant in NGO home jurisdictions, so most viable models are hybrid (commercial carrier + blockchain-assisted evidence and payout rail).",
    "signals": [
      {
        "q": "NGO-P2-CatJ-Q11",
        "w": 1.0,
        "role": "need",
        "why": "International insurance management for deployed staff - direct need signal for this UC"
      },
      {
        "q": "NGO-P2-CatJ-Q15",
        "w": 0.9,
        "role": "need",
        "why": "Biggest workforce-related risk - drives coverage priorities and claim sensitivity"
      },
      {
        "q": "NGO-P2-CatG-Q1",
        "w": 0.8,
        "role": "scale",
        "why": "Operational risk profile - scales the insurance footprint across asset and continuity risks"
      },
      {
        "q": "NGO-P2-CatG-Q11",
        "w": 0.6,
        "role": "fit_boost",
        "why": "Cyber incident exposure - informs asset-coverage scope and claim-evidence needs"
      },
      {
        "q": "NGO-P2-CatA-Q30",
        "w": 0.6,
        "role": "fit_boost",
        "why": "Single point of failure identification - surfaces catastrophe-class risks worth pooling"
      },
      {
        "q": "NGO-P2-CatA-Q6",
        "w": 0.5,
        "role": "fit_boost",
        "why": "Transfers blocked or delayed - speaks to payout-delivery constraints in crisis"
      }
    ],
    "fitGate": 2.75,
    "readinessGate": 2.75
  },
  "UC-E-080": {
    "name": "Board decision recording and verification",
    "blockchainFit": 3.4,
    "rationale": "Strong B3/B6/B7 case for cryptographically-attested board decisions with selective confidentiality. Value concentrates in multi-jurisdiction boards and donor-audit contexts. Moderated by: most NGO boards are small and minute-takers + e-signature workflows handle this adequately; blockchain adds value at the margins where director distribution, confidentiality tiering, or auto-execution (DAO-style) are real needs.",
    "signals": [
      {
        "q": "NGO-P2-CatE-Q1",
        "w": 0.8,
        "role": "need",
        "why": "Governance maturity / formality \u2014 higher formality = higher attestation value"
      },
      {
        "q": "NGO-P2-CatE-Q5",
        "w": 0.7,
        "role": "need",
        "why": "Board decision frequency and materiality"
      },
      {
        "q": "NGO-P0-S2-Q9",
        "w": 0.5,
        "role": "scale",
        "why": "Governance structure \u2014 board / trustee setup from P0",
        "when": [
          "Board of trustees/directors with appointed CEO/ED",
          "Federated structure (national affiliates with central coordination)",
          "Membership-elected leadership"
        ]
      },
      {
        "q": "NGO-P2-CatE-Q12",
        "w": 0.6,
        "role": "fit_boost",
        "why": "Donor / funder audit requirements on governance decisions"
      },
      {
        "q": "NGO-P2-CatC-Q7",
        "w": 0.4,
        "role": "fit_boost",
        "why": "Cross-partner governance friction \u2014 consortium board overlaps"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 2.5
  },
  "UC-E-081": {
    "name": "Policy version control and attestation",
    "blockchainFit": 3.3,
    "rationale": "Strong B3/B7 case for versioned-policy attestation with cryptographic proof of who signed what when. Clearest value when the NGO has a large policy portfolio, donor compliance requirements for evidence of live attestation, and a large attestor population (staff + partners). B6 active if safeguarding / PSEA attestations must remain anonymous at the individual level while being verifiable at the cohort level.",
    "signals": [
      {
        "q": "NGO-P2-CatE-Q2",
        "w": 0.8,
        "role": "need",
        "why": "Policy portfolio size and attestation discipline"
      },
      {
        "q": "NGO-P0-S6-Q20",
        "w": 0.7,
        "role": "need",
        "why": "Voluntary compliance frameworks signalling attestation culture",
        "when": [
          "IASC Data Responsibility Guidelines",
          "Sphere Standards data protection provisions",
          "CHS Alliance data commitments",
          "Beneficiary privacy policies (organisation-specific)",
          "Internal data governance framework"
        ]
      },
      {
        "q": "NGO-P2-CatE-Q12",
        "w": 0.6,
        "role": "fit_boost",
        "why": "Donor demand for attestation evidence"
      },
      {
        "q": "NGO-P0-S2-Q7",
        "w": 0.4,
        "role": "readiness",
        "why": "Staff size \u2014 scales attestor population"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 2.5
  },
  "UC-E-082": {
    "name": "Conflict of interest declaration management",
    "blockchainFit": 3.2,
    "rationale": "B3/B6 case for versioned, selectively-disclosed CoI declarations with optional B7 auto-recusal enforcement. Strongest for grant-making NGOs, institutional-trustee boards, and large consortia where a CoI affects who can sign what. Moderated by: simple CoI registers in spreadsheets or HR platforms work for many NGOs; blockchain earns its keep at the intersection of scale (many declarants), confidentiality (layered disclosure), and automation (programmatic recusal).",
    "signals": [
      {
        "q": "NGO-P2-CatE-Q3",
        "w": 0.8,
        "role": "need",
        "why": "Grant-making / resource-allocation authority \u2014 core CoI exposure"
      },
      {
        "q": "NGO-P0-S2-Q9",
        "w": 0.6,
        "role": "need",
        "why": "Board / governance structure identifies declarant population",
        "when": [
          "Board of trustees/directors with appointed CEO/ED",
          "Federated structure (national affiliates with central coordination)",
          "Membership-elected leadership",
          "Founder-led with advisory board",
          "Government-appointed or statutory body"
        ]
      },
      {
        "q": "NGO-P2-CatE-Q12",
        "w": 0.6,
        "role": "fit_boost",
        "why": "Donor CoI attestation requirements"
      },
      {
        "q": "NGO-P0-S5-Q17b",
        "w": 0.5,
        "role": "scale",
        "why": "Partner count \u2014 CoI exposure scales with partnership volume"
      },
      {
        "q": "NGO-P2-CatC-Q7",
        "w": 0.3,
        "role": "fit_boost",
        "why": "Cross-partner data-sharing friction that may surface CoI boundaries"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 2.5
  },
  "UC-E-083": {
    "name": "Standards compliance and accreditation certification",
    "blockchainFit": 3.6,
    "rationale": "Strong B3/B6/B7 case when the NGO holds multiple standards certifications (CHS, Sphere, ISO) and needs real-time status verification for donors and partners. B6 selective disclosure is key \u2014 certification status can be public while underlying audit evidence stays confidential. Particularly valuable where certification lapses have historically caused funding disruption (a concrete B7 enforcement use). Moderated by: standards bodies are only beginning to issue native VCs; most current deployments are hybrid (certificate issued traditionally, hash anchored on chain).",
    "signals": [
      {
        "q": "NGO-P2-CatE-Q4",
        "w": 0.9,
        "role": "need",
        "why": "Number of active standards certifications held"
      },
      {
        "q": "NGO-P0-S6-Q20",
        "w": 0.7,
        "role": "need",
        "why": "Voluntary compliance frameworks \u2014 proxy for certification portfolio",
        "when": [
          "IASC Data Responsibility Guidelines",
          "Sphere Standards data protection provisions",
          "CHS Alliance data commitments"
        ]
      },
      {
        "q": "NGO-P2-CatE-Q12",
        "w": 0.7,
        "role": "fit_boost",
        "why": "Donor requirement for certification evidence"
      },
      {
        "q": "NGO-P2-CatE-Q13",
        "w": 0.5,
        "role": "fit_boost",
        "why": "Partner / consortium certification cross-verification"
      },
      {
        "q": "NGO-P0-S4-Q15",
        "w": 0.4,
        "role": "scale",
        "why": "Funding sources \u2014 institutional donors have stricter certification expectations",
        "when": [
          "Institutional donors (USAID, DFID/FCDO, EU, etc.)",
          "UN agencies (as a sub-grantee or implementing partner)"
        ]
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 2.5
  },
  "UC-D-072": {
    "name": "Ethical sourcing verification",
    "blockchainFit": 3.7,
    "rationale": "Strong B1/B3/B4 case for multi-party supply-chain integrity where suppliers, certifiers, buyers, and auditors need shared truth without a central authority. Particularly strong for sector-sensitive commodities (textiles with SA8000, food with Fair Trade / Rainforest Alliance, electronics with conflict-minerals tracking). B7 active where procurement policies can programmatically enforce standards compliance at payment-authorisation time. Moderated by: mature commercial supply-chain traceability stacks exist as adoptable products rather than greenfield builds.",
    "signals": [
      {
        "q": "NGO-P2-CatD-Q1",
        "w": 0.8,
        "role": "need",
        "why": "Procurement volume and supply-chain complexity"
      },
      {
        "q": "NGO-P2-CatD-Q5",
        "w": 0.8,
        "role": "need",
        "why": "Supplier-integrity incident history and donor-ethical requirements"
      },
      {
        "q": "NGO-P2-CatD-Q8",
        "w": 0.6,
        "role": "scale",
        "why": "Supplier-population size"
      },
      {
        "q": "NGO-P0-S4-Q15",
        "w": 0.5,
        "role": "fit_boost",
        "why": "Institutional donor funding \u2014 ethical-sourcing compliance expectations",
        "when": [
          "Institutional donors (USAID, DFID/FCDO, EU, etc.)",
          "UN agencies (as a sub-grantee or implementing partner)"
        ]
      },
      {
        "q": "NGO-P2-CatE-Q13",
        "w": 0.4,
        "role": "fit_boost",
        "why": "Partner capacity verification \u2014 suppliers may be partners"
      }
    ],
    "fitGate": 2.75,
    "readinessGate": 2.5
  },
  "UC-D-073": {
    "name": "Food safety and quality tracking",
    "blockchainFit": 3.8,
    "rationale": "Strong B3/B4/B7 case for humanitarian food-aid at scale. Contamination / spoilage events with beneficiary-safety impact demand rapid, verifiable recall \u2014 blockchain's batch-to-beneficiary propagation pattern plus smart-contract recall trigger logic collapse recall time from days to hours. Particularly strong for fortified food, therapeutic nutrition, and fresh-produce programmes. Moderated by: high dependency on IoT and lab-integration which represents significant capex.",
    "signals": [
      {
        "q": "NGO-P2-CatD-Q3",
        "w": 0.9,
        "role": "need",
        "why": "Food-aid volume and batch complexity"
      },
      {
        "q": "NGO-P2-CatD-Q6",
        "w": 0.8,
        "role": "need",
        "why": "Safety-incident history and recall-capability gaps"
      },
      {
        "q": "NGO-P0-S1-Q7",
        "w": 0.5,
        "role": "scale",
        "why": "Operating-country count \u2014 multi-country recall coordination"
      },
      {
        "q": "NGO-P2-CatD-Q1",
        "w": 0.6,
        "role": "fit_boost",
        "why": "Supply-chain tier depth feeding into recall reach"
      }
    ],
    "fitGate": 2.75,
    "readinessGate": 2.5
  },
  "UC-C-052": {
    "name": "Whistleblower and reporting channel integrity",
    "blockchainFit": 3.5,
    "rationale": "Strong B3/B4/B6 case for channel-integrity (distinct from UC-E-072 whistleblower-identity protection). Value concentrates where tampering has been suspected, where deliverability-proof matters for regulatory compliance (EU Whistleblower Directive), or where reports must route across consortium members or to external oversight. Moderated by: mature open-source tooling (open-source whistleblowing platforms) already solves the core submission-secrecy problem; blockchain adds end-to-end tamper-evidence on top.",
    "signals": [
      {
        "q": "NGO-P0-S6-Q20",
        "w": 0.6,
        "role": "need",
        "why": "Follows voluntary data-protection standards, so a reporting channel is expected to prove it was not tampered with",
        "when": [
          "IASC Data Responsibility Guidelines",
          "Sphere Standards data protection provisions",
          "CHS Alliance data commitments",
          "Beneficiary privacy policies (organisation-specific)",
          "Internal data governance framework"
        ]
      },
      {
        "q": "NGO-P0-S2-Q7",
        "w": 0.5,
        "role": "scale",
        "why": "Staff size \u2014 reporter population scales integrity value"
      },
      {
        "q": "NGO-P2-CatE-Q14",
        "w": 0.6,
        "role": "fit_boost",
        "why": "Cross-org reporting channel needs (consortium whistleblowing)"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 2.5
  },
  "UC-B-039": {
    "name": "Cross-agency credential portability for humanitarian workforce",
    "blockchainFit": 4.2,
    "rationale": "Strong B1/B3/B6/B7 case \u2014 no central humanitarian HR authority, credential integrity matters across issuers, selective disclosure of sensitive attestations (safeguarding, medical), programmatic verification at surge-roster activation. Particularly strong for UN-family agencies, large INGOs with surge capacity (IRC, Save the Children, Mercy Corps), and consortium staffing arrangements. Moderated by issuer readiness (most HR and training providers are not VC-native yet) and the coordination cost of establishing trust frameworks across agencies.",
    "interagency": true,
    "signals": [
      {
        "q": "NGO-P0-S1-Q4",
        "w": 0.9,
        "role": "need",
        "why": "UN agency or consortium org type \u2014 strongest interagency signal",
        "when": [
          "UN agency or programme",
          "Network or consortium"
        ]
      },
      {
        "q": "NGO-P0-S5-Q18",
        "w": 0.8,
        "role": "need",
        "why": "Coordination mechanisms (clusters, consortia) \u2014 workforce mobility context",
        "when": [
          "UN OCHA coordination clusters",
          "Humanitarian consortium or alliance"
        ]
      },
      {
        "q": "NGO-P2-CatB-Q10",
        "w": 0.6,
        "role": "fit_boost",
        "why": "Cross-org sharing pattern \u2014 if org shares beneficiary populations, staff mobility often follows"
      },
      {
        "q": "NGO-P0-S1-Q7",
        "w": 0.6,
        "role": "scale",
        "why": "Operating countries \u2014 scales credential-portability value"
      },
      {
        "q": "NGO-P2-CatB-Q28",
        "w": 0.5,
        "role": "need",
        "why": "Key staff departure as failure point \u2014 credential continuity need"
      },
      {
        "q": "NGO-P0-S2-Q7",
        "w": 0.5,
        "role": "scale",
        "why": "Staff size \u2014 scales hire volume and re-verification burden"
      }
    ],
    "fitGate": 2.75,
    "readinessGate": 2.5
  },
  "UC-F-091": {
    "name": "Pooled fund disbursement tracking (CERF, CBPFs, MPTFO)",
    "blockchainFit": 4.0,
    "rationale": "Strong B3/B4/B7 case. Pooled funds are the clearest multi-party non-trusting fund-flow pattern in humanitarian finance \u2014 donors, pool manager, implementing agencies, sub-grantees, and beneficiaries all need shared truth without a single trusted authority. Programmatic milestone release (B7) and cryptographic allocation proofs (B3) significantly reduce audit cost. Particularly strong for agencies participating in CERF, UN CBPFs, MPTFO, or receiving institutional co-financing from multiple donors. Moderated by the fact that existing pooled-fund operations work \u2014 blockchain value is in reducing reporting burden and audit disputes, not solving a broken process.",
    "interagency": true,
    "signals": [
      {
        "q": "NGO-P0-S4-Q15",
        "w": 0.9,
        "role": "need",
        "why": "Funding sources including UN agencies / institutional donors \u2014 pooled-fund participation signal",
        "when": [
          "Institutional donors (USAID, DFID/FCDO, EU, etc.)",
          "UN agencies (as a sub-grantee or implementing partner)"
        ]
      },
      {
        "q": "NGO-P0-S1-Q4",
        "w": 0.7,
        "role": "need",
        "why": "UN agency or consortium org type \u2014 common pool-fund recipient profile",
        "when": [
          "UN agency or programme",
          "Network or consortium"
        ]
      },
      {
        "q": "NGO-P2-CatF-Q9",
        "w": 0.7,
        "role": "need",
        "why": "Independent verification / audit requests from donors"
      },
      {
        "q": "NGO-P0-S5-Q17b",
        "w": 0.6,
        "role": "scale",
        "why": "Partner count \u2014 sub-grantee chain depth"
      },
      {
        "q": "NGO-P2-CatA-Q7",
        "w": 0.5,
        "role": "fit_boost",
        "why": "Time spent on compliance / sanctions screening for transfers"
      },
      {
        "q": "NGO-P0-S4-Q14b",
        "w": 0.4,
        "role": "scale",
        "why": "Budget trend \u2014 volatile / growing often indicates pooled-fund activity"
      }
    ],
    "fitGate": 2.75,
    "readinessGate": 2.75
  },
  "UC-I-115": {
    "name": "Co-financed MRV registry (multi-funder climate and conservation programmes)",
    "blockchainFit": 4.3,
    "rationale": "Very strong B3/B4/B6/B7 case. Multi-funder MRV is exactly the problem blockchain solves \u2014 shared truth across parties that don't trust each other individually, with programmatic double-counting prevention. Particularly strong when carbon credits or climate-finance attribution is involved (B7 retirement smart-contracts). Active innovation space \u2014 carbon-rating providers and registry pilots are all moving in this direction. Moderated by: carbon-market blockchain solutions already exist as products, so for most NGOs the question is adoption not build; and traditional NGOs without carbon-market exposure may not need the full MRV registry pattern.",
    "interagency": true,
    "signals": [
      {
        "q": "NGO-P2-CatI-Q1",
        "w": 0.9,
        "role": "need",
        "why": "Climate / environmental programme activity \u2014 primary need signal"
      },
      {
        "q": "NGO-P0-S4-Q15",
        "w": 0.7,
        "role": "need",
        "why": "Funding sources \u2014 multi-donor climate co-financing",
        "when": [
          "Institutional donors (USAID, DFID/FCDO, EU, etc.)",
          "UN agencies (as a sub-grantee or implementing partner)",
          "Corporate partnerships"
        ]
      },
      {
        "q": "NGO-P2-CatI-Q5",
        "w": 0.7,
        "role": "need",
        "why": "Carbon credit / climate reporting requirements"
      },
      {
        "q": "NGO-P0-S5-Q18",
        "w": 0.5,
        "role": "fit_boost",
        "why": "Coordination mechanisms \u2014 climate-finance consortia",
        "when": [
          "Humanitarian consortium or alliance",
          "Donor coordination groups"
        ]
      },
      {
        "q": "NGO-P2-CatI-Q8",
        "w": 0.6,
        "role": "fit_boost",
        "why": "MRV and evidence-reporting burden"
      },
      {
        "q": "NGO-P0-S1-Q7",
        "w": 0.4,
        "role": "scale",
        "why": "Operating countries \u2014 scales MRV footprint"
      }
    ],
    "fitGate": 2.75,
    "readinessGate": 2.5
  },
  "UC-D-074": {
    "name": "Pooled humanitarian commodity claims and replenishment (UNHRD, WFP Hubs)",
    "blockchainFit": 3.9,
    "rationale": "Strong B1/B3/B4/B7 case. Shared stockpile operations are a textbook pooled-resource pattern \u2014 member agencies need to trust claim / replenishment integrity without a single operator controlling the truth. Particularly strong for agencies that regularly draw from UNHRD depots, WFP Global Logistics Cluster hubs, or IFRC pre-positioning networks. B7 auto-settlement logic cuts reconciliation time substantially. Moderated by the fact that existing pool operations are trust-based and function well \u2014 blockchain adds precision and dispute-resolution strength but doesn't fix a broken process.",
    "interagency": true,
    "signals": [
      {
        "q": "NGO-P0-S5-Q18",
        "w": 0.9,
        "role": "need",
        "why": "OCHA clusters / humanitarian consortia \u2014 strongest stockpile-access signal",
        "when": [
          "UN OCHA coordination clusters",
          "Humanitarian consortium or alliance"
        ]
      },
      {
        "q": "NGO-P0-S1-Q4",
        "w": 0.7,
        "role": "need",
        "why": "UN agency or Red Cross / Red Crescent movement \u2014 primary stockpile users",
        "when": [
          "UN agency or programme",
          "Red Cross or Red Crescent movement"
        ]
      },
      {
        "q": "NGO-P2-CatD-Q1",
        "w": 0.6,
        "role": "scale",
        "why": "Supply-chain complexity \u2014 pool access correlates with chain sophistication"
      },
      {
        "q": "NGO-P2-CatD-Q2",
        "w": 0.7,
        "role": "need",
        "why": "Emergency-response commodity flow needs"
      },
      {
        "q": "NGO-P0-S1-Q7",
        "w": 0.5,
        "role": "scale",
        "why": "Operating countries \u2014 multi-country ops more likely to use shared hubs"
      },
      {
        "q": "NGO-P2-CatE-Q13",
        "w": 0.4,
        "role": "fit_boost",
        "why": "Partner coordination \u2014 stockpile sharing often rides on cluster coordination"
      }
    ],
    "fitGate": 2.75,
    "readinessGate": 2.5
  },
  "UC-E-084": {
    "name": "Shared implementing-partner due diligence and sanctions screening",
    "blockchainFit": 4.1,
    "rationale": "Strong B3/B4/B6/B7 case. Shared DD is one of the clearest humanitarian-interagency efficiency wins \u2014 each agency currently runs independent DD on the same partners (wasted effort) with inconsistent outcomes (regulatory risk). Blockchain DD ledger with B6 selective disclosure and B7 continuous sanctions-screening is the obvious solution. Particularly strong for consortium members (Start Network, ACT Alliance), agencies with heavy sanctions-compliance obligations (OFAC-exposed work), and FCDO / EU-funded agencies. Moderated by the coordination challenge of establishing which findings become shared \u2014 agencies are sensitive about revealing their assessment approaches.",
    "interagency": true,
    "signals": [
      {
        "q": "NGO-P0-S5-Q17a",
        "w": 0.8,
        "role": "need",
        "why": "Partnership model \u2014 partner-heavy delivery = DD exposure",
        "when": [
          "Yes, extensively (most programmes delivered through partners)",
          "Yes, for some programmes"
        ]
      },
      {
        "q": "NGO-P0-S5-Q17b",
        "w": 0.8,
        "role": "need",
        "why": "Partner count scales DD burden"
      },
      {
        "q": "NGO-P0-S6-Q21",
        "w": 0.8,
        "role": "need",
        "why": "Financial regulatory / AML / sanctions compliance obligations",
        "when": [
          "AML/CFT (Anti-Money Laundering/Counter-Financing of Terrorism)",
          "OFAC or other sanctions compliance",
          "Financial reporting to regulators"
        ]
      },
      {
        "q": "NGO-P0-S5-Q18",
        "w": 0.7,
        "role": "need",
        "why": "Consortium / coordination mechanism participation",
        "when": [
          "UN OCHA coordination clusters",
          "Humanitarian consortium or alliance",
          "Technical working groups (e.g., CaLP, NetHope)",
          "Regional NGO networks or platforms",
          "Government coordination mechanisms",
          "Donor coordination groups"
        ]
      },
      {
        "q": "NGO-P0-S5-Q19",
        "w": 0.6,
        "role": "fit_boost",
        "why": "Data sharing practices \u2014 correlate with willingness to share DD",
        "when": [
          "Yes, regularly and systematically (shared platforms or data exchanges)",
          "Yes, but ad hoc (via email, reports, manual processes)",
          "We would like to but data protection concerns prevent it"
        ]
      },
      {
        "q": "NGO-P0-S1-Q4",
        "w": 0.5,
        "role": "scale",
        "why": "INGO / Network / consortium scale DD burden",
        "when": [
          "INGO (International NGO with HQ outside Africa)",
          "Regional INGO (headquartered in Africa, operating across multiple countries)",
          "Network or consortium"
        ]
      }
    ],
    "fitGate": 2.75,
    "readinessGate": 2.5
  },
  "UC-C-053": {
    "name": "Livestock traceability for pastoralists",
    "blockchainFit": 4.2,
    "rationale": "Strong B2/B3/B5 case where pastoralist provenance and cross-border movement are operationally critical. Honest-no triggers if connectivity / power floor is too low or if the protection threat model in active-conflict contexts is not addressed.",
    "tadamonCohort": true,
    "signals": [
      {
        "q": "NGO-P0-S1-Q9",
        "w": 1.0,
        "role": "need",
        "why": "Pastoralist beneficiary group is the primary fit signal",
        "when": [
          "Pastoralists and nomadic populations"
        ]
      },
      {
        "q": "NGO-P0-S5-Q25",
        "w": 0.9,
        "role": "fit_boost",
        "why": "Tadamon cohort flag promotes the food-security UC catalogue",
        "when": [
          "Tadamon (UNDP-IsDB Food Security Accelerator)"
        ]
      },
      {
        "q": "NGO-P0-S1-Q3",
        "w": 0.6,
        "role": "fit_boost",
        "why": "FCV context shapes data-risk design choices",
        "when": [
          "Post-conflict or transitional context",
          "Active conflict or complex emergency",
          "Mixed (you operate across several of the above at once)"
        ]
      },
      {
        "q": "NGO-P0-S5-Q17a",
        "w": 0.7,
        "role": "readiness",
        "why": "Delivers directly, with no implementing partner to act as the cooperative anchor",
        "when": [
          "Rarely",
          "No, we deliver directly"
        ]
      },
      {
        "q": "NGO-P0-S3-Q13",
        "w": 0.5,
        "role": "readiness",
        "why": "Field connectivity affects offline-first feasibility"
      },
      {
        "q": "NGO-P0-S3-Q13b",
        "w": 0.5,
        "role": "readiness",
        "why": "Power constraints affect device charging at field sites"
      }
    ],
    "fitGate": 2.75,
    "readinessGate": 2.5
  },
  "UC-D-075": {
    "name": "Food voucher tokenisation",
    "blockchainFit": 4.4,
    "rationale": "Strong B1/B3/B4 case. Mature pattern. High value when multiple implementing partners share geography and donor wants transaction-level audit. De-risked by cluster participation and verifiable credential availability.",
    "tadamonCohort": true,
    "signals": [
      {
        "q": "NGO-P1-S1-Q2",
        "w": 1.0,
        "role": "need",
        "why": "Voucher / food assistance pain identification",
        "when": [
          "Verifying food assistance reached intended households (vouchers, cash, in-kind food)"
        ]
      },
      {
        "q": "NGO-P0-S4-Q24",
        "w": 0.9,
        "role": "fit_boost",
        "why": "Cluster participation + Islamic finance funding lift case",
        "when": [
          "Participate in humanitarian cluster system (OCHA-coordinated)",
          "Participate in Food Security Cluster specifically",
          "Islamic finance instruments (zakat, qard hasan, waqf, sukuk)"
        ]
      },
      {
        "q": "NGO-P0-S5-Q25",
        "w": 0.8,
        "role": "fit_boost",
        "why": "Tadamon cohort flag promotes the food-security UC catalogue",
        "when": [
          "Tadamon (UNDP-IsDB Food Security Accelerator)"
        ]
      },
      {
        "q": "NGO-P0-S5-Q25b",
        "w": 0.7,
        "role": "readiness",
        "why": "Verifiable credential availability simplifies beneficiary identifier",
        "when": [
          "No",
          "Not sure"
        ]
      },
      {
        "q": "NGO-P0-S3-Q13",
        "w": 0.6,
        "role": "readiness",
        "why": "Beneficiary-side connectivity / SMS reach"
      },
      {
        "q": "NGO-P0-S5-Q17b",
        "w": 0.5,
        "role": "scale",
        "why": "Partner count affects deduplication value"
      }
    ],
    "fitGate": 2.75,
    "readinessGate": 2.5,
    "interagency": true
  },
  "UC-C-054": {
    "name": "Seed system integrity",
    "blockchainFit": 3.8,
    "rationale": "B2/B3 case for smallholder agricultural input verification. Counterfeit / adulteration must be a material problem. Requires certification authority engagement and farmer-side verification reach. Honest-no if traditional seed-saving dominates and certified seed is marginal.",
    "tadamonCohort": true,
    "signals": [
      {
        "q": "NGO-P1-S1-Q2",
        "w": 0.9,
        "role": "need",
        "why": "Counterfeit input pain identification",
        "when": [
          "Counterfeit, adulterated, or unverifiable agricultural inputs (especially seed)"
        ]
      },
      {
        "q": "NGO-P0-S1-Q9",
        "w": 0.8,
        "role": "need",
        "why": "Smallholder farmer beneficiary fit",
        "when": [
          "Smallholder farmers"
        ]
      },
      {
        "q": "NGO-P0-S5-Q25",
        "w": 0.7,
        "role": "fit_boost",
        "why": "Tadamon cohort flag promotes the food-security UC catalogue",
        "when": [
          "Tadamon (UNDP-IsDB Food Security Accelerator)"
        ]
      },
      {
        "q": "NGO-P0-S5-Q18",
        "w": 0.6,
        "role": "readiness",
        "why": "Part of no coordination mechanism, so the certification authority relationship starts from nothing",
        "when": [
          "None \u2014 we operate independently"
        ]
      },
      {
        "q": "NGO-P0-S3-Q13",
        "w": 0.5,
        "role": "readiness",
        "why": "Farmer-side verification UX depends on connectivity"
      }
    ],
    "fitGate": 2.5,
    "readinessGate": 2.5
  },
  "UC-B-040": {
    "name": "Farmer cooperative registry and member digital ID",
    "blockchainFit": 4.0,
    "rationale": "B1/B2/B5 case for cooperative-mediated identity. Strong multiplier when women-led cooperatives or Islamic finance lending is bundled. Issuer legitimacy is the critical path. Risks if national cooperative authority is politically captured.",
    "tadamonCohort": true,
    "signals": [
      {
        "q": "NGO-P0-S1-Q9",
        "w": 1.0,
        "role": "need",
        "why": "Cooperative-based beneficiary structure (smallholder / women-led)",
        "when": [
          "Smallholder farmers",
          "Women-led households and women's cooperatives"
        ]
      },
      {
        "q": "NGO-P0-S5-Q17a",
        "w": 0.9,
        "role": "need",
        "why": "Cooperative partnership model",
        "when": [
          "Yes, extensively (most programmes delivered through partners)",
          "Yes, for some programmes"
        ]
      },
      {
        "q": "NGO-P0-S5-Q25",
        "w": 0.8,
        "role": "fit_boost",
        "why": "Tadamon cohort flag promotes the food-security UC catalogue",
        "when": [
          "Tadamon (UNDP-IsDB Food Security Accelerator)"
        ]
      },
      {
        "q": "NGO-P0-S4-Q24",
        "w": 0.7,
        "role": "fit_boost",
        "why": "Islamic finance funding amplifies value (qard hasan, takaful)",
        "when": [
          "Islamic finance instruments (zakat, qard hasan, waqf, sukuk)"
        ]
      },
      {
        "q": "NGO-P0-S6-Q21",
        "w": 0.6,
        "role": "readiness",
        "why": "No financial regulation beyond basic accounting, so the cooperative regulator relationship is untested",
        "when": [
          "None beyond basic financial accounting"
        ]
      }
    ],
    "fitGate": 2.75,
    "readinessGate": 2.5
  },
  "UC-A-026": {
    "name": "Zakat and qard hasan distribution transparency",
    "blockchainFit": 4.3,
    "rationale": "Anchor Islamic finance UC. B1/B3/B6 case. Donor accountability vs recipient privacy tension is central. Programme-killing veto if shariah board not engaged. Annual flow threshold matters for overhead justification.",
    "tadamonCohort": true,
    "signals": [
      {
        "q": "NGO-P0-S4-Q24",
        "w": 1.0,
        "role": "need",
        "why": "Islamic finance instruments in funding ecosystem",
        "when": [
          "Islamic finance instruments (zakat, qard hasan, waqf, sukuk)"
        ]
      },
      {
        "q": "NGO-P0-S5-Q25",
        "w": 0.9,
        "role": "fit_boost",
        "why": "Tadamon cohort flag promotes the food-security UC catalogue",
        "when": [
          "Tadamon (UNDP-IsDB Food Security Accelerator)"
        ]
      },
      {
        "q": "TADAMON-P1-Q1",
        "w": 0.9,
        "role": "need",
        "why": "Verified Islamic finance exposure depth",
        "when": []
      },
      {
        "q": "NGO-P0-S4-Q14a",
        "w": 0.6,
        "role": "scale",
        "why": "Annual flow scale justifies overhead"
      },
      {
        "q": "NGO-P0-S5-Q18",
        "w": 0.6,
        "role": "readiness",
        "why": "Part of no coordination mechanism, so the Shariah authority relationship starts from nothing",
        "when": [
          "None \u2014 we operate independently"
        ]
      }
    ],
    "fitGate": 3.0,
    "readinessGate": 2.5
  },
  "UC-E-085": {
    "name": "Anticipatory action trigger proof",
    "blockchainFit": 4.0,
    "rationale": "B2/B4/B7 case. High value when donors (CERF-AA, Start Network, FbF) are pushing anticipatory action and partner coordination is strong enough to agree triggers. Pre-positioned fund existence is precondition.",
    "tadamonCohort": true,
    "signals": [
      {
        "q": "NGO-P1-S1-Q2",
        "w": 0.9,
        "role": "need",
        "why": "Anticipatory action trigger pain identification",
        "when": [
          "Anticipatory action trigger evidence (drought, flood, displacement) for early disbursement"
        ]
      },
      {
        "q": "NGO-P0-S4-Q24",
        "w": 0.8,
        "role": "fit_boost",
        "why": "Cluster + UN funding ecosystem alignment",
        "when": [
          "Participate in humanitarian cluster system (OCHA-coordinated)",
          "Participate in Food Security Cluster specifically",
          "Primarily UN system funding (UNHCR, WFP, UNICEF, UNDP, OCHA)"
        ]
      },
      {
        "q": "NGO-P0-S5-Q25",
        "w": 0.7,
        "role": "fit_boost",
        "why": "Tadamon cohort flag promotes the food-security UC catalogue",
        "when": [
          "Tadamon (UNDP-IsDB Food Security Accelerator)"
        ]
      },
      {
        "q": "NGO-P0-S1-Q3",
        "w": 0.7,
        "role": "fit_boost",
        "why": "FCV context strongly correlates with anticipatory-action relevance",
        "when": [
          "Post-conflict or transitional context",
          "Active conflict or complex emergency",
          "Mixed (you operate across several of the above at once)"
        ]
      },
      {
        "q": "NGO-P0-S5-Q17a",
        "w": 0.5,
        "role": "readiness",
        "why": "Partner coordination strength enables trigger consensus",
        "when": [
          "Rarely",
          "No, we deliver directly"
        ]
      }
    ],
    "fitGate": 2.75,
    "readinessGate": 2.5,
    "interagency": true
  }
}