Trust that survives cryptographic change
The wrong question
Buyers sometimes ask whether a vendor is “quantum-proof.” That framing invites theater: it sounds definitive, but protocols and devices do not flip to post-quantum overnight, and no serious team should promise universal instant immunity.
The better question is whether your trust layer can survive cryptographic change without breaking identity continuity, shredding provenance, or trapping you in a single-algorithm corner.
What HUMΛN does instead
We are crypto-agile by design:
- Classical-secure today — Production paths use modern, widely deployed algorithms appropriate to current threats and devices.
- Explicit metadata — Signed objects carry enough information (suite / algorithm, key references, versions) to verify under documented policies across mixed eras.
- Profile-based policy — Consumer, enterprise, self-hosted regulated, and government-grade deployments do not share identical cryptographic requirements on day one. Stricter modes are opt-in; we do not silently tighten verifier behavior on upgrade.
- Hybrid and PQ-native are selective — Where trust must last many years (key wrapping, some service-to-service channels, high-assurance artifacts), we make room for hybrid and post-quantum transitions without forcing every passkey flow into experimental crypto.
What we will not say
We avoid “quantum-proof,” “unbreakable,” and “future-proof forever.” Those claims age badly and mis-set expectations. We talk about migration readiness, trust continuity, and algorithm agility — the infrastructure properties serious enterprises actually need.
Where to read the normative spec
Internal and partner-facing Canon: kb/172 (strategy), kb/173 (suite registry and migration verbs), kb/174 (deployment profiles). Developer guides live under docs/post-quantum-*.md in the HUMΛN repository.
Bottom line
The trust layer between humans and AI has to last longer than any one elliptic curve. HUMΛN is building for that boring, hard requirement — without pretending the transition is already done everywhere.
Code & Docs