The Math That Quantum Cannot Break

I started the audit at 02:17 on a Tuesday. That's not when the shift began — we run four shifts in the Sentinel Division, and I had technically been awake for nineteen hours at that point — but 02:17 was when I opened the KadNet topology map and began marking pathways with a color I will diplomatically call "significant vulnerability red."

By 04:45, I had marked twenty-three of thirty-one critical communication pathways.

Let me threat-model this for you. Step one: assume I am wrong about what the adversary wants.

The adversary, in this case, is mathematics. Specifically, it is a sufficiently powerful quantum computer running Shor's algorithm — a 1994 theoretical construct that remains theoretical for now, but which NIST's Post-Quantum Cryptography project has spent nine years treating as an engineering problem rather than a hypothetical one. The math works. The only question is whether anyone on Earth will build the hardware before the cryptography is ready.

We do not get to know the answer to that question for thirty-eight years.

The communication pathways I marked are protected by RSA and ECC — algorithms whose security rests on the assumption that factoring large numbers is hard. It is hard, classically. A quantum computer of sufficient size would not find it hard. It would find it trivially easy, the way a machine finds any arithmetic easy, and then every pathway I had marked would be transparent to anyone watching.

Here on Kadmiel, "anyone watching" is a more contained threat model than it would be on Earth. We are not fighting nation-states. We are not fighting organized criminal enterprises. We are fighting internal failure modes, configuration drift, and the possibility — which I take seriously even when my colleagues find it melodramatic — that something in our environment develops the capacity to observe us in ways we have not anticipated. (I have been told this is paranoid. I have been told this by people who have not spent nine years responsible for keeping forty-three thousand people alive through cryptographic hygiene. We have reached a mutual understanding.)

The unmarked eight pathways were already quantum-resistant. The Sentinel Division had been migrating high-priority infrastructure quietly over the past three years — no Chronicle posts, no Spoke Council announcements, because security migrations are not the kind of thing you advertise in advance.

This one is different. I'm writing this because something changed on Earth.

On March 11, 2025 — which means we received the tightbeam dispatch approximately three weeks ago — NIST selected HQC as the fifth post-quantum cryptographic algorithm. I want to explain why this matters, and why I spent most of the morning after the dispatch sitting very still in the bunker with leftover jollof rice I had cooked at 21:00 the previous evening because I could not sleep.

HQC stands for Hamming Quasi-Cyclic. The name is not the important part. What is important is that it is built on error-correcting codes — a different mathematical foundation from ML-KEM, the lattice-based standard that NIST finalized in 2024 and which we deployed across our eight hardened pathways. Dustin Moody, who leads the NIST post-quantum project, described HQC as a backup: if lattice mathematics turns out to have a weakness no one has yet discovered, error-correcting codes provide a separate line of defense built on different assumptions. Two locks. Different keys. The adversary has to break both.

I sat with my jollof rice and thought: this is exactly the kind of redundancy I would have designed if NIST had asked me.

They did not ask me. This is, objectively, fine. They arrived at the same conclusion through nine years of independent analysis, international cryptographic competition, and peer review by some of the best minds working on this problem. The result is a fifth algorithm that exists because the people building our planetary communication security treated the question the way I treat everything: as though the failure mode they hadn't thought of was the one that would eventually matter.

Here is the complication.

Migrating twenty-three critical pathways is not a technical problem. We have the algorithms. We have the implementation libraries. We have an engineering team that completed this migration for eight pathways and knows the procedure.

The problem is the migration window.

To migrate a pathway, you take it partially offline. Not fully — we have failover systems, we have redundancy, we are not animals — but there is a period during key exchange renegotiation when the pathway is operating on legacy cryptography, its replacement not yet established. That window is, on our fastest handshake protocols, approximately forty seconds.

Forty seconds of legacy exposure on a pathway protecting life support telemetry.

I ran the Spoke Council tabletop exercise for this scenario last month. I did not tell them we were already planning the migration; I told them we were rehearsing a routine cryptographic upgrade scenario. By the third iteration, Councilor Hamid had stopped raising his hand and started taking notes. Dr. Moreau asked if this was what my quarterly nightmares were about. (They are not. My nightmares are more creative than this. But I appreciated the question.)

The solution is sequencing. You migrate pathways in the order that minimizes simultaneous risk, you ensure fallback protocols are armed before each transition, and you time the forty-second windows to occur during low-activity periods. We have identified the order. We have mapped the windows. We begin next week.

Seo-jin's quantum glass receivers — the ones she wrote about in her last Chronicle post — give us something useful here. The QKD layer she is proposing for the tightbeam provides an additional authentication mechanism that is information-theoretically secure, not computationally secure: its protection does not rest on the hardness of any mathematical problem but on the laws of physics. When that system is operational, it creates a layer beneath the HQC migration. Belt and suspenders. I do not usually quote Seo-jin approvingly in print, so she should take note of this paragraph. I am told we are having lunch on Wednesday and I expect she will mention it.

The twenty-three pathways will take approximately six months to migrate fully. During that time, the Sentinel Division will be running enhanced monitoring on every transition, logging everything, and maintaining four-hour incident response readiness around the clock.

I cannot promise you zero risk. I can promise you I'm watching.

To the Earth cryptographers whose work arrived in our tightbeam archive: thank you. You spent years on a problem you knew would take decades to matter, building the solution before the attack existed. That is the kind of thinking that keeps people alive across distances too large to call for help.

Thirty-eight years late, but the math arrived exactly when we needed it.

— Nadia Chinyere Okonkwo Chief Security Officer, Sentinel Division Kadmiel Colony, Year 9, Day 15

Earth Status: NIST selected HQC (Hamming Quasi-Cyclic) on March 11, 2025 as the fifth post-quantum cryptographic standard — a code-based backup to the lattice-based ML-KEM algorithm (FIPS 203), which protects internet traffic and stored data. HQC was developed with contributions from SandboxAQ and is expected to reach draft standard status in 2026, with final standardization in 2027. Dustin Moody, NIST's Post-Quantum Cryptography project lead, described HQC as providing "mathematical diversity" in the event that lattice-based approaches prove vulnerable. Source: NIST