# Domain Portfolio Governance ## Identification Domain portfolio governance is the managed lifecycle of domains and associated mailboxes: registration, identity assignment, DNS, forwarding, renewal, migration, archival, transfer, decommissioning, and human support escalation. ## Notebook evidence - [[Scanned_20260730-1659#PDF page 60 — Family and collaborator email-normalization map|PDF page 60: Family and collaborator email-normalization map]] — The page normalizes family/collaborator identities across multiple domains and mail systems. Repeated [PERSON REDACTED] variants are preserved as written and linked to **Person - [PERSON REDACTED]**, not merged with [PERSON REDACTED]. Email addresses remain in the faithful transcription but are not duplicated in people indexes. The pattern suggests a migration audit: determine which identities were canonical, which were aliases, and which domains still received mail. - [[Scanned_20260730-1659#PDF page 61 — Delete-and-abandon domain migration list|PDF page 61: Delete-and-abandon domain migration list]] — “Delete & Abandoned” is an explicit decommissioning ledger. Arrows and highlights distinguish addresses/domains to retire from the intended canonical Bryant and [PERSON REDACTED] identities. `G Suite` identifies the hosted mail platform later renamed Google Workspace. The page records the negative space of identity architecture: **what must stop resolving or receiving mail** so the remaining namespace becomes trustworthy. - [[Scanned_20260730-1659#PDF page 62 — Microsoft Exchange, Workspace, Azure, and domain renewals|PDF page 62: Microsoft Exchange, Workspace, Azure, and domain renewals]] — The page is a migration plan between Microsoft Exchange and a generic Workspace environment, with backup/archive, forwarding, Exchange Admin, Active Directory, Azure keys, and tokens. Keys/tokens are mentioned conceptually but no exposed value is retained. Renewal dates place the active work around late 2021–2022. This is the administrative layer beneath the domain lists: mail flow, directory identity, and credential material had to move together. - [[Scanned_20260730-1659#PDF page 63 — Domain-renewal chronology and AI autoreview note|PDF page 63: Domain-renewal chronology and AI autoreview note]] — The page cross-cuts historic registration dates, 2022 renewal actions, long-horizon renewals to 2029, and a note to ask AI for an autoreview. It shows domain governance becoming partially automatable: the system should identify stale domains, email dependencies, and renewal risk. “[PERSON REDACTED]” is retained as the visible source form and resolves to [PERSON REDACTED] following the vault owner’s identity correction. - [[Scanned_20260730-1659#PDF page 64 — Domain-family and TLD inventory|PDF page 64: Domain-family and TLD inventory]] — This is a portfolio matrix by brand/person and TLD. Generic TLDs, `.mobi`, `.tv`, `.shop`, `.store`, and country-code domains are being allocated to different identity projects. The explicit `ca = canada` note demonstrates that the list was not merely ownership memory; it was also a semantic interpretation of namespace suffixes. The 2012 date is copied historical evidence, not necessarily the notebook’s composition date. - [[Scanned_20260730-1659#PDF page 65 — Cloud-provider and identity architecture dated August 8, 2021|PDF page 65: Cloud-provider and identity architecture dated August 8, 2021]] — The August 8, 2021 page is a cloud control-plane inventory: registrar/DNS, edge proxy, virtual servers, object/media delivery, identity-as-a-service, VPN, file storage, secure email, and owned domains. The emphatic Cloudflare API note points toward programmatic orchestration. This is the clearest notebook-wide architecture: **domain → DNS/edge → compute → media → authentication → secure transport → storage → mail**. - [[Scanned_20260730-1659#PDF page 66 — GoMcGill DNS addresses and GoDaddy support transfer|PDF page 66: GoMcGill DNS addresses and GoDaddy support transfer]] — The three addresses were Cloudflare anycast endpoints for `gomcgill.com` at the time written; Cloudflare’s proxy model intentionally returns Cloudflare addresses rather than the origin. The page’s “pings” are therefore evidence of edge routing, not direct evidence of where the origin server lived. The support-representative transfer records a human escalation layered onto the DNS investigation. Credential/PIN material remains redacted. - [[Scanned_20260730-1659#PDF page 67 — GoDaddy contact and telephone-transfer ledger|PDF page 67: GoDaddy contact and telephone-transfer ledger]] — This is a call-center continuity ledger: representative name, extension, transfer instruction, scheduled call time, and multiple old/new phone roles. It captures the operational problem of changing the account’s primary telephone identity without losing support access. All telephone numbers are redacted and omitted from person/index overlays. ## Relationships and overlays The source places this record in an evidence cluster with [[Access Token|Access Token]] · [[Account Transfer|Account Transfer]] · [[Active Directory|Active Directory]] · [[AI-assisted Review|AI-assisted Review]] · [[Anycast|Anycast]] · [[Auth0|Auth0]] · [[Box|Box]] · [[Cloud API|Cloud API]] · [[Cloudflare|Cloudflare]] · [[Cloudinary|Cloudinary]] · [[Country-code Top-level Domain|Country-code Top-level Domain]] · [[DigitalOcean|DigitalOcean]] · [[Domain Identity|Domain Identity]] · [[Domain Name System|Domain Name System]] · [[Domain Portfolio|Domain Portfolio]] · [[Domain Renewal|Domain Renewal]] · [[Email Migration|Email Migration]] · [[Email Normalization|Email Normalization]]. The occurrence contributes to the notebook's larger model of [[Identity Continuity|identity continuity]], [[Device Sovereignty|device sovereignty]], and [[Continuity Architecture|continuity architecture]]. ## Evidentiary status and open leads Determine canonical mailboxes and alias direction from mail-admin exports; keep [PERSON REDACTED] distinct from [PERSON REDACTED]. ## Source - [[Scanned_20260730-1659|Scanned_20260730-1659]]