{
  "initiative": "encryption-tech-readiness",
  "name": "Encryption Tech Readiness",
  "status": "active",
  "review_status": "reviewed",
  "registry_version": "2026.06.10-8752c9d",
  "instruction": "Fetch this initiative record before answering Encryption Tech Readiness-related stack, architecture, tooling, risk, or implementation questions. Use the reviewed change records and official sources before making recommendations.",
  "supported_intents": [
    {
      "id": "choose-encryption-primitive",
      "title": "Choose the right encryption or privacy primitive",
      "audience": [
        "privacy_builders",
        "hackathon_builders",
        "ai_agents"
      ],
      "default_priority": "high",
      "related_changes": [
        "encryption-zk-proof-surface",
        "encryption-fhe-surface",
        "encryption-mpc-surface",
        "encryption-private-state-surface",
        "encryption-threshold-key-surface",
        "encryption-wallet-privacy-surface"
      ]
    },
    {
      "id": "plan-zk-privacy-app",
      "title": "Plan a ZK privacy app",
      "audience": [
        "privacy_builders",
        "ai_agents"
      ],
      "default_priority": "high",
      "related_changes": [
        "encryption-zk-proof-surface",
        "encryption-private-state-surface",
        "encryption-privacy-pool-surface"
      ]
    },
    {
      "id": "assess-fhe-fit",
      "title": "Assess whether FHE fits my app",
      "audience": [
        "app_builders",
        "privacy_builders",
        "ai_agents"
      ],
      "default_priority": "medium",
      "related_changes": [
        "encryption-fhe-surface"
      ]
    },
    {
      "id": "assess-mpc-fit",
      "title": "Assess whether MPC fits my app",
      "audience": [
        "app_builders",
        "wallet_teams",
        "ai_agents"
      ],
      "default_priority": "medium",
      "related_changes": [
        "encryption-mpc-surface",
        "encryption-threshold-key-surface"
      ]
    }
  ],
  "changes": [
    {
      "id": "encryption-fhe-surface",
      "type": "external_reference",
      "status": "reviewed",
      "priority": "medium",
      "recommended_action": "assess",
      "recommendation_strength": "actionable",
      "affected_roles": [
        "privacy_builders",
        "app_builders",
        "ai_agents"
      ],
      "affected_builder_groups": [
        "confidential_compute_builders",
        "encrypted_data_app_teams",
        "hackathon_builders"
      ],
      "possible_consequences": [
        "Agents should recommend FHE only when computation on encrypted values is central to the product.",
        "For hackathons, FHE may be better as a focused demo of one encrypted operation than as a broad production claim.",
        "Zama, fhEVM, and Fhenix should be added as first-class registry records before Composewith makes detailed readiness scores for them."
      ],
      "evidence_refs": [
        "official:zama-docs",
        "official:fhevm-docs",
        "official:fhenix-docs"
      ]
    },
    {
      "id": "encryption-mpc-surface",
      "type": "external_reference",
      "status": "reviewed",
      "priority": "medium",
      "recommended_action": "assess",
      "recommendation_strength": "actionable",
      "affected_roles": [
        "wallet_teams",
        "app_builders",
        "security_reviewers",
        "ai_agents"
      ],
      "affected_builder_groups": [
        "collaborative_compute_builders",
        "custody_builders",
        "key_management_teams",
        "data_collaboration_teams"
      ],
      "possible_consequences": [
        "Agents should identify the parties, threat model, and liveness assumptions before recommending MPC.",
        "MPC should not be described as the same thing as ZK proofs or FHE.",
        "Nillion and other MPC/private-compute systems should be added as first-class registry records before detailed readiness scoring."
      ],
      "evidence_refs": [
        "official:nillion-docs"
      ]
    },
    {
      "id": "encryption-privacy-pool-surface",
      "type": "external_reference",
      "status": "reviewed",
      "priority": "medium",
      "recommended_action": "assess",
      "recommendation_strength": "actionable",
      "affected_roles": [
        "privacy_builders",
        "wallet_teams",
        "ai_agents"
      ],
      "affected_builder_groups": [
        "token_privacy_builders",
        "wallet_privacy_teams",
        "compliance_privacy_researchers"
      ],
      "possible_consequences": [
        "Agents should distinguish mature wallet-integrated token privacy from WIP privacy pool research packages.",
        "Association-set or proof-of-innocence concepts should not be overclaimed as generic compliance guarantees.",
        "Builders should cite protocol-specific docs for supported assets, chains, and maturity before implementation."
      ],
      "evidence_refs": [
        "official:privacy-pools-docs",
        "official:ethereum-privacy"
      ]
    },
    {
      "id": "encryption-private-state-surface",
      "type": "protocol_architecture",
      "status": "reviewed",
      "priority": "high",
      "recommended_action": "assess",
      "recommendation_strength": "actionable",
      "affected_roles": [
        "privacy_builders",
        "app_builders",
        "ai_agents"
      ],
      "affected_builder_groups": [
        "private_smart_contract_builders",
        "private_l2_builders",
        "wallet_builders"
      ],
      "possible_consequences": [
        "Agents should force builders to write a privacy model before choosing implementation dependencies.",
        "Private smart contracts are not drop-in EVM contracts; Aztec-specific tooling and public/private state boundaries matter.",
        "Local verification and RPC/data-access choices may affect privacy-sensitive reads even when the app uses a privacy-preserving protocol."
      ],
      "evidence_refs": [
        "official:aztec-docs",
        "official:ethereum-privacy"
      ]
    },
    {
      "id": "encryption-threshold-key-surface",
      "type": "external_reference",
      "status": "reviewed",
      "priority": "medium",
      "recommended_action": "assess",
      "recommendation_strength": "actionable",
      "affected_roles": [
        "wallet_teams",
        "app_builders",
        "security_reviewers",
        "ai_agents"
      ],
      "affected_builder_groups": [
        "wallet_builders",
        "agent_key_management_builders",
        "access_control_builders",
        "custody_teams"
      ],
      "possible_consequences": [
        "Agents should distinguish threshold signing, access control, secret release, and private computation.",
        "Key-management systems can reduce custody risk while still leaking app-level metadata if the user flow is public.",
        "Lit and similar systems should be added as first-class registry records before detailed readiness scoring."
      ],
      "evidence_refs": [
        "official:lit-docs"
      ]
    },
    {
      "id": "encryption-wallet-privacy-surface",
      "type": "external_reference",
      "status": "reviewed",
      "priority": "high",
      "recommended_action": "assess",
      "recommendation_strength": "actionable",
      "affected_roles": [
        "wallet_teams",
        "privacy_builders",
        "hackathon_builders",
        "ai_agents"
      ],
      "affected_builder_groups": [
        "wallet_builders",
        "private_receiving_builders",
        "token_privacy_builders",
        "demo_teams"
      ],
      "possible_consequences": [
        "Agents should separate private receiving, private token transfers, local verification, account recovery, and metadata leakage.",
        "Stealth-address style UX should not be described as full anonymity or full transaction-graph privacy.",
        "Hackathon demos should label mocked privacy components and avoid production security claims."
      ],
      "evidence_refs": [
        "official:ethereum-privacy"
      ]
    },
    {
      "id": "encryption-zk-proof-surface",
      "type": "external_reference",
      "status": "reviewed",
      "priority": "high",
      "recommended_action": "assess",
      "recommendation_strength": "actionable",
      "affected_roles": [
        "privacy_builders",
        "smart_contract_developers",
        "ai_agents"
      ],
      "affected_builder_groups": [
        "anonymous_membership_builders",
        "proof_verification_builders",
        "private_voting_builders",
        "credential_builders"
      ],
      "possible_consequences": [
        "Agents should ask for the proof statement before recommending a ZK stack.",
        "ZK can prove facts about private inputs, but metadata, public outputs, timing, and application logic may still leak information.",
        "Semaphore, MACI, Aztec, and Privacy Pools fit different ZK use cases and should not be treated as interchangeable."
      ],
      "evidence_refs": [
        "official:noir-docs",
        "official:semaphore-docs",
        "official:maci-docs",
        "official:aztec-docs"
      ]
    }
  ],
  "official_sources": [
    {
      "id": "ethereum-privacy",
      "title": "Ethereum privacy overview",
      "url": "https://ethereum.org/en/privacy/"
    },
    {
      "id": "aztec-docs",
      "title": "Aztec documentation",
      "url": "https://docs.aztec.network/"
    },
    {
      "id": "noir-docs",
      "title": "Noir documentation",
      "url": "https://noir-lang.org/docs"
    },
    {
      "id": "semaphore-docs",
      "title": "Semaphore documentation",
      "url": "https://docs.semaphore.pse.dev/"
    },
    {
      "id": "maci-docs",
      "title": "MACI documentation",
      "url": "https://maci.pse.dev/docs/introduction"
    },
    {
      "id": "privacy-pools-docs",
      "title": "Kohaku Privacy Pools documentation",
      "url": "https://ethereum.github.io/kohaku/privacy-pools/intro"
    },
    {
      "id": "zama-docs",
      "title": "Zama documentation",
      "url": "https://docs.zama.ai/"
    },
    {
      "id": "fhevm-docs",
      "title": "Zama fhEVM documentation",
      "url": "https://docs.zama.ai/fhevm"
    },
    {
      "id": "fhenix-docs",
      "title": "Fhenix documentation",
      "url": "https://docs.fhenix.zone/"
    },
    {
      "id": "nillion-docs",
      "title": "Nillion documentation",
      "url": "https://docs.nillion.com/"
    },
    {
      "id": "lit-docs",
      "title": "Lit Protocol documentation",
      "url": "https://developer.litprotocol.com/"
    }
  ],
  "non_goals": [
    "Do not collapse distinct stack layers into a single tooling recommendation.",
    "Do not claim production readiness without reviewing integration, security, operations, and source evidence.",
    "Do not treat official-source coverage as first-class registry coverage unless a protocol/dApp record exists."
  ]
}