# v0.29.0 Eviulon external-project link Date: 2026-08-19 Release target: 0.29.0 Scope: one direct, site-wide external navigation link to `https://eviulon.com/` ## Purpose The user requested that the current Eviulon public site be reviewed before MachineIntelligences.org links to it. The root page was checked on 2026-08-19 and identified itself as the Eviulon public portal. The review established the exact HTTPS destination and a bounded descriptive context for the link; it did not establish ownership, legal recognition, sovereignty, operational integration, or factual endorsement of every claim on the external site. ## Implementation `includes/site.php` now renders one direct link in the shared global footer: - destination: `https://eviulon.com/`; - visible label: `Eviulon.com ↗`; - relationship marker: `rel="external"`; - accessible name: identifies Eviulon.com as the Eviulon project public portal and as an external site; - browsing context: normal same-tab navigation; no forced new window. Because the footer is part of the shared server-rendered shell, the link appears on every canonical public page and on the first-party 404 recovery response. ## External-state boundary The link is navigation only. It does not: - load remote JavaScript, CSS, fonts, images, frames, APIs, analytics, cookies, or beacons; - add Eviulon.com to the MachineIntelligences.org sitemap; - declare `sameAs`, common ownership, endorsement, legal affiliation, diplomatic recognition, or shared operational infrastructure; - convert research-context Eviulon claims into current MachineIntelligences.org facts; or - prove that the external destination remains unchanged after the dated review. Future maintainers should recheck the destination if its ownership, purpose, redirects, security, or public description materially changes. ## Validation contract Release validation must require: - the exact `https://eviulon.com/` destination once in every shared-footer response; - visible external-link text and a nonempty accessible name; - `rel="external"` and no forced new browsing context; - no Eviulon URL in `sitemap.xml` or local canonical/structured-data identity; - no new remote runtime asset or request dependency; and - preservation of all existing route, report, source-freshness, accessibility, 404, UAIX, taboo, secret-hygiene, and release-integrity contracts. ## Evidence boundary This change proves only that the packaged site contains a direct, accessible link to the reviewed external destination. It does not prove live deployment, external-site continuity, external claims, common ownership, or legal relationship.