Direct answer
That a federal standard now specifies a key-encapsulation mechanism, ML-KEM, in three parameter sets, believed secure against an adversary possessing a quantum computer.
Answer contract
Apply the definition lens only to the exact inspected source scope; do not infer authority from adjacent topics.
Evidence and exact locators
Inspected source 1 — §1 Introduction — ML-KEM and its three parameter sets (ML-KEM-512, -768, -1024).. Supports: The bounded scope recorded in the reviewed specification.
What the evidence does not establish
A specification is not a route, a release, or a public page.
Rights and reuse
Rights basis recorded in the reviewed specification; link and bounded original paraphrase only.
Dependencies and related concepts
applies-to: urn:maha:concept:governance:quantum-policy
implemented-by: urn:maha:property:maha-strategies
evidence-for: urn:maha:concept:governance
Questions this page can answer
What does FIPS 203, Module-Lattice-Based Key-Encapsulation Mechanism Standard state about quantum-policy?
That a federal standard now specifies a key-encapsulation mechanism, ML-KEM, in three parameter sets, believed secure against an adversary possessing a quantum computer.
Which exact locator in that source supports the claim on this page?
Inspected source 1, §1 Introduction — ML-KEM and its three parameter sets (ML-KEM-512, -768, -1024).
What does this source explicitly not establish about quantum-policy?
A specification is not a route, a release, or a public page.
Which canonical definition does this route depend on, and where is it owned?
applies-to: urn:maha:concept:governance:quantum-policy implemented-by: urn:maha:property:maha-strategies evidence-for: urn:maha:concept:governance
What would have to be inspected before this page could claim more than it does?
A source, locator, rights, scope, boundary, dependency, implementation, or release change requires a new exact-revision review.