Correction Log
Correction records can show public-safe issue categories, status, limits, and correction paths without exposing private incident detail.
Keep labeled until evidence supports a final classification.
Restore the technical class name, scan residue, and verify the rendered result.
Align visible labels with internal values and confirm the grouped settings update.
Hold from upload until markup and testing match the shared site logic.
Keep stronger installation, delivery, and public-use claims behind approval.
Keep account-level identity changes separate from website repository changes.
Apologies do not fix the source of a bad claim.
Story problem: The LLM apologized and generated more fixes without keeping the original claim visibly unverified.
NoDrift answer: NoDrift keeps suspect claims labeled until evidence supports a final classification, so the same source problem does not quietly spread.
The same drift should not keep coming back.
Story problem: Phase-two features kept sneaking back into Lena's current work.
NoDrift answer: NoDrift keeps recurring mistakes visible as correction items so the source problem is handled instead of merely apologized for.
Candidate Incident Under Review
A candidate incident remains visible while its final classification is unsupported. It is not counted as confirmed drift or confirmed hallucination unless the evidence review supports that classification.
Wordmark Class Replacement Defect
A broad text replacement temporarily changed a CSS class used by the NoDrift wordmark. The correction path was to restore the technical class name, scan for residue, and verify the rendered result.
Customization Preset Mismatch
A translated customization flow initially failed to update all grouped settings because visible labels and internal data values no longer matched. The correction path was alignment plus browser verification.
Free Preview Mobile Menu Defect
A PT-BR free-preview page used a different mobile-menu pattern from the shared header, so it stayed deferred from upload until the markup and testing path matched the shared site logic.
Governance And Package Readiness Findings
Private package review found readiness gaps that prevented stronger installation or public-use claims. The correction path was to fix approved items privately and keep the rest behind gates.
Organization Avatar Mismatch
The website repository did not contain the wrong image; the mismatch lived at the organization-profile level. The site avatar was corrected while the account-level change stayed a separate action.
Protected Detail
Public-safe issue groups can name cause, status, and correction path. Private incident transcripts, local evidence folders, exact internal cause files, and private corrective lessons remain outside the public docs.