Editorial / corrections and updates

Every correction is recorded in the change log.

When a material, claim or record contains an error, the editorial team checks the exact passage against an open source and records the result in a later release.

Current release boundary

The public protocol and template are available now.

There is no separate public intake channel yet. We do not publish an unverified address or promise automatic handling; a prepared request can be passed to the project owner through an already confirmed contact channel.

What to send

A precise request can be checked against a source and linked to a specific record.

Where is the error

Give the canonical page or JSON URL and the exact passage that needs checking.

What should change

Name the issue: fact, date, status, attribution, link or conclusion boundary. Add proposed wording.

What supports it

Provide an open link, publisher, publication date and a short explanation of why the source supports the correction.

How a check works

Record

The editorial team keeps the URL, passage and request date so the report can be checked again.

Compare

The source is opened separately; publisher, date, exact wording and scope are checked.

Decide

The correction is accepted, declined or turned into an open question when evidence is insufficient.

Release

The relevant material, claim or record is updated; the review date and change log remain visible.

What the editorial team separates

Factual error

An incorrect number, name, date, status or source relationship. This requires new supporting evidence.

Status update

A source changed or a new document appeared. The old wording is not replaced without a date and context.

Editorial preference

A style preference does not change a fact. It is considered separately from corrections and evidence boundaries.

Request template

Copy the fields and fill in only what can be checked.

URL:
Exact passage:
Problem:
Proposed correction:
Source:
Source date:
Conclusion boundary: