Same material.
Five conversations.
Each briefing is the same underlying analysis, translated for one audience's vocabulary, concerns, and decision authority.
Most PQC content is written for one audience and read by the wrong one. The five briefings below are designed for general staff, executives, IT technicians, privacy and legal professionals, and security architects. Each is 600–1,000 words and self-contained. Cross-references are noted where one briefing supports another's conversation.
For everyone who needs to understand what this is. Plain-language explanation of the threat and the response. No standards detail required.
For CIOs, CISOs, board members. Business-impact framing, the compliance landscape, and the strategic posture. Disciplined urgency, not reactive spending.
For network admins and systems engineers. Inventory, vendor questioning, hybrid deployment. Operator-grade, with the MTU, PKI, and IDS pitfalls flagged.
For DPOs, compliance, and legal. The HNDL legal-time dimension, retention obligations, and the structural temporal asymmetry that current breach-notification law does not yet resolve.
For cryptography leads and security architects. The FIPS 203/204/205 baseline, hybrid construction discipline, and the four structural problems that require explicit design attention in any PQC migration.
Each briefing is written to be read on its own. If you are routing the same material to multiple audiences inside one organization, choose the briefing that matches the room — not the most senior person in it. The privacy & legal briefing is the one most often read by the wrong audience; if your conversation is about retention obligations and breach posture, that is the one. The security architects briefing assumes familiarity with TLS 1.3 internals and is denser than the others by design.