Archive compliance CSVs 04182026–05062026; retain compliance_05072026.csv + compliance_05072026_r2.csv per CSV management policy (max 2 active versions).


Plans 09-12: trust path xwalk sourcing fix (library items as traversal sources), timeline_anchor rationale type added, 22 xwalk edges loaded. GeoFilter/SectorFilter wired into LibraryView + ComplianceView ForYouSection. normalize-vocab-tags CI script produces ISO 3166 + NAICS _r2 CSVs. 37 data integrity + unit tests added.


Plan 08: IR 8477 trust path filtering wired into compliance For You tab. traverseXwalkPaths engine, useApplicabilityWithPaths hook, TrustPathPopover component. Derived tier renders after advisory with confidence-propagated results and Why shown popover.


Plans 03-06: concept_xwalks_05072026.csv (22 edges, IR 8477 relationships), pqc-vocab-overlay.json (NAICS + ISO 3166 vocab), CBOM schema, confidence scale (high=85/medium=60/low=30), validator checks for provenance and schema compliance.

NIST CSWP 39
FIPS 203
FIPS 204
FIPS 205
NSA CNSA 2.0
AU-ASD-ISM-Crypto-2024
UK NCSC PQC Guidance
CA-TBS-SPIN-PQC-2025


Plans 01+02: module and workshop tool version gates with semver badges. ReviewedBadge, ConfidenceIndicator, ContentUpdatesFeed components. Learn module content version tracking wired into useModuleStore.


Plan 00 Foundation: revision log schema (revisions.jsonl), CODEOWNERS, PROV-DM provenance model. confidenceScale.ts (CONFIDENCE_SCALE high/medium/low). CI append-revision workflow stub. Baseline for Trust Engine Plans 01-12.


Baseline review — ai-security-pqc v1.0.0


Baseline review — api-security-jwt v1.0.0


Baseline review — arch-quantum-impact v1.0.0


Baseline review — compliance-strategy v1.0.0


Baseline review — confidential-computing v1.0.0


Baseline review — crypto-dev-apis v1.0.0


Baseline review — crypto-mgmt-modernization v1.1.0


Baseline review — data-asset-sensitivity v1.0.0


Baseline review — database-encryption-pqc v1.0.0


Baseline review — dev-quantum-impact v1.0.0


Baseline review — emv-payment-pqc v1.0.0


Baseline review — energy-utilities-pqc v1.0.0


Baseline review — entropy-randomness v1.0.0


Baseline review — exec-quantum-impact v1.0.0


Baseline review — legacy-app-p-q-c v1.0.0


Baseline review — merkle-tree-certs v1.0.0


Baseline review — migration-program v1.1.0


Baseline review — network-security-pqc v1.0.0


Baseline review — ops-quantum-impact v1.0.0


Baseline review — pqc-business-case v1.0.0


Baseline review — pqc-risk-management v1.0.0


Baseline review — p-q-c-testing-validation v1.0.0


Baseline review — platform-eng-pqc v1.0.0


Baseline review — quantum-threats v1.0.0


Baseline review — research-quantum-impact v1.0.0


Baseline review — secrets-management-pqc v1.0.0


Baseline review — secure-boot-pqc v1.0.0


Baseline review — standards-bodies v1.0.0


Baseline review — stateful-signatures v1.0.0


Baseline review — web-gateway-pqc v1.0.0


Data Self-Containment plan (DS01-DS22) execution complete. Phase 1 (foundations: schema/loader/validators), Phase 2 (writer patches: 8 scripts), Phase 3 tooling (backfill+merge+orphan-check), Phase 3 execution (DS14 backfill 6 families, DS22 library 80 records re-enriched, DS15 MD merge, DS21 corpus regen + sign with kid 11b723084d047b4c), Phase 4 partial (DS16 archive cleanup: 21 CSVs + 51 MDs archived; DS17 staged). Validators: CM-SC 638→232 (-64%), CM-SC-MD 632→54 (-91%), CM-STATUS PASS 9 families, CM-ORPHAN 5/323=1.5%. Trust path complete for restored records via regenerated rag-corpus.json (10704 chunks). 21 of 22 DS-tasks done + 1 n/a (DS11).


