# Reporting and recording corrections

## What to send

- the slice ID, file or field (for example `ensoforecast-ldeo2-1997-12-lead06`, `record_type`), or the ledger entry (for example `E4`);
- what is wrong and what you believe is right;
- the evidence: catalog or product documentation, a dated bulletin or issue record, a file header, or another primary source;
- whether you were involved in producing or maintaining the archive.

Contact for corrections: **https://vultax.com/contact**. Include the edition and affected record or slice.

## What we do

1. Check the claim against the transfer and the cited evidence. Source values are never edited; a correction changes interpretation, metadata or documentation, or adds evidence.
2. Log it with an ID (`ENSO-NNN`) in `CHANGELOG.md` and `data/corrections.json`, and update the evidence ledger entry it affects. Evidence that confirms an issue time, the anomaly baseline or the product definitions is recorded with its source and the status changes accordingly.
3. Issue a new edition number, regenerate checksums and keep earlier published editions unchanged.
4. Credit the reporter if they wish.

A correction from the archive's creators or custodians is recorded as theirs. It does not make the edition reviewed or endorsed by them.

## Current status

Edition `0.3.2` was published on 2026-10-25 by Christopher Geneth Kurg. Corrections ENSO-001 to ENSO-012 are listed in `CHANGELOG.md`; those after the first pass came from an independent internal review, not from the original creators. No external correction has been received.