privacy-architecturelisted

Selects and applies cryptographic primitives for privacy-by-design — systems where selective disclosure is structural, not procedural. Use when user says "build this with privacy built in", "how do I avoid collecting identity", "zero-knowledge proof for this", "anonymous credential", "can I prove X without revealing Y", "stealth address", "blind signature", "private transaction", "MPC", "homomorphic encryption", "differential privacy for analytics", "TEE", "can I verify without seeing the data", or when designing a new system, protocol, or product and wants privacy to be architectural rather than a policy layer added afterward. The Cypherpunk layer of the privacy suite — implements Eric Hughes' (1993) selective disclosure principle and Timothy May's (1988) anonymous transaction system program using contemporary cryptographic primitives. Distinct from all other privacy skills — those audit and repair; this one builds.
fevra-dev/Subrosa · ★ 0 · AI & Automation · score 72

Install: claude install-skill fevra-dev/Subrosa

# Privacy Architecture > *"Privacy in an open society requires anonymous transaction systems... An anonymous system empowers individuals to reveal their identity when desired and only when desired; this is the essence of privacy."* > — Eric Hughes, A Cypherpunk's Manifesto (1993) > *"The methods are based upon public-key encryption, zero-knowledge interactive proof systems, and various software protocols for interaction, authentication, and verification."* > — Timothy C. May, The Crypto Anarchist Manifesto (1988) Cryptographic primitive selection and implementation guidance for systems where privacy is structural. The goal is selective disclosure: users prove exactly what is necessary, reveal nothing more, and retain control. **Composable with:** - `threat-model-privacy` — run first to establish what must be protected and from whom; guides primitive selection - `data-minimization` — verify the minimized schema matches the architecture - `privacy-impact-assessment` — document architectural choices in a DPIA; ZK-based designs shrink the residual-risk register toward nil, but the assessment duty itself is procedural and remains (GDPR Art. 35 / Law 25 Art. 63.5 — see `taxonomy/regulatory-taxonomy--arch-rollup.md`, axis A12) - `regulatory-taxonomy` — the statutory payoff of every primitive here is mapped in `references/regulatory-dissolution.md` (primitive-first) and `taxonomy/regulatory-taxonomy--arch-rollup.md` (axis-first); cite records, not vibes --- ## Primitive Selecti