Compliance gap filled: faa-ac-119-1-ansp (gap=GAP-AERO-FAA-DO326A)


Compliance gap filled: etsi-tr-103949-qsc-migration (gap=GAP-AUTO-ETSI-ITS)


Compliance gap filled: eur-lex-42021x0387-pqc (gap=GAP-AUTO-UNECE-R155)


Compliance gap filled: common-criteria-v3.1r5-part1 (gap=GAP-CCRA-PORTAL)


Compliance gap filled: cisa-pqc-initiative (gap=GAP-CISA-PQC)


Compliance gap filled: oscca-cryptographic-regulations-cn (gap=GAP-CN-OSCCA)


Compliance gap filled: bsi-cc-certification (gap=GAP-DE-BSI-CC)


Compliance gap filled: etsi-ts-104-015-qsc-hybrid-key-exchange (gap=GAP-ETSI-104015)


Compliance gap filled: eu-2022-2554-cyber-resilience-act (gap=GAP-EU-DORA)


Compliance gap filled: eu-cyber-resilience-act-2022 (gap=GAP-EU-NIS2)


Compliance gap filled: fca-operational-resilience-uk (gap=GAP-FCA-CYBER)


Compliance gap filled: cert-in-directions-70b-2022 (gap=GAP-IND-CERTIN)


Compliance gap filled: jisec-japan-it-security-evaluation (gap=GAP-JP-JISEC)


Compliance gap filled: mas-technology-risk-management-guidelines (gap=GAP-MAS-TRM)


Compliance gap filled: occ-bulletin-2024-23-pqc (gap=GAP-OCC-2024)


Compliance gap filled: rbi-cyber-security-framework-2016 (gap=GAP-RBI-CYBER)


Compliance gap filled: cyber-resilience-act-2024-2847 (gap=GAP-RETAIL-EU-CRA)


Compliance gap filled: nca-sa-404-error (gap=GAP-SA-NCA-ECC)


Compliance gap filled: fda-pqc-compliance-framework (gap=GAP-US-FDA-CYBER)


Compliance gap filled: nerc-cip-005-7 (gap=GAP-US-NERC-CIP)


Compliance gap filled: popia-south-africa (gap=GAP-ZA-SABS)


Compliance gap filled: gsma-pq-01-pqc-impact-assessment (gap=gsma-pq-01)


Compliance gap filled: gsma-pq-02-quantum-risk-management (gap=gsma-pq-02)


Compliance gap filled: gsma-pq-03-pqc-guidelines (gap=gsma-pq-03)


Compliance gap filled: 3gpp-rel-19-pqc-compliance (gap=3gpp-rel19-pqc-study)


Compliance gap filled: 3gpp-rel20-pqc-study (gap=3gpp-rel20-pqc)


algorithms.md remediation: promoted pqc_complete_algorithm_reference_07062026.csv -> _07082026.csv (old archived). Corrected MAYO-1/2/3/5 from stale NIST Additional-Signatures Round-1 parameter sizes to the current Round-2 sizes (NIST CSRC mayo-spec-round2-web.pdf Table 2.1); filled previously-empty public-key/ciphertext sizes for the three hybrid-TLS groups (X25519MLKEM768, SecP256r1MLKEM768, SecP384r1MLKEM1024) derived from ML-KEM/ECDH component sizes per draft-ietf-tls-ecdhe-mlkem wire format. SP 800-230 citation for the SLH-DSA '-24' parameter sets was checked against csrc.nist.gov and confirmed already correct (no CSV change). Also corrected the CNSA 2.0 milestone timeline in cnsa20.ts (2027/2035 self-contradiction) to match NSA's published support-and-prefer / exclusive-use dates per category (2025/2026/2027 support-and-prefer; 2030/2033 exclusive).

automated, plan-driven remediation (pqctoday-hub-remediation-plans-07082026/algorithms.md item 5); sources cited in PR description


