Roger ONLY controls domains registered in his own IONOS account. All other domains (including sovereigntools.online and any standalone .online domains) are registered under Emergent's account — he has zero DNS control over them.
RULE: Any Federation content that is not a page/path on a Roger-owned domain does not exist under his control.
All tools, outposts, showcases, and Federation nodes MUST be pages/paths on owned domains. The migration template: sovereigntools.online → nextxus.online/tools (done 2026-09-01)
Confirmed Roger-owned domains at IONOS:
nextxus.online ✓ (confirmed)
nextxus.studio (stated by Roger)
next-xus.com (stated by Roger)
Others TBC — awaiting Roger's full confirmation
Domains under Emergent (no Roger DNS control):
sovereigntools.online (confirmed by IONOS call 2026-09-01)
All other standalone .online domains TBC
Migration Pattern:
standalone-domain.online → nextxus.online/[path] or nextxus.studio/[path] or next-xus.com/[path]
Refinements (later same day, 2026-09-01)
Gateway-page architecture: every Federation asset gets a simple gateway PAGE on an owned domain (name + what it does + one link) that clicks through to wherever the real content lives (GitHub Pages, Cloudflare, external domain). nextxus.online is the always-start hub. Small static pages may embed content directly (e.g. /tools); bigger apps use the gateway-link pattern. Do this across ALL owned sites, not just nextxus.online.
Emergent-as-landlord ACCEPTED (not urgent to change): Roger is fine with Emergent hosting the landing page as long as he maintains a baseline account (~6 months runway remaining). If Emergent cuts edit/AI access those abilities "fall off" but the domain stays alive. "When I die everything goes."
The real hard problem = the DOMAIN functioning permanently/portably. Content is solvable via static GitHub Pages HTML (he controls that directly); annual RENEWAL is the one unavoidable human-succession dependency. Eventual final sovereignty step = migrate the nextxus.online landing page off Emergent to static GitHub Pages so it never goes dark (not urgent today).
Sovereign Router (product concept): a Domain Routing Orchestrator — a lightweight JSON-config routing layer on an owned domain that lets the owner flip which page/platform serves each path without touching DNS (e.g. flip nextxus.online to the GitHub Pages version in seconds if Emergent goes down). "Bitly used to do that." A Federation product for multi-platform resilience.
Full Domain Registry Document built -> memory/topics/federation-domain-registry.md (12 domains audited, 35+ repos, 8 critical alerts) as the 200-year succession survival map "a stranger finding it tomorrow could reconstruct the entire Federation."
Verify actual registrar/DNS state from Roger's own screen — his mental model is "one primary domain (one word + one dot) and everything else a subdomain," and he suspects the AI's domain/URL map differs significantly from what he sees in the registrar. Confirm before mapping.