2026-06-03 / Production readiness
Site-wide
Status: Open
Public domain smoke shows eugenics.net is not yet serving this Astro site; deploy and DNS/Cloudflare binding remain production blockers.
Public trust record
Updates and Corrections Log
This log records substantive corrections, publication-state changes, and open production-readiness blockers.
How Updates Are Recorded
Substantive changes should name the page, issue type, review state, and date. Minor copy edits may be batched, but source corrections, safety wording, accessibility fixes, publication-state changes, and review-status changes should be visible here.
The article feed is available at rss.xml.
Current Records
2026-06-03 / Cloudflare status
Deployment
Status: Blocked
OpenClaw build, security checks, content checks, and browser QA passed. Cloudflare deploy and log review are blocked until Wrangler is authenticated with a non-interactive Cloudflare API token.
2026-06-03 / Review state
Site-wide
Status: Open
Internal V3 editorial review is represented in source packets. External subject-matter and affected-community review remains pending unless a page states otherwise.
2026-06-03 / Trust surface
Corrections and Contact
Status: Added
Added triage expectations and this public log route for substantive corrections and publication-state changes.
Correction Boundary
The corrections route is for accuracy, source quality, accessibility, historical context, and anti-endorsement framing. It is not a medical, reproductive, genetic counseling, legal, crisis-support, or advocacy channel.
Send corrections to corrections@eugenics.net.
Static source packet
Evidence Snapshot
Updates and Corrections Log documents publication-state changes, substantive corrections, review boundaries, and production blockers so sensitive historical material remains accountable.
Research Brief
Correction Records Prevent Silent Authority Claims
A site about eugenics history should not sound more certain than its review process justifies. This page records when internal editorial review is complete, when external review is pending, and when a page changes because a source, claim, warning, or accessibility issue was corrected. That makes the trust model visible instead of relying on institutional tone alone.
Publication State Is Evidence
A canonical URL in the source code is not the same as a live production site. Public smoke tests, domain routing, headers, robots, sitemap, and deployment records all matter. The log therefore records production blockers such as a parked domain or missing Cloudflare binding separately from editorial content status.
Source Mapping Needs the Right Source Type
A search-quality policy can support an editorial anti-spam rule, but it cannot support a historical claim about heredity, human dignity, or affected communities. This log gives the project a place to record source-mapping corrections so claim evidence remains aligned with source role and limits.
Sensitive History Needs Affected-Community Visibility
Corrections can involve more than factual dates or broken links. They can involve wording that centers institutions while minimizing people harmed by classification, segregation, sterilization, exclusion, or dehumanization. The log keeps those correction categories visible as part of responsible publication.
No-Advice Boundaries Stay in Scope
Updates to modern bioethics pages should preserve the site's no-advice boundary. The project can discuss consent, privacy, disability rights, genetic discrimination, and governance without giving medical, reproductive, genetic counseling, fertility, or legal advice.
Claim Map
Corrections and update records are part of the trust surface.
Google Search Central: Spam Policies is used only for publication-quality boundaries: a sensitive site should not rely on misleading summaries, expired-domain abuse, citation theater, or scaled low-value pages. A public update log helps readers evaluate whether the project corrects errors and tracks publication state.
Supported by: Google Search Central: Spam Policies
Historical and bioethics claims require sources that actually address history, genetics, rights, or teaching context.
NHGRI: Eugenics and Scientific Racism and UNESCO: Universal Declaration on the Human Genome and Human Rights support the distinction between genetic evidence, human dignity, and harmful claims about inherited worth. The update log records when source mapping or claim framing changes.
Supported by: NHGRI: Eugenics and Scientific Racism; UNESCO: Universal Declaration on the Human Genome and Human Rights
Teaching difficult eugenics history requires explicit anti-endorsement and source-use boundaries.
UCL: Teaching UCL's Eugenics Legacies Now and in the Future supports careful classroom framing, warnings, and source criticism. Updates to teaching guidance should be visible because unsafe classroom activities can reproduce the logic being studied.
Supported by: UCL: Teaching UCL's Eugenics Legacies Now and in the Future
Archive corrections must consider provenance, rights, context, and affected communities.
Eugenics Archives supports archive-centered interpretation and survivor or affected-community context. Changes to archive publication state, raw-source policy, or item-level warnings should be logged rather than hidden in silent edits.
Supported by: Eugenics Archives
Production readiness is separate from editorial readiness.
Cloudflare Pages custom-domain documentation shows that a Pages deployment and an apex custom domain require explicit Cloudflare zone and custom-domain setup. Until the domain serves the built site, production smoke and security-header checks cannot be considered closed.
Supported by: Cloudflare Pages: Custom domains
Source Coverage
Google Search Central: Spam Policies
Role: Search-quality policy source used only for editorial and SEO boundaries against expired-domain abuse, scaled low-value pages, and misleading content.
Supported claims: SEO should not substitute for usefulness or accuracy; Trust surfaces need visible editorial standards
Limits and caveats: This is not a historical or bioethics source; it applies only to publication quality controls.
Sensitive-language note: Use only for site-governance pages, not as evidence about eugenics history.
Affected communities: readers, educators, research users
NHGRI: Eugenics and Scientific Racism
Role: Official genomics source explaining eugenics as a scientifically inaccurate theory and showing how scientific racism used measurement language to support hierarchy.
Supported claims: Eugenics misused heredity and statistics; Scientific racism converted prejudice into claims of biological hierarchy
Limits and caveats: The source is a high-level fact sheet and should be paired with legal, archive, country, and affected-community sources for policy detail.
Sensitive-language note: Use the source to critique racist and ableist claims, not to repeat classification terms as neutral categories.
Affected communities: racialized communities, disabled people, institutionalized people
UNESCO: Universal Declaration on the Human Genome and Human Rights
Role: International human-rights instrument placing genetic science inside dignity, equality, freedom, consent, and non-discrimination principles.
Supported claims: Human dignity is not reducible to genetic traits; Genetic knowledge must be governed by rights
Limits and caveats: The declaration gives normative principles, not a detailed history of specific eugenic policies.
Sensitive-language note: Use to set rights boundaries rather than to offer medical, reproductive, or legal advice.
Affected communities: patients, families, disabled people, racialized communities
UCL: Teaching UCL's Eugenics Legacies Now and in the Future
Role: Institutional teaching resource for discussing eugenics legacies with explicit pedagogy, warnings, and critical classroom framing.
Supported claims: Teaching difficult eugenics history requires planning; Source use should not platform harmful claims
Limits and caveats: The toolkit is institution-specific and should be adapted to local classroom needs.
Sensitive-language note: Do not ask students to reenact classification, ranking, or reproductive policy decisions.
Affected communities: students, educators, affected communities
Eugenics Archives
Role: Archive and public-history source that includes contextual material, primary-source interpretation, and survivor or affected-community perspectives on eugenics history.
Supported claims: Survivor and affected-community context changes how sources should be read; Archives need warnings and interpretation
Limits and caveats: Archive entries vary by item; use the site as contextual evidence rather than a substitute for item-level review.
Sensitive-language note: Do not copy raw primary sources or testimony out of context; summarize respectfully and link to context.
Affected communities: survivors, families, disabled people, Indigenous and racialized communities
Cloudflare Pages: Custom domains
Role: Cloudflare platform documentation for binding custom domains to a Pages project and configuring apex domains through a Cloudflare zone.
Supported claims: A custom apex domain requires Cloudflare zone and custom-domain setup; A deployed static site still needs domain binding before the apex URL can be production smoke tested
Limits and caveats: This is deployment documentation, not a historical or bioethics source.
Sensitive-language note: Use only for production-state and deployment evidence.
Affected communities: readers, educators, research users
Teaching Use
Learning objectives
- Ask students to compare a page claim, source role, caveat, and correction history.
- Show how a correction log helps distinguish authority from accountability.
- Use production-state notes to explain why a URL can exist without being the final reviewed resource.
Discussion prompts
- Why is a visible correction record important on a site about dehumanizing historical claims?
- What kinds of changes should be public rather than silent?
- How should readers treat a page that is internally reviewed but still awaiting external review?
Classroom warnings
- Do not use correction records to relitigate whether targeted communities deserved rights.
- Do not treat a source link as sufficient support without checking source role and limits.
- Do not present pending review as completed review.
What This Page Does Not Do
- Updates and Corrections Log does not endorse eugenics, racial hierarchy, antisemitism, ableism, forced sterilization, genetic discrimination, or reproductive coercion.
- It does not provide medical, reproductive, genetic counseling, fertility, or legal advice.
- It does not treat SEO value as a reason to hide production blockers or review gaps.
- It does not publish raw propaganda, extremist material, or primary-source downloads without context and review.
- It does not convert internal editorial review into a claim of final external authority.
Last reviewed by Eugenics History & Bioethics Project editorial desk. Source packets are pre-launch editorial tools and remain subject to specialist or affected-community review before public launch.