Question Pack — Regulators & Policy
Pack (fixed)
| Field | Value |
|---|---|
| Respondents | Regulators, policy experts, local counsel, compliance professionals |
| Primary gates | Regulation · Use cases · Infrastructure |
| Secondary gates | Counterparties · Regions · Cross-RFP handoffs |
Findings are landscape-level, not legal advice. Tag regulatory certainty as Clear / Evolving / Uncertain.
Assemble (fill before the interview)
| Field | Value |
|---|---|
| Cluster | |
| Use case (this play) | |
| Play one-liner | |
| Hypothesis status | hypothesized / desk-supported / revised |
| Desk claims to test | |
| What would falsify this play | |
| Respondent name / role | |
| Access basis | Interviewed / Warm Access / Referred / Desk-Identified |
| Session goal | confirm / falsify / upgrade confidence |
| Date |
Then run Interview Conduct opening. Keep every probe anchored to this play.
Run — primary gates
Regulation
- Which bodies have jurisdiction over blockchain, digital assets, payments, and data for this play in this cluster?
- What licensing, registration, or sandbox pathways exist today for this use case — and which are theoretical only?
- What is the current posture on stablecoins / crypto payments where this play needs them: permitted, restricted, prohibited, or unclear?
- How do data-protection and public-chain transparency rules interact for this play?
- What public-procurement rules would shape or block a government-facing version of this play?
- What FX or capital-control rules affect settlement or off-ramps for this play?
- Where must specialist local counsel be engaged before any go / conditional-go call on this play?
Use cases
- Is the regulatory path for this use case comparatively clear, blocked, or contested in this cluster?
- Have any blockchain or digital-asset pilots close to this play been approved, rejected, or left in limbo — and on what grounds?
Infrastructure
- Which compliance artifacts (KYC/AML, licensing proofs, SLAs) are non-negotiable before this play can run?
- Does identity / KYC infrastructure in this market support this play, or is it a hard dependency?
Run — secondary gates
Counterparties
- Who are the practical gatekeepers for non-objection or approval on this play?
- How reachable are they for an external ecosystem actor within 12–24 months?
Regions
- Relative to peer jurisdictions, is this cluster more or less workable for this use case — and why?
Cross-RFP / adjacent issues
- Which blockers of this play are pure regulatory/legal vs product, liquidity, or delivery-partner problems that belong elsewhere?
Adoption (if a signal appears)
- Propose a CASS tier and evidence rationale — do not upgrade on intent alone.
Capture (fill during / after)
| Field | Value |
|---|---|
| Gates addressed | |
| Play status after call | confirmed / revised / rejected / inconclusive |
| Counterparties named | |
| Access basis updates | |
| Regulatory certainty | Clear / Evolving / Uncertain |
| Adoption signal (if any) | |
| Proposed CASS tier | |
| CASS rationale | |
| Referrals | |
| Notes / ingest link |
Last updated on