pqc-readinesslisted

# PQC Readiness ## Purpose Assess a system's readiness for post-quantum cryptography migration by inventorying classical crypto usage, mapping PQC replacements, evaluating implementation readiness, and planning migration timelines. ## Scope Constraints Reads source code, dependency manifests, and crypto library documentation for quantum readiness assessment. Does not modify files or execute code. Does not access production cryptographic infrastructure or key stores. ## Inputs - System architecture and crypto inventory - Current algorithm usage (key exchange, signatures, encryption) - Data sensitivity and protection timeline requirements - Performance constraints and resource budgets - Compliance and regulatory requirements ## Input Sanitization No user-provided values are used in commands or file paths. All inputs are treated as read-only analysis targets. ## Procedure ### Step 1: Inventory Classical Crypto Catalog all classical cryptographic algorithms in use: - **Key exchange**: RSA, ECDH, DH — key sizes, curves, usage contexts - **Digital signatures**: RSA, ECDSA, EdDSA — key sizes, curves, usage contexts - **Symmetric**: AES, ChaCha20 — key sizes (symmetric algorithms are quantum-resistant with doubled key size via Grover's, but inventory for completeness) - **Hashing**: SHA-2, SHA-3 — output sizes (hash outputs need doubling for quantum resistance) - Note: Focus on asymmetric algorithms as the primary migration targets ### Step 2: Map PQC Replacements For each c