revisions.md backfill (WS-C): PR #406 "Migrate data accuracy: close proof gaps, fix mistagged vendors, restore integrity gate" promoted 5 CSV snapshots that had shipped without a revisions entry. Computed diff vs. each dataset's prior surviving snapshot: vendors_05092026.csv->07072026.csv (126 new vendors, 290 rows updated, mostly trusted_source_id backfill); migrate_vendor_roadmap_05072026.csv->07072026.csv (69 new vendor roadmap rows, 50 updated, new status/deprecated_at/deprecated_reason columns added for deprecation tracking); migrate_cpe_xref_05102026.csv->07072026.csv and migrate_purl_xref (same range): 25 dangling rows removed from each (national-guidance documents like ANSSI/BSI/ETSI/GSMA PQC guidance that were never real catalog products, per the PR's own description), plus product_id backfilled across 724 purl_xref rows; pqc_product_catalog_06022026.csv->07072026.csv (90 new products, the same 25 non-product rows removed, 759 rows re-verified/corrected -- proof-gate remediation, 6 skip-list rechecks, 14 rows backfilled with downloaded proof). Also mirrors the PR's vendor_id mis-tagging fixes (ibm-hyper-protect-crypto, evertrust-stream, mtg-ag-clm, utimaco-utrust-hsm) and a false PQC claim revert (futurex-vectera-plus).

VND-357
VND-358
VND-056
VND-225
ibm-hyper-protect-crypto
evertrust-stream
mtg-ag-clm
utimaco-utrust-hsm
futurex-vectera-plus
Sophos XGS
SonicWall NSa / TZ (SonicOS)
ForgeRock Access Management (AM)
ANSSI PQC Migration Guidance
BSI PQC Recommendations

automated, plan-driven backfill (pqctoday-hub-remediation-plans-07082026/revisions.md item 2, WS-C); source PR #406 already human-merged (eramusa) 2026-07-07


revisions.md backfill (WS-C): PR #321 "repair 60 broken CC cert bindings + resync 19 stale PQC labels" (full history: 60 Common Criteria rows repointed off stale scraper cert-id slugs, 91 certification_level values and 19 pqc_algorithms mislabels resynced from the bound certificate across the 0602->0608 CSV history; xref unresolved count 60/1187 -> 0/1187). This entry's own computed diff covers the final registered hop, migrate_certification_xref_06062026.csv -> 06082026.csv: 13 rows changed (certification_level FIPS 140-3 L3 -> L1 corrections, pqc_algorithms resync e.g. Cohesity DataCloud 'No PQC Mechanisms Detected' -> 'HSS, LMS').

Cohesity DataCloud
Fortinet FortiGate (FortiOS)
Fortinet FortiManager
Fortinet FortiWeb
I4P Trident HSM

automated, plan-driven backfill (pqctoday-hub-remediation-plans-07082026/revisions.md item 2, WS-C); source PR #321 already human-merged (eramusa) 2026-06-08


revisions.md backfill (WS-C): PR #299 (3.18.0 release) included a routine migrate_saas_xref_05012026.csv -> 06042026.csv data refresh alongside its main playground/matrix work. 9 rows re-verified (last_verified_date bumped 2026-05-01 -> 2026-06-04); no content changes.

Descope Customer & Agentic Identity Platform

automated, plan-driven backfill (pqctoday-hub-remediation-plans-07082026/revisions.md item 2, WS-C); source PR #299 already human-merged (eramusa) 2026-06-05


revisions.md backfill (WS-C): compliance_05192026.csv -> 06262026_r2.csv (commit 9cb28390, "fix(accuracy): remediate confirmed factual inaccuracies across hub") shipped without a revisions entry. 154 of 154 framework rows touched: 98 with substantive corrections (website_url_quality re-verification, GDPR website URL fix, and the NIST row's own notes text corrected -- "FN-DSA (FIPS 206) published March 2025" was factually wrong and now reads "FN-DSA (FIPS 206) is not yet published as of 2026 (Falcon selected; draft pending)", matching NIST CSRC's own FIPS 206 status as an in-development/draft standard); 56 rows received only a CSWP.39 taxonomy-tag backfill with no other content change.

NIST's PQC Standardization Project (launched 2016) selected ML-KEM (FIPS 203), ML-DSA (FIPS 204), and SLH-DSA (FIPS 205) as the first post-quantum standards, published August 2024. FN-DSA (FIPS 206) published March 2025. NIST IR 8547 defines the transition timeline: deprecate 112-bit classical asymmetric by 2030, disallow by 2035. NIST also runs CMVP (module validation) and CAVP (algorithm validation) programs that enforce these standards globally.

