Corrections
A correction is part of the archive, not an embarrassment hidden from it.
Every material claim has dependencies. When evidence changes, pages, translations, search rows, maps, exports, structured data, and machine answers must change together.
Why the earlier site was contained
An earlier release made a register entry carry more weight than the evidence supported: it assigned disputed fields, treated one early entry as a proven bridge into a later lineage, and built place and solicitation language on that bridge. The same release also used privacy and intake language that did not match the actual data flow.
The immediate response was a minimal containment site. Release R1 restores substantive research content while leaving those person and lineage claims unpublished until their separate evidence and publication gates pass.
Correction workflow
Bind the challenge
Identify the public URL, statement or field, release version, and reason for concern.
Preserve both states
Keep the previous wording as change history, never as current metadata or uncited answer material.
Review the evidence
Check the source, reading provenance, identity and relationship logic, counterevidence, rights, privacy, and translation.
Propagate or explain
Rebuild every dependent output or publish a reasoned decision that the claim remains unchanged.
Issue a receipt
Record what changed, what did not, which release supersedes which, and whether further work remains open.
How to raise a concern now
There is no correction form in this release. You may write in your own words to hello@dobesh.org. Include the page, the exact statement, and a source or explanation if available. Sending an email does not grant publication permission.