Editorial Policy

Last updated: August 2026

How content is created

Post Quantum Field uses AI-assisted research combined with human editorial oversight. Our process:

1. Research – We gather information from primary sources: NIST FIPS publications, IETF draft specifications, vendor changelogs, security advisories, and official cryptographic library documentation.
2. Drafting – AI tools assist with structuring and drafting content based on verified sources.
3. Editorial review – A human editor reviews every article for technical accuracy, clarity, and completeness before publication.
4. Ongoing updates – Articles are revisited when standards evolve, vendors ship updates, or migration guidance changes.

Source hierarchy

Primary sources always take precedence. Our source priority order:

1. NIST publications – FIPS standards, SP 800-series documents, and official PQC competition results.
2. IETF drafts and RFCs – Protocol specifications, TLS extensions, and key exchange proposals.
3. Vendor changelogs and release notes – Official documentation of what shipped and when.
4. Academic papers – Peer-reviewed cryptanalysis, performance benchmarks, and security proofs.
5. Industry reporting – Used only when primary sources are unavailable, and always labeled as such.

Fact-checking methodology

Security claims are verified against official documentation. We do not rely on press releases, marketing materials, or vendor blog posts as primary evidence of cryptographic capability.

Specific verification practices:

• Algorithm support claims are verified against release notes, changelogs, or API documentation.
• Performance numbers are cross-referenced with published benchmarks or reproduced where possible.
• Compliance claims (e.g., "FIPS 203 compliant") are verified against the actual standard text.
• All vendor support claims carry a last-verified date indicating when we last confirmed the information against primary sources.

Maturity labels

We maintain a strict distinction between stages of vendor support:

• Announced – The vendor has publicly stated intent to support PQC algorithms, but no code has shipped. Not actionable for migration planning.
• Shipped in beta / preview – Code is available in a pre-release channel, behind feature flags, or explicitly labeled experimental. Clearly marked as not production-ready. Never presented as suitable for production workloads.
• Production GA – The feature is generally available, documented, supported under the vendor's standard SLA, and recommended for production use.

Experimental support is clearly labeled and never presented as production-ready. We do not conflate "announced" with "available."

Last-verified dates

All vendor support claims include a last-verified date. This tells readers when we last confirmed the information against official sources. If a claim has not been re-verified in more than 90 days, we flag it for review and note the staleness.

Corrections policy

If you find an error in our content:

1. Email hello@postquantumfield.com with the article URL and the correction needed.
2. We review and verify the correction against primary sources.
3. Confirmed corrections are published within 48 hours.
4. The article is updated with a visible correction notice and a new "Updated" date in the header.
5. Significant corrections (factual errors affecting recommendations) are noted prominently at the top of the article.

Independence

Editorial decisions are not influenced by affiliate relationships or advertising. Product and vendor assessments are based on technical merit, standards compliance, and security posture. See our Affiliate Disclosure for full details.