Corrections and revision policy

A correction should make the before-and-after state visible without silently rewriting the evidence trail.

Updated Core source baseline How we verify claims

What a correction records

  • the affected page or dataset record
  • the earlier wording or classification
  • the corrected wording or state
  • the source that justified the change
  • the review date and any remaining uncertainty

Current correction channel

A monitored public inbox or form has not been configured, so this site does not claim one. Until a contact channel is verified, correction work is recorded in the public update log and source-level revision notes. The absence of a form also means no correction-form data is collected.

What does not count as a correction

A later product announcement may update a status without making the earlier record wrong. Likewise, a company restatement is evidence of the new company position; it does not erase an earlier regulatory or research record.

October 8 research reconciliation

The local revision adds Studio 617.42, the explicit 6681537 fix history, Linux PB/NFB records, Enterprise U9 chronology, security-only 582.78 and CUDA 13.4.2. Historical open-issue relationships and release dates are preserved. The update log describes the scope and remaining limits.

[104][106][32]

Evidence trail

Sources used on this page

Source class describes ownership and form. It is not a reliability score.

  1. Studio 617.42 desktop package

    NVIDIA · 2026-10-06

    Official documentation
  2. Game Ready 617.14 notebook package: explicit bug fixes

    NVIDIA · 2026-09-22

    Official documentation
  3. CUDA Toolkit Archive

    NVIDIA Developer · Current release index

    Official documentation

Core source registry dated ; later page and record revisions carry their own dates. An inaccessible link triggers source maintenance.