Purpose: thin index so teams land on the right problems fast. Each domain page lists what belongs, primary use cases, shortest-path patterns, and adjacent vendors. Keep these pages short; link back to /use-cases, /patterns, /vendors.
The map covers privacy infrastructure for institutions and users at the boundary: financial institutions, governments, central banks, NGOs, civil society, and resilience or adversarial deployments. Domains describe reusable privacy problem areas across those settings. The same privacy primitives apply whether the actor is a custodian routing settlement, a public agency disbursing benefits, an NGO operating in a hostile jurisdiction, or a community running a credentialed petition.
Domains:
- Payments
- Trading
- Funds & Assets
- Custody
- Identity & Compliance
- Data & Oracles
- Civic Coordination & Governance
- Post-Quantum Threats
Conventions:
- Each use case declares exactly one primary
domain:in its front-matter. - Patterns/vendors do not get new fields; just link them from domains.
- Prefer one-liners; avoid duplicating content from the use case/pattern cards.