NIST's PQC Standardization Project (launched 2016) selected ML-KEM (FIPS 203), ML-DSA (FIPS 204), and SLH-DSA (FIPS 205) as the first post-quantum standards, published August 2024. FN-DSA (FIPS 206) is not yet published as of 2026 (Falcon selected; draft pending). NIST IR 8547 defines the transition timeline: deprecate 112-bit classical asymmetric by 2030, disallow by 2035. NIST also runs CMVP (module validation) and CAVP (algorithm validation) programs that enforce these standards globally.

automated, plan-driven backfill (pqctoday-hub-remediation-plans-07082026/revisions.md item 2, WS-C); source commit already human-merged (eramusa) 2026-07-02; FIPS 206 status re-verified against csrc.nist.gov 2026-07-08


revisions.md backfill (WS-C): PR #408 "Patents refresh, CycloneDX Crypto Registry + SBOM modules, algorithms FIPS-default fix" promoted library_07082026.csv. No prior library-domain entry exists after the 2026-05-07 concept_xwalks entry, and the earliest library CSV snapshot still present in the repo is library_06022026_r1.csv (older snapshots were archived out over time), so this backfill spans that full surviving range. 44 new references added (incl. KpqC-Competition-Results, Korea's national PQC standard selection); 312 existing references received substantive updates (title/date/status refreshes -- e.g. NIST-FIPS140-3-IG-PQC's title and last_update_date corrected to the actual 2026-04-09 IG revision); the remaining 537 rows show only the newly-added superseded_by column defaulting to empty (schema change, not content correction).

FIPS 140-3 Implementation Guidance for Post-Quantum Cryptography

Implementation Guidance for FIPS 140-3 and the Cryptographic Module Validation Program

automated, plan-driven backfill (pqctoday-hub-remediation-plans-07082026/revisions.md item 2, WS-C); source PR #408 already human-merged (eramusa) 2026-07-08


revisions.md backfill (WS-C): PR #408 also promoted patents_07072026.csv. No patents snapshot has ever been logged to this feed; the earliest surviving snapshot is patents_05062026.csv, so this backfill spans that full range. 773 new patents added; 250 existing patent rows received substantive enrichment (previously-empty analysis fields -- one_sentence_summary, primary_inventive_claim, crypto_agility_mode, quantum_relevance, standards_referenced, pqc_migration_score/reason -- backfilled); the remaining 654 rows only gained the newly-added filing_date column (schema change, not content correction).


revisions.md backfill (WS-C item 4): the historical BIKE-1/3/5 status mislabel, cited as already-fixed in both algorithms.md's and threats.md's 07-08 audits, was never itself logged. PR #324 "correct stale count, status labels & remove duplicate algorithm rows" relabeled BIKE-1/3/5 from the stale 'NIST PQC Round 4 (Alternate)' to 'NIST PQC Round 4 (concluded 2025; not selected)' -- BIKE lost to HQC's selection in March 2025 and was never actually promoted to Round 4. Same PR also fixed FrodoKEM-640/976/1344 (mislabeled Round 4 Alternate; actually a Round 3 alternate, never advanced) and removed 4 duplicate bare rows (HQC, Classic-McEliece, LMS, XMSS) that duplicated their parameterized siblings. Backfilled here even though it predates the general 2026-05-19 cutoff because the diff was trivially available from the commit's own message.

NIST Round 3 alternate (not advanced); BSI/ANSSI & ISO 18033-2 recommended

automated, plan-driven backfill (pqctoday-hub-remediation-plans-07082026/revisions.md item 4, WS-C); source PR #324 already human-merged (eramusa) 2026-06-09


migrate.md remediation item 7: normalized 4 rows with lowercase verification_status="verified" to "Verified" in pqc_product_catalog (07072026 -> 07082026); cosmetic only, deriveVerificationStatus() already re-derived these correctly at load time regardless.

python-cryptography microsoft-365 python-ssl-module prometheus

automated, plan-driven (pqctoday-hub-remediation-plans-07082026/migrate.md item 7, WS-C); local commit 3ed654c3 on fix/wave1-migrate-0708, not yet merged


