Submit evidence or a correction

Reports accepted

• New lifecycle record backed by public evidence
• Changed status or completed shutdown
• Incorrect date, operator, entity type, or current-state wording
• Broken, redirected, or repurposed source URL
• Stronger primary source for an existing event
• Duplicate record or incorrectly grouped models/features

What to include

• Record name and current public URL, if available
• Entity type: tool, service, product, API, model, feature, company, or hardware
• What changed and why the existing record may be incomplete or incorrect
• Event date, announcement date, or best-supported approximate date
• At least one public evidence URL
• Whether each source is official, archived official material, or secondary reporting
• A short neutral summary of the proposed correction or new entry

Evidence rules

Prefer official announcements, documentation, support pages, changelogs, archived official pages, regulator records, or acquisition statements. Secondary reporting is useful when primary material is unavailable, but unsupported claims and private information should not be submitted.

Review process

Submissions are checked against the archive methodology. A proposal may be accepted, rewritten, left as needs review, or declined when the available public evidence is insufficient. Submitted text may be edited into neutral registry wording.

Public submission channel

Use GitHub Issues only for information that can be public. Do not include personal data, private correspondence, account credentials, confidential material, or unverified accusations.