timeline.md remediation item 1 (mandate-label completion sweep): timeline_06262026_r4.csv -> timeline_07082026.csv (old file archived, not deleted); timelineFacts.generated.ts regenerated in the same commit. Labeled the US Digital-Signature Migration Deadline (2031) row HARD to match the already-HARD 2030 Key-Establishment row -- both derive from EO 14412, verified against whitehouse.gov (both dates use binding "shall" language). Audited and labeled the remaining 27 of 37 Deadline-category rows plus 5 CNSA 2.0 Migration-category lanes (signing/web-cloud/networking/OS/PKI) against each row's own primary source (NSA CNSA 2.0 advisory, EO 14412, EO 14306, Canada ITSM.40.001, EU Commission Recommendation C(2024) 5871, BSI TR-02102, MAS Circular MAS/TCRS/2024/01, ASD Guidelines for Cryptography, India DST Quantum-Safe Ecosystem report, and others -- see commit 8dfc2ca5 message and session record for the full per-row source list). Raised Canada's confidence_score 60->75 (label was already HARD but under-evidenced; ITSM.40.001 has a real enforcement mechanism -- mandatory PQC procurement clauses on GC contracts after April 2026 -- so the label stands, just better-sourced now). Introduced a DRAFT mandate_type value for genuinely unresolved sourcing rather than guessing HARD or SOFT: the two US "112-bit Security" rows (source is NIST IR 8547, still an Initial Public Draft per csrc.nist.gov as of verification) and two Hong Kong HKMA rows (source is a strategy/"blueprint" press release, not a confirmed formal supervisory circular). Left the Microsoft "Full PQC Transition" row unlabeled (NONE) -- a vendor's own roadmap commitment is not a government mandate/guidance in the sense this field measures. Also fixed a pre-existing bug this sweep exposed: GanttDetailPopover.tsx only showed the mandate badge for Deadline-phase rows, so the new CNSA-lane labels (Migration category) would never have displayed -- now any row with an event-level label shows its badge, regardless of phase.

United States / Digital-Signature Migration Deadline (EO June 22 2026)

United States / 112-bit Security Deprecated

automated, plan-driven (pqctoday-hub-remediation-plans-07082026/timeline.md item 1, WS-C); local commit 8dfc2ca5 on wave2-timeline-0708, not yet merged; EO 14412 dates independently re-verified against whitehouse.gov presidential-actions page 2026-07-09; NIST IR 8547 draft status independently re-verified against csrc.nist.gov/pubs/ir/8547/ipd 2026-07-09; CNSA 2.0 staged schedule cross-checked against two independent secondary sources (entrust.com transition-timetable summary, postquantum.com CNSA 2.0 guide) consistent with the already-verified src/components/Algorithms/cnsa20.ts CNSA20_TIMELINE


compliance.md remediation item 1: added the EO 14412 ("Securing the Nation Against Advanced Cryptographic Attacks") landscape row -- the operative US PQC executive order previously existed only in the timeline CSV, not the compliance framework list. HARD mandate (requires_pqc=yes); key-establishment migration deadline Dec 31 2030 (FIPS 203/ML-KEM), digital-signature migration deadline Dec 31 2031 (FIPS 204/ML-DSA); excludes National Security Systems (remain under CNSA 2.0/NSA). Source verified independently against whitehouse.gov and the Federal Register (doc 2026-12909, Vol. 91 No. 121 pp. 38483-38486) before writing, per the timeline audit's discipline of not guessing the EO number. Snapshot compliance_06262026_r2.csv (archived) -> compliance_07092026.csv. Same commit also rewrote complianceCuriousPrefaces.ts (DORA/CNSA-2/ANSSI/BSI/ENISA prefaces walked back to match their CSV rows' actual claims), removed the dead PERSONA_COMPLIANCE_TABS 6-tab config, fixed Records-tab staleness/Refresh honesty, collapsed the first-visit banner stack for returning visitors, added FIPS-row deep links into Records, and removed the low-signal confidenceScore badge from the landscape/popover views -- none of those are CSV changes so are not itemized as separate rows here.

automated, plan-driven (pqctoday-hub-remediation-plans-07082026/compliance.md item 1, WS-C); local commits 2b35d23d/8a2d2d5a on wave2-compliance-0708, not yet merged


patents.md item 5: patents_07072026.csv -> patents_07082026.csv. Corrected 13 rows (plan's audit estimated 6; the wired 07072026 snapshot actually had 13) where nist_round_status mapped a McEliece-family algorithm ("McEliece" or "Classic McEliece") to status "classical" -- Classic McEliece is a NIST Round 4 candidate (not selected; HQC was chosen in March 2025 per NISTIR 8545) and remains BSI-recommended for long-term confidentiality; it is not a classical/pre-quantum scheme. Corrected to round4_candidate, matching the status already used on 16 other Classic McEliece entries in the same CSV. Unrelated array entries (Niederreiter, RSA, ECC) in the same rows were left untouched -- still genuinely classical. patents_06092026_r2.csv (superseded diff baseline) archived in the same change.

automated, plan-driven (pqctoday-hub-remediation-plans-07082026/patents.md item 5, WS-C); McEliece Round 4 / BSI status re-verified against csrc.nist.gov (NISTIR 8545, HQC selection announcement) and bsi.bund.de 2026-07-09; local commit on wave2-patents-0708, not yet merged


leaders.md remediation (wave2): refreshed leaders CSV (leaders_06242026_r3 -> leaders_07092026). Spot-checked 10 curated profiles against current public sources; fixed 1 confirmed error (Vadim Lyubashevsky Country United States -> Switzerland; he is based at IBM Research Europe, Zurich) and 1 stale title (Jaime Gomez Garcia -> Global Head of Quantum Threat Program). Added verified_date column (141 existing + 10 fresh 2026-07-09 re-checks), now surfaced in the UI. Backfilled peer_reviewed/vetting_body for the 196 rows linked via keyResourceRefs by joining against library_07082026.csv: 107 blank rows backfilled, 51 rows correctly a stale "no" (artifact of a 2026-05-06 column rename, not a real assessment) corrected to the linked library reference's actual value, 14 rows with disagreeing linked refs set to "partial". Added 2 new sourced entries (Matthew Green, Skeptic/Critic; Lori Beer, Industry Adopter) to categories the audit flagged as near-empty (item 5, stretch). Also: tiered the 124 auto-imported stub rows from the 208 curated rows via a new sourceKind field (code change, not a data correction, but the classification is CSV-content-derived) and fixed the executive persona sort-override bug in LeadersGrid.tsx.

Vadim Lyubashevsky
Jaime Gomez Garcia
Matthew Green
Lori Beer

automated, plan-driven (pqctoday-hub-remediation-plans-07082026/leaders.md items 1-5, WS-C); local commit 9d672ca2 on wave2-leaders-0708, not yet merged


learn.md remediation item 1+2 (WS-C): shipped pqcquiz_07082026.csv (archives pqcquiz_06242026.csv), adding 96 new quiz questions across 7 new QuizCategory values (sbom, cbom, crypto-registry, verification-closure, pqc-grc, skills-team-structure, soc-implementation-pqc) so four previously-untestable supply-chain/governance modules and three newly-routed orphan modules are covered by at least one persona checkpoint's quiz categories. Every question is traceable to a sentence in the corresponding module's content.ts/rag-summary.md -- no invented facts. Also retired the redundant pqc-team module (same 1-FTE-per-500-instances staffing heuristic as the fuller skills-team-structure, which absorbs its role in the executive path) -- not a CSV change, noted here for completeness.

sbom cbom crypto-registry verification-closure pqc-grc skills-team-structure soc-implementation-pqc

automated, plan-driven (pqctoday-hub-remediation-plans-07082026/learn.md items 1+2, WS-C); local commit 4d350c9a on wave2-learn-0708, not yet merged


library.md remediation (fix/hub-remediation-wave2-0708, wave2-library-0708, local commit db9d8b2e, not yet merged): library_07082026.csv -> library_07092026.csv. 156 rows substantively changed, 42 additionally gained the new purpose column (27 purpose-only). Backfilled 29 thin/title-echo or empty short_description rows by promoting real content from the library-doc-enrichments corpus (no fresh enrichment runs needed given 98.4% coverage). Proof-gate sweep on the 10 active rows with a recorded failed download check: 8 re-verified live and recovered (incl. correcting ETSI TS 103 744 -- v1.3.1 does not exist, real latest is v1.2.1 March 2025), 2 deprecated (thequantumfinanceboardroom.com confirmed NXDOMAIN). url_needs_review backlog cut from 100 to 8 active rows via direct re-fetch (90 recovered, 2 more deprecated for fabricated ETSI document numbers -- TS 103 774, GR QSC 020 -- that do not exist in ETSI's catalog); the remaining 8 are left as needs-review (verified as an environment-level bot block, not confirmed dead). Fixed the Falcon-Spec-v12 FIPS 206 cross-reference (no longer claims FIPS 206 is published; still IPD/draft per csrc.nist.gov). Also corrected IETF RFC 9701's document_title (was mislabeled with an unrelated draft's title; real title per rfc-editor.org is "JSON Web Token (JWT) Response for OAuth Token Introspection"), exposed as a live contradiction once its description was backfilled against the real document. Normalized 21 rows off a stray 0.9/0.95 confidence-score scale onto the 0-100 scale used elsewhere; surfaced confidence score in the detail drawer. Added a dedicated purpose CSV column (resolvePurpose()) overriding the manual_category keyword heuristic for 42 manually-reviewed rows.

now describes FIPS 206 as "forthcoming ... still in draft; not yet published" instead of claiming it is already standardized

automated, plan-driven remediation (pqctoday-hub-remediation-plans-07082026/library.md, all items P1-P3); facts re-verified against rfc-editor.org, csrc.nist.gov, etsi.org, and live HTTP checks on 2026-07-09; local commit db9d8b2e on fix/hub-remediation-wave2-0708 (branch wave2-library-0708), not yet merged/pushed


library.md follow-up: library_07092026.csv -> library_07102026.csv. Added PKCS11-V32-OS-OASIS for the PKCS#11 v3.2 OASIS Standard finalized 2026-06-03, and deprecated the prior PKCS11-V32-OASIS row (Committee Specification Draft 01 / CS01) with superseded_by=PKCS11-V32-OS-OASIS so it surfaces as a previous revision in the Library detail drawer rather than being deleted (matches the existing PKCS11-V31-OASIS -> PKCS11-V3-OASIS supersession pattern). Verified via the OS spec's own Appendix C Revision History (pkcs11-spec-v3.2-os.pdf pp.473-475) and matching table-of-contents pagination against the CSD01 PDF that no technical content changed after Working Draft 13 (16 Apr 2025) -- CSD01/CS01/OS are content-identical, only the approval-stage label and status/date fields changed. Proof file public/library/PKCS11-V32-OS-OASIS.html downloaded live from docs.oasis-open.org before marking the row active (gitignored, local-only per existing convention).

automated, user-directed ("add the final release to our library — older release should show as previous revision"); PKCS#11 v3.2 OS status re-verified against docs.oasis-open.org 2026-07-10; local commits 4c7525b4/7c400a1c on test/all-changes-0710, not yet merged/pushed


Data-pipelines remediation (executed on fix/data-pipelines-remediation-0709, not yet merged/pushed): quality pass across timeline, algorithms, library, threats, compliance, and migrate catalog data. Timeline: filled missing source evidence, corrected non-canonical values, refreshed enrichment on 15 rows. Algorithms: corrected 4 protocol citation errors and an inaccurate FIPS 206 status claim. Library: recovered 18 missing or broken source documents, including 2 corrected ETSI document version numbers; repointed 21 internal cross-references. Threats: corrected a wrong RFC citation and replaced one row's evidence file with real content. Compliance: fixed a fine-lookup key mismatch affecting an executive KPI, corrected PQC-coverage on 4 certification records against their published NIST security policies, and populated product links on 1,040 certification cross-reference rows. Migrate catalog: deprecated 3 duplicate product entries, corrected an inaccurate PQC-support claim, fixed a status label that displayed non-PQC products as fully verified, and remapped 64 rows to the current category taxonomy. Also: quiz category list, leader resource links (33 rows), and concept cross-references cleaned up; source snapshots archived to the standard 2-version limit. Every correction was checked against the original publisher (standards bodies, vendor docs, or government sources) before being applied.

user-approved data-pipelines remediation plan, executed 2026-07-09/10; local commits on fix/data-pipelines-remediation-0709, not yet merged/pushed